Terminal, network node, and base station

Abstract

This terminal comprises: a reception unit that receives, from a base station, notification information including information indicating that manual cell selection is permitted and information indicating that a limited local communication carrier service at the time of manual cell selection is permitted; and a transmission unit that transmits, to the base station, a first message including information indicating that the service is requested and information which is used for requesting initial registration and which includes information indicating that the registration request precedes the request for the service. The reception unit receives, from the base station, a second message including information which indicates that the initial registration preceding the request for the service is accepted and which includes a network layer provisional identifier and an application layer provisional identifier used at the time of service usage.

Description

Terminal, network node, and base station

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

[0002] In 3GPP (Registered Trademark) (3rd Generation Partnership Project), in order to achieve further increased system capacity, further increased data transmission speed, further reduced latency in the radio section, etc., a radio communication method called 5G or NR (New Radio) (hereinafter, this radio communication method is referred to as "5G" or "NR") is being studied. In 5G, various radio technologies are being studied in order to meet the requirement of achieving a throughput of 10 Gbps or more while reducing the latency in the radio section to 1 ms or less.

[0003] In addition, the network architectures in 5GC (5G Core Network) or 5GS (5G System), which is the core network in 5G, and 6GC (6G Core Network) or 6GS (6G System), which is the successor to 5G, are also being studied (for example, Non-Patent Documents 1-2).

[0004] 3GPP TS 23.501 V18.7.0 (2024-09) 3GPP TS 23.502 V18.7.0 (2024-09) 3GPP TS 23.401 V18.7.0 (2024-09)

[0005] In the 5G femtocell, the owner of the CAG (Closed Access Group) can make the terminal accessible to the CAG cell by additionally setting a permitted CAG identifier in the subscriber information of the visitor's terminal.

[0006] Here, when the home network of the terminal is not the same as the network to which the CAG cell belongs, or when no roaming contract has been concluded with the network, the terminal cannot be set to be accessible to the CAG cell.

[0007] The present invention has been made in view of the above points, and aims to enable a wireless communication system to configure a terminal's access to a CAG cell, regardless of the relationship between the terminal's home network and the network to which the CAG cell belongs.

[0008] According to the disclosed technology, a terminal is provided having a receiving unit that receives broadcast information from a base station including information indicating that manual cell selection is permitted and information indicating that limited local carrier services are permitted when manual cell selection is performed; and a transmitting unit that transmits a first message to the base station including information requesting initial registration including information indicating that it is a registration request prior to a request for the service and information indicating that the service is requested, wherein the receiving unit receives a second message from the base station including information accepting the initial registration prior to a request for the service, including a network layer provisional identifier and an application layer provisional identifier to be used when using the service.

[0009] According to the disclosed technology, in a wireless communication system, it is possible to configure a terminal's access to a CAG cell regardless of the relationship between the terminal's home network and the network to which the CAG cell belongs.

[0010] This is a diagram illustrating an example of a communication system. This is a diagram illustrating an example of a communication system in a roaming environment. This is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a second sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a third sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a fourth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a fifth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a sixth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a seventh sequence diagram in an embodiment of the present invention. This is a diagram showing an example of an eighth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a ninth sequence diagram in an embodiment of the present invention. This 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. This is a diagram showing an example of the functional configuration of a terminal 20 in an embodiment of the present invention. This 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. This is a diagram showing an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

[0011] Embodiments of the present invention will be described below with reference to the drawings. The embodiments described below are examples, and the embodiments to which the present invention applies are not limited to those described below. Furthermore, in the following description, " / " means "and / or" unless otherwise specified, or unless it is clear from the context that it has a different meaning.

[0012] In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE, but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced, LTE-Advanced and later technologies (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.

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

[0014] Figure 1 is a diagram illustrating an example of a communication system. As shown in Figure 1, the communication system consists of a terminal 20 (UE) and multiple network nodes 30. Hereafter, one network node 30 will be assumed to correspond to each function, but one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Also, the "connection" described below may be a logical connection or a physical connection.

[0015] The RAN (Radio Access Network) is a network node 30 having wireless access functionality, which may include a base station 10, and is connected to a UE, AMF (Access and Mobility Management Function), and 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), registration management, connection management, reachability management, and terminal mobility management. The UPF is a network node 30 interconnected with the DN (Data Network) and having functions related to processing user plane data, such as a PDU (Protocol Data Unit) session point to the outside, packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and DN constitute a network slice. In the wireless communication network in the embodiment of the present invention, a plurality of network slices are constructed.

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

[0017] The SMF is a network node 30 that has functions such as session management, IP (Internet Protocol) address allocation and management for UEs, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming functionality. The NEF is a network node 30 that has the function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node 30 that has functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which the UE connects. The PCF is a network node 30 that has the function of controlling network policies. The AF is a network node 30 that has the function of controlling application servers. The NRF is a network node 30 that has the function of discovering NF instances that provide services. The UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to the UDR (User Data Repository) that holds the said data.

[0018] Figure 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Figure 2, the network consists of a terminal 20 (UE) and multiple network nodes 30. Hereafter, one network node 30 will be assigned to each function, but one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Also, the "connection" described below may be a logical connection or a physical connection.

[0019] The RAN is a network node 30 having wireless access functionality and is connected to the UE, AMF, and 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 interconnected with the DN, having functions such as external PDU session point, packet routing and forwarding, and user plane QoS handling. The UPF and DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

[0020] AMF is connected to UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

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

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

[0023] Figure 3 is a diagram illustrating an example of an IMS network. As shown in Figure 3, the IMS network consists of a terminal 20 (UE) and multiple network nodes 30 in both the originating network and the terminating network. Hereafter, one network node 30 will be assumed to correspond to each function, but one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Also, the "connection" described below may be a logical connection or a physical connection. The network node 30 has the following functions, for example, as described in Non-Patent Document 2.

[0024] The IMS-AGW (Access Gateway) is a network node 30 that has the functions of a gateway between the UE and the IMS network, as well as functions related to voice communication access processing.

[0025] P-CSCF (Proxy-Call Session Control Function) is a network node 30 that has proxy functions between the UE and the IMS network, as well as access control functions for voice communications.

[0026] S-CSCF (Serving-Call Session Control Function) is a network node 30 that has functions related to session control for the UE.

[0027] The I-CSCF (Interrogate-Call Session Control Function) is a connection point on the receiving side between networks in the IMS network (for example, between the originating network and the receiving network), and is a network node 30 that has functions such as forwarding received SIP requests to its own network's S-CSCF.

[0028] The IMS AS (IP Multimedia Subsystem Application Server) is a network node 30 in the IMS network that has functions such as communicating with the DCSF for event notification and receiving data channel control instructions from the DCSF and communicating with the MF. The IMS AS also receives a registration request for the communication termination point from the DCSF (Data Channel Signalling Function), converts the received registration request into a SIP Register, and sends it to the S-CSCF (Serving-Call Session Control Function). Furthermore, the IMS AS converts a data channel establishment request received from the DCSF into a SIP INVITE and sends it to the S-CSCF.

