Network node and communication method
The network node configuration empowers CAG cell holders to manage access to their CAG cells by updating subscriber information and using OIDC CIBA for secure authorization, addressing the lack of control over temporary access permissions in existing systems.
Patent Information
- Application Number
- PCT/JP2023/020486
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-06-01
- Publication Date
- 2024-12-05
AI Technical Summary
CAG cell holders lack the ability to control access to their own CAG cells in wireless communication systems, limiting their temporary access permissions for visitors or guests.
A network node configuration that allows CAG cell holders to manage access by setting human-readable network names (HRNN) and updating subscriber information, enabling them to grant or revoke access permissions through a series of messages and authentication processes involving AMF, UDM, and UDR, using OIDC CIBA for secure authorization.
Enables CAG cell holders to effectively control access to their CAG cells, allowing temporary access permissions for visitors while maintaining secure authentication and authorization within the wireless communication system.
Smart Images

Figure JP2023020486_05122024_PF_FP_ABST
Abstract
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).
[0004] 3GPP TS 23.501 V18.1.0 (2023-03) 3GPP TS 23.401 V18.1.0 (2023-03) 3GPP TS 38.413 V17.4.0 (2023-03) 3GPP TS 29.503 V18.1.0 (2023-03) 3GPP TS 29.505 V18.1.0 (2023-03) 3GPP TS 38.331 V17.4.0 (2023-03) 3GPP TS 38.304 V17.4.0 (2023-03) 3GPP TS 23.122 V18.2.0 (2023-03) 3GPP TS 23.502 V18.1.1 (2023-04) 3GPP TS 29.504 V18.1.0 (2023-03) 3GPP TS 24.501 V18.2.1 (2023-03) OpenID Connect Core 1.0 incorporating errata set 1OpenID Connect Client-Initiated Backchannel Authentication Flow Core 1.0
[0005] The CAG (Closed Access Group, see section 5.30.3 of Non-Patent Document 1) used for access control to PNI (Public Network Integrated) NPN (Non-Public Network) cells is specified based on the CSG (Closed Subscriber Group, see section 4.3.13 of Non-Patent Document 2) used for access control to Home eNB cells. In addition, the CAG can be used for access control to NC-AP (Network Controlled-Access Point) cells consisting of Home gNB cells and Local Gateways.
[0006] An NC-AP cell (hereinafter referred to as a CAG cell) that a terminal can access is defined in the subscriber information of the terminal in a public land mobile network (PLMN). The CAG cell also broadcasts a human-readable network name (HRNN), which is a network name that can be read by the user of the terminal that accesses it. For example, a visitor, such as a family member or friend, who visits a house where a CAG cell is installed can check the HRNN of the CAG cell. However, if the visitor's terminal's subscriber information does not include the CAG identifier of the CAG cell, the visitor cannot access the CAG cell. In this way, access to the CAG cell is controlled based on the terminal's subscriber information. However, there is a problem in that a CAG cell owner cannot control access to the CAG cell it owns, for example, by temporarily allowing a visitor's terminal to access the CAG cell.
[0007] The present invention has been made in consideration of the above points, and aims to enable a CAG cell holder to control access of terminals accessing the CAG cell held by the holder in a wireless communication system.
[0008] According to the disclosed technique, a network node is provided.
[0009] According to the disclosed technology, in a wireless communication system, a CAG cell holder can control access of terminals that access the CAG cell that the holder holds.
[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 a fifth sequence diagram in an embodiment of the present invention. FIG. 6 is a diagram showing an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. FIG. 7 is a diagram showing an example of the functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 8 is a diagram showing an example of the hardware configuration of a base station 10, a terminal 20, and a network node 30 in an embodiment of the present invention. FIG. 9 is a diagram showing an example of the configuration of a vehicle 2001 in an embodiment of the present invention.
[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] Furthermore, the network nodes described in Figures 1 and 2 may be accessible to a network node having a CAPIF (Common API Framework) authorization function, a CAPIF core function, and a PPF (Privacy Preservation Function) having a privacy protection function for performing user authentication based on, for example, OIDC (Open ID Connect) or OIDC CIBA (Open ID Connect Client Initiated Backchannel Authentication). CAPIF is a 3GPP framework that brings together common functions for providing northbound APIs. The CAPIF authorization function has, for example, a function to accept an authentication request and issue an authorization code. The CAPIF core function has, for example, a function to receive an authorization code and issue an ID token and an access token. The authorization function may also be referred to as an authentication function. The PPF has, for example, a function to act as an entity representing an end user in an OIDC authorization code acceptance flow.
[0024] (Example 1) Example 1 will be described. Example 1 shows a process for enabling a CAG cell holder to control access of terminals accessing the CAG cell held by the CAG cell holder in a wireless communication system. Fig. 3 is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. In this sequence, a setting update process in base station 10 will be described. The process of each step in Fig. 3 will be described below.
[0025] Step S301: A CAG cell owner sets a human-readable network name (HRNN) in the CAG cell it owns. The HRNN is a network name that can be read by a user of a terminal accessing the CAG cell.
[0026] Step S302: The base station 10 sends a RAN CONFIGURATION UPDATE (see Section 8.7.2.2 of Non-Patent Document 3) message to the AMF. The message includes an information element (IE) called Extended RAN Node Name (see Section 9.2.6.4 of Non-Patent Document 3). The information element includes a list of combinations of CAG identifiers and HRNNs, which are newly defined information elements. This list is expressed as [CAG ID, HRNN].
[0027] Step S303: The AMF retains (for example, by storing in a storage device such as memory or a hard disk) a list containing the combination of CAG identifier and HRNN contained in the message received from the base station 10 in step S302.
[0028] The following process will be explained using Figure 4. Figure 4 is a diagram showing an example of a second sequence diagram in an embodiment of the present invention. In this sequence, the setting process of a CAG user by a CAG cell holder will be explained. The process of each step in Figure 4 will be explained below.
[0029] Step S304: A user terminal (such as a personal computer or smartphone) operated by the CAG cell holder sends a message (Nnef_CE_Configuration_Create request) to the NEF to request configuration of a CAG user based on the operation of the CAG cell holder. The message includes a CAG identifier, an added CAG cell user identifier, and a deleted CAG cell user identifier. Here, the CAG identifier is the identifier of the CAG cell held by the CAG cell holder and may also be referred to as a CAG cell identifier. The added CAG cell user identifier and the deleted CAG cell user identifier are the identifier of a user to be newly added to the list of users who can use the CAG cell (can access the CAG cell) and the identifier of a user to be deleted from the list of users who can use the CAG cell (can access the CAG cell), respectively. The user identifier may be an identifier that identifies the user's terminal.
[0030] Step S305: Based on the message received in step S304, the NEF sends a message (Nudm_ParameterProvision_Update request, see 5.6.2.2.2 of Non-Patent Document 4) to the UDM to update the subscriber information of the CAG cell holder. The message includes the CAG cell holder identifier, the CAG identifier, the added CAG cell user identifier, and the deleted CAG cell user identifier. Furthermore, any type of identifier may be used as the identifier to identify the CAG cell holder, instead of SUPI or GPSI. For example, SUPI (Subscription Permanent Identifier) or GPSI (Generic Public Subscription Identifier) may be used as the identifier to identify the CAG cell user (the same applies to the subsequent processes).
[0031] Step S306: The UDM sends to the UDR a message (Nudr_DataRepository request, see non-patent document 5) to update the subscriber information of the CAG cell holder, including the information contained in the message received in step S305.
[0032] Step S307: The UDR updates subscriber information about the CAG cell holder based on the received message. That is, the UDR updates a list of the CAG cell holder's contact information (e.g., telephone number, email address, etc.), the identifier of the CAG cell, and the identifiers of users who can use the CAG cell (i.e., can access the CAG cell), corresponding to the CAG cell holder's identifier. This subscriber information is expressed, for example, as a list of [CAG cell holder identifier, CAG cell holder contact information, [CAG cell identifier, list of CAG cell users]]. Here, the CAG cell holder does not need to be a general subscriber. For example, the CAG cell holder may be a subscriber registered as a CAG holder, rather than a subscriber registered as a PLMN user.
[0033] Step S308: Based on the message received in step S304, the NEF sends a message (Nudm_ParameterProvision_Update request, see section 5.6.2.2.2 of NPL 4) to the UDM to update the subscriber information of each of the added CAG cell user and the deleted CAG cell user. The message includes a PpData information element (see Table 6.5.3.2.3.1-2 of NPL 4). In the PpData information element, a cagData information element (see section 6.1.6.2.4 of NPL 4) is newly defined. The cagData information element includes a cagInfos information element (map of CagInfo, see section 6.1.6.2.36 of NPL 4). The cagInfos information element includes an allowedCagList information element (array of CagId, see section 6.1.6.2.37 of NPL 4). The information element allowedCagList is a list of identifiers of CAGs that are permitted to access. For example, when a specific CAG cell is newly added as available to the subscriber information of a CAG cell user, the message includes the identifier of the target CAG in the information element allowedCagList. Also, when a specific CAG cell is deleted as unavailable from the subscriber information of a CAG cell user, the message does not include the identifier of the target CAG in the information element allowedCagList.
[0034] Step S309: The UDM sends a message (Nudr_DataRepository request, see non-patent document 5) to each of the UDRs, including the information contained in the message received in step S308, to update the subscriber information of each of the added CAG cell users and the deleted CAG cell users.
[0035] Step S310: The UDR updates the subscriber information corresponding to the added CAG cell user identifier and the deleted CAG cell user identifier based on the received message.
[0036] The following process will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of a third sequence diagram in an embodiment of the present invention. In this sequence, a cell selection process based on existing specifications will be described. The process of each step in Fig. 5 will be described below.
[0037] Step S311: The base station 10 transmits a message (SIB1) including broadcast information to the terminal 20. The message includes an information element cellAccessRelatedInfo (see section 6.2.2 of Non-Patent Document 6). The information element includes an information element npn-IdentityInfoList (see section 6.3.2 of Non-Patent Document 6; the same applies to the information elements shown below). The information element is composed of multiple information elements NPN-IdentityInfo. The information element includes npn-IdentityList. The information element is composed of multiple information elements NPN-Identity. The information element includes information elements pni-npn. The information element is composed of an information element plmn-Identity and an information element cag-IdentityList (a list of CAG identifiers). The information element is composed of multiple information elements CAG-IdentityInfo (information related to CAG identifiers). This information element consists of the information element cag-Identity (CAG identifier) and the information element manualCAGselectionAllowed.
[0038] Step S312: The base station 10 transmits a message (SIB10) including broadcast information to the terminal 20. The message includes an information element hrnn-List (see Section 6.3.1 of Non-Patent Document 6). The information element is composed of multiple information elements HRNN (see Section 6.3.1 of Non-Patent Document 6), and the information element cag-Identity (CAG identifier) and the information element HRNN are associated with each other.
[0039] Step S313: The AS layer (Access Stratum layer) of terminal 20 transmits information regarding the CAG identifier and HRNN received in step S312 (information including at least one combination of CAG identifier and HRNN) to the NAS layer (Non-Access Stratum layer) of terminal 20 (see Section 4.2 of non-patent document 6).
[0040] Step S314: The NAS layer of the terminal 20 transmits information about the received CAG identifier and HRNN to the upper layer of the terminal 20 (see Section 4.4.3.1.2 of Non-Patent Document 7).
[0041] Step S315: The terminal 20 displays the received information about the HRNN on the screen and accepts an operation by the user to select an HRNN. An upper layer of the terminal 20 selects a CAG cell corresponding to the HRNN selected by the user.
[0042] Step S316: The upper layer of the terminal 20 notifies the NAS layer of the terminal 20 of the CAG cell selected by the user.
[0043] Step S317: The NAS layer of the terminal 20 notifies the AS layer of the terminal 20 of the CAG cell selected by the user.
[0044] Step S318: The AS layer of the terminal 20 selects a CAG cell selected by the user (see section 4.2 of Non-Patent Document 7).
[0045] Step S319: The AS layer of the terminal 20 notifies the NAS layer of the selected CAG cell (see section 4.2 of Non-Patent Document 7).
[0046] The next process will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of a fourth sequence diagram in the embodiment of the present invention. In this sequence, the process of mobility registration will be described. The process of each step in Fig. 6 will be described below.
[0047] Step S320: The terminal 20 transmits an RRCSetupRequest to the base station 10 via the CAG cell selected by the terminal 20 in the sequence diagram of Fig. 5 (see Section 5.3.3.1 of Non-Patent Document 6). The list of permission to use (access permission) the subscriber information of the terminal 20 contained in the UDR does not include the identifier of the CAG cell.
[0048] Step S321: The base station 10 transmits RRC Setup to the terminal 20 (see Section 5.3.3.1 of Non-Patent Document 6).
[0049] Step S322: The terminal 20 transmits an RRCSetupComplete message to the base station 10 via the CAG cell selected by the terminal 20 (see Section 5.3.3.1 of Non-Patent Document 6). The message includes a registration request.
[0050] Step S323: The base station 10 sends an NGAP Initial UE message to the AMF (see Section 8.6.1.2 of Non-Patent Document 3). The message includes an information element NAS PDU (see Section 9.2.5.1 of Non-Patent Document 3). The information element includes a registration request. The message also includes an information element NPN Access Information (see Section 9.2.5.1 of Non-Patent Document 3). The information element includes an information element Cell CAG List (see Section 4.3.3.46 of Non-Patent Document 3). The information element is configured with multiple CAG IDs (CAG identifiers) (see Section 4.3.3.47 of Non-Patent Document 3). The multiple CAG IDs include the CAG ID selected by the terminal 20 in the process described in the sequence diagram of FIG. 5.
[0051] Step S324: The AMF sends a message (Nudm_UECM_Registration request) to the UDM (see step 14a in section 4.2.2.2.2 of non-patent document 3).
[0052] Step S325: The UDM sends a message (Nudm_UECM_Registration response) to the AMF (see step 14a in section 4.2.2.2.2 of non-patent document 3).
[0053] Step S326: The AMF sends a message (Nudm_SDM_Get request) to the UDM (see step 14b in section 4.2.2.2.2 of non-patent document 3).
[0054] Step S327: The UDM sends a message (Nudm_SDM_Get response) to the AMF (see step 14b in section 4.2.2.2.2 of non-patent document 3). The message includes an information element AccessAndMobilitySubscriptionData (see Table 6.1.3.5.3.1-3 in non-patent document 4). The information element includes an information element cagData (see section 6.1.6.2.4 in non-patent document 4). The information element includes cagInfos (a map of CagInfo) (see section 6.1.6.2.36 in non-patent document 4). The information element includes an information element allowedCagList (an array of CagId) (see section 6.1.6.2.37 in non-patent document 4).
[0055] Step S328: The AMF recognizes that the(multiple) CAG IDs obtained from the base station 10 are not included in the(multiple) CAG IDs obtained from the UDM, i.e., according to the subscriber information registered in the UDM, the terminal 20 cannot access the CAG cell corresponding to the(multiple) CAG IDs obtained from the base station 10.
[0056] The next process will be described using Fig. 7. Fig. 7 is a diagram showing an example of a fifth sequence diagram according to an embodiment of the present invention. In this sequence, mobility registration processing will be described. In addition, in this sequence, user authentication based on OIDC CIBA is performed, with the AMF acting as the OIDC RP (Relaying Party), the CAPIF authorization function acting as the OIDC CIBA backchannel authentication termination point, and the PPF acting as the OIDC CIBA authentication device (AD). The process of each step in Fig. 7 will be described below.
[0057] Step S329: The AMF sends an authentication request message to a network node having a CAPIF authorization function (hereinafter referred to as the CAPIF authorization function) to confirm with the holder of the CAG cell that the terminal 20 is temporarily permitted to use the CAG cell. The message includes a login_hint, which is information generally used to identify a user's login ID. Here, the login_hint includes, for example, an identifier of the terminal 20 (SUPI (Subscription Permanent Identifier), GPSI (Generic Public Subscription Identifier)), a terminal selection CAG ID, a terminal selection HRNN, etc. The terminal selection CAG ID is the identifier of the CAG cell selected by the terminal 20 in the sequence diagram of Figure 5, and the terminal selection HRNN is the HRNN corresponding to the terminal selection CAG ID (this also applies to subsequent processing).
[0058] Step S330: The CAPIF authorization function sends an authentication request acceptance message to the AMF, which includes an authentication request identifier (auth_req_id).
[0059] Step S331: The CAPIF authorization function sends a message (Nppf_Authorization request) to the PPF, which message includes the authentication request received in step S329.
[0060] Step S332: The PPF sends a message (Nppf_Authorization response) to the CAPIF authorization function as a response to the received message.
[0061] Step S333: The PPF sends a message (Nudr_DataRepositoryQuery request, see section 5.2.2.2 of Non-Patent Document 10) to the UDR. The message includes query parameters for searching for CAG cell holders and CAG cell users using the terminal selection CAG ID as a key.
[0062] Step S334: The UDR sends a message (Nudr_DataRepositoryQuery Response, see Section 5.2.2.2 of Non-Patent Document 10) to the PPF in response to the received message. The message includes the CAG cell holder, the CAG cell holder's contact information, and the CAG cell user for the terminal selection CAG ID.
[0063] Step S335: If the PPF confirms that the information indicating the CAG cell user contained in the message received in step S334 does not match the SUPI or GPSI in the login_hint contained in the message received in step S331, it executes the following step S336.
[0064] Step S336: The PPF accesses the CAG cell holder included in the message received in step S334, presents the terminal selection CAG ID and terminal selection HRNN to the CAG cell holder, and obtains consent to use of the target CAG cell from the user corresponding to the SUPI or GPSI in the login_hint included in the message received in step S331. For example, the PPF sends a message including the HRNN corresponding to the CAG cell to be permitted to use and information about the user (e.g., the user's SUPI or GPSI) to the terminal device operated by the CAG cell holder, and receives a message indicating that the CAG cell holder has consented to use it in response.
[0065] Step S337: The PPF sends a message (Nppf_AuthorizationNotify request) to the CAPIF authorization function, which message includes an authentication response.
[0066] Step S338: In parallel, the AMF sends a CIBA polling request message to the CAPIF core function, which acts as a token termination point in OIDC CIBA. The message includes the authentication request identifier (auth_req_id) received in step S330.
[0067] Step S339: The CAPIF core function accesses the CAPIF authorization function using the authentication request identifier (auth_req_id).
[0068] Step S340: The CAPIF core function generates an ID token and an access token based on the information obtained from the CAPIF authorization function.
[0069] Step S341: The CAPIF core function sends a CIBA polling response message to the AMF. The message includes an ID token and an access token. The ID token includes information about the time period during which the token ID is valid (this may also be called the validity time or expiration time).
[0070] Step S342: The AMF sends a message (NGAP DL NAS transport, see step 21 in section 4.2.2.2.2 of Non-Patent Document 9) to the base station 10. The message includes a registration acceptance for the registration request received in step S323. The registration acceptance includes an information element, CAG information list (see section 8.2.7.1 of Non-Patent Document 1). The information element includes a combination of multiple CAG identifiers and validity times (see section 5.30.3.3 of Non-Patent Document 1 and section 9.11.3.18A of Non-Patent Document 11). The validity time is information regarding the validity period of access to the CAG cell, i.e., the period during which access is possible. The combination of information elements includes a terminal selection CAG ID and validity time, and the validity time is set to the same value as the validity time of the ID token described above.
[0071] Step S343: The base station 10 sends a message (DL information transfer, see section 8.6.2.2 of Non-Patent Document 3 and step 21 of section 4.2.2.2.2 of Non-Patent Document 9) to the terminal 20. The message includes the registration acceptance received in step S342.
[0072] The above-described embodiment enables a CAG cell holder to control access of terminals accessing the CAG cell held by the CAG cell holder in a wireless communication system.
[0073] (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.
[0074] <Base Station 10 and Network Node 30> Fig. 8 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30. As shown in Fig. 8, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 8 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.
[0075] 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.
[0076] 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.
[0077] As described in the embodiment, the control unit 140 performs processing related to congestion notification. The control unit 140 also performs processing related to communication with the terminal 20. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.
[0078] <Terminal 20> Fig. 9 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 9, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 9 is merely an example. As long as the operations related to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. In addition, the communication device that becomes the resource holder 20 may have the same functional configuration as the terminal 20.
[0079] 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.
[0080] The setting unit 230 stores various pieces of setting information received from the network node 30 by the receiving unit 220 in a storage device, and reads them out from the storage device as needed. The setting unit 230 also stores setting information that is set in advance.
[0081] As described in the embodiment, the control unit 240 performs processing related to congestion notification. The signal transmission functional unit in the control unit 240 may be included in the transmitting unit 210, and the signal reception functional unit in the control unit 240 may be included in the receiving unit 220.
[0082] (Hardware Configuration) The block diagrams (FIGS. 8 and 9) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.
[0083] 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.
[0084] For example, the base station 10, the network node 30, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 10 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The network node 30 may have the same hardware configuration as the base station 10. The above-described base station 10 and the terminal 20 may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.
[0085] 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.
[0086] 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.
[0087] 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.
[0088] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 8 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. For example, the control unit 240 of the terminal 20 shown in FIG. 9 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.
[0089] 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.
[0090] 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.
[0091] 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.
[0092] 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).
[0093] 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.
[0094] 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.
[0095] Fig. 11 shows an example configuration of a vehicle 2001. As shown in Fig. 11, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.
[0096] 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.
[0097] 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).
[0098] 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.
[0099] 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.
[0100] 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.
[0101] 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.
[0102] 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.
[0103] 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.
[0104] 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.
[0105] (Summary of the embodiment) As described above, according to the embodiment of the present invention, there is provided a network node having a control unit that manages a list of subscriber information related to CAG (Closed Access Group) cells, a receiving unit that receives a request to update the list from a first network node and receives an inquiry request including an identifier of a CAG cell from a second network node, and a transmitting unit that transmits information regarding a CAG cell holder, contact information of the CAG cell holder, and a CAG cell user corresponding to the identifier of the CAG cell to the second network node.
[0106] The above configuration enables a CAG cell holder to control access of terminals accessing the CAG cell held by the CAG cell holder in a wireless communication system.
[0107] The list may include information about CAG cell holders, CAG cell holder contacts, CAG cells, and CAG users.
[0108] In addition, according to an embodiment of the present invention, a network node is provided which has a receiving unit that receives a registration request from a terminal via a CAG cell that is not included in the terminal's permission list, and a transmitting unit that transmits a request to the holder of the CAG cell to confirm that the terminal is temporarily permitted to use the CAG cell, wherein the transmitting unit transmits to the terminal an identifier of the CAG cell and information regarding the validity period of permission to use the CAG cell if the holder permits use of the CAG cell.
[0109] The above configuration enables a CAG cell holder to control access of terminals accessing the CAG cell held by the CAG cell holder in a wireless communication system.
[0110] The receiving unit may receive a list of CAG cell identifiers and HRNNs (Human-Readable Network Names) corresponding to the identifiers from the base station, and the transmitting unit may transmit the identifier of the terminal, the identifier of the CAG cell used by the terminal, and the HRNN corresponding to the identifiers when sending the confirmation.
[0111] Also, according to an embodiment of the present invention, there is provided a communication method executed by a network node, comprising the steps of: managing a list of subscriber information related to a CAG (Closed Access Group) cell; receiving a request to update the list from a first network node; receiving an inquiry request including an identifier of a CAG cell from a second network node; and transmitting information regarding a CAG cell holder, a contact point of the CAG cell holder, and a user of the CAG cell corresponding to the identifier of the CAG cell to the second network node.
[0112] The above configuration enables a CAG cell holder to control access of terminals accessing the CAG cell held by the CAG cell holder in a wireless communication system.
[0113] In addition, according to an embodiment of the present invention, there is provided a communication method executed by a network node, which includes a receiving step of receiving a registration request from a terminal via a CAG cell that is not included in the terminal's permission list, and a transmitting step of transmitting a request to the holder of the CAG cell to confirm that the terminal is temporarily permitted to use the CAG cell, wherein the transmitting step, if the holder permits use of the CAG cell, transmits to the terminal an identifier of the CAG cell and information regarding the validity period of permission to use the CAG cell.
[0114] The above configuration enables a CAG cell holder to control access of terminals accessing the CAG cell held by the CAG cell holder in a wireless communication system.
[0115] (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.
[0116] 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.
[0117] 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).
[0118] 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.
[0119] 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).
[0120] 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.
[0121] 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.
[0122] In the present disclosure, the determination may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a comparison of numerical values (e.g., comparison with a predetermined value).
[0123] 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.
[0124] 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.
[0125] 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.
[0126] 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.
[0127] As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0128] 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.
[0129] 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.
[0130] 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.
[0131] 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.
[0132] 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.
[0133] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," and the like may be used interchangeably.
[0134] 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.
[0135] 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.
[0136] 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.
[0137] 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.
[0138] 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.
[0139] 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.
[0140] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.
[0141] 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."
[0142] 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.
[0143] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.
[0144] 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.
[0145] 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.
[0146] 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."
[0147] 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).
[0148] 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.
[0149] 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 network node having: a control unit that manages a list of subscriber information related to CAG (Closed Access Group) cells; a receiving unit that receives a request to update the list from a first network node and receives an inquiry request including a CAG cell identifier from a second network node; and a transmitting unit that transmits information regarding a CAG cell holder, a CAG cell holder's contact information, and a CAG cell user corresponding to the CAG cell identifier to the second network node.
2. The network node of claim 1, wherein the list includes information about CAG cell holders, CAG cell holder contacts, CAG cells, and CAG users.
3. A network node having a receiving unit that receives a registration request from a terminal via a CAG cell that is not included in the terminal's permission list, and a transmitting unit that transmits a request to a holder of the CAG cell to confirm that the terminal is temporarily permitted to use the CAG cell, wherein if the holder permits use of the CAG cell, the transmitting unit transmits to the terminal an identifier of the CAG cell and information regarding the validity period of permission to use the CAG cell.
4. The network node of claim 3, wherein the receiving unit receives from a base station a list of CAG cell identifiers and HRNNs (Human-Readable Network Names) corresponding to the identifiers, and the transmitting unit transmits, when transmitting the confirmation, an identifier of the terminal, an identifier of a CAG cell used by the terminal, and an HRNN corresponding to the identifiers.
5. A communication method performed by a network node, comprising the steps of: managing a list of subscriber information related to CAG (Closed Access Group) cells; receiving a request to update the list from a first network node and receiving a query request including a CAG cell identifier from a second network node; and transmitting information regarding CAG cell holders, CAG cell holder contact information, and CAG cell users corresponding to the CAG cell identifier to the second network node.
6. A communications method executed by a network node, comprising: a receiving step of receiving a registration request from a terminal via a CAG cell that is not included in the terminal's permission list; and a transmitting step of transmitting a request to the holder of the CAG cell to confirm that the terminal is temporarily permitted to use the CAG cell, wherein the transmitting step, if the holder permits use of the CAG cell, transmits to the terminal an identifier of the CAG cell and information regarding the validity period of permission to use the CAG cell.
Citation Information
Patent Citations
Control device, wireless communication system, control method, and program
WO2020209161A1
Management device, management method, wireless communication device, and wireless communication method
WO2022050044A1
