Network node and communication method

Abstract

Provided is a network node comprising a transmission unit that transmits a digital asset presentation request to a specific network node which is provided outside a core network, and a reception unit that receives, from the specific network node, a digital asset which is requested through the digital asset presentation request.

Description

Network Node and Communication Method

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

[0002] In 3GPP (Registered Trademark) (3rd Generation Partnership Project), in order to achieve further increase in system capacity, further increase in data transmission speed, further reduction in latency in the radio section, etc., a wireless communication method called 5G or NR (New Radio) (hereinafter, this wireless communication method is referred to as "5G" or "NR") has been introduced. In 5G, various wireless technologies have been introduced in order to meet the requirement of achieving a throughput of 10 Gbps or more while reducing the latency in the radio section to 1 ms or less. Also, the introduction of various network (NW) functions has been incorporated. Furthermore, studies on 6G, which is a future communication system, are also being conducted.

[0003] In 3GPP Rel-19 SA1 FS_Metaverse (TR 22.856), the requirements for the 3GPP (Registered Trademark) system to support a digital asset container that stores electronic assets such as a user's avatar and ID are defined. On the other hand, recently, in industry groups other than 3GPP (Registered Trademark), electronic asset storage for users that can be regarded as equivalent to a digital asset container such as a cloud wallet has been standardized.

[0004] 3GPP TS 23.502 V18.7.0 (2024-09)

[0005] It is assumed that the electronic assets of a user held by a digital asset container defined in 3GPP (Registered Trademark) and the electronic assets of a user held by a cloud wallet or the like defined by other groups are shared or synchronized with each other.

[0006] However, with conventional technology, if the digital asset container is located within the operator's core network, there is no mechanism to share or synchronize electronic assets between that digital asset container and a cloud wallet located on an application server outside the core network.

[0007] The present invention has been made in view of the above points, and aims to provide a technology that enables network nodes located inside a core network to acquire electronic assets from network nodes located outside the core network.

[0008] According to the disclosed technology, a network node is provided which includes a transmitting unit that transmits an electronic asset presentation request to a specific network node located outside the core network, and a receiving unit that receives the electronic asset requested by the electronic asset presentation request from the specific network node.

[0009] According to the disclosed technology, a technology is provided that enables network nodes within the core network to acquire electronic assets from network nodes outside the core network.

[0010] This is a diagram illustrating an example of a communication system. This is a diagram illustrating an example of a communication system in a roaming environment. This is a diagram showing the specified contents of a digital asset container. This is a diagram showing an example of the configuration of a communication system in an embodiment of the present invention. This is a diagram showing the flow of SM Policy Association Establishment. This is a diagram showing the flow of SMF initiated SM Policy Association Modification. This is a diagram showing example operation sequence 1. This is a diagram showing the flow of PCF initiated SM Policy Association Modification. This is a diagram showing example operation sequence 2. This is a diagram showing example operation sequence 3. This is a diagram showing an example of the functional configuration of network node 100 in an embodiment of the present invention. This is a diagram showing an example of the hardware configuration of network node 100 in an embodiment of the present invention. This is a diagram showing an example of the configuration of vehicle 2001 in an embodiment of the present invention.

[0011] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.

[0012] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE or existing NR, but are not limited to these.

[0013] First, in this embodiment, we will describe an example of the configuration of a 5G core network, which is an example of the operator's (telecommunications carrier's) network (NW), and then we will describe the configuration and operation related to this embodiment.

[0014] Figure 1 is a diagram illustrating an example of a communication system corresponding to a core network. As shown in Figure 1, this communication system consists of a UE (Terminal 20) and multiple network nodes. Hereafter, one network node will be assigned to each function, but one network node may implement multiple functions, or multiple network nodes may implement one function. Also, the "connection" described below may be a logical connection or a physical connection.

[0015] The (R)AN ((Radio) Access Network) 10 is a network node having radio access functionality, and may include a base station 10, and is connected to the UE 20, AMF (Access and Mobility Management Function) 30, and UPF (User plane function) 80. The AMF 30 is a network node having functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management. The UPF 80 is a network node having functions such as PDU (Protocol Data Unit) session point to the outside, interconnected with the DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and DN constitute a network slice.

