Network device and communication control method

Abstract

This network device: issues security information including at least a security key to be used for communication between a terminal and a radio access network node or another network device; and transmits the security information to another network device for another plane provided separately from a user plane and a control plane.

Description

Network Device and Communication Control Method

[0001] The present disclosure relates to a network device and a communication control method that support processing in planes according to functions.

[0002] The 3rd Generation Partnership Project (3GPP: registered trademark) has specified the 5th generation mobile communication system (also called 5G, New Radio (NR), or Next Generation (NG)), and is also promoting the specification of the next generation, called Beyond 5G, 5G Evolution, or 6G.

[0003] In 5G (NR), a user plane (U-plane) responsible for transferring user data transmitted and received by a terminal (User Equipment, UE) and a control plane (C-plane) responsible for managing signaling and control messages are defined (Non-Patent Document 1).

[0004] 3GPP TS 38.300 V18.4.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 18), 3GPP, December 2024

[0005] On the other hand, in 6G, a new plane other than the U-plane and C-plane (hereafter, referred to as the "X-plane" for convenience) may be introduced. In the X-plane, for example, sensing data by sensors, AIML data related to artificial intelligence / machine learning models (AI / ML Model), positioning data related to the position information of the UE, and energy-related data related to energy consumption in the mobile network are assumed to be handled. In the X-plane, processing such as collection, retention, and calculation of such data may be performed by separate network functions (NF).

[0006] Thus, when multiple NFs (which may also be called XPFs) providing X-planes are established, UEs and radio access network nodes (6G RAN nodes) such as radio base stations (gNBs) may be able to communicate directly with those NFs.

[0007] However, in 5G, the Access and Mobility Management Function (AMF), a Network Device (NF) that manages UE (User) registration, UE network connectivity, UE mobility, and UE security, centrally manages security information, including the issuance of security keys applied to communication between the UE and the AMF or gNB. Therefore, ensuring security when the XPF communicates directly with the UE or 6G RAN node becomes a problem.

[0008] Therefore, the following disclosure is made in light of these circumstances and aims to provide network equipment and communication control methods that contribute to ensuring the security of communication between the UE and the NF providing the X-plane, even when new planes other than U-plane and C-plane are introduced.

[0009] One aspect of the present disclosure is a network device (AMF70) comprising a control unit (control unit 77) that issues security information including at least a security key used for communication between a terminal (UE200) and a wireless access network node (e.g., gNB100) or other network device (XPF50), and a transmission unit (security information management unit 75) that transmits the security information to the other network device on a separate plane provided separately from the user plane and the control plane.

[0010] One aspect of the present disclosure is a network device (AMF70) comprising a control unit (control unit 77) that issues security information including at least a security key used for communication between a terminal and a wireless access network node or other network device, and a transmission unit (security information management unit 75) that transmits the security information to a proxy network device connected to a plurality of the other network devices in a separate plane provided separately from the user plane and the control plane.

[0011] Figure 1 is an overall schematic diagram of the wireless communication system 10. Figure 2 is a diagram of configuration example 1 of 6G-CN30. Figure 3 is a diagram of configuration example 2 of 6G-CN30. Figure 4 is a functional block configuration diagram of XPF50. Figure 5 is a functional block configuration diagram of AMF70. Figure 6 is a functional block configuration diagram of gNB100. Figure 7 is a diagram of a sequence example related to security establishment between AMF and UE. Figure 8 is a diagram of sequence example 1 between AMF and XPF (XX NF) related to operation example 1. Figure 9 is a diagram of sequence example 2 between AMF and XPF (XX NF) related to operation example 1. Figure 10 is a diagram of sequence example 3 between AMF and XPF (XX NF) related to operation example 1. Figure 11 is a diagram of sequence example 1 between 6G RAN node and XPF (XX NF) related to operation example 2. Figure 12 is a diagram of sequence example 2 between 6G RAN node and XPF (XX NF) related to operation example 2. Figure 13 shows sequence example 3 between the 6G RAN node and XPF (XX NF) related to operation example 2. Figure 14 shows sequence example 4 between the 6G RAN node and XPF (XX NF) related to operation example 2. Figure 15 shows sequence example 5 between the 6G RAN node and XPF (XX NF) related to operation example 2. Figure 16 shows sequence example 6 between the 6G RAN node and XPF (XX NF) related to operation example 2. Figure 17 shows sequence example 7 between the 6G RAN node and XPF (XX NF) related to operation example 2. Figure 18 shows sequence example 8 between the 6G RAN node and XPF (XX NF) related to operation example 2. Figure 19 shows sequence example 9 between the 6G RAN node and XPF (XX NF) related to operation example 2. Figure 20 shows sequence example 10 between the 6G RAN node and XPF (XX NF) related to operation example 2. Figure 21 shows sequence example 11 between a 6G RAN node and XPF (XX NF) related to operation example 2. Figure 22 shows sequence example 12 between a 6G RAN node and XPF (XX NF) related to operation example 2. Figure 23 shows sequence example 1 between a 6G RAN node and XPF (XX NF) related to operation example 3.Figure 24 shows sequence example 2 between a 6G RAN node and XPF (XX NF) related to operation example 3. Figure 25 shows sequence example 3 between a 6G RAN node and XPF (XX NF) related to operation example 3. Figure 26 shows sequence example 4 between a 6G RAN node and XPF (XX NF) related to operation example 3. Figure 27 shows sequence example 5 between a 6G RAN node and XPF (XX NF) related to operation example 3. Figure 28 shows sequence example 6 between a 6G RAN node and XPF (XX NF) related to operation example 3. Figure 29 shows an example of the hardware configuration of XPF50, UPF60, AMF70, gNB100 and UE200. Figure 30 shows an example of the configuration of vehicle 2001.

