Network node and communication method

Abstract

A network node comprising a reception section that receives, from a first network node, a first message requesting setting of setting information pertaining to a user who is accessing a visited public land mobile network (VPLMN), a control section that sets the setting information in additional subscriber information of the user in the VPLMN, and a transmission section that transmits, to the first network node, a second message responding to the first message, wherein: the reception section receives a third message requesting the additional subscriber information of the user from a second network node; and the transmission section transmits a fourth message including the additional subscriber information to the second network node.

Description

Network node and communication method

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

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

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

[0004] 3GPP TS 23.501 V18.4.0 (2023-12) 3GPP TS 23.401 V18.4.0 (2023-12) 3GPP TS 23.502 V18.4.0 (2023-12)

[0005] In EPS, a CSG Subscriber Server (CSS) is introduced to manage an authorized CSG (Closed Subscriber Group) list related to cell access control for roaming-in users (see, for example, Non-Patent Document 2). In 5GS, it is being considered to provide an authorized CAG (Closed Access Group) list, which is equivalent to the authorized CSG list, to roaming-in users.

[0006] However, since the CSS implemented in EPS cannot be implemented in 5GS, it is necessary to consider a method that enables the setting of an authorized CAG list that allows access to roaming-in users in 5GS.

[0007] The present invention has been made in view of the above points, and has as its object to set additional subscriber information in a VPLMN (Visited Public Land Mobile Network) in a communication system.

[0008] According to the disclosed technology, there is provided a network node having a receiving unit that receives from a first network node a first message requesting the setting of configuration information related to a user accessing a Visited Public Land Mobile Network (VPLMN), a control unit that sets the configuration information to additional subscriber information of the user in the VPLMN, and a transmitting unit that transmits to the first network node a second message in response to the first message, wherein the receiving unit receives from a second network node a third message requesting additional subscriber information of the user, and the transmitting unit transmits to the second network node a fourth message including the additional subscriber information.

[0009] According to the disclosed technology, in a communication system, additional subscriber information can be set in a Visited Public Land Mobile Network (VPLMN).

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

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

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

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

[0014] Fig. 1 is a diagram illustrating an example of a communication system. As shown in Fig. 1, the communication system is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0015] The RAN (Radio Access Network) is a network node 30 having a radio access function, which may include a base station 10, and is connected to a UE, an AMF (Access and Mobility Management Function), and a UPF (User plane function). The AMF is a network node 30 having functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU (Protocol Data Unit) session point to the outside that interconnects with a DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

[0016] The AMF is connected to the UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are mutually connected via interfaces based on their respective services, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

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

[0018] Fig. 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Fig. 2, the network is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

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

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

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

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

[0023] The Closed Access Group (CAG) used for access control to a Public Network Integrated (PNI) Non-Public Network (NPN) cell is specified based on the Closed Subscriber Group (CSG) used for access control to a Home eNB cell (see Section 4.3.13 of Non-Patent Document 2). In the EPS, a CSG Subscriber Server (CSS) is introduced to manage an allowed CSG list, which is a list of CSG identifiers that are permitted to be accessed by roaming-in users (see Sections 4.4.11, 5.3.12, and 5.3.13 of Non-Patent Document 2). In 5GS, it is being considered to provide roaming-in users with an allowed CAG list, which is a list of CAG identifiers that are permitted to be accessed, similar to the EPS.

[0024] However, the CSS implemented in EPS cannot be implemented in 5GS. For example, EPS does not specify the procedure for an MME to access a CSS or the procedure for an administrator to update the CSS.

[0025] (Embodiment) An embodiment will be described. In this embodiment, a method for setting additional subscriber information in a VPLMN (Visited Public Land Mobile Network) in a communication system will be described.

[0026] In this embodiment, an identifier (referred to as an administrator-added CAG permission identifier) ​​indicating whether or not the CAG administrator is permitted to add information about authorized CAGs is introduced into the subscriber information. The subscriber can set the administrator-added CAG permission identifier in the HPLMN via the NEF. For example, the administrator-added CAG permission identifier is set to a value of 1 or 0, indicating that the CAG administrator is permitted or not permitted to add information about authorized CAGs, respectively. Furthermore, if the administrator-added CAG permission identifier is set, it may indicate that the roaming-in user's VPLMN-added subscriber information exists in the VPLMN.