[0029] The DCSF (Data Channel Signaling Function) is a network node 30 that has functions such as receiving event reports from IMS-AS and deciding whether or not to allow the provision of data channel services, managing bootstrap data channels, and HTTP web server functionality.

[0030] The Media Function (MF) is a network node 30 in the IMS network that has functions such as media resource management and data channel media traffic forwarding. The MF also processes media between the Data Channel Application Server (DCAS), which is the communication termination point, and the destination termination point based on the configuration information received from the Data Channel Application Server (DCSF). The MF may also be called the Data Channel Media Function (DCMF). The MF may also be called the Multimedia Resource Function (MRF).

[0031] DCAS (Data Channel Application Server) is a network node 30 that has functions such as being a communication termination point for media and signaling in the IMS network.

[0032] Furthermore, the IMS network may be equipped with an E-CSCF (Emergency Call Session Control Function) for handling emergency calls, and an IBCF (Interconnection Border Control Function) for handling SIP-related processing in interconnections between different domains.

[0033] (Example) This section describes a method for enabling a terminal to access a CAG cell in a wireless communication system, regardless of the relationship between the terminal's home network and the network to which the CAG cell belongs.

[0034] (Prerequisites) In this embodiment, base station 10 is a small base station called a femtocell. In the RAN sharing configuration, base station 10 is connected to the core network of the first network (PLMN#1) to which it belongs, as well as the core networks of the country's second network (PLMN#2) and third network (PLMN#3). Base station 10 also includes PLMN#1, PLMN#2, and PLMN#3 in its broadcast information, but normally only PLMN#1 is accessible. Here, the broadcast information may also include HRNN (Human Readable Network Name) to enable humans to easily identify and select the network name. The home network (HPLMN) of terminal 20 is PLMN#2.

[0035] Furthermore, in this embodiment, the "terminal token" used for verifying terminal 20 may also be referred to as the "wireless network layer token." Also, the "base station token verification information" used by base station 10 to verify terminal tokens may also be referred to as "verification information for verifying wireless network layer tokens."

[0036] (Outline of the method) Terminal 20 connects to PLMN#1's AMF30A in a limited service state in which normal services are unavailable, as manually selected by the user. In this connection, a mechanism similar to 4G's RLOS (Restricted Local Operator Services, see Non-Patent Document 3) may be used.

[0037] Furthermore, terminal 20 connects to FemtoNF (Femto Network Function) 30D using an RLOS PDU session and notifies it of the user ID and password obtained from the femto owner.

[0038] After verifying that the notified user ID and password are identical to those pre-configured by the femto owner, FemtoNF30D notifies AMF30A1 that authorization was successful.

[0039] AMF30A1 prompts the terminal 20 to execute re-registration to the network. When the terminal 20 executes re-registration, it transmits token verification information to the base station 10 and switches to AMF30A2 in PLMN#2. The terminal 20 executes registration to AMF30A2 to obtain a token.

[0040] When the terminal 20 accesses the base station 10 next time, it presents the obtained token. The base station 10 verifies the presented token and connects to AMF30A2.

[0041] (Method details) Hereinafter, the details of the processing in this embodiment will be described using a sequence diagram.

[0042] (Setting of user ID and password) The processing related to the setting of the user ID and password in this embodiment will be described. FIG. 3 is a diagram showing an example of the first sequence diagram in the embodiment of the present invention. Hereinafter, the processing of each step will be described.

[0043] S101: AF30F transmits a request message (Nnef_AuthorizationDataManagement request) regarding authorization data management (registration of the user ID and password of a user using a femtocell) to NEF30E. The request message includes the owner ID of the femtocell, the user ID and password to be registered. Alternatively, instead of the user ID and password to be registered, information requesting generation of the user ID and password to be registered may be included.

[0044] S102: Based on the Common API Framework, NEF30E authenticates the owner of the femtocell included in the message received in S101. If the authentication is successful, it authorizes the operation by the owner on the base station indicated by the femto ID included in the message.

[0045] S103: NEF30E sends a request message (Nfemtonf_AuthorizationDataManagement request) regarding authorization data management (registration of user ID and password of users using the femtocell) to FemtoNF30D. The request message includes the owner ID of the femtocell, the user ID and password to be registered. Alternatively, instead of the user ID and password to be registered, information requesting generation of the user ID and password to be registered may be included.

[0046] S104: FemtoNF30D stores the user ID and password received in S103 in response to the request message received in S103. Alternatively, if the request message includes information requesting generation of the user ID and password to be registered, it executes generation of the user ID and password and stores the generated user ID and password.

[0047] S105: FemtoNF30D sends a response message (Nfemtonf_AuthorizationDataManagement response) regarding authorization data management to NEF30E for the request message received in S103. The response message includes information indicating successful registration. Alternatively, if the request message includes information requesting generation of the user ID and password to be registered, the response message includes the generated user ID and password (and may further include information indicating successful registration).

[0048] S106: NEF30E sends a response message (Nnef_AuthorizationDataManagement response) regarding authorization data management to AF30F for the request message received in S101. The response message includes information indicating successful registration. Alternatively, if the request message includes information requesting generation of the user ID and password to be registered, the response message includes the generated user ID and password (and may further include information indicating successful registration).

[0049] (Cell Selection) The process related to cell selection in this embodiment, following S106, will now be described. Figure 4 is a diagram showing an example of a second sequence diagram in an embodiment of the present invention. As a premise, it is assumed that base station 10 is connected to PLMN#1's AMF30A1 and UPF (UPF30B), and at the same time, to PLMN#2's AMF30A2 and UPF, and PLMN#3's AMF30A3 and UPF. It is also assumed that the owner of terminal 20 has obtained a user ID and password for accessing the femtocell from the owner of the femtocell (base station 10). The processing of each step will be described below.

[0050] S201: The base station 10 transmits broadcast information (SIB1) to the terminal 20. The broadcast information may include information indicating that manual cell selection is permitted for PLMN#1, information indicating that limited local carrier services are permitted for PLMN#1 when manual cell selection is performed, information indicating that it is connected to the core network of PLMN#2, information indicating that PLMN#2 is a cell reserved for other purposes, information indicating that it is connected to the core network of PLMN#3, and information indicating that PLMN#3 is a cell reserved for other purposes. The broadcast information may also include a cell identifier. Furthermore, the broadcast information may be configured so that the terminal 20 cannot normally access PLMN#2 and PLMN#3. For example, the broadcast information is SIB1(cellAccessRelatedInfo(plmn-IdentityInfoList(PLMN-IdentityInfo(plmn-IdentityList(PLMN-Identity=PLMN#1))), PLMN-IdentityInfo(plmn-IdentityList(PLMN-Identity=PLMN#2), cellReservedForOperatorUse=true)), PLMN-IdentityInfo(plmn-IdentityList(PLMN-Identity=PLMN#3), cellReservedForOperatorUse=true)), npn-IdentityInfoList(NPN-IdentityInfo(npn-IdentityList(NPN-Identity(pni-npn(plmn-Identity=PLMN#1), cag-IdentityList(CAG-IdentityInfo(cag-Identity=CAG#65, manualCAGselectionAllowed =true, It is written as `manualCAGselectionRlos-Enabled=true)))))))))`.

[0051] S202: The base station 10 transmits broadcast information (SIB10) to the terminal 20. The broadcast information may include a list of HRNNs containing the network names of femtocells corresponding to the base station 10. For example, the broadcast information is written as SIB10(hrnn-List(HRNN(Alice's Femto))).

[0052] S203: Terminal 20 accepts manual cell selection operations from the user. For example, the femtocell corresponding to base station 10 is displayed on the screen of terminal 20 as "PLMN#1 Alice's Femto", and the user selects that femtocell.

[0053] S204: Terminal 20 displays a question on its screen to the user asking whether or not to connect to Restricted Local Operator Services, which is related to manual CAG selection. Furthermore, Terminal 20 accepts the user's action of selecting "Yes" to this question. Based on the result of this action, Terminal 20 decides to perform initial registration and PDU session establishment.

[0054] (Initial Registration) Following S204, the process related to initial registration in this embodiment will be described. Figure 5 is a diagram showing an example of a third sequence diagram in an embodiment of the present invention. For the process of initial registration in existing specifications, please refer to section 4.2.2.2 of Non-Patent Document 2. The process of each step will be described below.

[0055] S301: Terminal 20 sends a request message (RRCSetupRequest) to base station 10 requesting an RRC connection.

[0056] S302: Base station 10 sends a message (RRCSetup) related to RRC connection to terminal 20.

[0057] S303: Terminal 20 sends a message (RRCSetupComplete) to base station 10 indicating completion of RRC connection. This message may include information requesting initial registration, which includes information indicating that it is a registration request preceding the request for limited local carrier services when manually selecting a cell, and information indicating that it is requesting limited local carrier services when manually selecting a cell. The message may also include network information (PLMN#2) in the encrypted subscriber identifier (SUCI). For example, the message is written as RRCSetupComplete (selectedPLMN-Identity=PLMN#1, dedicatedNAS-Message(Registration request(5GS mobile identity(SUCI=PLMN#2+other information), 5GS registration type=initial registration, 5GS update type=forManualCAGselectionRlos)), manualCAGselectionRlos-Request=true).

[0058] S304: Base station 10 selects AMF30A1, which belongs to PLMN#1 and is capable of handling the limited local carrier service (manualCAGselectionRlos) during manual cell selection.

[0059] S305: Base station 10 sends an Initial UE message to AMF30A1 containing information requesting initial registration, including information indicating that it is a registration request preceding a limited local carrier service request when a cell is manually selected.

[0060] S306: AMF30A1 authorizes registration by skipping the procedures related to authentication, security, AMF registration, and subscriber information acquisition.

[0061] S307: AMF30A1 sends a request message (Nfemtonf_EventExposure_Subscribe request) to FemtoNF30D that includes a request to subscribe to an application layer authorization state change event and a request to assign an application layer provisional identifier. For example, the message is written as Nfemtonf_EventExposure_Subscribe request (event ID = authorization state change, application terminal ID assignment request).

[0062] S308: FemtoNF30D may send a response message (Nfemtonf_EventExposure_Subscribe response) to AMF30A1 for the request message received in S306. The response message may include an application layer provisional identifier, for example, written as Nfemtonf_EventExposure_Subscribe response (application terminal ID=abc).

[0063] S309: The AMF30A1 assigns a network layer provisional identifier (5G GUTI (Globally Unique Temporary UE Identity)), associates this network layer provisional identifier with the application layer provisional identifier received in S308, and stores it in the terminal context.

[0064] S310: The AMF30A1 sends a message (Downlink NAS Transport) to base station 10 that includes a network layer provisional identifier and an application layer provisional identifier, and contains information accepting the initial registration prior to the request for limited local carrier services during manual cell selection. For example, the message is written as Downlink NAS Transport (NAS-PDU(Registration accept(5G-GUTI, 5GS registration result=Registered forManualCAGselectionRlos, Application terminal ID forManualCAGselectionRlos=abc))).

[0065] S311: Base station 10 sends a message (DLInformationTransfer) to terminal 20 that includes information accepting the initial registration prior to the request for limited local carrier services when manually selecting a cell, including the network layer provisional identifier (5G-GUTI) and the application layer provisional identifier used when using limited local carrier services when manually selecting a cell. For example, the message is written as DLInformationTransfer (dedicatedNAS-Message(Registration accept(5G-GUTI, 5GS registration result=Registered forManualCAGselectionRlos, application terminal ID forManualCAGselectionRlos=abc))).

[0066] (PDU Session Establishment) The process for establishing a PDU session in this embodiment, following S311, will now be described. Figure 6 is a diagram showing an example of a fourth sequence diagram in an embodiment of the present invention. For the process of establishing a PDU session in existing specifications, please refer to Section 4.3.2 of Non-Patent Document 2. The process for each step will be described below.

[0067] S401: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that includes a PDU session establishment request, which contains information indicating that it is a PDU session for a limited local carrier service when a manual cell is selected. For example, the message is written as ULInformationTransfer(dedicatedNAS-Message(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment request), DNN=forManualCAGselectionRlos))).

[0068] S402: Base station 10 sends a message (Uplink NAS Transport) to AMF30A1 containing a PDU session establishment request that includes information indicating that it is a PDU session for limited local carrier services when a manual cell is selected. For example, the message is written as Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment request), DNN=forManualCAGselectionRlos))).