[0016] AMF30 is connected to UE20, (R)AN10, SMF (Session Management function)85, NSSF (Network Slice Selection Function), NEF (Network Exposure Function)50, NRF (Network Repository Function), UDM (Unified Data Management)40, AUSF (Authentication Server Function), PCF (Policy Control Function)90, and AF (Application Function)60. AMF30, SMF85, NSSF, NEF50, NRF, UDM40, AUSF, PCF90, and AF60 are network nodes that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0017] Figure 1 also shows the Network Data Analytics Function (NWDAF). As shown in Figure 1, the NWDAF can communicate with the AMF 30 and the like. In this embodiment, the NWDAF can also communicate with the (R)AN 10 (base station). Figure 1 also shows the Charge Function (CHF) 95, which is a network node with a billing function.

[0018] SMF85 is a network node with functions such as session management, IP (Internet Protocol) address allocation and management for UEs, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming functionality. NEF50 is a network node with the function of notifying other NFs (Network Functions) of capabilities and events. NSSF is a network node with functions such as selecting the network slice to which UE20 connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which UE20 connects. PCF90 is a network node with the function of controlling network policy. AF60 is a network node with the function of controlling application servers. NRF is a network node with the function of discovering NF instances that provide services. UDM40 is a network node that manages subscriber data and authentication data. The UDM 40 is connected to the UDR (User Data Repository) 45, which holds the data in question.

[0019] NWDAF is a network node that collects and analyzes data from NF (Network Function) or OAM (Operation, Administration and Management). As described above, NWDAF can also collect data from (R)AN10. OAM may also be referred to as the maintenance, operation, and management function.

[0020] Figure 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Figure 2, the network consists of a terminal 20 (UE) and multiple network nodes.

[0021] SEPP is an opaque proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). In Figure 2, vSEPP is SEPP in the visited network, and hSEPP is SEPP in the home network.

[0022] As shown in Figure 2, UE20 is in a roaming environment connected to (R)AN and AMF30 in the Visited PLMN. The Visited PLMN and Home PLMN are connected via vSEPP and hSEPP. UE20 can communicate with the UDM of the Home PLMN, for example, via the AMF of the Visited PLMN.

[0023] (Regarding the challenges) As mentioned above, it is conceivable that users' digital assets held by a digital asset container defined by 3GPP (registered trademark) and users' digital assets held by cloud wallets etc. defined by other organizations may need to be shared or synchronized with each other.

[0024] However, with conventional technology, if the digital asset container is located within the operator's core network, there is no mechanism to share and synchronize digital assets with a cloud wallet located on an application server outside the core network.

[0025] For reference, Figure 3 shows the definition of digital asset container in 3GPP TR 22.856 V2.0.0 (2023-06) Feasibility Study on Localized Mobile Metaverse Services (Release 19).

[0026] (Outline of the Embodiment) In this embodiment, a user electronic asset storage 70 is provided within the core network. The user electronic asset storage 70 corresponds to, for example, a digital asset container. The user electronic asset storage 70 may be a new function or an extension of UDR45 / UDM40. For example, the UDR45 may be functionally enhanced, and the functionally enhanced UDR45 may be used as the user electronic asset storage 70.

[0027] There are two main methods for the user electronic asset storage 70 to acquire user electronic assets from AF60: Method 1 and Method 2, as described below.

[0028] In Method 1, triggered by an event based on the SMF85's judgment, the user electronic asset storage 70 requests the 3rd party (AF60) to present the user electronic assets, and the AF60, upon receiving the request, presents the user electronic assets. In Method 2, regardless of the SMF85 event, the 3rd party (AF60) presents the user electronic assets to the user electronic asset storage 70.

[0029] In addition to the function of acquiring user electronic assets, the user electronic asset storage 70 also has a verification function as a Verifier.

[0030] Furthermore, the user electronic asset storage 70 can also rewrite the policy in UDR45 based on the user electronic assets presented by AF60 to change QoS control and billing control.