[0027] When the AMF receives a registration request from the roaming-in user's terminal, it discovers the UDM that manages the roaming-in user's VPLMN additional subscriber information based on the administrator additional CAG allowed identifier included in the subscriber information and information identifying the HPLMN. Furthermore, the AMF obtains the user's VPLMN additional subscriber information based on an identifier (SUPI, Subscription Permanent Identifier) ​​that identifies the roaming-in user. The SUPI is a user identifier used within the HPLMN. The AMF also concatenates the permitted CAG list included in the VPLMN additional subscriber information with the permitted CAG list included in the normal subscriber information in the HPLMN, and notifies the base station 10 and the terminal 20.

[0028] When setting up a CAG in the VPLMN to allow access, the CAG administrator specifies the roaming-in user to be permitted by using a GPSI (Generic Public Subscription Identifier). The GPSI is a user identifier used outside the HPLMN. The NEF queries the UDM in the HPLMN for the SUPI corresponding to the GPSI. The UDM returns the SUPI corresponding to the GPSI only if the SUPI has already been registered in the VPLMN. In the VPLMN, the additional subscriber information of the roaming-in user and information on the CAG administrator's operation history regarding CAG permission may be managed by different UDMs. Furthermore, if the VPLMN roams with multiple network operators, the VPLMN additional subscriber information is stored for each network operator.

[0029] The following describes the processing executed by the terminal 20 of a roaming-in user and the network nodes 30 in the VPLMN and HPLMN, using sequence diagrams.

[0030] The network nodes in the VPLMN are AMF 30A, UDM 30B, UDM 30C, NRF 30D, NEF 30E, and NN (CAG administrator) 30F.

[0031] UDM30B manages VPLMN additional subscriber information, and UDM30C manages information related to CAG administrators. UDM30B and UDM30C store the information they manage in a UDR. The UDR may be included in UDM30B and UDM30C, or may be a network node separate from UDM30B and UDM30C.

[0032] The NN (CAG administrator) 30F is a network node used when the CAG administrator registers the authorized CAG information of a roaming-in user in the VPLMN. For example, the CAG administrator connects to the NN (CAG administrator) 30F via a personal computer or a smartphone, and causes the NN (CAG administrator) 30F to execute the requested processing.

[0033] The network nodes in the HPLMN are the NRF 30G, the UDM 30H, the NEF 30I, and the NN (subscriber) 30J. The NN (subscriber) 30J is a network node used by a subscriber when setting an administrator-added CAG allowable identifier. For example, the subscriber connects to the NN (subscriber) 30J via a personal computer or a smartphone, and causes the NN (subscriber) 30J to execute the requested processing.

[0034] Furthermore, information, requests, responses, etc. sent and received in the sequence diagram may be referred to as messages. Figure 3 is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. In this sequence diagram, an administrator-added CAG permission identifier indicating that the CAG administrator is permitted to add information about authorized CAGs is set in the subscriber information in the HPLMN. The processing of each step in Figure 3 is described below.

[0035] S101: The NN (subscriber) 30J sends a request message (Nnef_ParameterProvision_Create request) to the NEF 30I to request the setting of subscriber information. The request message includes an administrator-added CAG permission identifier indicating that the CAG administrator is permitted to add information about authorized CAGs to the subscriber information. The message also includes an identifier (e.g., GPSI or SUPI) that identifies the subscriber to whom information is to be added.

[0036] S102: The NEF 30I sends to the UDM 30H a request message (Nudm_ParameterProvision_Create request) containing the same content as the request message received in S101.

[0037] S103: Based on the request message received in S101, UDM30H sets an administrator-added CAG permission identifier that allows the CAG administrator to add information about the authorized CAG to the subscriber information. Note that this setting is not limited to the above method, and for example, the network operator may set this to the subscriber information without going through NEF30I.