[0069] S403: AMF30A1 checks whether registration for the limited local carrier service (forManualCAGselectionRlos) has been performed when terminal 20 manually selects a cell.

[0070] S404: Confirm that AMF30A1 has information regarding the limited local carrier service during manual cell selection (AMF Configuration Data forManualCAGselectionRlos), which includes information regarding the SMF to be connected, corresponding to the Data Network Name (DNN).

[0071] S405: AMF30A1 sends a request message (Nsmf_PDUSession_CreateSMContext request) to SMF30C requesting session establishment, which includes information indicating that it is a PDU session for limited local carrier services when a manual cell is selected. For example, the message is written as Nsmf_PDUSession_CreateSMContext request(Dnn=forManualCAGselectionRlos, SmContextCreateData(n1SmMsg(PDU session establishment request))).

[0072] S406: SMF30C sends a response message (Nsmf_PDUSession_CreateSMContext response) to AMF30A1 for the request message received in S405.

[0073] S407: Confirm that the SMF30C has information regarding limited local carrier services during manual cell selection (SMF Configuration Data forManualCAGselectionRlos), including information related to the UPF and FemtoNF to be connected, which are compatible with DNN.

[0074] S408: SMF30C sends a request message (Nfemtonf_ConnectionManagement request) to FemtoNF30D regarding the connection for the uplink (UL) to FemtoNF30D.

