Network node and communication method

Abstract

A network node that connects to another network node via a reference point, the network node comprising: a reception unit that receives a first control signal including information indicating the purpose of a connection requested by the other network node; a control unit that determines whether the connection for the purpose is possible; and a transmission unit that transmits, to the other network node, a second control signal including information indicating the result of the determination.

Description

[Technical field]

[0001] The present disclosure relates to a network node and a communication method. [Background technology]

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

[0003] For NR, network architectures under consideration include 5GC (5G Core Network), which corresponds to EPC (Evolved Packet Core), the core network in the network architecture of LTE (Long Term Evolution), and NG-RAN (Next Generation - Radio Access Network), which corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), the RAN (Radio Access Network) in the network architecture of LTE.

[0004] In the 5GC network architecture, N32 is defined as a reference point at the connection point between a user equipment (UE)'s home network (Home Public Land Mobile Network (HPLMN)) and the UE's visited network (Visited Public Land Mobile Network (VPLMN)) (see non-patent document 1).

[0005] The N32 interface can be logically considered as two different interfaces: -N32-c: A control plane interface between Security Edge Protection Proxies (SEPPs) to establish initial connections (handshake) and negotiate parameters to be applied to the actual N32 message transfer. -N32-f: A transfer interface between SEPPs used to transfer signals between service consumers and service producers after applying application-level security protection [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] 3GPP TS 23.501 V17.1.1 (2021-06) [Non-Patent Document 2] 3GPP TS 29.573 V17.1.0 (2021-06) Summary of the Invention

[0007] In Release 17, the Service Based Architecture (SBA) was standardized to enable the rapid and mutual addition of functions between the caller's SMSC (Short Message Service Centre) and the callee's SMSC in the 5G core network, and to develop a wide variety of services. This allows for interconnection in addition to roaming as a purpose of connection between operators.

[0008] Under the current regulations, the use of N32 is limited to roaming, so SEPP can determine whether or not N32 can be connected only based on the presence or absence of a roaming relationship.

[0009] On the other hand, in theory, N32 can be used for purposes other than roaming, such as Interconnect.

[0010] However, since there are currently no parameters that can be used to confirm the purpose, if N32 is used for purposes other than roaming, it becomes difficult for SEPP to determine whether N32 can be connected.

[0011] One aspect of the present disclosure provides a network node and a communication method that can appropriately determine whether or not an N32 can be connected, even when the N32 is used for multiple purposes.

[0012] A network node according to one embodiment of the present disclosure is a network node that connects to another network node via a reference point, and includes a receiving unit that receives a first control signal including information indicating a purpose of the connection requested by the other network node, a control unit that determines whether a connection for the purpose is possible, and a transmitting unit that transmits a second control signal including information indicating a result of the determination to the other network node.

[0013] A communication method according to one embodiment of the present disclosure is a communication method between a first network node and a second network node via a reference point, in which the first network node transmits a first control signal to the second network node, the first control signal including information indicating a purpose of a requested connection, the second network node determines whether a connection for the purpose is possible, and the second network node transmits a second control signal to the first network node, the second control signal including information indicating a result of the determination. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is a diagram for explaining an example of a communication system according to an embodiment of the present disclosure. [Diagram 2] FIG. 11 is a diagram for explaining another example of a communication system according to an embodiment of the present disclosure. [Diagram 3]1 is a sequence diagram for explaining a procedure of negotiation between SEPPs in a communication system according to an embodiment of the present disclosure. FIG. [Figure 4] A figure showing a definition of SecNegotiationReqData according to one embodiment of the present disclosure. [Diagram 5] A diagram showing a definition of SecNegotiationRspData in one embodiment of the present disclosure. [Figure 6] FIG. 11 is a diagram showing an example in which the use of N32 is defined in ENUM type according to an embodiment of the present disclosure. [Figure 7] A sequence diagram for explaining the procedure of signal transfer between an NF service consumer and an NF service producer according to one embodiment of the present disclosure. [Figure 8] FIG. 2 is a diagram illustrating an example of a functional configuration of a SEPP according to an embodiment of the present disclosure. [Figure 9] FIG. 2 is a diagram illustrating an example of a hardware configuration of a terminal, a base station, a data hub access support device, or another network node according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. Note that the embodiments described below are merely examples, and embodiments to which the present disclosure is applicable are not limited to the following embodiments.

