WO2023084635A1 - Nœud de réseau et procédé de communication - Google Patents

Nœud de réseau et procédé de communication Download PDF

Info

Publication number
WO2023084635A1
WO2023084635A1 PCT/JP2021/041329 JP2021041329W WO2023084635A1 WO 2023084635 A1 WO2023084635 A1 WO 2023084635A1 JP 2021041329 W JP2021041329 W JP 2021041329W WO 2023084635 A1 WO2023084635 A1 WO 2023084635A1
Authority
WO
WIPO (PCT)
Prior art keywords
api
network node
function
information
network
Prior art date
Application number
PCT/JP2021/041329
Other languages
English (en)
Japanese (ja)
Inventor
悠司 鈴木
Original Assignee
株式会社Ｎｔｔドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Priority to PCT/JP2021/041329 priority Critical patent/WO2023084635A1/fr
Publication of WO2023084635A1 publication Critical patent/WO2023084635A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/30—Security of mobile devices; Security of mobile applications
    • H04W12/37—Managing security policies for mobile devices or for controlling mobile applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols

Definitions

  • the present invention relates to a network node and communication method in a communication system.
  • 5G or NR New Radio
  • NR New Radio
  • 5G A wireless communication system called “5G” (hereinafter, the wireless communication system is referred to as “5G” or "NR”) is under study.
  • 5G various radio technologies are being studied in order to meet the requirements of realizing a throughput of 10 Gbps or more and keeping the delay in the radio section to 1 ms or less.
  • 5GC 5G Core Network
  • EPC Evolved Packet Core
  • LTE Long Term Evolution
  • E-UTRAN Radio Access Network
  • NG-RAN Next Generation-Radio Access Network
  • Evolved Universal Terrestrial Radio Access Network A network architecture including NG-RAN (Next Generation-Radio Access Network) corresponding to Evolved Universal Terrestrial Radio Access Network
  • NEF Network Exposure Function
  • AF Application Function
  • CAPIF Common API Framework
  • the resource holder needs to perform registration for all API-provided functions, which may increase the resource holder's processing.
  • the present invention has been made in view of the above points, and aims to efficiently register an API (Application Program Interface) that can be called by a resource holder in a network.
  • API Application Program Interface
  • API Application Program Interface
  • FIG. 1 is a diagram for explaining an example of a communication system
  • FIG. 1 is a diagram for explaining an example of a communication system in a roaming environment
  • FIG. FIG. 4 is a diagram for explaining an example (1) of API registration
  • FIG. 11 is a diagram for explaining an example (2) of API registration
  • FIG. 11 is a diagram for explaining an example (3) of API registration
  • FIG. 4 is a sequence diagram for explaining an example of API registration according to the embodiment of the present invention
  • 3 is a diagram showing an example of functional configurations of a base station 10 and a network node 30 according to an embodiment of the present invention
  • FIG. 2 is a diagram showing an example of the functional configuration of terminal 20 according to the embodiment of the present invention
  • FIG. 2 is a diagram showing an example of hardware configurations of base station 10 and terminal 20 according to an embodiment of the present invention
  • LTE Long Term Evolution
  • LTE-Advanced and LTE-Advanced and later systems eg: NR
  • wireless LAN Local Area Network
  • “configuring" the wireless parameters and the like may mean that predetermined values are set in advance (pre-configure), or the network node 30 or A wireless parameter notified from the terminal 20 may be set.
  • FIG. 1 is a diagram for explaining an example of a communication system.
  • a communication system consists of a UE, which is a terminal 20 , and a plurality of network nodes 30 .
  • one network node 30 corresponds to each function, but one network node 30 may realize a plurality of functions, or a plurality of network nodes 30 may realize one function.
  • the "connection" described below may be a logical connection or a physical connection.
  • AMF is UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function) and AF (Application Function) are connected.
  • AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF are interconnected via respective service-based interfaces Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, Naf. network node 30 .
  • the SMF is a network node 30 that has functions such as session management, UE IP (Internet Protocol) address allocation and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function.
  • a NEF is a network node 30 that has the function of notifying other NFs (Network Functions) of capabilities and events. NSSF selects the network slice to which the UE connects, determines the allowed NSSAI (Network Slice Selection Assistance Information), determines the NSSAI to be set, determines the AMF set to which the UE connects. be.
  • a PCF is a network node 30 having a function of performing network policy control.
  • AF is a network node 30 having the function of controlling an application server.
  • An NRF is a network node 30 that has the ability to discover NF instances that provide services.
  • a UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to a UDR (User Data Repository) that holds the data.
  • UDR User Data Repository
  • FIG. 2 is a diagram for explaining an example of a communication system in a roaming environment.
  • the network consists of a UE, which is a terminal 20 , and a plurality of network nodes 30 .
  • one network node 30 corresponds to each function, but one network node 30 may realize a plurality of functions, or a plurality of network nodes 30 may realize one function.
  • the "connection" described below may be a logical connection or a physical connection.
  • RAN is a network node 30 with radio access functionality and is connected with UE, AMF and UPF.
  • the AMF is a network node 30 having functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management.
  • a UPF is a network node 30 that has functions such as PDU session point to the outside world interconnecting DNs, packet routing and forwarding, user plane QoS handling, and so on.
  • UPF and DN constitute a network slice.
  • a plurality of network slices are constructed in the wireless communication network according to the embodiment of the present invention.
  • AMF is connected to UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy).
  • AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF are interconnected via respective service-based interfaces Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, Naf. network node 30 .
  • the SMF is a network node 30 that has functions such as session management, UE IP address allocation and management, DHCP function, ARP proxy, roaming function, and the like.
  • a NEF is a network node 30 that has the function of notifying other NFs of capabilities and events.
  • the NSSF is a network node 30 that has functions such as selecting a network slice to which the UE connects, determining allowed NSSAIs, determining configured NSSAIs, determining the AMF set to which the UE connects, and so on.
  • a PCF is a network node 30 having a function of performing network policy control.
  • AF is a network node 30 having the function of controlling an application server.
  • An NRF is a network node 30 that has the ability to discover NF instances that provide services.
  • SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks).
  • the vSEPP shown in FIG. 2 is the SEPP in the visited network, and the hSEPP is the SEPP in the home network.
  • the UE is in a roaming environment connected with RAN and AMF in VPLMN (Visited PLMN).
  • VPLMN and HPLMN are connected via vSEPP and hSEPP.
  • the UE may, for example, communicate with the HPLMN's UDM via the VPLMN's AMF.
  • the 3GPP core network opens APIs (Application Program Interfaces) for external applications, and APIs can be called from third-party applications. Furthermore, by extending CAPIF (Common API Framework), resource owners are being considered to authorize core network API calls.
  • the resource holder registers with the API exposing function or resource owner registration handling function in advance, and uses the API exposing function or resource holder registration processing function at the necessary timing. , it is possible to access the resource holder and inquire whether the API can be called.
  • FIG. 3 is a diagram for explaining example (1) of API registration.
  • a CAPIF core function 30A receives application pre-registration sent from an API invoker 30E and authenticates and authorizes third party applications.
  • the API providing function 30B receives a core network API call sent from an API caller and opens the API for authenticated and authorized external applications.
  • the resource holder 20 registers with the API providing function 30B. After being registered, the API providing function 30B can access the resource holder 20 and confirm whether or not the API can be called at a necessary timing. For example, the resource holder 20 may send a registration request for permission to use the API to the API providing function 30B.
  • the API caller 30E is, for example, a third-party application provider, and has the ability to support authentication by providing an identifier for the API caller, the ability to support mutual authentication with the CAPIF core function 30A, and the service API. It may have the ability to obtain authentication for access, the ability to discover information related to service APIs, and the ability to call service APIs.
  • the CAPIF core function 30A has, for example, the ability to support mutual authentication with the API caller 30E, the ability to authenticate the API caller 30E when accessing the service API, and the ability to publish and store information related to the service API. , the ability to perform service API access control based on policies set by the PLMN operator, the ability to record service API call logs and provide service API call logs to approval agencies, billing based on service API call logs monitoring service API calls; adding and removing API callers 30E; supporting access to logs for auditing, e.g. may have the ability to expose information related to service APIs with the CAPIF core functionality of
  • API providing function 30B, API publishing function 30C (API publishing function), and API management function 30D (API management function) may be functions or nodes belonging to one API provider.
  • the API providing function 30B is a provider that provides service APIs, and has the ability to authenticate the API caller 30E based on the information provided by the CAPIF core function 30A and to verify the authentication provided by the CAPIF core function 30A. capability, the ability to log service API calls in the CAPIF core function 30A.
  • API publishing function 30C may have the ability to publish to the CAPIF core function 30A information related to the service API of the API provider.
  • the API management function 30D is a function that allows the API provider to manage service APIs, and has the ability to audit service API call logs received from the CAPIF core function 30A and monitor events reported from the CAPIF core function 30A. ability to set the policy of the API provider in the CAPIF core function 30A; ability to monitor the status of the service API; ability to add and delete API callers 30E; may have the ability to register and maintain;
  • the CAPIF core function 30A, the API providing function 30B, the API public function 30C, the API management function 30D, and the API caller 30E may each be configured as the network node 30.
  • the API providing function 30B, the API public function 30C and API management function 30D may be configured as one network node 30.
  • the resource holder 20 may be, for example, a communication device such as a terminal or a server, or may be another communication device.
  • FIG. 4 is a diagram for explaining example (2) of API registration.
  • the resource holder 20 may register its own device information in the API providing function 30B, or may register the resource owner registration handling function (resource owner registration handling function) included in the CAPIF core function 30A. function).
  • the resource holder 20 registers information about its own device in the API providing function 30B. good.
  • FIG. 5 is a diagram for explaining example (3) of API registration. As shown in FIG. 5, when there are multiple API providing functions 30B, the resource holder 20 needs to register all API providing functions 30B, which may increase the processing in the resource holder 20. there were.
  • the API providing function 30B may similarly perform registration on behalf of the resource holder 20 with respect to the API providing function 30B that requires registration.
  • FIG. 6 is a diagram for explaining an example of API registration in the embodiment of the present invention.
  • resource holder 20 sends a registration request to API providing function 30B-1.
  • the API providing function 30B-1 receives, from the CAPIF core function 30A, information related to the API providing function 30B that requires registration of the resource holder 20, for example, an API related to the resource holder 20. You may acquire the information of the API provision function 30B which exists. Subsequently, based on the acquired information, the API providing function 30B-1 may notify the API providing function 30B-2 and the API providing function 30B-3 of the information of the resource holder 20 and perform registration. .
  • FIG. 7 is a sequence diagram for explaining an example of API registration according to the embodiment of the present invention.
  • the resource holder 20 sends a registration request to the API providing function 30B-1.
  • the API providing function 30B-1 verifies the registration request.
  • the API providing function 30B-1 transmits an acquisition request for information related to the API providing function to the CAPIF core function 30A.
  • the CAPIF core function 30A searches for an API providing function associated with the resource holder 20 in question.
  • the target API providing function may be an API providing function that requires registration of the resource holder 20 or an API providing function for which an API related to the resource holder 20 is open to the public.
  • the CAPIF core function 30A returns information related to the API providing function to the API providing function 30B-1.
  • the API providing function 30B-1 transmits a registration request to the API providing function 30B-2.
  • the API providing function 30B-2 verifies the registration request.
  • the API providing function 30B-2 transmits a registration response to the API providing function 30B-1.
  • the API providing function 30B-1 transmits a registration response to the resource holder 20.
  • the API-providing function 30B-1 receives information indicating a plurality of API-providing functions from the CAPIF core function 30A.
  • steps S106 to S109 may be repeated a required number of times, or steps S106 to S108 may be repeated a required number of times, and a combined registration response is sent to the resource holder 20 once in step S109.
  • the resource owner when registration is required for multiple API-providing functions, can register for one API-providing function to register for all the necessary API-providing functions. Also, an API providing function can send a registration request to another API providing function on behalf of the API caller. Also, the API providing function can acquire information related to API providing functions having APIs associated with the same resource holder from the CAPIF core function.
  • APIs Application Program Interfaces
  • the base station 10, network node 30, and terminal 20 include functionality to implement the embodiments described above. However, each of the base station 10, network node 30, and terminal 20 may have only part of the functions in the embodiments.
  • FIG. 8 is a diagram showing an example of functional configurations of the base station 10 and the network node 30.
  • the base station 10 has a transmitter 110 , a receiver 120 , a setter 130 and a controller 140 .
  • the functional configuration shown in FIG. 8 is merely an example. As long as the operation according to the embodiment of the present invention can be performed, the functional division and the names of the functional units may be arbitrary.
  • the network node 30 may have a functional configuration similar to that of the base station 10 . Also, the network node 30 having multiple different functions on the system architecture may be composed of multiple network nodes 30 separated for each function.
  • the transmission unit 110 includes a function of generating a signal to be transmitted to the terminal 20 or another network node 30 and transmitting the signal by wire or wirelessly.
  • the receiving unit 120 includes a function of receiving various signals transmitted from the terminal 20 or other network nodes 30 and acquiring, for example, higher layer information from the received signals.
  • the setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in the storage device, and reads them from the storage device as necessary.
  • the content of the setting information is, for example, information related to service APIs in the network.
  • the control unit 140 performs processing related to service API settings in the network, as described in the embodiment. Also, the control unit 140 performs processing related to communication with the terminal 20 .
  • a functional unit related to signal transmission in control unit 140 may be included in transmitting unit 110
  • a functional unit related to signal reception in control unit 140 may be included in receiving unit 120 .
  • FIG. 9 is a diagram showing an example of the functional configuration of the terminal 20.
  • the terminal 20 has a transmitting section 210, a receiving section 220, a setting section 230, and a control section 240.
  • the functional configuration shown in FIG. 9 is merely an example. As long as the operation according to the embodiment of the present invention can be performed, the functional division and the names of the functional units may be arbitrary. Also, the communication device that becomes the resource holder 20 may have the same functional configuration as the terminal 20 .
  • the transmission unit 210 creates a transmission signal from the transmission data and wirelessly transmits the transmission signal.
  • the receiving unit 220 wirelessly receives various signals and acquires a higher layer signal from the received physical layer signal.
  • the receiving unit 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL control signals, reference signals, etc. transmitted from the network node 30 .
  • the setting unit 230 stores various types of setting information received from the network node 30 by the receiving unit 220 in the storage device, and reads them from the storage device as necessary.
  • the setting unit 230 also stores preset setting information.
  • the content of the setting information is, for example, information related to service APIs in the network.
  • the control unit 240 performs processing related to service API settings in the network, as described in the embodiment.
  • a functional unit related to signal transmission in control unit 240 may be included in transmitting unit 210
  • a functional unit related to signal reception in control unit 240 may be included in receiving unit 220 .
  • each functional block may be implemented using one device physically or logically coupled, or directly or indirectly using two or more physically or logically separated devices (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices.
  • a functional block may be implemented by combining software in the one device or the plurality of devices.
  • Functions include judging, determining, determining, calculating, calculating, processing, deriving, examining, searching, checking, receiving, transmitting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, assuming, Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc.
  • a functional block (component) that performs transmission is called a transmitting unit or transmitter. In either case, as described above, the implementation method is not particularly limited.
  • FIG. 10 is a diagram illustrating an example of hardware configurations of the base station 10 and the terminal 20 according to an embodiment of the present disclosure.
  • the network node 30 may have hardware configuration similar to that of the base station 10 .
  • the base station 10 and terminal 20 described above are physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. good too.
  • the term "apparatus” can be read as a circuit, device, unit, or the like.
  • the hardware configuration of the base station 10 and terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured without some devices.
  • Each function of the base station 10 and the terminal 20 is performed by the processor 1001 performing calculations and controlling communication by the communication device 1004 by loading predetermined software (programs) onto hardware such as the processor 1001 and the storage device 1002. or by controlling at least one of data reading and writing in the storage device 1002 and the auxiliary storage device 1003 .
  • the processor 1001 for example, operates an operating system and controls 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 device, registers, and the like.
  • CPU central processing unit
  • the control unit 140 , the control unit 240 and the like described above may be implemented by the processor 1001 .
  • the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and executes various processes according to them.
  • programs program codes
  • software modules software modules
  • data etc.
  • the program a program that causes a computer to execute at least part of the operations described in the above embodiments is used.
  • control unit 140 of base station 10 shown in FIG. 8 may be implemented by a control program stored in storage device 1002 and operated by processor 1001 .
  • the control unit 240 of the terminal 20 shown in FIG. 9 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001 .
  • FIG. Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via an electric communication line.
  • the storage device 1002 is a computer-readable recording medium, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be configured.
  • the storage device 1002 may also be called a register, cache, main memory (main storage device), or the like.
  • the storage device 1002 can store executable programs (program code), software modules, etc. for implementing the communication method according to an embodiment of the present disclosure.
  • the auxiliary storage device 1003 is a computer-readable recording medium, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, a Blu -ray disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, and/or the like.
  • the storage medium described above may be, for example, a database, server, or other suitable medium including at least one of storage device 1002 and secondary storage device 1003 .
  • the communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like.
  • the communication device 1004 includes 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).
  • FDD frequency division duplex
  • TDD time division duplex
  • the transceiver may be physically or logically separate implementations for the transmitter and receiver.
  • the input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives input from the outside.
  • the output device 1006 is an output device (for example, display, speaker, LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).
  • Each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information.
  • the bus 1007 may be configured using a single bus, or may be configured using different buses between devices.
  • the base station 10 and the terminal 20 include hardware such as microprocessors, digital signal processors (DSPs), ASICs (Application Specific Integrated Circuits), PLDs (Programmable Logic Devices), and FPGAs (Field Programmable Gate Arrays). , and part or all of each functional block may be implemented by the hardware.
  • processor 1001 may be implemented using at least one of these pieces of hardware.
  • a receiving unit that receives a registration request for permission to use an API (Application Program Interface) from a communication device; a transmitting unit configured to transmit a request for information related to an associated API providing function to a first network node, wherein the receiving unit receives the information from the first network node; , a network node for transmitting a registration request for permission to use an API of said communication device to a second network node based on said information;
  • API Application Program Interface
  • the resource owner can register for one API-providing function to register for all necessary API-providing functions.
  • an API providing function can send a registration request to another API providing function on behalf of the API caller.
  • the API providing function can acquire information related to API providing functions having APIs associated with the same resource holder from the CAPIF core function. That is, in the network, it is possible to efficiently register an API (Application Program Interface) that can be called by a resource holder.
  • the communication device may be a resource holder
  • the first network node may be a CAPIF core function (Common API Framework core function)
  • the second network node may be an API providing function.
  • the resource owner can register for one API-providing function to register for all necessary API-providing functions.
  • an API providing function can send a registration request to another API providing function on behalf of the API caller.
  • the API providing function can acquire information related to API providing functions having APIs associated with the same resource holder from the CAPIF core function.
  • the information may be information specifying a second network node that provides an API that the communication device permits the API caller to use.
  • the resource owner can register for one API-providing function to register for all necessary API-providing functions.
  • an API providing function can send a registration request to another API providing function on behalf of the API caller.
  • the API providing function can acquire information related to API providing functions having APIs associated with the same resource holder from the CAPIF core function.
  • the second network node may be a plurality of network nodes respectively corresponding to a plurality of API providing functions.
  • the receiving unit may receive a registration response from the second network node, and the transmitting unit may transmit the registration response to the communication device.
  • the resource owner can register for one API-providing function to register for all necessary API-providing functions.
  • an API providing function can send a registration request to another API providing function on behalf of the API caller.
  • the API providing function can acquire information related to API providing functions having APIs associated with the same resource holder from the CAPIF core function. That is, in the network, it is possible to efficiently register an API (Application Program Interface) that can be called by a resource holder.
  • the operations of a plurality of functional units may be physically performed by one component, or the operations of one functional unit may be physically performed by a plurality of components.
  • the processing order may be changed as long as there is no contradiction.
  • the network node 30 and terminal 20 have been described using functional block diagrams for convenience of process description, such devices may be implemented in hardware, software, or a combination thereof.
  • the software operated by the processor of the network node 30 according to the embodiment of the invention and the software operated by the processor of the terminal 20 according to the embodiment of the invention are respectively stored in random access memory (RAM), flash memory, read-only memory. (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other appropriate storage medium.
  • notification of information is not limited to the aspects/embodiments described in the present disclosure, and may be performed using other methods.
  • notification of information includes physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof.
  • RRC signaling may also be called an RRC message, for example, RRC It may be a connection setup (RRC Connection Setup) message, an RRC connection reconfiguration message, or the like.
  • a specific operation performed by the network node 30 in this specification may be performed by its upper node in some cases.
  • various operations performed for communication with terminal 20 may be network node 30 and other network nodes other than network node 30 (eg, but not limited to MME or S-GW).
  • MME Mobility Management Entity
  • S-GW Serving Mobility Management Entity
  • Information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may be input and output via multiple network nodes.
  • Input/output information may be stored in a specific location (for example, memory) or managed using a management table. Input/output information and the like can be overwritten, updated, or appended. The output information and the like may be deleted. The entered information and the like may be transmitted to another device.
  • the determination in the present disclosure may be performed by a value represented by 1 bit (0 or 1), may be performed by a boolean value (Boolean: true or false), or may be performed by comparing numerical values (e.g. , comparison with a predetermined value).
  • Software whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.
  • software, instructions, information, etc. may be transmitted and received via a transmission medium.
  • the software uses at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.) to website, Wired and/or wireless technologies are included within the definition of transmission medium when sent from a server or other remote source.
  • wired technology coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.
  • wireless technology infrared, microwave, etc.
  • data, instructions, commands, information, signals, bits, symbols, chips, etc. may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. may be represented by a combination of
  • the channel and/or symbols may be signaling.
  • a signal may also be a message.
  • a component carrier may also be called a carrier frequency, a cell, a frequency carrier, or the like.
  • system and “network” used in this disclosure are used interchangeably.
  • information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information.
  • radio resources may be indexed.
  • base station BS
  • radio base station base station
  • base station device fixed station
  • NodeB NodeB
  • eNodeB eNodeB
  • gNodeB gNodeB
  • a base station can accommodate one or more (eg, three) cells.
  • the overall coverage area of the base station can be partitioned into multiple smaller areas, each smaller area being a base station subsystem (e.g., an indoor small base station (RRH:
  • RRH indoor small base station
  • the term "cell” or “sector” refers to part or all of the coverage area of at least one of the base stations and base station subsystems serving communication services in this coverage.
  • MS Mobile Station
  • UE User Equipment
  • a mobile station is defined 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 It may also be called a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.
  • At least one of the base station and mobile station may be called a transmitting device, a receiving device, a communication device, or the like.
  • At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, or the like.
  • the mobile object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ).
  • at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations.
  • at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.
  • IoT Internet of Things
  • the base station in the present disclosure may be read as a user terminal.
  • communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.)
  • the terminal 20 may have the functions of the network node 30 described above.
  • words such as "up” and “down” may be replaced with words corresponding to inter-terminal communication (for example, "side”).
  • uplink channels, downlink channels, etc. may be read as side channels.
  • user terminals in the present disclosure may be read as base stations.
  • the base station may have the functions that the above-described user terminal has.
  • determining and “determining” used in this disclosure may encompass a wide variety of actions.
  • “Judgement” and “determination” are, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (eg, lookup in a table, database, or other data structure);
  • "judgment” and “determination” are used for receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access (accessing) (for example, accessing data in memory) may include deeming that a "judgment” or “decision” has been made.
  • judgment and “decision” are considered to be “judgment” and “decision” by resolving, selecting, choosing, establishing, comparing, etc. can contain.
  • judgment and “decision” may include considering that some action is “judgment” and “decision”.
  • judgment (decision) may be read as “assuming”, “expecting”, “considering”, or the like.
  • connection means any direct or indirect connection or coupling between two or more elements, It can include the presence of one or more intermediate elements between two elements being “connected” or “coupled.” Couplings or connections between elements may be physical, logical, or a combination thereof. For example, “connection” may be read as "access”.
  • two elements are defined using at least one of one or more wires, cables, and printed electrical connections and, as some non-limiting and non-exhaustive examples, in the radio frequency domain. , electromagnetic energy having wavelengths in the microwave and optical (both visible and invisible) regions, and the like.
  • the reference signal can also be abbreviated as RS (Reference Signal), and may also be called Pilot depending on the applicable standard.
  • RS Reference Signal
  • any reference to elements using the "first,” “second,” etc. designations 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, reference to a first and second element does not imply that only two elements can be employed or that the first element must precede the second element in any way.
  • a and B are different may mean “A and B are different from each other.”
  • the term may also mean that "A and B are different from C”.
  • Terms such as “separate,” “coupled,” etc. may also be interpreted in the same manner as “different.”
  • notification of predetermined information is not limited to being performed explicitly, but may be performed implicitly (for example, not notifying the predetermined information). good too.
  • base station 110 transmitting unit 120 receiving unit 130 setting unit 140 control unit 20 terminal 210 transmitting unit 220 receiving unit 230 setting unit 240 control unit 30 network node 1001 processor 1002 storage device 1003 auxiliary storage device 1004 communication device 1005 input device 1006 output device