[0075] S409: FemtoNF30D sends a response message (Nfemtonf_ConnectionManagement response) to SMF30C for the request message received in S408. This response message includes a Tunnel Endpoint Identifier (TEID) for UL for FemtoNF30D, which is information about the endpoint for receiving UL data within the device.

[0076] S410: SMF30C sends a first request message (PFCP Session Establishment request) for UL to FemtoNF30D and a second request message (PFCP Session Establishment request) for DL ​​originating from FemtoNF30D to UPF30B, requesting that UPF30B set the endpoint within FemtoNF30D as the destination for the packet forwarding settings of the UL data. The first request message includes a packet forwarding action rule (FAR) with the TEID for UL to FemtoNF30D set, which was received in S409.

[0077] S411: UPF30B transmits to SMF30C a first response message (PFCP Session Establishment response) to the first request message for UL for FemtoNF30D received in S410, and a second response message (PFCP Session Establishment response) to the second request message for DL ​​originating from FemtoNF30D. The second response message includes the DL TEID within UPF30B, which is information about the endpoint for receiving DL data within UPF30B.

[0078] S412: SMF30C sends a request message (Nfemtonf_ConnectionManagement request) to FemtoNF30D requesting that it set the destination of the DL data packet forwarding settings to a termination point within UPF30B. This request message includes the packet forwarding settings (FAR) with the DL TEID for UPF30B that was received in S411.

[0079] S413: FemtoNF30D sends a response message (Nfemtonf_ConnectionManagement response) to SMF30C for the request message received in S412.

[0080] S414: SMF30C sends a message to AMF30A1 containing information indicating acceptance of the PDU session establishment request (Namf_Communication_N1N2MessageTransfer request). For example, the request message is written as Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData(n1MessageContainer(PDU Session Establishment accept) n2InfoContainer(smInfo(n2InfoContent(PDU Session Resource Setup Request Transfer))))).

[0081] S415: AMF30A1 sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30C for the request message received in S414.

[0082] S416: The AMF30A1 sends a request message to base station 10 for setting up a PDU session resource (PDU Session Resource Setup request). For example, the request message is written as PDU Session Resource Setup request(NAS-PDU(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment accept))), PDU Session Resource Setup Request Transfer).

[0083] S417: The base station 10 sends a message to the terminal 20 regarding the reconfiguration of the RRC (RRCReconfiguration), which includes information indicating acceptance of the PDU session establishment request. For example, the message is written as RRCReconfiguration(dedicatedNAS-Message(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment accept)))).

[0084] S418: Terminal 20 sends a message to base station 10 indicating that RRC reconfiguration is complete (RRCReconfigurationComplete).

[0085] S419: Base station 10 sends a response message (PDU Session Resource Setup response) to AMF30A1 for the request message received in S416. For example, this response message is written as PDU Session Resource Setup response (PDU Session Resource Setup Response Transfer).

[0086] S420: AMF30A1 sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF30C requesting a context update for the PDU session. For example, this request message is written as Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n2SmInfo(PDU Session Resource Setup Response Transfer))).

[0087] S421: SMF30C sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30A1 for the request message received in S420.

[0088] S422: SMF30C sends a request message (PFCP Session Modification request) to UPF30B for updating the user data transfer path.

[0089] S423: UPF30B sends a response message (PFCP Session Modification response) to SMF30C for the request message received in S422.

[0090] (Coordination with FemtoNF within the U-plane) Following S423, the process relating to coordination with FemtoNF within the U-plane in this embodiment will be described. Figure 7 is a diagram showing an example of a fifth sequence diagram in an embodiment of the present invention. The process of each step will be described below.

[0091] S501: Terminal 20 sends a request message (Nfemtonf_FrontPage Get request) to FemtoNF30D requesting the display of the front page.

[0092] S502: FemtoNF30D sends a response message (Nfemtonf_FrontPage Get response) to terminal 20 for the request message received in S501.

[0093] S503: Terminal 20 displays the front page on its screen and accepts user input of user ID, password, and application terminal ID (ID forManualCAGselectionRlos=abc). Here, the application terminal ID may be explicitly entered manually by the user, or it may be entered automatically based on a software mechanism.

[0094] S504: Terminal 20 sends a request message (Nfemtonf_Authorize request) to FemtoNF30D requesting application layer authorization, which includes an application layer provisional identifier (i.e., application terminal ID) and an application layer token for using the base station (i.e., user ID and password). For example, the message is written as Nfemtonf_Authorize request (application terminal ID forManualCAGselectionRlos=abc, user ID, password).

[0095] S505: FemtoNF30D performs verification of the application layer token for base station use, which was received in S504. That is, FemtoNF30D verifies the combination of user ID and password, recognizes that the verification was successful, and decides to return a success message.

[0096] S506: FemtoNF30D sends a response message (Nfemtonf_Authorize response) to terminal 20 for the request message received in S504. This response message includes information indicating that the application layer token has been successfully verified.

[0097] S507: FemtoNF30D sends a notification message (Nfemtonf_EventExposure_Notify request) to AMF30A1 regarding an application layer authorization status change event corresponding to the application layer provisional identifier, which includes information indicating that the application layer token verification was successful (information indicating that the application layer authorization status for the application layer provisional identifier was successful). The notification message may also include information regarding the validity period of the verification result. For example, the notification message is written as Nfemtonf_EventExposure_Notify request (event ID = authorization status change, authorization status = authorization successful, optional information = validity period).

[0098] S508: Based on the notification message received in S507, the AMF30A1 recognizes that authorization for the application terminal ID (=abc) has been successful.

[0099] S509: AMF30A1 sends a response message (Nfemtonf_EventExposure_Notify response) to FemtoNF30D for the notification message received in S507.

[0100] (Release of PDU session) Based on the procedure for releasing a PDU session in the existing specification (see Section 4.3.4.2 of Non-Patent Document 2), the PDU session established in Figure 6 is released.

[0101] (Deregistration) Following S509, the process for deregistration in this embodiment will be described. Figure 8 is a diagram showing an example of the sixth sequence diagram in an embodiment of the present invention. For the process of deregistration in existing specifications, please refer to Section 4.2.2.3 of Non-Patent Document 2. The process of each step will be described below.

[0102] S601: The AMF30A1 decides to prompt terminal 20 to re-register while retaining the context of terminal 20.

[0103] S602: The AMF30A1 sends a message (Downlink NAS Transport) to base station 10 that includes a de-registration request, which includes information requesting a re-initial registration, which includes a network layer provisional identifier (5G-GUTI). For example, the message is written as Downlink NAS Transport (NAS-PDU(De-registration request (UE terminated de-registration)(De-registration type=re-registration required, 5GMM cause=re-initial registration required with the allocated 5G-GUTI))).