[0016] In the operation of the wireless communication system according to the embodiment of the present disclosure, an existing technology may be used as appropriate. The existing technology may be, for example, the existing LTE or the existing 5G, but is not limited to the existing LTE or the existing 5G.

[0017] In addition, in the following explanation, we use node names, signal names, etc. currently described in the 5G specifications (or LTE specifications), but node names, signal names, etc. having similar functions may be called by different names.

[0018] For example, in the embodiment of the present disclosure described below, terms such as SS (Synchronization Signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical Broadcast Channel), PRACH (Physical Random Access Channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel) used in existing LTE may be used. In addition, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, NR-PDCCH, NR-PDSCH, NR-PUCCH, NR-PUSCH, and the like. However, even if a signal is used in NR, it is not necessarily specified as "NR-".

[0019] (System configuration example) Next, a communication system 1 according to an embodiment of the present disclosure will be described with reference to Fig. 1. Fig. 1 illustrates the configuration of a communication system in a roaming mode.

[0020] The communication system 1 is composed of, for example, UE 10 (which may be called User Equipment: (user) terminal), which is a communication terminal used by a user, and multiple network nodes 20, 30-1 to 30-12 (which may be called NFs (Network Functions)), 40. In the following, it is assumed that one network node corresponds to each function, but one network node may realize multiple functions, or multiple network nodes may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0021] The communication system 1 is a system included in the 5G network system, and is a system that provides a network service through data communication to the UE 10. The network service refers to a service that uses network resources, such as a communication service (such as a dedicated line service) or an application service (such as a service that uses a sensor device such as video distribution or an embedded device).

[0022] 1, it is assumed that UE 10 is in a roaming environment. UE 10 being in a roaming environment indicates a state in which UE 10 is accessing and communicating with VPLMN, which is a network in which UE 10 is present (visited network), different from HPLMN, which is a network (home network) of a service provider with which the user of UE 10 has a contract. In this embodiment, VPLMN is a first network, and HPLMN is a second network.

[0023] The VPLMN of the communication system 1 is composed of a UE 10, an (R)AN ((Radio) Access Network) 20, an AMF (Access and Mobility Management Function) 30-1, an SMF (Session Management function) 30-2, an NSSF (Network Slice Selection Function) 30-3, a NEF (Network Exposure Function) 30-4, an NRF (Network Repository Function) 30-5, a PCF (Policy Control Function) 30-8, an NSACF (Network Slice Admission Control Function) 30-10, a SEPP (Security Edge Protection Proxy) 30-12, and a UPF (User Plane Function) 40.

[0024] The HPLMN of the communication system 1 is composed of an SMF 30-2, an NSSF 30-3, an NEF 30-4, an NRF 30-5, a Unified Data Management (UDM) 30-6, an Authentication Server Function (AUSF) 30-7, a PCF 30-8, an Application Function (AF) 30-9, an NSACF 30-10, a Network Slice Specific Authentication and Authorization Function (NSSAAF) 30-11, a SEPP 30-12, and a UPF 40.

[0025] (R)AN20 is a network node having radio access functionality, and may be, for example, a gNB (next generation Node B) (which may also be referred to as a base station) 20.

[0026] The AMF 30-1 is a network node having functions such as a RAN interface termination, a NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management.

[0027] The SMF 30-2 is a network node having functions such as session management, allocation and management of UE IP (Internet Protocol) addresses, a Dynamic Host Configuration Protocol (DHCP) function, an Address Resolution Protocol (ARP) proxy, and a roaming function.

[0028] NSSF30-3 is a network node that has functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which the UE connects.

[0029] The NEF 30-4 is a network node that has the function of notifying other NFs of capabilities and events.

[0030] The NRF 30-5 is a network node that has the function of discovering NF instances that provide services.

[0031] The UDM 30-6 is a network node that manages subscriber data and authentication data, and is connected to a User Data Repository (UDR) that holds the data.