Abstract

L'invention concerne un nœud de réseau comprenant : une unité de réception pour recevoir, en provenance d'un dispositif de communication, une demande d'enregistrement pour une autorisation d'utilisation d'une interface de programme d'application (API) ; et une unité de transmission pour transmettre, à un premier nœud de réseau sur la base de la demande d'enregistrement, une demande d'informations concernant une fonction de fourniture d'API associée à l'unité de communication. L'unité de réception reçoit les informations en provenance du premier nœud de réseau. L'unité de transmission transmet, à un second nœud de réseau sur la base des informations, une demande d'enregistrement concernant l'autorisation d'utilisation d'API pour l'unité de communication.
PCT/JP2021/041329 2021-11-10 2021-11-10 Nœud de réseau et procédé de communication WO2023084635A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2021/041329 WO2023084635A1 (fr) 2021-11-10 2021-11-10 Nœud de réseau et procédé de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2021/041329 WO2023084635A1 (fr) 2021-11-10 2021-11-10 Nœud de réseau et procédé de communication

Publications (1)

Publication Number Publication Date
WO2023084635A1 true WO2023084635A1 (fr) 2023-05-19

Family

ID=86335246

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/041329 WO2023084635A1 (fr) 2021-11-10 2021-11-10 Nœud de réseau et procédé de communication