[0012] The embodiments will be described below with reference to the drawings. Note that identical or similar reference numerals are used to denote the same functions and components, and their descriptions will be omitted as appropriate.

[0013] (1) Overall schematic diagram 1 of the wireless communication system is an overall schematic diagram of the wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system that conforms to a method called Beyond 5G, 5G Evolution, or 6G (hereinafter referred to as 6G), and includes a Radio Access Network 20 (hereinafter referred to as 6G-RAN20) and a terminal 200 (hereinafter referred to as UE200, User Equipment, UE). Note that the wireless communication system 10 may also be a wireless communication system that conforms to 5G New Radio (NR).

[0014] 6G-RAN20 includes a wireless base station 100 (hereinafter referred to as gNB100). Note that gNB may also be simply called Node B, and the specific configuration of the wireless communication system 10, including the number of gNBs and UEs, is not limited to the example shown in Figure 1.

[0015] The gNB100 is a 6G-compliant wireless base station that performs 6G-compliant wireless communication with the UE200. The gNB100 and UE200 can support Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional antenna beam by controlling the radio signals transmitted from multiple antenna elements; carrier aggregation (CA), which uses multiple component carriers (CCs) bundled together; and dual connectivity (DC), which enables simultaneous communication between the UE and two or more RAN Nodes.

[0016] The gNB100 may also consist of a CU (Central Unit, first device) and a DU (Distributed Unit, second device), and the DU may be separated from the CU and installed in a geographically different location (CU-DU split). One or more DUs may be connected to the CU. In this embodiment, the gNB100 may be called a RAN node (Radio Access Network node). The CU may be called a communication device or a central device, etc. The DU may be called a distributed device, etc. The RAN node may include nodes other than the CU / DU (for example, an RU (Radio Unit)).

[0017] gNB100 (gNB-CU) may be connected via the Xn interface, and CU and DU may be connected via the F1 interface. Furthermore, DUs may also be connected via the Xn interface.

[0018] Furthermore, in the wireless communication system 10, not only Layer 3 mobility control of the UE200 (which may also be called L3 Mobility) but also Layer 1 and / or Layer 2 mobility control (LTM: Lower Layer Triggered Mobility) may be applied. L3 Mobility may be interpreted as mobility control at the Radio Resource Control Layer (RRC). On the other hand, LTM may be interpreted as mobility control at the Physical Layer (PHY), Medium Access Control Layer (MAC), Radio Link Control Layer (RLC), and Packet Data Convergence Protocol Layer (PDCP).

[0019] In a broad sense, the mobility of the UE200 may refer to the ease of movement and maneuverability of the UE200, but in this embodiment, it may also refer to the minimization of call drop, radio link (including beam) failure, unnecessary handovers, ping-pong situations, etc.

[0020] 6G-RAN20 is actually connected to 6G-CN30, a core network conforming to 6G, which includes multiple radio access network nodes (RAN Nodes), specifically gNBs. Note that 6G-RAN20 and 6G-CN30 may simply be referred to as the "network." 6G-CN30 may include various network functions (NFs).

[0021] For example, 6G-CN30 may include X-plane Function 50 (a provisional name is acceptable, hereafter XPF50), User Plane Function 60 (hereafter UPF60), and Access and Mobility Management Function (AMF70), etc.

[0022] XPF50 may perform processing on an X-plane, which is separate from the user plane (U-plane) and control plane (C-plane). The X-plane is a provisional name and may also be called a data plane or service plane. Data not belonging to the U-plane or C-plane may be processed on the X-plane.

[0023] For example, X-plane may handle sensing data from sensors, AIML data related to artificial intelligence (AI) / machine learning (ML) models, positioning data related to the location information of the UE200, and energy-related data related to energy consumption within the mobile network (NES: Network Energy Saving). X-plane may be responsible for processing such data, including collection, storage, and computation.

[0024] UPF60 may perform processing on the U-plane. For example, UPF60 provides functions for relaying and terminating the U-plane of a PDU (Protocol Data Unit) session. AMF70 may perform processing on the C-plane. AMF70 provides access and mobility management functions for UE200. For example, AMF70 may manage UE (user) registration, UE network connectivity, UE mobility, and UE security. AMF may also be called CPF (Control Plane Function).

[0025] These NFs may also be referred to by names such as network devices, core network nodes, components, or entities. Furthermore, 6G-CN30 may include other NFs besides XPF50, UPF60, and AMF70. Examples of other NFs will be discussed later.