[0104] S603: Base station 10 sends a message (DLInformationTransfer) to terminal 20 that includes a de-registration request, which includes information requesting a re-initial registration, which includes a network layer provisional identifier (5G-GUTI). For example, the message is written as DLInformationTransfer (dedicatedNAS-Message(De-registration request (UE terminated de-registration)(De-registration type=re-registration required, 5GMM cause=re-initial registration required with the allocated 5G-GUTI))).

[0105] S604: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that contains information indicating acceptance of the deregistration request. For example, the message is written as ULInformationTransfer(dedicatedNAS-Message(De-registration accept (UE terminated de-registration))).

[0106] S605: Base station 10 sends a message (Uplink NAS Transport) to AMF30A1 containing information indicating acceptance of the deregistration request. For example, the message is written as Uplink NAS Transport(NAS-PDU(De-registration accept (UE terminated de-registration))).

[0107] S606: The AMF30A1 sends a message (UE Context Release Command) to the base station 10 instructing it to release the context information of the terminal 20.

[0108] S607: Base station 10 sends a message (RRC Release) to terminal 20 instructing it to release the RRC connection.

[0109] S608: Base station 10 sends a message (UE Context Release Complete) to AMF30A1 notifying it that the release of the context information of terminal 20 is complete.

[0110] (Initial Registration (Second Time)) Following S608, the process for the second initial registration in this embodiment will be described. Figure 9 is a diagram showing an example of the seventh sequence diagram in an embodiment of the present invention. For the initial registration process in existing specifications, please refer to Section 4.2.2.2 of Non-Patent Document 2. The process for each step will be described below.

[0111] S701: Terminal 20 sends a request message (RRCSetupRequest) to base station 10 requesting an RRC connection.

[0112] S702: Base station 10 sends a message (RRCSetup) related to RRC connection to terminal 20.