[0032] The AUSF 30-7 is a network node that authenticates the subscriber / UE 10 against the subscriber data held in the UDR.

[0033] The PCF 30-8 is a network node having a function of controlling the policy of the network.

[0034] The AF30-9 is a network node having a function of controlling the application server.

[0035] The NSACF30-10 is a network node that has the function of controlling the admission of network slices.

[0036] NSSAAF30-11 is a network node that has the function of controlling authentication and authorization of network slices.

[0037] The SEPP30-12 is a network node having a proxy that controls message filtering and policy restrictions in control plane exchanges between operators. The SEPP30-12 on the VPLMN side is described as vSEPP30-12v, and the SEPP30-12 on the HPLMN side is described as hSEPP30-12h. The vSEPP30-12v and hSEPP30-12h provide functions related to the security and integrity of messages (HTTP Request, HTTP Response, etc.) transmitted and received between the VPLMN and the HPLMN.

[0038] The UPF 40 is a network node having functions such as a Protocol Data Unit (PDU) session point for the outside, packet routing and forwarding, and user plane Quality of Service (QoS) handling.

[0039] N1, N2, N3, N4, and N9 are reference points between network nodes. N32 between the vSEPP30-12v and the hSEPP30-12h is a reference point at the connection point between the VPLMN and the HPLMN.

[0040] (R)AN20 is connected to UE10, AMF30-1 and UPF40.

[0041] In the VPLMN, the AMF 30-1, the SMF 30-2, the NSSF 30-3, the NEF 30-4, the NRF 30-5, the PCF 30-8, and the NSACF 30-10 are connected to each other via interfaces Namf, Nsmf, Nnssf, Nnef, Nnrf, Npcf, and Nsacf based on their respective services.

[0042] In the HPLMN, SMF30-2, NSSF30-3, NEF30-4, NRF30-5, UDM30-6, AUSF30-7, PCF30-8, AF30-9, NSACF30-10, and NSSAAF30-11 are connected to each other via interfaces Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, Naf, Nsacf, and Nnssaaf, respectively, based on their respective services.

[0043] vSEPP30-12v is connected to AMF30-1, SMF30-2, NSSF30-3, NEF30-4, NRF30-5, PCF30-8 and NSACF30-10 of VPLMN, and is connected to hSEPP30-12h via N32.

[0044] hSEPP30-12h is connected to SMF30-2, NSSF30-3, NEF30-4, NRF30-5, UDM30-6, AUSF30-7, PCF30-8, AF30-9, NSACF30-10, and NSSAAF30-11 of the HPLMN, and is connected to vSEPP30-12v via N32.

[0045] The UPF 40 on the VPLMN side is interconnected with the (R)AN 20, the SMF 30-2, and the UPF 40 on the HPLMN side. The UPF 40 in the HPLMN is interconnected with the SMF 30-2 and a DN (Data Network) 50.

[0046] The communications system in the Interconnect format has the configuration shown in Figure 2. In the case of Interconnect, the SEPP (cSEPP) on the consumer side (calling side) corresponds to the vSEPP30-12v in Roaming (Figure 1), and the SEPP (pSEPP) on the producer side (receiving side) corresponds to the rSEPP30-12r in Roaming (Figure 1).

[0047] (Initial connection established: N32-c) Next, a process of determining whether or not an initial connection can be established (handshake) of N32 in consideration of the purpose of the connection between operators according to this embodiment will be described with reference to FIG. 3 to FIG.

[0048] As shown in FIG. 3, negotiation between SEPPs is performed in the following steps.

[0049] (Step 1) The initiating SEPP30-12i sends an HTTP POST request including SecNegotiateReqData to the responding SEPP30-12r. The responding SEPP30-12r uses a determination process described below to determine whether the request is successful or unsuccessful, that is, whether an N32 connection can be established. In FIG. 3, the determination process performed by the responding SEPP30-12r is represented by ●.

[0050] (Step 2a) If the request is successful, the responding SEPP 30-12r sends a "200 OK" status code including SecNegotiateRspData to the initiating SEPP 30-12i.

[0051] (Step 2b) If the request fails, the responding SEPP 30-12r transmits a "4xx / 5xx" status code and ProblemDetails indicating the reason for the rejection to the initiating SEPP 30-12i.