[0031] (System Configuration) Figure 4 shows an example of the configuration of the communication system in this embodiment. As shown in Figure 4, this communication system includes UE20, (R)AN10, AMF30, UPF80, SMF85, PCF90, CHF95, user electronic asset storage 70, UDM / UDR (40, 45), NEF50, and AF60 (e.g., cloud wallet).

[0032] AF60 is a third-party device located outside the core network. AMF30, UPF80, SMF85, PCF90, CHF95, User Electronic Asset Storage 70, UDM / UDR (40, 45), and NEF50 are located within the core network. The core network is a network managed by the operator (telecommunications carrier).

[0033] AF60 has a function 61 for storing the user's electronic assets and for presenting the user's electronic assets. User electronic asset storage 70 stores the user's electronic assets.

[0034] Before explaining the operation of the communication system having the above configuration, for reference, the SM Policy Association Establishment (Figure 5) and Modification (Figure 6) disclosed in Non-Patent Document 1 are shown.

[0035] The UDM / UDR (UDM40 or UDR45) holds the network identifier, public key information, private key information, certificate information, authentication method selection policy, etc.

[0036] Below, we will describe three examples of operation sequences of the communication system according to this embodiment, namely Operation Sequence Examples 1 to 3.

[0037] Before explaining example operation sequence 1, for reference, Figure 5 shows "Figure 4.16.4-1: SM Policy Association Establishment" disclosed in Non-Patent Literature 1, and Figure 6 shows "Figure 4.16.5.1-1: SMF initiated SM Policy Association Modification" disclosed in Non-Patent Literature 1.

[0038] In both the Figure 5 and Figure 6 flows, the PCF obtains information from the UDR and other sources and determines the policy, triggered by the SMF. Note that the conventional technology flow does not include the acquisition of information regarding electronic assets.

[0039] The following describes example operation sequences 1 to 3. Example operation sequences 1 and 2 assume a situation where the network policy for users associated with electronic assets is changed on the core network side. The policy change is implemented on the core network side using user electronic assets obtained from AF60. In example operation sequence 3, the user electronic asset storage 70 obtains user electronic assets from AF60 based on a trigger provided from outside the core network, or based on the user electronic asset storage 70's own judgment.

[0040] In operation sequence examples 1 to 3, the user electronic assets that the user electronic asset storage 70 acquires from AF60 include, for example, the user's ID, the user's certificate, the user's avatar, or information about external services used by the user (services provided outside the core network).

[0041] Furthermore, the "policy change" mentioned above is merely one example of why the user electronic asset storage 70 acquires user electronic assets from AF60.

[0042] (Example of Operation Sequence 1) Example of operation sequence 1 will be explained with reference to Figure 7. Note that the example shown in Figure 7 is an example in which communication between AF60 and user electronic asset storage 70 is via NEF50. However, it is not mandatory to go through NEF50. Communication may be performed directly between AF60 and user electronic asset storage 70 without going through NEF50.

[0043] In S101, SMF85 sends a session policy control request to PCF90. For example, if SMF85 decides to change the policy to prioritize user communication, SMF85 sends a session policy control request to PCF90. The Npcf_SMPolicyControl_Update request shown in Figure 6 may be used as the session policy control request message.

[0044] Assume that when PCF90 implements a policy change for a certain user, the corresponding user's electronic assets (e.g., certificates) are required. In S102, PCF90 sends a user electronic asset presentation request to the user electronic asset storage 70. The user electronic asset presentation request contains information identifying which user's which electronic assets are being requested.

[0045] In S103, the user electronic asset storage 70 that has received the user electronic asset presentation request makes a determination regarding the user electronic asset presentation request. Specifically, the user electronic asset storage 70 determines whether it or UDR45 (or other nodes within the core network) already holds the requested electronic assets. If the core network (including the user electronic asset storage 70, UDR45, other nodes, etc.) already holds the requested electronic assets, the process proceeds to S109. Here, assume that the requested electronic assets are not held.

[0046] In S104, the user electronic asset storage 70 sends the user electronic asset presentation request to NEF50. In S105, NEF50 sends the user electronic asset presentation request to AF60.