[0026] As described above, AIML may be applied in the 6G-RAN20 and / or 6G-CN30 of the wireless communication system 10. Specifically, a learning model (AI / ML Model) may be used to optimize the mobility or handover of the UE200 (which may be rephrased as transition, cell transition, cell selection, cell re-selection, etc.).

[0027] The AI / ML Model may be expressed using other terms that mean AI or ML, such as an artificial intelligence (AI) model or a machine learning (ML) model. In the wireless communication system 10, such an AI / ML Model can be used to optimize the mobility or handover of the UE200. The AI / ML Model may be located on the network side, on the gNB100 (and may be called the NW-side model), or on the UE200 (and may be called the UE-side model).

[0028] In this embodiment, the channel includes a control channel and a data channel. The control channel includes PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), PRACH (Physical Random Access Channel), and PBCH (Physical Broadcast Channel), among others.

[0029] Furthermore, data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel), among others.

[0030] Reference signals may include Demodulation Reference Signal (DMRS), Sounding Reference Signal (SRS), Phase Tracking Reference Signal (PTRS), and Channel State Information-Reference Signal (CSI-RS), while signals may include channels and reference signals. Data may also refer to data transmitted via a data channel, and such data may include user data transmitted and received via a U-plane.

[0031] (2) Example of Core Network Configuration Figure 2 shows Example 1 of 6G-CN30 configuration. As shown in Figure 2 and as described above, 6G-CN30 may include XPF50, UPF60 and AMF70. 6G-CN30 may also include other NFs such as Session Management Function (SMF) which provides session management functionality, Location Management Function (LMF) which provides UE location information management functionality, Network Repository Function (NRF) which provides network service registration and management functionality, Policy Control Function (PCF) which provides policy and billing control functionality for user sessions, Unified Data Management (UDM) which provides user data management functionality, UE radio Capability Management Function (UCMF) which provides content management functionality, Network Data Analytics Function (NWDAF) which provides core network data analysis functionality, and Network Exposure Function (NEF) which provides network function exposure and management functionality.

[0032] XPF50 may include NFs that manage AIML data, sensing (ISAC: Integrated Sensing and Communication), IoT (Internet of Things), location services, and energy consumption. For IoT, for example, UEs mounted on UAVs (Unmanned Aerial Vehicles) may be targeted. For location services, similar functions to those of the LMF described above may be provided. Note that XPF50 may include other NFs besides those mentioned above, and some of the NFs mentioned above do not necessarily have to be included.

[0033] As mentioned above, XPF50 may provide the functions necessary for processing in the X-plane, but the data processed in the X-plane may be different from user data processed in the U-plane, and also different from essential control data such as signaling or communication control. Furthermore, from this perspective, the size of the data processed in the X-plane may be larger than the size of the data processed in the C-plane.

[0034] In the configuration example shown in Figure 2, an interface (for convenience, referred to as the XX interface (tentative name)) may be configured to directly connect the 6G RAN node (gNB100) and the XPF50 (X-plane). The XX interface may be connected to each NF (service) that provides the XPF50. In this way, the 6G RAN node may be connected to an X-plane based on the Service Based Architecture (SBA). In addition, the UPF60 may be connected to an external data network (DN).

[0035] Figure 3 shows Configuration Example 2 of 6G-CN30. Compared with Configuration Example 1 shown in Figure 2, Configuration Example 2 may include a new NF (referred to here as "XX NF" for convenience) between the 6G RAN node and the XPF50.

[0036] XX NF can connect to each NF that provides XPF50. A 6G RAN node may communicate with each NF that provides XPF50 via XX NF. An XX interface may be configured between the 6G RAN node and XX NF. XX NF may be interpreted as one of the NFs that provide XPF50, or as a separate, independent NF. XX NF may connect to the 6G RAN node as a proxy for the NF that provides XPF50, and in this respect, XX NF may be called a proxy network device (Proxy).

[0037] XX NF may be responsible for managing the UE200's identification information (UE ID), the UE200's context, and the security information (security key) and security context for the UE200. While these management functions are primarily provided by AMF70, XX NF may also assume these functions. Alternatively, XX NF may take over these management functions from AMF70.

[0038] The UE200 context may include, for example, location, authentication status, connection status, and network settings. The security context may include, for example, authentication information, security key, session key, and other security parameters. The XX NF may also exchange the UE ID, UE context, security key, and security context with the AMF70.

[0039] (3) Functional Block Configuration of the Wireless Communication System Next, the functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configurations of XPF50, AMF70, and gNB100 will be described. Figure 4 is a functional block configuration diagram of XPF50. Figure 5 is a functional block configuration diagram of AMF70. Figure 6 is a functional block configuration diagram of gNB100.

[0040] Please note that Figures 4 to 6 show only the main functional blocks relevant to the description of the embodiment, and the device has other functional blocks (e.g., a power supply unit). Also, Figures 4 to 6 show the functional block configuration of the device; please refer to Figure 29 for the hardware configuration.