[0052] Fig. 4 is a diagram showing the definition of the control signal SecNegotiationReqData, and Fig. 5 is a diagram showing the definition of the control signal SecNegotiationRsqData.

[0053] 4 is obtained by adding a new attribute, usagePurpose, to the definition of type SecNegotiationReqData described in Table 6.1.5.2.2-1 of Non-Patent Document 2. The initiating SEPP 30-12i specifies the purpose of the connection by usagePurpose.

[0054] 5 is obtained by adding a new attribute, usagePurpose, to the Definition of type SecNegotiationRspData described in Table 6.1.5.2.3-1 of Non-Patent Document 2. The responding SEPP 30-12r specifies the purpose of the approved connection by usagePurpose.

[0055] The use (purpose) of N32 may be defined in an ENUM type (enumeration type) table, as shown in FIG.

[0056] Connection uses (purposes) include Roaming, Interconnect, General (general inquiries, etc.), Roaming test, Interconnect test, General test, etc.

[0057] Roaming refers to the exchange of necessary signals between the VPLMN and the HPLMN, such as obtaining subscriber information, authentication, location registration, and establishing a session for communication via the home network.

[0058] Interconnect is the exchange of signals to provide services between users of different operators.

[0059] General refers to uses other than Roaming and Interconnect, such as access to the NRF for device discovery (NF Discovery) and status notifications from the NRF or other NF Producers.

[0060] The roaming test is an exchange of identification signals to test whether connection is possible or not before starting roaming.

[0061] An Interconnect test is an exchange of identification signals to test whether a connection is possible or not before starting an Interconnect.

[0062] The General test is an exchange of identification signals to test whether connection is possible or not before starting General.

[0063] The determination process of the responding SEPP 30-12r will be described below.

[0064] When the responding SEPP 30-12r receives an HTTP POST request including SecNegotiateReqData from the initiating SEPP 30-12i in step 1 of FIG. 3, the responding SEPP 30-12r determines the purpose requested by the initiating SEPP 30-12i based on usagePurpose of SecNegotiateReqData.

[0065] Then, the responding SEPP 30-12r determines whether or not a connection for the requested purpose is possible under the agreement (policy) between the carriers.

[0066] If the use is permitted under the agreement, the responding SEPP 30-12r specifies the use in the usagePurpose of the SecNegotiationRspData, and transmits a "200 OK" status code including SecNegotiateRspData to the initiating SEPP 30-12i (step 2a in FIG. 3).

[0067] On the other hand, if the use is not permitted under the agreement, the responding SEPP 30-12r transmits a "4xx / 5xx" status code and ProblemDetails indicating the reason for the refusal to the initiating SEPP 30-12i (step 2b in FIG. 3).

[0068] As described above, in this embodiment, a new attribute, usagePurpose, which clearly indicates the purpose is added to SecNegotiationReqData and SecNegotiationRsqData. Then, in establishing an initial connection, the initiating SEPP30-12i transmits SecNegotiationReqData including usagePurpose to the responding SEPP30-12r via N32. The responding SEPP30-12r determines whether or not a connection based on the purpose indicated by usagePurpose in SecNegotiationReqData is possible.

[0069] As described above, according to this embodiment, a parameter that can confirm the purpose is added to the control signal from the initiating SEPP30-12i, so that even when N32 is used for purposes other than roaming, the responding SEPP30-12r can appropriately determine whether or not N32 can be connected.

[0070] (Signal transmission: N32-f) Next, a process of determining whether or not a signal can be transferred between an NF service consumer and an NF service producer after an initial connection is established will be described with reference to FIG.

[0071] As shown in Figure 7, signal transfer between an NF service consumer that uses an NF service and an NF service producer that provides an NF service is performed in the following procedure.

[0072] (Step 1) The SEPP (c-SEPP) on the NF service consumer side and the SEPP (p-SEPP) on the NF service producer side negotiate security functions. The SEPP uses TLS (Transport Layer Security) as the security policy. A TLS connection is set up between the c-SEPP and the p-SEPP for N32-f transfer.