[0047] In S106, AF60 sends a user electronic asset presentation response to NEF50. The user electronic asset presentation response contains the user electronic assets (e.g., certificates). When AF60 discloses the electronic assets in S106, AF60 may attach information such as a signature to the electronic assets. The user electronic asset storage 70 that has received the signed electronic assets can verify the signature to confirm who the original owner of the electronic assets is.

[0048] In S107, NEF50 sends the user electronic asset presentation response to the user electronic asset storage 70.

[0049] In S108, the user electronic asset storage 70 verifies whether the user electronic assets included in the user electronic asset presentation response are legitimate. If the verification is successful, the user electronic assets are stored in the storage device.

[0050] The user electronic asset storage 70 may perform verification of user electronic assets by querying an external certification authority or the like. Alternatively, the user electronic asset storage 70 may use the user ID of the user associated with the acquired user electronic asset to obtain the user's subscriber information (or contract information) from the UDR 45, and perform verification by comparing this subscriber information with the user electronic asset. For example, verification may be performed by checking whether the name included in the subscriber information matches the name included in the user electronic asset.

[0051] In S109, the user electronic asset storage 70 sends a user information update request to the UDR 45. The UDR 45 updates the user information. Specifically, for example, the user electronic asset storage 70 sends a policy (e.g., QoS policy, billing policy) based on the user electronic asset information acquired in S107 to the UDR 45, and the UDR 45 rewrites the policy for that user.

[0052] In S110, the UDR45 sends a user information update response to the user electronic asset storage 70.

[0053] In S111, the user electronic asset storage 70 sends a notification to the PCF 90 indicating the completion of the user electronic asset presentation request. In S112, the PCF 90 retrieves updated information (specifically, the updated policy) from the UDR 45.

[0054] In S113, a procedure related to billing control is performed between PCF90 and CHF95. For example, if a user who uses a specific external service is to receive a discount on communication charges, and PCF90 determines, based on the updated UDR45 information, that the user is using a specific external service, it instructs CHF95 to apply the discount to that user.

[0055] In S114, PCF90 sends a session policy control response to SMF85.

[0056] Next, we will explain example operation sequence 2, but before that, as a reference, Figure 8 shows the flow of "Figure 4.16.5.2-1: PCF initiated SM Policy Association Modification" disclosed in Non-Patent Literature 1. The flow shown in Figure 8 is a flow in which the PCF takes the lead in making policy changes based on information obtained from UDRs, etc. Note that the conventional technology flow does not describe the acquisition of information regarding electronic assets.

[0057] (Operation Sequence Example 2) Operation Sequence Example 2 will be explained with reference to Figure 9. The example shown in Figure 9 is an example where communication between AF60 and user electronic asset storage 70 goes through NEF50. However, going through NEF50 is not mandatory. Communication may be performed directly between AF60 and user electronic asset storage 70 without going through NEF50. Note that since S202 to S213 are the same as S102 to S113 in Operation Sequence Example 1, only the sequence description is provided.

[0058] In S201, AF60 notifies PCF90 of a service event. This service event notification is, for example, a notification that an event has occurred that requires a policy change (e.g., the execution of an application with a large amount of data traffic).

[0059] In S202, the PCF90 transmits a user electronic asset presentation request to the user electronic asset storage 70.

[0060] Upon receiving a user electronic asset presentation request, the user electronic asset storage 70 makes a decision regarding the user electronic asset presentation request in S203.

[0061] In S204, the user electronic asset storage 70 transmits a user electronic asset presentation request to the NEF 50. In S205, the NEF 50 transmits a user electronic asset presentation request to the AF 60.

[0062] In S206, AF60 transmits a user electronic asset presentation response to NEF50. The user electronic asset presentation response includes the user electronic asset.

[0063] In S207, the NEF 50 transmits a user electronic asset presentation response to the user electronic asset storage 70.

[0064] In S208, the user electronic asset storage 70 verifies the user electronic asset included in the user electronic asset presentation response, and if the verification is successful, stores the user electronic asset in the storage device.

[0065] In S209, the user electronic asset storage 70 sends a user information update request to the UDR 45. The UDR 45 updates the user information and, in S210, sends a user information update response to the user electronic asset storage 70.