[0041] (3.1) XPF50 As shown in Figure 4, the XPF50 comprises a network interface unit 51, an X-plane processing unit 53, and a control unit 55. The XPF50 may include multiple network functions (NFs) as described above, but each NF may comprise the functional block, or the entire XPF including the multiple NFs may comprise the functional block.

[0042] The network IF unit 51 provides a network interface (IF) with a 6G RAN node (gNB100). Specifically, the network IF unit 51 may provide an XX interface connected to the 6G RAN node (in the case of Configuration Example 1 shown in FIG. 2). The XX interface connected to the 6G RAN node may have the same specifications as, for example, the NG interface.

[0043] Further, the network IF unit 51 may provide a network IF with an XX NF (in the case of Configuration Example 2 shown in FIG. 3). For example, the network IF unit 51 may provide a network IF similar to the network IF connecting the NFs included in the XPF50 for the XX NF.

[0044] The X-plane processing unit 53 executes processing in the X-plane. Specifically, the X-plane processing unit 53 may transmit and receive X-plane data via an XX interface connected to a 6G RAN node (radio access network node).

[0045] As described above, in the X-plane, data not belonging to the U-plane and the C-plane may be the target of processing. The X-plane may be called a separate plane provided separately from the U-plane and the C-plane.

[0046] The control unit 55 controls each functional block constituting the XPF50. In the present embodiment, the control unit 55 may control network functions (NFs) in the X-plane.

[0047] Specifically, the control unit 55 may control at least any one of the NFs included in the XPF50. For example, the control unit 55 may control the transmission and reception of X-plane data via an XX interface.

[0048] Further, when an XX NF (see FIG. 3) is provided, the control unit 55 may control the transmission and reception of X-plane data between the XPF50 and the XX NF.

[0049] (3.2) AMF70 As shown in Figure 5, the AMF70 comprises a network IF unit 71, a C-plane processing unit 73, a security information management unit 75, and a control unit 77.

[0050] The network interface unit 71 provides a network interface (IF) to the 6G RAN node (gNB100). For example, the network interface unit 71 may provide an NG interface as the network interface to the 6G RAN node.

[0051] The C-plane processing unit 73 executes processing on the C-plane. Specifically, the C-plane processing unit 73 may execute processing related to signaling and control messages. For example, the C-plane processing unit 73 may execute processing related to connecting or disconnecting the UE200 from the network, authentication of the UE200, location management of the UE200, and session management with the UE200.

[0052] Furthermore, authorization can be defined as verifying the UE200 (the user), while authentication can be defined as granting legitimate authority to the UE200 (the user). In this context, authentication may also be interpreted as including authorization.

[0053] The security information management unit 75 manages the security information of UE200. Specifically, the security information management unit 75 may manage security information (security key) and security information (security context) for UE200.

[0054] The security information management unit 75 may transmit the security information to other network devices in X-plane, specifically to XPF 50. In this embodiment, the security information management unit 75 may constitute a transmission unit.

[0055] Furthermore, the security information management unit 75 may transmit security information to multiple other network devices in X-plane, specifically to XX NFs (proxy network devices) connected to XPF50 (the NF providing XPF50).

[0056] A security key is, for example, any of the keys in the key hierarchy defined in 3GPP TS33.501 Chapter 6.2.1 (e.g., K, CK (Cipher Key), IK (Integrity Key), K AMF , K N3IWF , K gNB ) may mean the following. Furthermore, the security context may include authentication information, key information (security key), session key, and other security parameters.

[0057] The security information management unit 75 may transmit the terminal context (UE context) containing the security information to the XPF 50 (the NF providing it). The UE context may include the UE's location, authentication status, connection status, and network settings, as described above.

[0058] The control unit 77 controls each functional block that constitutes the AMF 70. In this embodiment, the control unit 77 may control the issuance of the security information described above. Specifically, the control unit 77 may issue security information that includes at least a security key used for communication between the UE200 and the 6G RAN node (gNB100) or XPF50. More specifically, the control unit 77 may control the security information management unit 75 and issue security information used for communication with the UE200.

[0059] Furthermore, the control unit 77 may grant access only to UEs that have completed registration or authentication by AMF70. Specifically, the control unit 77 may grant access to XPF50 or XX NF only to UEs that have been registered and / or authorized by AMF70.

[0060] (3.3) gNB100 As shown in Figure 6, the gNB100 comprises a wireless communication unit 110, a network IF unit 120, a C / U / X-plane processing unit 130, and a control unit 140.

[0061] The wireless communication unit 110 transmits a downlink signal (DL signal) in accordance with 6G to the UE200. The wireless communication unit 110 also receives an uplink signal (UL signal) in accordance with 6G from the UE200.

[0062] The network IF unit 120 provides a network interface (IF) with the 6G-CN30. For example, the network IF unit 120 may provide an NG interface as a network IF with the NFs (excluding the XPF50) included in the 6G-CN30. Alternatively, the network IF unit 120 may provide an XX interface connected to the XPF50 (in the case of Configuration Example 1 shown in Figure 2). Or, the network IF unit 120 may provide an XX interface connected to XX NFs (in the case of Configuration Example 2 shown in Figure 3).