[0113] S703: Terminal 20 sends a message (RRCSetupComplete) to base station 10 indicating the completion of the RRC connection. This message includes a network layer provisional identifier (Additional GUTI) and is addressed to AMF30A1, the network node to which the network layer provisional identifier received in S602 in Figure 8 was assigned, and requests initial registration. For example, this message is written as RRCSetupComplete (selectedPLMN-Identity=PLMN#1, registeredAMF=(plmn-Identity=PLMN#1, amf-Identifier=AMF#1), dedicatedNAS-Message(Registration request(5GS mobile identity(SUCI=PLMN#2+other information), Additional GUTI, 5GS registration type=initial registration))).

[0114] S704: Base station 10 selects AMF30A1.

[0115] S705: Base station 10 sends an Initial UE message to AMF30A1 that includes a network layer provisional identifier and a message requesting initial registration. For example, this message is written as Initial UE message (NAS-PDU(Registration request(5GS mobile identity(SUCI=PLMN#2+other information), Additional GUTI, 5GS registration type=initial registration))).

[0116] S706: The AMF30A1 recognizes that the application layer authorization status is successful with respect to the application layer provisional identifier corresponding to the network layer provisional identifier. That is, the AMF30A1 recognizes that authorization was successful for the application terminal ID (=abc) by checking the value of 5G-GUTI set in the network layer provisional identifier (Additional GUTI) contained in the message received in S705.

[0117] S707: Based on the message received in S705, AMF30A1 recognizes that the terminal's HPLMN is different from the PLMN to which its own device belongs, and decides to perform an AMF reallocation of PLMN#2 to AMF30A2 for terminal 20.

[0118] S708: The AMF30A1 decides to send a terminal token to terminal 20 and base station token verification information to base station 10 for the terminal 20 to use base station 10 for a certain period of time. Here, the terminal token and base station token verification information may be the same information. Also, the terminal token and base station token verification information may include information about their validity period.

[0119] S709: The AMF30A1 sends a request message (Reroute NAS request) to base station 10 requesting a change of NAS message delivery destination, which includes forwarding destination PLMN information, information requesting initial registration received from base station 10 in S705, inter-node forwarding information including a wireless network layer token, and verification information for verifying the wireless network layer token. For example, the message is written as Reroute NAS Request (NGAP message, target PLMN=PLMN#2, Source to Target AMF Information Reroute(terminal token), gNB token verification information).

[0120] S710: Base station 10 stores the base station token verification information contained in the request message received in S709 in its own device. Also, base station 10 determines the destination AMF30A2 based on the destination PLMN information contained in the request message received in S709.

[0121] S711: Base station 10 sends a message (Initial UE message) to AMF30A2 that includes information requesting initial registration received from AMF30A1 in S709, and network node transfer information including a wireless network layer token. For example, the message is written as Initial UE message (NAS-PDU(Registration request(5GS mobile identity(SUCI=PLMN#2+other information), Additional GUTI, 5GS registration type=initial registration)), Source to Target AMF Information Reroute(terminal token)).

[0122] S712: AMF30A2 decides to ignore the Network Layer Provisional Identifier (Additional GUTI) included in the message received in S711 and proceed with the normal initial registration procedure. AMF30A2 also decides to send a message indicating registration acceptance, including the terminal token, to terminal 20.

[0123] S713: AMF30A2 sends a request message (Nausf_UEAuthentication_Authenticate request) to AUSF30G requesting authentication to be performed.

[0124] S714: AUSF30G sends a request message (Nudm_UEAuthentication_Get request) to UDM30H requesting authentication information.

[0125] S715: UDM30H sends a response message (Nudm_UEAuthentication_Get response) to AUSF30G for the request message received in S714.

[0126] S716: AUSF30G sends a response message (Nausf_UEAuthentication_Authenticate response) to AMF30A2 for the request message received in S713.

[0127] S717: The AMF30A2 sends a message (Downlink NAS Transport) to base station 10 that includes a request for authentication. For example, this message is written as Downlink NAS Transport (NAS-PDU (Authentication request)).

[0128] S718: The base station 10 sends a message (DLInformationTransfer) containing an authentication request to the terminal 20. For example, this message is written as DLInformationTransfer(dedicatedNAS-Message(Authentication request)).

[0129] S719: Terminal 20 sends a message (ULInformationTransfer) containing the authentication execution response to base station 10. For example, this message is written as ULInformationTransfer(dedicatedNAS-Message(Authentication response)).

[0130] S720: Base station 10 sends a message (Uplink NAS Transport) containing the authentication execution response to AMF30A2. For example, this message is written as Uplink NAS Transport (NAS-PDU (Authentication response)).

[0131] The process following S720 will now be described. Figure 10 is a diagram showing an example of the eighth sequence diagram in an embodiment of the present invention. The process of each step will be described below.

[0132] S721: AMF30A2 sends a request message (Nausf_UEAuthentication_Authenticate request) to AUSF30G requesting authentication to be performed.

[0133] S722: AUSF30G performs authentication on terminal 20.

[0134] S723: AUSF30G sends a response message (Nausf_UEAuthentication_Authenticate response) to AMF30A2 for the request message received in S721.

[0135] S724: SEAF within AMF30A2 performs authentication for terminal 20.

[0136] S725: AUSF30G sends a request message (Nudm_UEAuthentication_ResultConfirmation request) to UDM30H indicating that authentication has been confirmed.

[0137] S726: UDM30H sends a response message (Nudm_UEAuthentication_ResultConfirmation response) to AUSF30G for the request message received in S725.

[0138] S727: The AMF30A2 sends a request message (Initial Context Setup request) to the base station 10 requesting the configuration of the terminal 20's context.

[0139] S728: Base station 10 sends a message (SecurityModeCommand) to terminal 20 regarding the security settings of the wireless portion.

[0140] S729: Terminal 20 sends a message (SecurityModeComplete) to base station 10 notifying it that the security settings for the wireless portion have been completed.

[0141] S730: Base station 10 sends a response message (Initial Context Setup response) to AMF30A2 for the request message received in S727.

[0142] S731: The AMF30A2 sends a message (Downlink NAS Transport) regarding NAS security settings to base station 10. For example, this message is written as Downlink NAS Transport (NAS-PDU (Security Mode Command)).

[0143] S732: Base station 10 sends a message (DLInformationTransfer) regarding NAS security settings to terminal 20. For example, this message is written as DLInformationTransfer(dedicatedNAS-Message(Security Mode Command)).

[0144] S733: Terminal 20 sends a message (ULInformationTransfer) to base station 10 notifying it that the NAS security settings have been completed. For example, this message is written as ULInformationTransfer(dedicatedNAS-Message(Security Mode Complete)).

[0145] S734: Base station 10 sends a message (Uplink NAS Transport) to AMF30A2 notifying it that the NAS security settings have been completed. For example, this message is written as Uplink NAS Transport (NAS-PDU (Security Mode Complete)).

[0146] S735: AMF30A2 sends a request message (Nudm_UECM_Registration request) to UDM30H requesting registration of terminal 20.

[0147] S736: UDM30H sends a response message (Nudm_UECM_Registration response) to AMF30A2 for the request message received in S735.

[0148] S737: AMF30A2 sends a request message (Nudm_SDM_Get request) to UDM30H requesting subscriber information for terminal 20.

[0149] S738: UDM30H sends a response message (Nudm_SDM_Get response) to AMF30A2 for the request message received in S737.

[0150] S739: The AMF30A2 sends a message (Downlink NAS Transport) to base station 10 that includes a wireless network layer token and information indicating acceptance of initial registration. For example, the message is written as Downlink NAS Transport (NAS-PDU(Registration accept(terminal token))).

[0151] S740: Base station 10 sends a message (DLInformationTransfer) to terminal 20 that includes a wireless network layer token and information indicating acceptance of initial registration. For example, the message is written as DLInformationTransfer (dedicatedNAS-Message(Registration accept (terminal token))).

[0152] S741: Terminal 20 stores in its own device a combination of the terminal token contained in the message received by S740 and the received cell.

[0153] (Service Request) The processing related to the service request in this embodiment, following S741, will now be described. Figure 10 is a diagram showing an example of the eighth sequence diagram in an embodiment of the present invention. For the processing of service requests in existing specifications, please refer to Section 4.2.3 of Non-Patent Document 2. The processing of each step will be described below.

[0154] S801: Terminal 20 is currently set to idle mode.

[0155] S802: Terminal 20 recognizes that it possesses a wireless network layer token based on the received cell identifier and the combination information of the wireless network layer token and cell identifier stored within its own terminal. Furthermore, if terminal 20 is to reconnect to the cell from which it received the terminal token, and the terminal token is still valid, it decides to ignore the information indicating that limited local carrier services are permitted when manually selecting a cell for PLMN#2 (cellReservedForOperatorUse=true), assign the terminal token, and connect to PLMN#2.

[0156] S803: Terminal 20 sends a request message (RRCSetupRequest) to base station 10 requesting an RRC connection.

[0157] S804: Base station 10 sends a message (RRCSetup) related to RRC connection to terminal 20.

[0158] S805: Terminal 20 sends a message (RRCSetupComplete) to base station 10 indicating that the RRC connection is complete. This message is addressed to AMF30A2 belonging to HPLMN and is a connection request message that includes a wireless network layer token (terminal token). For example, it is written as RRCSetupComplete (selectedPLMN-Identity=PLMN#2, registeredAMF=(plmn-Identity=PLMN#2, amf-Identifier=AMF#2), terminal token, dedicatedNAS-Message(Service request)).

[0159] S806: Base station 10 verifies the terminal token contained in the message received in S805 using base station token verification information. If the verification is successful (i.e., if it is confirmed that the terminal token is valid), it connects to the AMF30A2 of PLMN#2, which is not normally connected to. In addition, if the verification information includes information related to the validity period, base station 10 may invalidate the verification information after the validity period has expired and determine that the wireless network layer token (terminal token) that should have been verified with the invalidated verification information is invalid.

[0160] S807: Base station 10 sends a message (Initial UE message) to AMF30A2 containing information indicating a service request. For example, this message is written as Initial UE message (NAS-PDU (Service request)).

[0161] The above embodiment makes it possible to configure a wireless communication system to allow a terminal to access a CAG cell, regardless of the relationship between the terminal's home network and the network to which the CAG cell belongs.

[0162] (Device Configuration) Next, an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processing and operations described above will be explained. The base station 10, network node 30, and terminal 20 include the functions to perform the embodiments described above. However, the base station 10, network node 30, and terminal 20 may each be equipped with only some of the functions in the embodiments.

[0163] <Base Station 10 and Network Node 30> Figure 12 shows an example of the functional configuration of a base station 10 and a network node 30. As shown in Figure 12, 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 Figure 12 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions on the system architecture may be composed of multiple network nodes 30 separated by function.

[0164] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or other network node 30 and transmitting the signal by wire or wireless. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 or other network node 30 and obtaining information from the received signal, for example, information from a higher layer. A communication unit including the transmitting unit 110 and the receiving unit 120 may be configured.

[0165] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads them from the storage device as needed.

[0166] The control unit 140 performs the processes described in the embodiment. The control unit 140 also performs processing related to communication with the terminal 20. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.

[0167] <Terminal 20> Figure 13 is a diagram showing an example of the functional configuration of terminal 20. As shown in Figure 13, 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 Figure 13 is merely an example. Any functional classification and name of functional unit is acceptable as long as it can perform the operations according to the embodiment of the present invention. Furthermore, the communication device that becomes the resource holder 20 may have a functional configuration similar to that of terminal 20.

[0168] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving control signals or reference signals transmitted from the network node 30. A communication unit including the transmitting unit 210 and the receiving unit 220 may be configured.

[0169] The setting unit 230 stores various setting information received from the network node 30 by the receiving unit 220 in its storage device and reads it from the storage device as needed. The setting unit 230 also stores pre-configured setting information.

[0170] The control unit 240 performs the processing described in the embodiment. The signal transmission function in the control unit 240 may be included in the transmission unit 210, and the signal reception function in the control unit 240 may be included in the reception unit 220.

[0171] (Hardware Configuration) The block diagrams (Figures 12 and 13) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, 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 it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the above one device or the above multiple devices with software.

[0172] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0173] For example, the base station 10, network node 30, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 14 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 according to one embodiment of the present disclosure. The network node 30 may have a hardware configuration similar to that of the base station 10. The above-mentioned base station 10 and 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.

[0174] In the following explanation, the term "device" can be read as "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0175] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the storage device 1002 and auxiliary storage device 1003.

[0176] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0177] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 12 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 13 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained 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 also be transmitted from the network via a telecommunications line.

[0178] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of the present disclosure.

[0179] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc 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 multipurpose disk, a Blu-ray® disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0180] 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 referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting and receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

[0181] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0182] 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 different buses may be configured for each device.

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

[0184] Figure 15 shows an example of the configuration of vehicle 2001. As shown in Figure 15, 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 this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0185] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also 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, which is operated by the user.

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

[0187] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front and rear wheel rotation speed signals acquired by rotation speed sensor 2022, front and rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

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

[0189] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

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

[0191] 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 external devices. For example, it can send and receive various types of information with external devices 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 or a mobile station.

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

[0193] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers 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 the external device 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-2029, etc., provided in the vehicle 2001.

[0194] <Note> In the following notes, terms, step numbers, and network nodes etc. corresponding to the above-described embodiments are also included. (Note 1) A terminal having: (S201) a receiving unit that receives broadcast information from a base station including information indicating that manual cell selection is permitted and information indicating that limited local carrier services are permitted when manual cell selection is performed; (S303) a transmitting unit that sends a first message to the base station including information requesting initial registration including information indicating that it is a registration request preceding a request for the service and information indicating that the service is requested, wherein the receiving unit receives a second message from the base station including information accepting initial registration preceding a request for the service, including a network layer provisional identifier (=5G-GUTI) and an application layer provisional identifier to be used when using the service; (S311) (Note 2) The transmitting unit transmits to the base station a first message including a PDU session establishment request, which includes information indicating that it is a PDU (Packet Data Unit) session relating to the service (S401) The receiving unit receives a second message from the base station, which includes acceptance of PDU session establishment (S417) The terminal as described in Note 1. (Note 3) The transmitting unit transmits to the first network node (=FemtoNF30D) a third message requesting application layer authorization, which includes the application layer provisional identifier and an application layer token (=User ID + Password) for using the base station (S504) The receiving unit receives a fourth message from the first network node, which includes information indicating that the verification of the application layer token was successful (S506) The terminal as described in Note 1.(Note 4) The receiving unit receives a fifth message from the base station, which includes a deregistration request, which includes information requesting a re-execution of the initial registration, which includes the network layer provisional identifier (S603) The transmitting unit sends a sixth message to the base station, which includes information requesting the initial registration, which includes the network layer provisional identifier, addressed to the second network node (=AMF30A1) to which the network layer provisional identifier was assigned (S703) The receiving unit receives a seventh message from the base station, which includes information accepting the initial registration, which includes a radio network layer token, which includes a radio network layer token (S740) The terminal according to Note 1, further comprising a control unit that stores a combination of the radio network layer token and the identifier of the currently contained cell (S741). (Note 5) A terminal having: (S201) a receiving unit that receives broadcast information from a base station including a cell identifier, information indicating that the terminal is connected to the core network of its home network, and information indicating that the cell is set aside for other purposes for the home network; (S802) a receiving unit that recognizes that the terminal possesses a wireless network layer token based on the cell identifier and combination information of a wireless network layer token and cell identifier stored in the terminal; (S805) a transmitting unit that sends a message to the base station requesting connection to a network node (=AMF30A2) belonging to the home network, including a wireless network layer token.(Note 6) The device includes: (S305) a receiving unit that receives a first message from a base station that includes information requesting initial registration, including information indicating that it is a registration request prior to a request for limited local carrier services when a cell is manually selected; (S307) a transmitting unit that sends a second message to a first network node (=FemtoNF30D) that includes a request to subscribe to an application layer authorization state change event and a request to assign an application layer provisional identifier; the receiving unit receives a third message from the first network node that includes an application layer provisional identifier; (S308) assigns a network layer provisional identifier (=5G GUTI) to the terminal; (S309) the terminal context further includes a control unit that stores the network layer provisional identifier and the application layer provisional identifier; (S309) the transmitting unit sends a fourth message to the base station that includes information accepting initial registration prior to a request for the service, including the network layer provisional identifier and the application layer provisional identifier; (S310) Network node (=AMF30A1). (Note 7) A network node (=AMF30A1) having: (S507) a receiving unit that receives a first message from a first network node (=FemtoNF30D) that includes information indicating that the application layer authorization status for the application layer provisional identifier has been successful; (S601) a transmitting unit that sends a second message to a base station that includes a deregistration request, which includes information requesting a re-execution of the initial registration, which includes the network layer provisional identifier; and (S602)(Note 8) A network node (=AMF30A1) having: (S705) a receiving unit that receives a first message from a base station that includes a network layer provisional identifier and information requesting initial registration; (S705) a control unit that recognizes that the application layer authorization status is successful with respect to the application layer provisional identifier corresponding to the network layer provisional identifier, (S706) a control unit that recognizes that the terminal's home network is different from the network to which the device belongs; (S707) a transmitting unit that sends a second message to the base station requesting a change of message delivery destination, which includes destination network information, inter-network node transfer information including the first message and a wireless network layer token, and verification information for verifying the wireless network layer token; (S709). (Note 9) The network node described in Note 8, wherein the wireless network layer token and the verification information include information regarding the validity period. (Note 10) A network node (=AMF30A2) having a receiving unit that receives a first message from a base station including information requesting initial registration and network node-to-network transfer information including a wireless network layer token (S711) and a transmitting unit that transmits a second message to the base station including information accepting initial registration, including a wireless network layer token (S739). (Note 11) A base station having a control unit that generates broadcast information including information indicating that manual cell selection is permitted for the first network, information indicating that limited local carrier services are permitted when manual cell selection is performed for the first network, information indicating that it is connected to the core network of the second network, and information indicating that it is a cell reserved for other purposes for the second network (S201) and a transmitting unit that transmits the broadcast information to a terminal (S201).(Appendix 12) The base station according to Appendix 11, further comprising a receiving unit that receives a first message from a terminal, which includes information requesting initial registration and information indicating that the service is requested, (S303) the control unit selects a first network node (=AMF30A1) belonging to the first network that is capable of handling the service, (S304) the transmitting unit transmits a second message to the first network node, which includes information requesting initial registration, (S305) (Note 13) The receiving unit receives verification information from the first network node for verifying the wireless network layer token, (S709) The control unit stores the verification information, (S710) The receiving unit receives a third message from the terminal, which includes the wireless network layer token and requests connection to the second network node (=AMF30A2) belonging to the second network, (S805) The control unit uses the verification information to verify the wireless network layer token and confirms that the wireless network layer token is valid, (S806) The transmitting unit sends a fourth message to the second network node requesting connection, (S807) The base station as described in Note 11. (Note 14) If the verification information includes information relating to the validity period, the control unit invalidates the verification information after the validity period has elapsed and determines that the wireless network layer token to be verified with the invalidated verification information is invalid, (S806) The base station as described in Note 13. (Note 15) A base station having: (S709) a receiving unit that receives a second message from a first network node (=AMF30A1) requesting a change of message delivery destination, which includes destination network information and information requesting initial registration that the device has sent to the first network node; (S709) a transmitting unit that determines the destination second network node (=AMF30A2) based on the destination network information, (S710) and transmits the information requesting initial registration to the second network node; and (S711)(Note 16) A network node (=FemtoNF30D) having a receiving unit that receives a request message regarding authorization data management, including an application layer token to be registered, from a first network node (=NEF30E) (S103), a control unit that recognizes that the application layer token to be registered is different from any of the existing application layer tokens and stores the application layer token to be registered (S104), and a transmitting unit that sends a response message regarding authorization data management, including an indication of successful registration, to the first network node (S105). (Note 17) A network node (=FemtoNF30D) having a receiving unit that receives a request message relating to authorization data management, including an application layer token generation request, from a first network node (=NEF30E), (S103) a control unit that generates an application layer token different from any of the existing application layer tokens and stores the generated application layer token, (S104) a transmitting unit that sends a response message relating to authorization data management, including the generated application layer token, to the first network node, (S105). (Note 18) A network node (=FemtoNF30D) having a receiving unit that receives a first message from a first network node (=AMF30A1), including an application layer authorization state change event subscription request and an application layer provisional identifier assignment request, (S307) a transmitting unit that sends a second message, including the application layer provisional identifier, to the first network node, (S308).(Note 19) A network node (=FemtoNF30D) having: (S504) a receiving unit that receives a request message from a terminal requesting application layer authorization, which includes an application layer provisional identifier and an application layer token (=user ID + password) for using the base station; (S504) a control unit that verifies the application layer token and recognizes that the verification of the application layer token has been successful; (S506) a transmitting unit that sends a response message to the terminal regarding application layer authorization, which includes information indicating that the verification of the application layer token has been successful; and (S507) a notification message to the first network node (=AMF30A1) regarding an application layer authorization state change event corresponding to the application layer provisional identifier, which includes information indicating that the verification of the application layer token has been successful. (Note 20) The network node (=FemtoNF30D) described in Note 19, where the information indicating that the verification of the application layer token has been successful includes information regarding the validity period of the application layer authorization.

[0195] Any of the provisions of Appendix 1 to Appendix 20 can enable a wireless communication system to configure a terminal to access a CAG cell, regardless of the relationship between the terminal's home network and the network to which the CAG cell belongs.

[0196] (Supplement to Embodiments) Embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but 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, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may 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 other appropriate storage medium.

[0197] Furthermore, notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper 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. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0198] Each aspect / embodiment described in this disclosure refers to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20 may apply to at least one system utilizing UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. Alternatively, multiple systems may be applied in combination (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0199] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

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

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

[0202] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

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

[0204] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

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

[0206] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0207] In addition, terms used 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 the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0208] The terms “system” and “network” as used in this disclosure are interchangeable.

[0209] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0210] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0211] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station equipment", "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. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0212] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0213] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

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