[0066] In S211, the user electronic asset storage 70 sends a completion notification of the user electronic asset presentation request to the PCF 90. Also, in S212, the PCF 90 acquires information from the UDR 45. In S213, a procedure related to billing control is performed between the PCF 90 and the CHF 95. In S214, a session policy control update is performed between the PCF 90 and the SMF 85.

[0067] (Operation Sequence Example 3) Operation Sequence Example 3 will be explained with reference to Figure 10. The example shown in Figure 10 is an example where communication between AF60 and user electronic asset storage 70 goes through NEF50. However, going through NEF50 is not mandatory. Communication may be performed directly between AF60 and user electronic asset storage 70 without going through NEF50. Note that since S303 to S309 are the same as S104 to S110 in Operation Sequence Example 1, only the sequence description is provided.

[0068] In S301, AF60 notifies the user electronic asset storage 70 of a service event. The service event notification is, for example, a notification of an event that requires the user's electronic assets during processing on the core network side. Upon receiving the service event notification, the user electronic asset storage 70 issues, for example, a user electronic asset presentation request.

[0069] Upon receiving a service event, the user electronic asset storage 70 makes a decision regarding the user electronic asset presentation request in S302. Specifically, the user electronic asset storage 70 determines whether it already possesses the electronic asset requested in the user electronic asset presentation request. Here, it is assumed that the user does not possess the electronic asset.

[0070] In S303, the user electronic asset storage 70 transmits a user electronic asset presentation request to the NEF 50. In S304, the NEF 50 transmits a user electronic asset presentation request to the AF 60.

[0071] In S305, AF60 transmits a user electronic asset presentation response to NEF50. The user electronic asset presentation response includes the user electronic asset.

[0072] In S306, the NEF 50 transmits a user electronic asset presentation response to the user electronic asset storage 70.

[0073] In S307, the user electronic asset storage 70 verifies the user electronic asset included in the user electronic asset presentation response, and if the verification is successful, stores the user electronic asset in the storage device.

[0074] In S308, the user electronic asset storage 70 sends a user information update request to the UDR 45. The UDR 45 updates the user information and, in S309, sends a user information update request to the user electronic asset storage 70.

[0075] The updated policy in UDR45 can be used for QoS control or billing control for the user in question within the core network.

[0076] (Effects of the technology according to the embodiment) According to the technology according to this embodiment, a network node located inside the core network (e.g., a digital asset container) can acquire electronic assets from a network node located outside the core network (e.g., a third-party cloud wallet).

[0077] For example, a network node within the core network can write a policy based on acquired electronic assets to the UDR, thereby enabling QoS control or billing control based on electronic assets.

[0078] (Device Configuration) Next, we will describe an example of the functional configuration of AF60 and user electronic asset storage 70, which perform the processing and operations described above. Hereinafter, network nodes such as AF60 and user electronic asset storage 70 will be collectively referred to as "network node 100".

[0079] <Network Node 100> Figure 11 shows an example of the functional configuration of network node 100.

[0080] As shown in Figure 11, the network node 100 includes a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 11 is merely an example. Any functional classification and functional unit names are acceptable as long as they enable the operation according to the embodiment of the present invention.

[0081] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or other network node and transmitting the signal by wire or wireless. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 or other network node and obtaining information from the received signal, for example, information of a higher layer. A communication unit including the transmitting unit 110 and the receiving unit 120 may be configured.

[0082] The setting unit 130 stores various setting information in a storage device and reads it from the storage device as needed. The storage device of the setting unit 130 may also store user electronic assets. The control unit 140 controls the network node 100. The control unit 140 includes a verification function. The signal transmission function in the control unit 140 may be included in the transmission unit 110, and the signal reception function in the control unit 140 may be included in the reception unit 120. The transmission unit 110 and the reception unit 120 may also be called the transmitter and receiver, respectively.

[0083] (Hardware Configuration) The block diagram (Figure 11) used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the above one device or the above multiple devices with software.

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

[0085] For example, the network node 100 in one embodiment of the present disclosure may function as a computer that processes the communication method of the present disclosure. Figure 12 is a diagram showing an example of the hardware configuration of the network node 100 according to one embodiment of the present disclosure. The network node 100 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