[0063] The C / U / X-plane processing unit 130 may perform processing in the C-plane, U-plane, and X-plane. Specifically, the C / U / X-plane processing unit 130 may perform signaling and control message management, etc., in accordance with the control unit 140. The C / U / X-plane processing unit 130 may perform sending and receiving user data, etc., in accordance with the control unit 140.

[0064] Furthermore, the C / U / X-plane processing unit 130 may send and receive X-plane data via the XX interface connected to the XPF50, which provides network functionality (NF) in the X-plane.

[0065] For example, the C / U / X-plane processing unit 130 may perform actions such as establishing the XX interface (which may be called setup), resetting and notifying errors, updating RAN settings, updating NF settings, notifying NF status, and notifying network overload status via the XX interface.

[0066] Furthermore, the C / U / X-plane processing unit 130 may perform actions such as setting up (which may be called setup), releasing, modifying, and updating the UE context via the XX interface.

[0067] The control unit 140 controls each functional block that constitutes the gNB100. In this embodiment, the control unit 140 may perform data processing in the C-plane, U-plane, and X-plane. Specifically, the control unit 140 may control the C / U / X-plane processing unit 130 and perform processing in each plane.

[0068] (4) Operation of the Wireless Communication System Next, the operation of the wireless communication system 10 will be described. Specifically, the operation related to ensuring security in communication with the UE on the X-plane, which is provided separately from the U-plane and C-plane, will be described.

[0069] In this embodiment, as in the conventional system, the AMF70 may centrally manage security information, such as the issuance of security keys applied to communication with the UE200. On the other hand, the XPF50 may also communicate directly with the UE200 or gNB100, not just the AMF70 and gNB100. In this case, ensuring security when performing such direct communication becomes an issue.

[0070] Specifically, the issues include providing a security key used for communication between XPF50 (the NF providing it) and the UE, and ensuring communication between XPF50 (the NF providing it) and registered and / or authorized / authenticated UEs. The following describes an example of an operation that can resolve these issues.

[0071] Furthermore, the technical challenges that can be addressed by the following examples of operation are not limited to those challenges, and other technical challenges not mentioned can be clearly understood by a person with ordinary skill in the art from the description of this embodiment.

[0072] (4.1) Example of operation 1 As described above, AMF may issue a security key and / or security context used for communication between XPF (the NF providing it) and the UE.

[0073] Figure 7 shows an example sequence for establishing security between the AMF and the UE. Specifically, Figure 7 shows an example of the security mode command procedure in the Non-Access Layer (NAS) as defined in 3GPP TS33.501 Chapter 6.7.2.

[0074] As shown in Figure 7, the AMF may initiate integrity protection and send a NAS Security Mode Command to the UE. The NAS Security Mode Command (SMC) may include a security key, encryption algorithm, integrity algorithm, etc.

[0075] The UE may verify the integrity of the NAS SMC received from the AMF and perform encryption and integrity protection of the UL and DL. Upon receiving "NAS Security Mode Complete" from the UE, the AMF may begin encrypting the DL. In this way, security is ensured between the AMF and the UE, and similar procedures may be used to ensure security in communication between the XPF and the UE (or gNB).

[0076] Figure 8 shows example sequence 1 between AMF and XPF (XX NF) related to operation example 1. As shown in Figure 8, AMF may notify XPF (each NF providing it, hereinafter the same) or XX NF (when the configuration example in Figure 3 is applied) of the UE context of the UE under AMF. The notification content may include at least one of the following: UE ID, UE context associated with the UE ID, and UE context ID that identifies the UE context.

[0077] Furthermore, AMF may notify XPF of the security key and / or security context of the UE under its control. The notification may include the UE ID, the security key or security context associated with the UE ID, and the security context ID that identifies the security context.

[0078] Figure 9 shows sequence example 2 of AMF and XPF (XX NF) related to operation example 1. Figure 10 shows sequence example 3 of AMF and XPF (XX NF) related to operation example 1.

[0079] As shown in Figure 9, AMF may send the UE ID, UE context, temporary ID or security token of the UE to XPF (XX NF). Here, the information to be sent may be limited to the UE ID, UE context, temporary ID or token of the UE for which registration, authentication, or authorization processing has been completed.

[0080] Alternatively, as shown in Figure 10, AMF may send the UE ID, UE context, and the UE's temporary ID or token to XPF (XX NF) (registration, authentication, or authorization is not required). Similarly, the UE may also send the UE ID, UE context, and the UE's temporary ID or token to XPF (XX NF) (registration, authentication, or authorization is not required).

[0081] XPF (XX NF) may compare the information sent from AMF with the information sent from UE and accept it if they match. On the other hand, if they do not match, XPF (XX NF) may not accept or use the UE ID, UE context, UE temporary ID, or token.

[0082] (4.2) Operation Example 2 This operation example describes the sequence on the XX interface that directly connects the 6G RAN node (gNB) and the XPF (or XX NF).