[0038] 4 is a diagram showing an example of a second sequence diagram according to an embodiment of the present invention. In this sequence diagram, a process related to setting an authorized CAG is executed in the VPLMN. The process of each step in FIG. 4 will be described below.

[0039] S201: The NN (administrator) 30F sends a request message (Nnef_ParameterProvision_Create request) to the NEF 30E to request the setting of a permitted CAG. The request message includes the identifier of the CAG administrator, the first identifier (GPSI=aa) of the subscriber (roaming-in user) in the subscriber information to which the setting of a permitted CAG is to be added, and the CAG identifier to which the subscriber is permitted to access.

[0040] S202: Based on the request message received in S201, the NEF 30E recognizes that it is necessary to obtain a second identifier (SUPI) corresponding to the first identifier (GPSI=aa) of the roaming-in user from the HPLMN.

[0041] S203: The NEF 30E sends to the NRF 30D a request message (Nnrf_NFDiscovery request) requesting discovery of a UDM that manages the subscriber information of a roaming-in user identified by a first identifier (GPSI=aa). The request message includes the first identifier (GPSI=aa) of the roaming-in user.

[0042] S204: The NRF 30D sends to the NRF 30G a request message (Nnrf_NFDiscovery request) that includes the same content as the request message received in S203.

[0043] S205: The NRF 30G transmits to the NRF 30D, as a response to the request message received in S204, a response message (Nnrf_NFDiscovery response) including information (UDM instance) related to the requested UDM.

[0044] S206: The NRF 30D sends to the NEF 30E, as a response to the request message received in S204, a response message (Nnrf_NFDiscovery response) containing the same content as the response message received in S205.

[0045] S207: The NEF 30E confirms that the requested UDM is the UDM 30H based on the information about the UDM included in the response message received in S206. Furthermore, the NEF 30E transmits to the UDM 30H a request message (Nudm_SDM_Get request) requesting acquisition of the administrator-added CAG allowable identifier set in S103 of FIG. 3 and a second identifier (SUPI) corresponding to the first identifier (GPSI=aa) included in the request message received in S201. The request message includes the first identifier (GPSI=aa). Furthermore, because the request message requests conversion of the first identifier (GPSI) to the second identifier (SUPI), it may be expressed as Nudm_SDM_Get request (identifier translation, GPSI=aa).

[0046] S208: The UDM 30H confirms that the second identifier (SUPI) corresponding to the first identifier (GPSI=aa) included in the request message received in S207 has been registered in the VPLMN in which the NEF 30E resides, i.e., that the second identifier (SUPI) has been disclosed to the VPLMN. If the terminal 20 has roamed in the VPLMN, the second identifier (SUPI) is transmitted to the VPLMN in the registration procedure (see Section 4.2.2.2 of Non-Patent Document 3), and therefore the second identifier is registered (disclosed).

[0047] S209: The UDM 30H sends a response message (Nudm_SDM_Get response) to the NEF 30E in response to the request message received in S207. The response message includes the requested administrator-added CAG permitted identifier and second identifier (SUPI). Here, for example, based on the judgment of the network operator, the response message including the second identifier (SUPI) may be sent only if it is confirmed in S208 that the second identifier (SUPI) has been registered in the VPLMN in which the NEF 30E exists.

[0048] S210: If the administrator-added CAG permission identifier received in S209 indicates that the CAG administrator is allowed to add information about the permitted CAG, NEF30E decides to set the CAG identifier that the subscriber is allowed to access in the VPLMN-added subscriber information based on the request received in S201.

[0049] S211: The NEF 30E sends the NRF 30D a request message (Nnrf_NFDiscovery request) requesting the discovery of a UDM that manages information related to the CAG administrator.

[0050] S212: The NRF 30D sends to the NEF 30E, as a response to the request message received in S211, a response message (Nnrf_NFDiscovery response) including information (UDM instance) about the requested UDM.