[0073] (Step 2) The NF service consumer forwards the Nnrf_NF Discovery request to the c-NRF.

[0074] (Step 3) c-NRF forwards the Nnrf_NF Discovery request to c-SEPP.

[0075] (Step 4) c-SEPP sets up a TLS tunnel with the authoritative server in p-SEPP.

[0076] (Step 5) c-SEPP sets the apiRoot of the Request URI to the apiRoot of p-SEPP, inserts the 3gpp-Sbi-Target-apiRoot header (Custom header) set in the apiRoot of p-NRF, and sends an Nnrf_NF Discovery request to p-SEPP.

[0077] (Step 6) The p-SEPP forwards the Nnrf_NF Discovery request to the p-NRF.

[0078] (Step 7) The p-NRF sends an Nnrf_NF Discovery response to the p-SEPP.

[0079] (Step 8) The p-SEPP forwards the Nnrf_NF Discovery response to the c-SEPP within the TLS tunnel.

[0080] (Step 9) c-SEPP forwards the Nnrf_NF Discovery response to c-NRF.

[0081] (Step 10) The c-NRF forwards the Nnrf_NF Discovery response to the NF service consumer.

[0082] (Step 11) The NF service consumer initiates an HTTP message using a URI with the "http" scheme and forwards the HTTP / 2 Service request to the c-SEPP.

[0083] (Step 12) c-SEPP forwards the HTTP / 2 Service request to p-SEPP within the TLS tunnel.

[0084] (Step 13) The p-SEPP forwards it to the NF service producer.

[0085] (Step 14) The NF service producer forwards the HTTP / 2 Service response to the p-SEPP.

[0086] (Step 15) p-SEPP forwards the HTTP / 2 Service response to c-SEPP within the TLS tunnel.

[0087] (Step 16) c-SEPP forwards the HTTP / 2 Service response to the NF service consumer.

[0088] In this embodiment, the NF service consumer sets a Custom header in at least one of an Nnrf_NF Discovery request and an HTTP / 2 Service request, which are signals addressed to other networks, and writes information indicating the purpose therein.

[0089] c-SEPP or p-SEPP judges whether the purpose written in the Nnrf_NF Discovery request or HTTP / 2 Service request (hereinafter referred to as "request purpose") is included in the purpose (purpose) of the N32 established in the initial connection, that is, the purpose for which a connection with the opposite operator is permitted (hereinafter referred to as "permitted purpose"). Note that in Figure 7, the judgment process performed by c-SEPP or p-SEPP is represented by ●.

[0090] If the requested usage is included in the permitted usages, c-SEPP or p-SEPP transfers the signal (Steps 6 and 13 in FIG. 7).

[0091] On the other hand, if the requested usage is not included in the permitted usages, c-SEPP or p-SEPP does not transfer the signal and returns an error response including information indicating that signal transfer is not possible to the NF service consumer.

[0092] As described above, in this embodiment, the NF service consumer writes the requested usage into at least one of the Nnrf_NF Discovery request and the HTTP / 2 Service request. Then, c-SEPP or p-SEPP determines whether the requested usage is included in the permitted usages.

[0093] As described above, according to this embodiment, since a parameter capable of confirming the usage is added to the control signal from the NF service consumer, even when N32 is used for usages other than roaming, SEPP can appropriately determine whether N32 can be connected.

[0094] In addition, by receiving an error response including information indicating that signal transfer is not possible, the NF service consumer can grasp the reason for the error, which cannot be determined only by the HTTP response code.

[0095] <Configuration of SEPP> FIG. 8 is a diagram showing an example of the functional configuration of SEPP30-12 according to an embodiment of the present disclosure. As shown in FIG. 8, SEPP30-12 includes a transmission unit 710, a reception unit 720, a setting unit 730, and a control unit 740. The functional configuration shown in FIG. 8 is merely an example. As long as the operations according to the embodiments of the present disclosure can be executed, the functional divisions and the names of the functional units may be any.

[0096] The transmitter 710 has a function of generating a signal to be transmitted and transmitting the generated signal to a network. The receiver 720 has a function of receiving various signals and acquiring, for example, information of a higher layer from the received signals.