[0083] Figure 11 shows example sequence 1 of the interaction between a 6G RAN node and XPF (XX NF) related to operation example 2. As shown in Figure 11, XPF (XX NF) may send an XX interface setup request to the 6G RAN node. The 6G RAN node may return an XX interface setup response in response to the XX interface setup request. The XX interface setup request may be used to establish connectivity on the interface between network devices (elements), similar to the protocol on the NG interface (NGAP) specified in 3GPP TS 38.413.

[0084] Figure 12 shows example sequence 2 between a 6G RAN node and XPF (XX NF) related to operation example 2. As shown in Figure 12, XPF (XX NF) may send XX interface setup failure to the 6G RAN node. XX interface setup failure may be sent when the connection on that interface fails. XX interface setup failure may include the reason for the failure (e.g., unsupported PLMN or slice).

[0085] Figure 13 shows example sequence 3 of the interaction between the 6G RAN node and XPF (XX NF) related to operation example 2. As shown in Figure 13, the 6G RAN node may send a RAN configuration update to XPF (XX NF) via the XX interface. XPF (XX NF) may return a RAN configuration update Ack in response to the RAN configuration update. The RAN configuration update may be performed to change the settings or parameters of the 6G-RAN20.

[0086] Figure 14 shows example sequence 4 between the 6G RAN node and XPF (XX NF) related to operation example 2. As shown in Figure 14, XPF (XX NF) may send a RAN configuration update failure to the 6G RAN node. A RAN configuration update failure may be sent when the setting or parameter change of 6G-RAN20 fails.

[0087] Figure 15 shows example sequence 5 between a 6G RAN node and XPF (XX NF) related to operation example 2. As shown in Figure 15, XPF (XX NF) may send an XPF / XX NF configuration update to the 6G RAN node. The 6G RAN node may return an XPF / XX NF configuration update Ack in response to the XPF / XX NF configuration update. The XPF / XX NF configuration update may be performed to change the settings or parameters of XPF (XX NF).

[0088] Figure 16 shows example sequence 6 between a 6G RAN node and XPF (XX NF) related to operation example 2. As shown in Figure 16, XPF (XX NF) may send an XPF / XX NF configuration update failure to the 6G RAN node. An XPF / XX NF configuration update failure may be sent when the XPF (XX NF) configuration or parameter change fails.

[0089] Figure 17 shows example sequence 7 between a 6G RAN node and an XPF (XX NF) related to operation example 2. As shown in Figure 17, the XPF (XX NF) may send an XPF / XX NF status indication to the 6G RAN node. The XPF / XX NF status indication may be used to notify the current status of the XPF (XX NF).

[0090] Figure 18 shows example sequence 8 between a 6G RAN node and an XPF (XX NF) related to operation example 2. As shown in Figure 18, the XPF (XX NF) may send an XPF / XX NF reset to the 6G RAN node. The 6G RAN node may send back an XPF / XX NF reset Ack in response to the XPF / XX NF reset. The XPF / XX NF reset may be used to reset (release) the connection between the 6G RAN node and the XPF (XX NF).

[0091] Figure 19 shows example sequence 9 between a 6G RAN node and XPF (XX NF) related to operation example 2. As shown in Figure 19, the 6G RAN node may also send XPF / XX NF reset to XPF (XX NF). In response to XPF / XX NF reset, XPF (XX NF) may send back an XPF / XX NF reset Ack.

[0092] Figure 20 shows a sequence example 10 between a 6G RAN node and an XPF (XX NF) related to operation example 2. As shown in Figure 20, the 6G RAN node and the XPF (XX NF) may exchange error indications. Error indications may be used to notify each other that an error has occurred between the devices.

[0093] Figure 21 shows an example sequence 11 between a 6G RAN node and an XPF (XX NF) related to Operation Example 2. As shown in Figure 21, the XPF (XX NF) may send an Overload start to the 6G RAN node. The Overload start may be used to notify the XPF (XX NF) that it is in an overload state.

[0094] Figure 22 shows a sequence example 12 between a 6G RAN node and an XPF (XX NF) related to operation example 2. As shown in Figure 22, the XPF (XX NF) may send an Overload stop to the 6G RAN node. The Overload stop may be used to notify the XPF (XX NF) that it has recovered from an overload condition.

[0095] (4.3) Operation Example 3 In this operation example, as in Operation Example 2, we will describe the sequence on the XX interface that directly connects the 6G RAN node (gNB) and XPF (or XX NF). This operation example will describe the sequence related to UE context management.

[0096] Figure 23 shows example sequence 1 between a 6G RAN node and XPF (XX NF) related to operation example 3. As shown in Figure 23, XPF (XX NF) may send an Initial context setup request to the 6G RAN node. The 6G RAN node may return an Initial context setup response in response to the Initial context setup request. The Initial context setup request may be used to collect and construct the information necessary for the network to set up the initial context of the UE, similar to the protocol on the NG interface (NGAP) specified in 3GPP TS 38.413.

[0097] Figure 24 shows example sequence 2 between a 6G RAN node and XPF (XX NF) related to operation example 3. As shown in Figure 24, the 6G RAN node may send an Initial context setup failure to XPF (XX NF). Initial context setup failure may mean an error that occurs when the network is unable to set the initial context of the UE.