[0051] S213: NEF30E confirms that the requested UDM is UDM30C based on the information about the UDM included in the response message received in S212. Furthermore, NEF30E sends a request message (Nudm_ParameterProvision_Create request) to UDM30C requesting that information about the CAG administrator be set. The request message includes the CAG administrator identifier, the subscriber's first identifier (GPSI=aa), the CAG identifier that grants access to the subscriber, and the second identifier (SUPI) included in the response message received in S209, all of which are included in the request message received in S201.

[0052] S214: UDM30C sets information about the CAG administrator in accordance with the request message received in S213. For example, UDM30C associates and stores the CAG administrator identifier, the subscriber's first identifier (GPSI=aa), the CAG identifier that grants access to the subscriber, and the second identifier (SUPI), all of which are included in the request message received in S213.

[0053] S215: The UDM 30C transmits to the NEF 30E a response message (Nudm_ParameterProvision_Create response) in response to the request message received in S213.

[0054] S216: The NEF 30E sends a request message (Nnrf_NFDiscovery request) to the NRF 30D to request discovery of a UDM that manages the roaming-in user's VPLMN additional subscriber information. The request message includes the identifier of the roaming-in user's HPLMN (HPLMN=hh).

[0055] S217: The NRF 30D sends to the NEF 30E, as a response to the request message received in S216, a response message (Nnrf_NFDiscovery response) including information (UDM instance) about the requested UDM.

[0056] S218: Based on the information about the UDM included in the response message received in S217, the NEF 30E confirms that the requested UDM is UDM 30B. Furthermore, the NEF 30E sends a request message (Nudm_ParameterProvision_Create request) to UDM 30B requesting that additional subscriber information for the roaming-in user be set in the VPLMN. The request message includes the CAG identifier that grants access to the subscriber, which is included in the request message received in S201, and the second identifier (SUPI) included in the response message received in S209.

[0057] S219: UDM30B sets VPLMN additional subscriber information in the subscriber information of the roaming-in user in response to the request message received in S218. For example, UDM30B uses the CAG identifier for which access is permitted and the second identifier (SUPI) included in the request message received in S218 to add the CAG identifier to the permitted CAG list in the VPLMN included in the subscriber information corresponding to the second identifier (SUPI).

[0058] S220: The UDM 30B transmits to the NEF 30E a response message (Nudm_ParameterProvision_Create response) in response to the request message received in S218.

[0059] S221: The NEF 30E transmits a response message (Nnef_ParameterProvision_Create response) to the request message received in S201 to the NN (administrator) 30F.

[0060] S222: The UDM 30B transmits a request message (Nudm_SDM_Notification Notify request) to the AMF 30A to request notification regarding updates to the subscriber information. The request message includes the CAG identifier for which access is permitted, which was set in S219.

[0061] S223: AMF 30A adds the CAG identifier received in S222 to the permitted CAG list for VPLMN in the VPLMN additional subscriber information of the roaming-in user received from UDM 30B in advance (when the registration procedure for terminal 20 to VPLMN was executed). Furthermore, AMF 30A generates a permitted CAG list that concatenates the permitted CAG list for VPLMN in the roaming-in user's normal subscriber information and the permitted CAG list for VPLMN in the roaming-in user's VPLMN additional subscriber information. Here, AMF 30A obtained the roaming-in user's normal subscriber information in advance (when the registration procedure for terminal 20 to VPLMN was executed).

[0062] S224: AMF 30A transmits a message (UE Configuration Update Command) including the CAG list generated in S223 to the terminal 20 via the base station 10. That is, the base station 10 and the terminal 20 receive the CAG list.

[0063] 5 is a diagram showing an example of a third sequence diagram according to an embodiment of the present invention. In this sequence diagram, a process related to a registration procedure (see section 4.2.2.2 of Non-Patent Document 3) is executed in a VPLMN when terminal 20 roams in. The process of each step in FIG. 5 will be described below.

[0064] S301: The terminal 20 transmits a request message requesting registration to the AMF 30A.

[0065] S302: Based on the registration procedure of the existing specifications, processing related to authentication and security is executed. Here, the AMF 30A acquires the second identifier (SUPI=bb) of the roaming-in user.