[0215] 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 several other appropriate terms.

[0216] 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 also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0217] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this 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 terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0218] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

[0219] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0220] The terms “connected,” “coupled,” or any variation thereof, mean 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” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0221] The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0222] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0223] Any reference to elements using the designations “first,” “second,” etc., as 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. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

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

[0225] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0226] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0227] In this 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 "combine" may be interpreted similarly to "different."

[0228] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0229] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0230] 10 Base station 110 Transmitting unit 120 Receiving unit 130 Setting unit 140 Control unit 20 Terminal 210 Transmitting unit 220 Receiving unit 230 Setting unit 240 Control unit 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023 Air 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 Driver assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

1. A terminal comprising: a receiving unit that receives broadcast information from a base station including information indicating that manual cell selection is permitted and information indicating that limited local carrier services are permitted when manual cell selection is performed; and a transmitting unit that transmits a first message to the base station including information requesting initial registration including information indicating that it is a registration request prior to a request for the service and information indicating that the service is requested, wherein the receiving unit receives a second message from the base station including information accepting the initial registration prior to a request for the service, including a network layer provisional identifier and an application layer provisional identifier to be used when using the service.

2. A terminal having: a receiving unit that receives broadcast information from a base station including a cell identifier, information indicating that the terminal is connected to the core network of its home network, and information indicating that the cell is reserved for other purposes for the home network; a control unit that recognizes that the terminal possesses a wireless network layer token based on the cell identifier and combination information of a wireless network layer token and cell identifier stored in the terminal; and a transmitting unit that sends a message to the base station requesting connection, including a wireless network layer token, addressed to a network node belonging to the home network.