[0098] Figure 25 shows example sequence 3 between a 6G RAN node and XPF (XX NF) related to operation example 3. As shown in Figure 25, XPF (XX NF) may send a UE context release command to the 6G RAN node. The 6G RAN node may return a UE context release complete in response to the UE context release command. The UE context release command may be used to instruct the network to release the connection context to the UE. A UE context release request may also be used.

[0099] Figure 26 shows example sequence 4 between a 6G RAN node and XPF (XX NF) related to operation example 3. As shown in Figure 26, XPF (XX NF) may send a UE context modification request to the 6G RAN node. The 6G RAN node may send a UE context modification response in response to the UE context modification request. The UE context modification request may be used by the network to change the existing context of the UE.

[0100] Figure 27 shows example sequence 5 between a 6G RAN node and XPF (XX NF) related to operation example 3. As shown in Figure 27, the 6G RAN node may send a UE context modification failure to XPF (XX NF). A UE context modification failure may refer to an error that occurs when the network attempts to change the context of the UE.

[0101] Figure 28 shows example sequence 6 between a 6G RAN node and XPF (XX NF) related to operation example 3. As shown in Figure 28, the 6G RAN node may send an Initial UE message to XPF (XX NF). An Initial UE message is a message sent when a UE attempts to connect to the network for the first time, and may provide initial information for establishing a session with the network.

[0102] (4.4) Other examples of operation In order to prevent unauthorized UEs that have not been registered, authenticated and / or authorized by the network from accessing each NF (XPF) or XX NF (hereinafter referred to as XPF (XX NF)) that provides X-plane, the AMF may allow only registered / authorized / authenticated UEs to access the XPF (XX NF).

[0103] To implement these restrictions, as shown in Figure 10, AMF may notify XPF (XX NF) of the UE ID, UE context, temporary ID, or token of UEs that have already been registered / authorized / authenticated. Alternatively, the Initial UE message sent from the UE or 6G RAN node to XPF (XX NF) may include the UE ID, UE context, temporary ID, or token of the device (UE).

[0104] XPF (XX NF) may compare the UE ID, UE context, temporary ID, or token received from AMF with the UE ID, UE context, temporary ID, or token received from the UE, and only accept the UE and grant it access to the network if the comparison results match. When an access request (e.g., Initial UE message) is sent from a UE or 6G RAN node to XPF (XX NF), XPF (XX NF) may also check with AMF whether the UE has been registered / authorized / authenticated. XPF (XX NF) may only accept the UE if AMF responds that it has been registered / authorized / authenticated.

[0105] Alternatively, a common ID (TMSI (Temporary Mobile Subscriber Identity)) may be created to manage UEs between AMF, XPF (XX NF), UE, and 6G RAN nodes. Or, existing UE IDs (e.g., 5G-GUTI (Global Unique Temporary ID), S (Serving)-TMSI, TMSI) may be reused.

[0106] As illustrated by the operational example above, AMF can issue a security context containing a security key for the UE and provide the issued security information to XPF (or XX NF). Therefore, even if a new X-plane other than U-plane and C-plane is introduced, the security of communication between the UE and XPF (XX NF) can be reliably ensured.

[0107] Furthermore, in this embodiment, AMF can also share the UE context with XPF (XX NF). This allows for quick and easy configuration of communication between the UE and XPF (XX NF) while ensuring the security of such communication. In addition, AMF can also ensure that only UEs that have been registered / authorized / authenticated can access XPF (XX NF). This further enhances the security of such communication.

[0108] (5) Other Embodiments Although embodiments have been described above, it will be obvious to those skilled in the art that various modifications and improvements are possible, and that the embodiments are not limited to those described above.

[0109] For example, in the embodiment described above, the AMF70 issued security information and provided it to the XPF50, but another NF (e.g., SMF) may issue and provide the security information to the XPF50.

[0110] In the above description, configure, activate, update, indicate, enable, specify, and select may be interpreted as interchangeable. Similarly, link, associate, correspond, and map may be interpreted as interchangeable, and allocate, assign, monitor, and map may also be interpreted as interchangeable.

[0111] Furthermore, "specific," "dedicated," "UE specific," and "UE individual" may be interpreted interchangeably. Similarly, "common," "shared," "group-common," "UE common," and "UE shared" may be interpreted interchangeably.

[0112] In this disclosure, terms such as “precoding,” “precoder,” “weight (precoding weight),” “quasi-co-location (QCL),” “transmission configuration indication state (TCI state),” “spatial relation,” “spatial domain filter,” “transmit power,” “phase rotation,” “antenna port,” “antenna port group,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “resource group,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” and “panel” may be used interchangeably.

[0113] Furthermore, the block diagrams (Figures 4 to 6) used in the description of the embodiments above show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Moreover, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

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

[0115] Furthermore, the XPF50, UPF60, AMF70, gNB100, and UE200 (the devices) described above may function as computers that process the wireless communication methods of this disclosure. Figure 29 shows an example of the hardware configuration of the device. As shown in Figure 29, the device may be configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, and bus 1007.