[0066] S303: The AMF 30A transmits a request message (Nudm_UECM_Registration request) requesting registration to the UDM 30H. The request message includes the roaming-in user's identifier (SUPI=bb).

[0067] S304: Based on the request message received in S303, the UDM 30H sets the second identifier (SUPI=bb) of the roaming-in user to be registered in the VPLMN.

[0068] S305: UDM30H sends a response message (Nudm_UECM_Registration response) to AMF30A in response to the request message received in S303.

[0069] S306: The AMF 30A sends a request message (Nudm_SDM_Get request) to the UDM 30H to request acquisition of the subscriber information of the roaming-in user. The request message includes the second identifier (SUPI=bb) of the roaming-in user.

[0070] S307: The UDM 30H transmits a response message (Nudm_SDM_Get response) to the request message received in S306 to the AMF 30A. The response message includes the requested subscriber information.

[0071] S308: AMF30A checks the administrator-added CAG permission identifier included in the subscriber information received in S307.

[0072] S309: If an administrator-added CAG permission identifier is set in the subscriber information, AMF30A decides to obtain the VPLMN-added subscriber information of the roaming-in user.

[0073] S310: The AMF 30A sends a request message (Nnrf_NFDiscovery request) to the NRF 30D to request discovery of a UDM that manages the roaming-in user's VPLMN additional subscription information. The request message includes the roaming-in user's HPLMN identifier (HPLMN=hh).

[0074] S311: The NRF 30D sends to the AMF 30A a response message (Nnrf_NFDiscovery response) including information (UDM instance) about the requested UDM as a response to the request message received in S310.

[0075] S312: AMF 30A confirms that the requested UDM is UDM 30B based on the information about the UDM included in the response message received in S311. Furthermore, AMF 30A sends a request message (Nudm_SDM_Get request) to UDM 30B requesting acquisition of the VPLMN additional subscriber information of the roaming-in user. The request message includes the second identifier (SUPI=bb) of the roaming-in user.

[0076] S313: UDM 30B sends a response message (Nudm_SDM_Get response) to AMF 30A in response to the request message received in S312. The response message includes the requested VPLMN additional subscriber information. The VPLMN additional subscriber information also includes an authorized CAG list for the VPLMN.

[0077] S314: AMF30A generates an authorized CAG list by concatenating the authorized CAG list for VPLMN in the roaming-in user's normal subscriber information received from UDM30H and the authorized CAG list for VPLMN in the roaming-in user's VPLMN additional subscriber information received from UDM30B.

[0078] S315: AMF 30A sends a response message accepting registration to the terminal 20 via the base station 10 as a response message corresponding to the request message received in S301. The response message includes the permitted CAG list generated in S314. That is, the base station 10 and the terminal 20 receive the CAG list.

[0079] According to the above embodiment, additional subscriber information can be set in a Visited Public Land Mobile Network (VPLMN) in a communication system.

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

[0081] <Base Station 10 and Network Node 30> Fig. 6 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30. As shown in Fig. 6, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 6 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

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

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

[0084] As described in the embodiment, the control unit 140 performs processes related to setting the permitted CAG, etc. The control unit 140 also performs processes related to communication with the terminal 20. A functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0085] <Terminal 20> Fig. 7 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 7, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 7 is merely an example. As long as the operations related to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. In addition, the communication device that becomes the resource holder 20 may have the same functional configuration as the terminal 20.

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

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

[0088] As described in the embodiment, the control unit 240 performs processing related to setting of the permitted CAG, etc. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

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

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

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

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

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

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

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

[0096] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

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

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

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

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

[0101] Furthermore, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0102] Fig. 9 shows an example configuration of a vehicle 2001. As shown in Fig. 9, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

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

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

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

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

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

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

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

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

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