[0097] The setting unit 730 stores preset information and setting information in a storage device (storage unit), and reads out the preset information and setting information from the storage device as necessary. The setting unit 730 may be included in the control unit 740.

[0098] The control unit 740 controls the entire SEPP 30-12. The functional units in the control unit 740 related to signal transmission may be included in the transmission unit 710, and the functional units in the control unit 740 related to signal reception may be included in the reception unit 720.

[0099] (Hardware configuration) The block diagrams 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. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.

[0100] Functions include, but are not limited to, judgment, determination, judgment, 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, allocation, mapping, assignment, etc. For example, a functional block (component) that performs the function of transmission is called a transmitting unit or a transmitter. In either case, as described above, there is no particular limitation on the method of realization.

[0101] For example, a base station, a terminal, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 9 is a diagram showing an example of a hardware configuration of a terminal, a base station, a data hub access support, and other network nodes according to an embodiment of the present disclosure. The above-mentioned terminal 10, base station 20, and other network nodes 30-1 to 30-12, 40 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0102] In the following description, the term "apparatus" may be replaced with circuit, device, unit, etc. The hardware configurations of the terminal 10, the base station 20, and the other network nodes 30-1 to 30-12, 40 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.

[0103] Each function in the terminal 10, the base station 20 and the other network nodes 30-1 to 30-12, 40 is realized by loading a specific software (program) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communications by the communication device 1004, and control at least one of reading and writing of data in the memory 1002 and the storage 1003.

[0104] The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with 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 740, etc. may be realized by the processor 1001.

[0105] Moreover, the processor 1001 reads out a program (program code), a software module, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to the read out programs. As the program, a program that causes a computer to execute at least a part of the operations described in the above-mentioned embodiment is used. For example, the control unit 740 may be realized by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be similarly realized. Although the above-mentioned various processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from a network via a telecommunication line.

[0106] The memory 1002 is a computer-readable recording medium, and may be configured by at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), a Random Access Memory (RAM), etc. The memory 1002 may be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), software modules, etc. that are executable to implement a wireless communication method according to an embodiment of the present disclosure.

[0107] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, 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, and the like. Storage 1003 may be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0108] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, 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., in order to realize at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-mentioned transmitting unit 710, receiving unit 720, etc. may be realized by the communication device 1004.

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

[0110] In addition, 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 may be configured using different buses between each device.

[0111] Furthermore, the terminal 10, the base station 20, and the other network nodes 30-1 to 30-12, 40 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), a field programmable gate array (FPGA), etc., 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.

[0112] (Information notification, signaling) 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. In addition, the RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0113] (Applicable system) Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other suitable systems, and next-generation systems extended based on these. In addition, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G, etc.) may be applied.

[0114] (Processing procedures, etc.) The order of the steps, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. 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.

[0115] (Base station operation) In the present disclosure, a specific operation performed by a base station may be performed by its upper node in some cases. 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 may be performed by at least one of the base station and other network nodes other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case in which there is one other network node other than the base station, it may also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0116] (Input / Output direction) Information, etc. (see the "Information, Signals" section) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input / output via multiple network nodes.

[0117] (Handling of input and output information, etc.) The input and output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added to. The output information may be deleted. The input information may be transmitted to another device.

[0118] (Judgment method) The determination may be based on a value represented by a single bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0119] (software) 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.

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

[0121] (Information, Signals) The information, signals, etc. described in this disclosure may be represented using any of a variety of 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 voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0122] In addition, the terms described in this disclosure and the 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). Also, a signal may be a message. Also, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0123] ("System", "Network") As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0124] (parameter, channel name) In addition, the information, parameters, etc. described in the present disclosure may be represented using absolute values, may be represented using relative values ​​from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by an index.

[0125] The names used for the above-mentioned parameters are not limiting in any way. Moreover, the formulas 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 limiting in any way.

[0126] (Base station (wireless base station)) In this disclosure, terms such as "base station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", "component carrier", etc. may be used interchangeably. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.

[0127] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire 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 term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or a base station subsystem that provides communication services in this coverage.

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

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