Country Status (1)

Country Link
WO (1) WO2023084635A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020167095A1 (fr) * 2019-02-16 2020-08-20 Samsung Electronics Co., Ltd. Procédé et appareil permettant d'enregistrer des entités de fonction de domaine de fournisseur d'api sur une entité de fonction de noyau capif

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020167095A1 (fr) * 2019-02-16 2020-08-20 Samsung Electronics Co., Ltd. Procédé et appareil permettant d'enregistrer des entités de fonction de domaine de fournisseur d'api sur une entité de fonction de noyau capif

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on application enablement aspects for subscriber-aware northbound API access; (Release 18)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.700-95, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V0.3.0, 25 October 2021 (2021-10-25), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 15, XP052082845 *

Similar Documents

Publication Publication Date Title
WO2020145300A1 (fr) Dispositif d'utilisateur, nœud de réseau et système de communication
JP7412419B2 (ja) ネットワークノード
JP7245266B2 (ja) ネットワークノード、ネットワークシステム及び通知方法
JP7169827B2 (ja) 端末及び通信方法
JP7341167B2 (ja) ネットワークノード、ユーザ装置、及び通信方法
WO2022195878A1 (fr) Nœud de réseau et procédé de communication
WO2022091188A1 (fr) Nœud de réseau et procédé de communication
WO2022113370A1 (fr) Nœud de réseau et procédé de communication
WO2023084635A1 (fr) Nœud de réseau et procédé de communication
WO2022239160A1 (fr) Équipement utilisateur et procédé de communication
WO2022172443A1 (fr) Nœud de réseau et procédé de communication
WO2022029957A1 (fr) Terminal, nœud de réseau, et procédé de communication
WO2023275996A1 (fr) Nœud de réseau et procédé de communication
WO2023275997A1 (fr) Nœud de réseau et procédé de communication
WO2022157899A1 (fr) Nœud de réseau, système de communication sans fil et procédé de communication
WO2022162921A1 (fr) Nœud de réseau, procédé de communication et transport
WO2022097290A1 (fr) Terminal et système de communication
WO2022162920A1 (fr) Nœud de réseau et procédé de communication
WO2023013078A1 (fr) Nœud de réseau et procédé de communication
WO2023013076A1 (fr) Nœud de réseau et procédé de communication
WO2023275998A1 (fr) Terminal, nœud de réseau, et procédé de communication
WO2023195368A1 (fr) Nœud de réseau et procédé de communication
WO2023021583A1 (fr) Nœud de réseau et procédé de communication
WO2020144856A1 (fr) Dispositif de gestion de communication et dispositif de gestion de données

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21963994

Country of ref document: EP

Kind code of ref document: A1