[0112] <Supplementary Notes> (Supplementary Item 1) A network node comprising: a receiving unit that receives, from a first network node, a first message requesting configuration information for a user accessing a Visited Public Land Mobile Network (VPLMN), a control unit that sets the configuration information in additional subscriber information of the user in a VPLMN, and a transmitting unit that transmits a second message responding to the first message to the first network node, wherein the receiving unit receives, from a second network node, a third message requesting additional subscriber information of the user, and the transmitting unit transmits a fourth message including the additional subscriber information to the second network node. (Supplementary Item 2) A network node comprising: a receiving unit that receives, from a first network node in a Home Public Land Mobile Network (HPLMN) of the user, a first message including subscriber information of a user accessing a Visited Public Land Mobile Network (VPLMN), a control unit that confirms that an identifier indicating that additional subscriber information exists in the VPLMN is set in the subscriber information, and a transmitting unit that transmits a second message requesting the additional subscriber information to a second network node in the VPLMN. (Supplementary Item 3) The network node according to Supplementary Item 1 or Supplementary Item 2, wherein the additional subscriber information is accommodated for each HPLMN (Home Public Land Mobile Network) of the user. (Supplementary Item 4) The network node according to Supplementary Item 1 or Supplementary Item 2, wherein the additional subscriber information includes setting information relating to a CAG (Closed Subscriber Group) to which the user is permitted access.(Supplementary clause 5) A network node comprising: a receiving unit that receives, from a first network node in a Visited Public Land Mobile Network (VPLMN), a first message including a request to convert a first user identifier used outside a Home Public Land Mobile Network (HPLMN) into a second user identifier used within the HPLMN, and a transmitting unit that, if the second user identifier has already been transmitted to the VPLMN, transmits a second message including the second user identifier to the first network node. (Supplementary clause 6) A communication method executed by a network node, comprising: receiving, from the first network node, a first message requesting configuration information related to a user accessing the Visited Public Land Mobile Network (VPLMN), setting the configuration information in additional subscriber information of the user in the VPLMN, transmitting to the first network node a second message responding to the first message, receiving from a second network node a third message requesting additional subscriber information of the user, and transmitting to the second network node a fourth message including the additional subscriber information.

[0113] Any of Supplementary Items 1 to 6 allows additional subscriber information to be set in a Visited Public Land Mobile Network (VPLMN) in a communication system.

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

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

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

[0117] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0134] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0135] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

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

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

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

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

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

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

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

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

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

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

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

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

[0148] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Tire pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A receiving unit that receives a first message requesting setting of setting information related to a user accessing a VPLMN (Visited Public Land Mobile Network) from a first network node; a control unit that sets the setting information in additional subscriber information of the user in the VPLMN; and a transmitting unit that transmits a second message responding to the first message to the first network node. The receiving unit receives a third message requesting additional subscriber information of the user from a second network node, and the transmitting unit transmits a fourth message including the additional subscriber information to the second network node. A network node.

2. A receiving unit that receives a first message including subscriber information of a user accessing a VPLMN (Visited Public Land Mobile Network) from a first network node in the user's HPLMN (Home Public Land Mobile Network); a control unit that confirms that an identifier indicating the presence of additional subscriber information in the VPLMN is set in the subscriber information; and a transmitting unit that transmits a second message requesting the additional subscriber information to a second network node in the VPLMN. A network node having.

3. The network node according to claim 1 or claim 2, wherein the additional subscriber information is accommodated for each HPLMN (Home Public Land Mobile Network) of the user.

4. The network node according to claim 1 or claim 2, wherein the additional subscriber information includes setting information related to a CAG (Closed Subscriber Group) that permits access to the user.

5. A receiving unit that receives a first message including a request to convert a first user identifier used outside the HPLMN (Home Public Land Mobile Network) into a second user identifier used inside the HPLMN from a first network node in the VPLMN (Visited Public Land Mobile Network); and a transmitting unit that transmits a second message including the second user identifier to the first network node when the second user identifier has already been transmitted to the VPLMN. A network node having the above components.

6. A communication method executed by a network node, the method including: receiving a first message from a first network node, the first message requesting setting of setting information related to a user accessing the VPLMN (Visited Public Land Mobile Network); setting the setting information in additional subscriber information of the user in the VPLMN; transmitting a second message responding to the first message to the first network node; receiving a third message from a second network node, the third message requesting the additional subscriber information of the user; and transmitting a fourth message including the additional subscriber information to the second network node.

Images