3. A network node comprising: a receiving unit that receives a first message from a base station, which includes information requesting initial registration, including information indicating that it is a registration request prior to a request for limited local carrier services when a cell is manually selected; and a transmitting unit that transmits a second message to a first network node, which includes a request to subscribe to an application layer authorization state change event and a request to assign an application layer provisional identifier, wherein the receiving unit further has a control unit that receives a third message from the first network node, which includes an application layer provisional identifier, assigns a network layer provisional identifier to a terminal, and stores the network layer provisional identifier and the application layer provisional identifier in the terminal context; and the transmitting unit transmits a fourth message to the base station, which includes information accepting initial registration prior to a request for the service, which includes the network layer provisional identifier and the application layer provisional identifier.

4. A network node having: a receiving unit that receives a first message from a base station that includes a network layer provisional identifier and information requesting initial registration; a control unit that recognizes that the application layer authorization status is successful with respect to the application layer provisional identifier corresponding to the network layer provisional identifier and recognizes that the terminal's home network is different from the network to which the device belongs; and a transmitting unit that sends a second message to the base station requesting a change of message delivery destination, which includes destination network information, inter-network node transfer information including the first message and a wireless network layer token, and verification information for verifying the wireless network layer token.

5. A base station having a control unit that generates broadcast information including information indicating that manual cell selection is permitted for a first network, information indicating that limited local carrier services are permitted for manual cell selection for the first network, information indicating that it is connected to the core network of a second network, and information indicating that it is a cell reserved for other purposes for the second network; and a transmission unit that transmits the broadcast information to a terminal.

6. A network node having: a receiving unit that receives a request message regarding authorization data management, including an application layer token to be registered, from a first network node; a control unit that recognizes that the application layer token to be registered is different from any of the existing application layer tokens and stores the application layer token to be registered; and a transmitting unit that sends a response message regarding authorization data management, including an indication of successful registration, to the first network node.

Images