[0086] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the network node 100 and the terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

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

[0088] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0089] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the network node 100 shown in Figure 11 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained 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 also be transmitted from the network via a telecommunications line.

[0090] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of the present disclosure.

[0091] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc 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 multipurpose disk, a Blu-ray® disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0092] 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 referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting and receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

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

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

[0095] Furthermore, the network node 100 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

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

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

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

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

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

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

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

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

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

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

[0106] Furthermore, if the communication module 2013 includes a network node 100 (or terminal 20), the communication module 2013 can perform the operations of the network node 100 described above.

[0107] This specification discloses at least the configurations described in the following appendix.

[0108] <Notes> (Note 1) A network node comprising a transmitting unit that transmits an electronic asset presentation request to a specific network node located outside the core network, and a receiving unit that receives the electronic asset requested by the electronic asset presentation request from the specific network node. (Note 2) The network node according to Note 1, wherein the transmitting unit changes the policy in the user data repository in the core network based on the information of the electronic asset. (Note 3) The network node according to Note 1, further comprising a control unit that performs verification to confirm whether the electronic asset is legitimate or not. (Note 4) The network node according to Note 1, further comprising a control unit that determines whether or not to transmit the electronic asset presentation request by confirming whether or not the electronic asset is already held within the core network. (Note 5) A network node comprising a receiving unit that receives an electronic asset presentation request transmitted from a specific network node located inside the core network, and a transmitting unit that transmits the electronic asset requested by the electronic asset presentation request to the specific network node. (Appendix 6) A communication method performed by a network node, comprising the steps of: transmitting an electronic asset presentation request to a specific network node located outside the core network; and receiving the electronic asset requested by the electronic asset presentation request from the specific network node.

[0109] According to any of the appendices 1 through 6, network nodes within the core network can acquire electronic assets from network nodes outside the core network. According to appendice 2, policy control or billing control becomes possible. According to appendice 3, electronic assets can be verified. According to appendice 4, the transmission of unnecessary electronic asset presentation requests can be avoided.

[0110] (Supplement to Embodiments) While embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the network node 100 has been described using a functional block diagram, but such a device may be realized in hardware, software, or a combination thereof. The software operated by the processor of the EES 30 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.

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

[0112] Each aspect / embodiment described in this disclosure refers to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20 may apply to at least one system utilizing UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. Alternatively, multiple systems may be applied in combination (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0113] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

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

[0115] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

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

[0117] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

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

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

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

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

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

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

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

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

[0126] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

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

[0128] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" 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 several other appropriate terms.

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

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

[0132] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

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

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

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

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

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

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

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

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

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

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

[0143] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0144] 10 Base station ((R)AN) 20 Terminal (UE) 30 AMF 40 UDM 45 UDR 50 NEF 60 AF 70 User electronic asset storage 80 UPF 85 SMF 90 PCF 95 CHF 100 Network node 110 Transmitter 120 Receiver 130 Configuration unit 140 Control unit 210 Transmitter 220 Receiver 230 Configuration unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A network node comprising: a transmitting unit that transmits an electronic asset presentation request to a specific network node located outside the core network; and a receiving unit that receives the electronic asset requested by the electronic asset presentation request from the specific network node.

2. The network node according to claim 1, wherein the transmitting unit modifies the policy in the user data repository in the core network based on the information of the electronic assets.

3. The network node according to claim 1, further comprising a control unit for verifying whether or not the electronic asset is legitimate.

4. The network node according to claim 1, further comprising a control unit that determines whether or not to transmit the electronic asset presentation request by checking whether or not the electronic asset is already held within the core network.

5. A network node comprising a receiving unit that receives an electronic asset presentation request transmitted from a specific network node located within the core network, and a transmitting unit that transmits the electronic asset requested by the electronic asset presentation request to the specific network node.

6. A communication method performed by a network node, comprising the steps of: transmitting an electronic asset presentation request to a specific network node located outside the core network; and receiving the electronic asset requested by the electronic asset presentation request from the specific network node.

Images