[0130] (Base station / Mobile station) 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 be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving body (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 include a device that does not necessarily move during communication operation. 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.

[0131] Furthermore, the base station in the present disclosure may be read as a user terminal. For example, each aspect / embodiment 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 a plurality of user terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 10 may be configured to have the functions of the base station 20 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, an uplink channel, a downlink channel, etc. may be read as a side channel.

[0132] Similarly, the terminal in the present disclosure may be interpreted as a base station. In this case, the base station 20 may be configured to have the functions of the terminal 10 described above.

[0133] (Meaning and interpretation of terms) 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, search, inquiry (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 a memory), and the like. In addition, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to be a "judgment" or "decision." In other words, "judgment" and "decision" can include considering some action to be a "judgment" or "decision." In addition, "judgment" can be interpreted as "assuming," "expecting," "considering," etc.

[0134] 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 at least one of one or more wires, cables, and 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.

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

[0136] (meaning "based on") 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."

[0137] ("First", "Second") Any reference to an element using a designation such as "first," "second," etc., 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 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 precede the second element in some way.

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

[0139] (Open format) 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." Further, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0140] (Time units such as TTI, frequency units such as RB, radio frame structure) A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed 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.

[0141] Numerology may be a communication parameter that applies to the transmission and / or reception of a signal or channel, such as SubCarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, a particular filtering operation performed by the transceiver in the frequency domain, a particular windowing operation performed by the transceiver in the time domain, etc.

[0142] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) in the time domain. A slot may be a time unit based on numerology.

[0143] A slot may include multiple minislots. Each minislot may be composed of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may be composed of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0144] A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit for transmitting a signal. The radio frame, the subframe, the slot, the minislot, and the symbol may each be referred to by a different name.

[0145] 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. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit expressing the TTI may be called a slot, a minislot, or the like, instead of a subframe.

[0146] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0147] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) in which a transport block, a code block, a code word, etc. are actually mapped may be shorter than the TTI.

[0148] In addition, when one slot or one minislot is called TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. Also, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled.

[0149] A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, etc.

[0150] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

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

[0152] In addition, the time domain of the RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. Each of one TTI, one subframe, etc. may be composed of one or more resource blocks.

[0153] Note that one or more RBs may be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0154] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0155] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a numerology on a carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0156] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0157] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be replaced with "BWP".

[0158] The above-mentioned structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio 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, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

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

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

[0161] (Variations of form, etc.) Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).

[0162] 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 in the present disclosure. 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. [Industrial Applicability]

[0163] One aspect of the present disclosure is useful for mobile communication systems. [Explanation of symbols]

[0164] 10UE 20(R)AN 30-12 SEPP 30-12v vSEPP 30-12h hSEPP 30-12i Starter SEPP 30-12r Responding SEPP 710 Transmitter 720 Receiving unit 730 Setting Department 740 Control Unit

Claims

1. A network node that connects to other network nodes via an N32 interface, the network node is a Responding Security Edge Protection Proxy (SEPP); the other network node is an Initiating SEPP; A receiving unit for receiving a request including information indicating a purpose of use of the N32 connection from the other network node; A control unit that determines whether the request is successful or unsuccessful; a sender for sending a response to the other network node if the request is successful, the response including information indicating the permitted use of the N32 connection; A network node comprising:

2. The purpose of using the N32 connection includes roaming and a roaming test performed before the start of the roaming. A network node according to claim 1.

3. A network node that connects to other network nodes via an N32 interface, the network node is an Initiating Security Edge Protection Proxy (SEPP); the other network node is a Responding SEPP; a sending unit for sending a request including information indicating a purpose of use of the N32 connection to the other network node; a receiving unit configured to receive, if the request is successful, a response from the other network node, the response including information indicating an allowed purpose of use of the N32 connection in the other network node; A network node comprising:

4. A method for communication between a first network node and a second network node via an N32 interface, comprising: the first network node is an Initiating Security Edge Protection Proxy (SEPP); the second network node is a Responding SEPP; the first network node sending a request to the second network node including information indicating the intended use of the N32 connection; the second network node determining whether the request is successful or unsuccessful; if the request is successful, the second network node sends a response to the first network node including information indicating the permitted uses of the N32 connection. Communication methods.

Images