[0116] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the device may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.

[0117] Each functional block of the device (see Figures 4 to 6) is implemented by any hardware element of the computer device, or a combination of such hardware elements.

[0118] Furthermore, each function in the device is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of the reading and writing of data in the memory 1002 and storage 1003.

[0119] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, and so on.

[0120] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. Moreover, the above-mentioned various processes may be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.

[0121] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store a program (program code), software module, etc., that can execute a method according to one embodiment of this disclosure.

[0122] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., Compact Disc, Digital Multipurpose Disc, Blu-ray® Disc), a smart card, flash memory (e.g., a card, stick, key drive), a floppy® disk, a magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The recording medium described above may also be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0123] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc.

[0124] The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD).

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

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

[0127] Furthermore, the device may include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field-programmable gate array (FPGA), and some or all of each functional block may be implemented by such hardware. For example, processor 1001 may be implemented using at least one of these hardware components.

[0128] Furthermore, notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0129] Each aspect / embodiment described herein may be applied to at least one of the following: Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (where x is, for example, an integer or decimal), Future Radio Access (FRA), New Radio (NR), W-CDMA®, GSM®, CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0130] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be reordered, provided they do not contradict each other. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

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

[0132] Information and signals (such as data) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.

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

[0134] 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 numerical comparison (for example, a comparison with a predetermined value).

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

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

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

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

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

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

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

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

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

[0144] A base station can house one or more (e.g., three) cells (also called sectors). If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0145] The terms "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base stations and base station subsystems that provide communication services in this coverage.

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

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

[0148] 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 appropriate term.

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

[0150] Furthermore, the term "base station" in this disclosure may be interpreted as "mobile station" (user terminal, hereinafter the same). For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). In this case, the mobile station may have the functions that a base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc. may be interpreted as side channel (or side link).

[0151] Similarly, the term "mobile station" in this disclosure may be interpreted as "base station." In this case, the base station may be configured to have the functions that a mobile station has.

[0152] A wireless frame may consist of one or more frames in the time domain. Each of these one or more frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0153] Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0154] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). A slot may also be a time unit based on neurology.

[0155] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called PDSCH (or PUSCH) mapping type B.

[0156] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0157] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0158] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0159] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Note that when a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0160] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0161] A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0162] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0163] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0164] Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0165] One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0166] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0167] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a given BWP.

[0168] A BWP may include BWPs for UL (UL BWP) and BWPs for DL ​​(DL BWP). One or more BWPs may be set within a single carrier for a UE.

[0169] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0170] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

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

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

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

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

[0175] Any reference to elements using designations such as “First,” “Second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the First and Second elements do not imply that only two elements may be employed therein, or that the First element must precede the Second element in any way.

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

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

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

[0179] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0180] Figure 30 shows an example of the configuration of vehicle 2001. As shown in Figure 30, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right 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.

[0181] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and rear wheels based on the operation of the steering wheel operated by the user. The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2027 provided in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

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

[0183] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of Vehicle 1.

[0184] Information Services Unit 2012 may include input devices that accept input from external sources (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) and output devices that perform output to external sources (e.g., displays, speakers, LED lamps, touch panels, etc.).

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

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

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

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

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

[0190] This application is based on Japanese Patent Application No. 2025-019436, filed on February 7, 2025. All of its contents are included herein.

[0191] 10 Wireless communication system 20 6G-RAN 30 6G-CN 50 XPF 51 Network IF unit 53 X-plane processing unit 55 Control unit 60 UPF 70 AMF 71 Network IF unit 73 C-plane processing unit 75 Security information management unit 77 Control unit 100 gNB 110 Wireless communication unit 120 Network IF unit 130 C / U / X-plane processing unit 140 Control unit 200 UE 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic Control Unit 2012 Information Services Unit 2013 Communication Module 2021 Current Sensor 2022 Rotation Speed ​​Sensor 2023 Pneumatic 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

Claims

A control unit that issues security information including at least a security key used for communication between a terminal and a wireless access network node or other network device, A network device comprising a transmission unit that transmits the security information to other network devices in a separate plane, which is provided separately from the user plane and the control plane. 　 A control unit that issues security information including at least a security key used for communication between a terminal and a wireless access network node or other network device, A network device comprising a transmission unit that transmits the security information to a proxy network device connected to a plurality of other network devices, in a separate plane provided in addition to the user plane and the control plane. 　 The network device according to claim 1 or 2, wherein the transmitting unit transmits the context of the terminal, including the security information, to the other network device. 　 The network device according to claim 1 or 2, wherein the control unit permits access only to the terminals that have been registered or authenticated by the network device. 　　 A step of issuing security information which includes at least a security key used for communication between a terminal and a wireless access network node or other network device, A communication control method in a network device, comprising the step of transmitting the security information to another network device in a separate plane provided separately from the user plane and the control plane. 　 A step of issuing security information which includes at least a security key used for communication between a terminal and a wireless access network node or other network device, A communication control method in a network device, comprising the step of transmitting the security information to a proxy network device that connects to a plurality of other network devices in a separate plane provided separately from the user plane and the control plane.

Images