[go: up one dir, main page]

WO2025182045A1 - Nœud de réseau, terminal et procédé de communication - Google Patents

Nœud de réseau, terminal et procédé de communication

Info

Publication number
WO2025182045A1
WO2025182045A1 PCT/JP2024/007639 JP2024007639W WO2025182045A1 WO 2025182045 A1 WO2025182045 A1 WO 2025182045A1 JP 2024007639 W JP2024007639 W JP 2024007639W WO 2025182045 A1 WO2025182045 A1 WO 2025182045A1
Authority
WO
WIPO (PCT)
Prior art keywords
eas
information
category
satellite backhaul
ees
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/JP2024/007639
Other languages
English (en)
Japanese (ja)
Inventor
淳平 魚島
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NTT Docomo Inc
Original Assignee
NTT Docomo Inc
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 NTT Docomo Inc filed Critical NTT Docomo Inc
Priority to PCT/JP2024/007639 priority Critical patent/WO2025182045A1/fr
Publication of WO2025182045A1 publication Critical patent/WO2025182045A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/084—Load balancing or load distribution among network function virtualisation [NFV] entities; among edge computing entities, e.g. multi-access edge computing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/06—Airborne or Satellite Networks

Definitions

  • the present invention relates to a network node, a terminal, and a communication method in a communication system.
  • NR is considering a network architecture that includes 5GC (5G Core Network), which corresponds to EPC (Evolved Packet Core), the core network in the LTE (Long Term Evolution) network architecture, and NG-RAN (Next Generation Radio Access Network), which corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), the RAN (Radio Access Network) in the LTE network architecture (for example, Non-Patent Document 1).
  • 5GC 5G Core Network
  • EPC Evolved Packet Core
  • LTE Long Term Evolution
  • NG-RAN Next Generation Radio Access Network
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • the RAN Radio Access Network
  • Non-Patent Document 1 Non-Patent Document 1
  • edge computing is being considered, which would enable efficient services by providing operator and third-party services in locations close to the UE access point, thereby reducing end-to-end latency and reducing the load on the transport network.
  • edge computing functions are configured in terminals and servers, and communication is enabled using a server located close to the terminal (for example, Non-Patent Document 2).
  • NTN Non-Terrestrial Network
  • NTN uses non-terrestrial networks such as satellites to provide services to areas that cannot be covered by terrestrial 5G networks, mainly due to cost reasons (for example, Non-Patent Document 3 and Non-Patent Document 4).
  • the present invention was made in consideration of the above points, and aims to provide suitable satellite edge computing in an NTN (Non-Terrestrial Network) environment.
  • NTN Non-Terrestrial Network
  • the disclosed technology provides a network node having a receiving unit that acquires satellite backhaul category information and a control unit that configures EAS (Edge Application Server) resources based on the satellite backhaul category information.
  • EAS Electronic Application Server
  • the disclosed technology makes it possible to provide suitable satellite edge computing in an NTN (Non-Terrestrial Network) environment.
  • NTN Non-Terrestrial Network
  • FIG. 1 is a diagram illustrating an example of a communication system.
  • FIG. 1 is a diagram illustrating an example of a communication system in a roaming environment.
  • FIG. 1 is a diagram for explaining an example (1) of edge computing.
  • FIG. 10 is a diagram for explaining an example (2) of edge computing.
  • FIG. 1 is a diagram illustrating an example of NTN.
  • FIG. 1 is a diagram illustrating an example (1) of edge computing according to an embodiment of the present invention.
  • FIG. 10 is a sequence diagram illustrating an example of a service provision request according to an embodiment of the present invention.
  • FIG. 10 is a sequence diagram illustrating an example of a service provision subscription request according to an embodiment of the present invention.
  • FIG. 10 is a sequence diagram illustrating an example of a service provision subscription request according to an embodiment of the present invention.
  • FIG. 10 is a sequence diagram illustrating an example of an EEC registration request according to an embodiment of the present invention.
  • FIG. 10 is a sequence diagram illustrating an example of an EAS discovery request according to an embodiment of the present invention.
  • FIG. 10 is a diagram illustrating an example (2) of edge computing according to an embodiment of the present invention.
  • FIG. 10 is a sequence diagram illustrating an example of an EAS registration request according to an embodiment of the present invention.
  • FIG. 10 is a sequence diagram illustrating an example of an AC registration request according to an embodiment of the present invention.
  • FIG. 10 is a sequence diagram illustrating an example of an EAS discovery request according to an embodiment of the present invention.
  • FIG. 10 is a sequence diagram illustrating an example of an EAS discovery and subscription request according to an embodiment of the present invention.
  • FIG. 2 is a diagram illustrating an example of the functional configuration of a base station 10 and a network node 30 according to an embodiment of the present invention.
  • FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to an embodiment of the present invention.
  • 2 is a diagram illustrating an example of a hardware configuration of a base station 10 and a terminal 20 according to an embodiment of the present invention.
  • FIG. FIG. 2 is a diagram showing an example of the configuration of a vehicle 2001 according to an embodiment of the present invention.
  • LTE Long Term Evolution
  • NR Universal Terrestrial Radio Access
  • LAN Local Area Network
  • "configuring" radio parameters etc. may mean that predetermined values are pre-configured, or that radio parameters notified from the network node 30 or terminal 20 are configured.
  • Figure 1 is a diagram illustrating an example of a communication system.
  • the communication system is composed of a UE, which is a terminal 20, and multiple network nodes 30.
  • a UE which is a terminal 20
  • multiple network nodes 30 it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function.
  • the "connection" described below may be a logical connection or a physical connection.
  • the RAN Radio Access Network
  • the RAN is a network node 30 with radio access functionality, which may include a base station 10, and is connected to a UE, an AMF (Access and Mobility Management Function), and a UPF (User plane function).
  • the AMF is a network node 30 with functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management.
  • the UPF is a network node 30 with functions such as a PDU (Protocol Data Unit) session point to the outside that interconnects 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. In the wireless communication network of an embodiment of the present invention, multiple network slices are constructed.
  • the AMF is connected to the UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function).
  • the AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via their respective service-based interfaces: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.
  • 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.
  • the NEF is a network node 30 that has the function of notifying other NFs (Network Functions) of capabilities and events.
  • the NSSF is a network node 30 that has functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which the UE connects.
  • the PCF is a network node 30 that has the function of controlling network policies.
  • the AF is a network node 30 that has the function of controlling application servers.
  • the NRF is a network node 30 that has the function of discovering NF instances that provide services.
  • the UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to the UDR (User Data Repository) that holds this data.
  • Figure 2 is a diagram illustrating an example of a communication system in a roaming environment.
  • the network is composed of a terminal 20 (UE) and multiple network nodes 30.
  • UE terminal 20
  • network nodes 30 it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function.
  • connection described below may be a logical connection or a physical connection.
  • the RAN is a network node 30 with radio access functionality, and is connected to the UE, AMF, and UPF.
  • the AMF is a network node 30 with functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management.
  • the UPF is a network node 30 with functions such as a PDU session point to the outside that interconnects with the DN, packet routing and forwarding, and user plane QoS handling.
  • the UPF and DN constitute a network slice. In the wireless communication network of an embodiment of the present invention, multiple network slices are constructed.
  • the AMF is connected to the UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy).
  • the AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via their respective service-based interfaces: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.
  • the SMF is a network node 30 that has functions such as session management, UE IP address allocation and management, DHCP function, ARP proxy, and roaming function.
  • the NEF is a network node 30 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 the network slice to which the UE connects, determining the allowed NSSAI, determining the configured NSSAI, and determining the AMF set to which the UE connects.
  • the PCF is a network node 30 that has the function of controlling network policies.
  • the AF is a network node 30 that has the function of controlling application servers.
  • the NRF is a network node 30 that has the function of discovering NF instances that provide services.
  • the SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks).
  • the vSEPP shown in Figure 2 is a SEPP in the visited network
  • the hSEPP is
  • the UE is in a roaming environment connected to the RAN and AMF in the VPLMN (Visited PLMN).
  • the VPLMN and HPLMN (Home PLMN) are connected via vSEPP and hSEPP.
  • the UE can communicate with the UDM of the HPLMN, for example, via the AMF of the VPLMN.
  • edge computing is being considered, which would enable efficient services by providing operator and third-party services in locations close to the UE's access point, thereby reducing end-to-end latency and reducing the load on the transport network.
  • edge computing functions are configured in terminals and servers, and communication is enabled using a server located close to the terminal (see, for example, non-patent document 2).
  • FIG. 3 is a diagram for explaining an example of edge computing (1).
  • an architecture is disclosed in which a UPF is installed on a satellite in GEO (Geostationary Orbit) to perform edge computing.
  • GEO Globalstar Orbit
  • HAPS High Altitude Platform Station
  • FIG 4 is a diagram illustrating an example of edge computing (2). As shown in Figure 4, application communication is performed between the Edge Application Server (EAS) and the Application Client (AC), and the Edge Enabler Server (EES) and Edge Enabler Client (EEC) perform operations to connect to the Edge Data Network (EDN).
  • EAS Edge Application Server
  • AC Application Client
  • EES Edge Enabler Server
  • EEC Edge Enabler Client
  • the UE, the edge data network, and the edge configuration server (ECS) may be connected via the core network.
  • EDGE-1 Enables interoperability between the EES and EEC. Registers and deregisters the EEC to the EES. Searches and acquires EAS configuration information. Discovers available EASs in the EDN. Executes service continuity procedures, such as initiating ACR (Application Context Relocation).
  • EDGE-2 Enables interaction between EES and APIs for retrieving core network functions and network capability information. Supports access via SCEF (Service Capability Exposure Function) and NEF APIs, or direct access to core network functions from EESs located within the MNO (Mobile Network Operator) trust domain.
  • SCEF Service Capability Exposure Function
  • NEF Network Exposure Function
  • EDGE-3 Enables interoperability between EES and EAS. Supports registration of EAS with availability information, such as time constraints and location constraints. Also deregisters EAS from EES. Also discovers target EAS to support ACT (Application Context Transfer). Also provides access to network capability information such as location information. Also requests establishment of a data session between AC and EAS to which a specific QoS applies, and obtains QoS information. Also supports service continuity procedures such as ACR state.
  • EDGE-4 Enables interoperability between the ECS and EEC. Provides edge configuration information to the EEC.
  • EDGE-5 Enables interoperability between AC and EEC.
  • EDGE-6 Enables interoperability between the ECS and EES. Registers EES information to the ECS. Also, unregisters EES information from the ECS. Also, searches for target EES information from the ECS.
  • EDGE-7 Enables interoperability between EAS and APIs to retrieve core network functions and network capability information. Supports access via SCEF and NEF APIs, or direct access to core network functions from EAS located within the MNO trust domain.
  • EDGE-8 Enables interoperability between the ECS and APIs to retrieve core network functions and network capability information. Supports access via SCEF and NEF APIs, or direct access to core network functions from an ECS located within the MNO trust domain.
  • EDGE-9 enables interoperability between EESs. Two EESs connected by EDGE-9 may be included in different EDNs or the same EDN. To support ACR, it discovers target EAS information. It also supports EEC context relocation procedures. It also transparently transfers application context in ACRs managed by the EEL (Edge Enabler layer).
  • the EES and ECS interact with the notification management server connected via NM-S
  • the SEAL ECS interacts with the SEAL notification management client.
  • the SEAL notification management server and SEAL notification management client are connected via NM-UU.
  • edge computing applications are defined here, they are not currently optimized for edge computing on NTN.
  • Non-Patent Documents 1 and 6 the following satellite backhaul categories are defined, as shown in Table 1: GEO, MEO (Medium Earth Orbit), LEO, OTHERSAT, DYNAMIC_GEO, DYNAMIC_MEO, DYNAMIC_LEO, DYNAMIC_OTHERSAT, and NON_SATELLITE (see Non-Patent Documents 1 and 6). Additionally, parameters such as the 5G system delay when using satellite communications are defined (see Non-Patent Document 7).
  • satellite backhaul category information is transmitted using the following flow (see Non-Patent Document 1 and Non-Patent Document 8).
  • the AMF When the UPF acts as a PSA (PDU Session Anchor), the AMF provides satellite backhaul category information as a parameter to the PCF (UL CL (Uplink Classifier)/BP (Branching Point)). The PCF adds the satellite backhaul category information as a parameter to the generation of the URSP (UE Route Selection Policy) rule (Route Selection Descriptor). The SMF executes the PSA UPF selection procedure.
  • PSA PDU Session Anchor
  • the AMF provides satellite backhaul category information as a parameter to the PCF (UL CL (Uplink Classifier)/BP (Branching Point)).
  • the PCF adds the satellite backhaul category information as a parameter to the generation of the URSP (UE Route Selection Policy) rule (Route Selection Descriptor).
  • the SMF executes the PSA UPF selection procedure.
  • the AMF determines the GEO satellite ID from the global RAN node ID, etc.
  • the SMF selects the UL CL/BP/local PSA based on the GEO satellite ID provided by the AMF.
  • FIG. 5 is a diagram illustrating an example of an NTN.
  • an NTN is realized by a satellite in space or a flying object in the air.
  • a GEO (Geostationary Orbit) satellite may be a satellite located at an altitude of 35,786 km and having a geostationary orbit.
  • a LEO (Low Earth Orbit) satellite may be a satellite located at an altitude of 500-2000 km and orbiting every 88-127 minutes.
  • a HAPS High Altitude Platform Station
  • GEO satellites, LEO satellites, and HAPS aircraft may be connected to ground stations (gNBs) via gateways.
  • gNBs ground stations
  • the service areas may be larger in the order of HAPS, LEO, and GEO.
  • NTNs can extend 5G network coverage to unserved or served areas. Also, for example, NTNs can improve service continuity, availability, and reliability on ships, buses, trains, aircraft, space stations, spacecraft, or other critical communications.
  • an environment equivalent to the satellite category is assumed on the AC (Application Client) or EEC side on the UE, and AC resources are provided in a fixed manner.
  • An environment equivalent to the satellite category is assumed on the EAS (Edge Application Server) or EES (Edge Enabler Server) side on the EDN (Edge Data Network), and EAS or AC resources are provided in a fixed manner.
  • FIG. 6 is a diagram illustrating an example (1) of edge computing in an embodiment of the present invention. For example, as shown in Figure 6, the following operations 1) to 5) may be executed.
  • Operation 1 By adding satellite backhaul category information to AC-related information, an optimal AC resource allocation method may be introduced.
  • the AC may obtain satellite backhaul category information from URSP policy rules, etc.
  • the value of each IE (Information Element) of AC service KPIs (Key performance indicators) may be changed based on the value of AC SatelliteBackhaulCategory.
  • Satellite backhaul category information may be added to EAS-related information.
  • a new IE, EAS SatelliteBackhaulCategory may be added to the EAS profile.
  • the values of each IE in the EAS service KPIs may be changed based on EAS SatelliteBackhaulCategory.
  • Satellite backhaul category information may be added to the EEC association.
  • the EEC may obtain satellite backhaul category information from URSP policy rules, etc. This may be performed as a preliminary step to the processes 1)-6) below.
  • An IE indicating satellite backhaul category information may be added to the EEC Context. 2) An IE indicating satellite backhaul category information may be added to the service provisioning request. 3) An IE indicating satellite backhaul category information may be added to the service provisioning subscription request. 4) An IE indicating satellite backhaul category information may be added to the EEC registration request. 5) An IE indicating satellite backhaul category information may be added to the EAS discovery request. 6) An IE indicating satellite backhaul category information may be added to the EAS discovery filter.
  • Satellite backhaul category information may be added to the EES association.
  • An IE indicating satellite backhaul category information may be added to the EES profile.
  • Satellite backhaul category information may be added to the ECS-related information.
  • An IE indicating satellite backhaul category information may be added to the ECS profile.
  • An IE indicating satellite backhaul category information may be added to the EDN configuration information.
  • the AC Profile is used to determine the service and required service characteristics.
  • An AC Profile may include an IE, AC SatelliteBackhaulCategory, which indicates satellite backhaul category information. This IE contains the satellite backhaul category or type of the AC, for example, GEO. An implementation may set a specific value to this IE.
  • the EAS Profile is used to describe the service and the service characteristics offered.
  • the EAS Profile may include an IE, EAS SatelliteBackhaulCategory, which indicates satellite backhaul category information.
  • This IE contains the satellite backhaul category or type of the EAS, for example GEO.
  • An implementation may set a specific value to this IE.
  • the EEC Context contains information related to the EEC for receiving Edge Enabler services.
  • the EEC Context may include an IE, EEC SatelliteBackhaulCategory, which indicates information about the satellite backhaul category.
  • This IE contains the satellite backhaul category or type of the EEC, for example, GEO. A specific value may be set in this IE depending on the implementation.
  • FIG. 7 is a sequence diagram illustrating an example of a service provisioning request in an embodiment of the present invention.
  • the EEC sends a service provisioning request to the ECS.
  • the service provisioning request may include an IE, EEC SatelliteBackhaulCategory, indicating satellite backhaul category information.
  • the IE contains the satellite backhaul category or type of the EEC, for example GEO. A specific value may be set in the IE depending on the implementation.
  • the ECS processes the request.
  • the ECS sends a service provisioning response to the EEC.
  • FIG 8 is a sequence diagram illustrating an example of a service provisioning subscription request in an embodiment of the present invention.
  • the EEC sends a service provisioning subscription request to the ECS.
  • the service provisioning subscription request may include an IE, EEC SatelliteBackhaulCategory, indicating satellite backhaul category information.
  • the IE contains the satellite backhaul category or type of the EEC, for example GEO. A specific value may be set in the IE depending on the implementation.
  • the ECS processes the request.
  • the ECS sends a service provisioning subscription response to the EEC.
  • FIG. 9 is a sequence diagram illustrating an example of an EEC registration request in an embodiment of the present invention.
  • the EEC sends an EEC registration request to the EES.
  • the EEC registration request may include an IE, EEC SatelliteBackhaulCategory, indicating satellite backhaul category information.
  • the IE includes the satellite backhaul category or type of the EEC, for example, GEO. A specific value may be set in the IE depending on the implementation.
  • the EES requests validation.
  • the EES obtains the EEC context.
  • the EES sends an EEC registration response to the EEC.
  • FIG. 10 is a sequence diagram illustrating an example of an EAS discovery request in an embodiment of the present invention.
  • the EEC sends an EAS discovery request to the EES.
  • the EAS discovery request may include an IE, EEC SatelliteBackhaulCategory, indicating information about the satellite backhaul category.
  • the IE includes the EEC satellite backhaul category or type, for example, GEO.
  • the EAS discovery request may also include an IE, EAS SatelliteBackhaulCategory, indicating information about the satellite backhaul category.
  • the IE includes the EAS satellite backhaul category or type, for example, GEO. A specific value may be set in the IE depending on the implementation.
  • the EES confirms authorization.
  • the EES sends an EAS discovery response to the EEC.
  • EAS discovery filters are a set of characteristics for determining the requested EAS, and are an IE included in the EAS discovery request.
  • An IE indicating satellite backhaul category information, EAS SatelliteBackhaulCategory, may be added to the EAS discovery filters.
  • This IE contains the satellite backhaul category or type of EAS, for example GEO. A specific value may be set in this IE depending on the implementation.
  • the EES Profile contains information about the EES and the services it provides.
  • An EES Profile may include an IE, EES SatelliteBackhaulCategory, which indicates information about the satellite backhaul category.
  • This IE contains the satellite backhaul category or type of the EES, for example GEO.
  • An implementation may set a specific value for this IE.
  • the ECS Profile contains information related to the ECS and the EDN configuration information to be provided.
  • An IE, EASID SatelliteBackhaulCategory, which indicates information about the satellite backhaul category, may be added to the ECS Profile.
  • This IE contains the satellite backhaul category or type of EASID (Edge Application Server Identification), for example, GEO. A specific value may be set in this IE depending on the implementation.
  • the EDN configuration information may include an IE, EDN SatelliteBackhaulCategory, indicating satellite backhaul category information.
  • This IE contains the satellite backhaul category or type of the EDN, such as GEO. A specific value may be set in this IE depending on the implementation.
  • satellite backhaul category information exists for each of the AC, EAS, EEC, EES, and ECS, and how to select and provide optimal AC and EAS resources based on the satellite backhaul category information.
  • FIG. 11 is a diagram illustrating an example (2) of edge computing in an embodiment of the present invention. As shown in FIG. 11, the following operations may be performed: 1) providing optimal resources when registering with an EAS; and 2) providing optimal resources when registering with an AC.
  • Operation 1 Providing optimal resources during EAS registration 1.
  • the EAS provider or EAS user defines and configures the required EAS resources based on the information of the satellite backhaul category. 2. Modify EAS resources based on satellite backhaul category information, which may include application migration, etc. 3. Check whether you meet the registration requirements. 4. Implement EAS registration requirements. 5. Carry out registration approval confirmation. 6. Perform EAS registration request response.
  • Operation 2 Providing optimal resources during AC registration 1.
  • the AC provider defines and configures the required AC resources based on the information of the satellite backhaul category. 2. Modifying AC resources based on satellite backhaul category information, which may include application migration, etc. 3. Check whether you meet the registration requirements. 4. Implement EAS registration requirements. 5. Carry out registration approval confirmation. 6. Perform EAS registration request response.
  • FIG. 12 is a sequence diagram illustrating an example of an EAS registration request in an embodiment of the present invention.
  • the sequence in FIG. 12 may be based on the following prerequisites 1)-3).
  • the EAS is set to EASID. 2)
  • the EAS is set with the address of the EES (for example, a URI (Uniform Resource Identifier)).
  • a URI Uniform Resource Identifier
  • step S101 the EAS provider or EAS user defines and sets the required EAS resources based on the satellite backhaul category information.
  • step S102 the EAS sets the EAS resources based on the satellite backhaul category information.
  • the EAS provider or EAS user may also define and set the required AC resources based on the satellite backhaul category information.
  • step S102 the EAS may also set the AC resources based on the satellite backhaul category information.
  • step S103 the EAS determines that registration is required.
  • step S104 the EAS sends an EAS registration request to the EES.
  • step S105 the EES performs a registration authorization confirmation.
  • step S106 the EES sends an EAS registration response to the EAS.
  • FIG. 13 is a sequence diagram illustrating an example of an AC registration request in an embodiment of the present invention.
  • the AC provider defines and configures the required AC resources based on the information about the satellite backhaul category.
  • the AC configures the AC resources based on the information about the satellite backhaul category.
  • the AC provider may also define and configure the required EAS resources based on the information about the satellite backhaul category.
  • the AC may also configure the EAS resources based on the information about the satellite backhaul category.
  • step S203 the AC sends an AC registration request to the EEC.
  • step S204 the EES performs request verification.
  • step S205 the EEC sends an AC registration response to the AC.
  • Table 2 shows each IE of the AC service KPIs.
  • the AC service KPIs may include IEs indicating connection bandwidth, request rate, response time, availability, compute resources, graphic compute resources, memory, and storage.
  • the value of each IE in the AC service KPIs may be changed based on the value of AC SatelliteBackhaulCategory, which indicates information about the AC's satellite backhaul category.
  • the value to be changed may be set by the edge computing provider or specified by the user. The change may be performed in any of the AC, EEC, EAS, and EES.
  • FIG. 14 is a sequence diagram illustrating an example of an EAS discovery request in an embodiment of the present invention.
  • the sequence in FIG. 14 may be based on the following prerequisites 1)-3).
  • the EEC already has the address of the EES (e.g., a Uniform Resource Identifier (URI), an IP address). 2) The EEC has already obtained the appropriate security credentials to enable communication with the EES. 3) The EES is configured with an Edge Computing Service Provider (ECSP) policy for EAS discovery.
  • ECSP Edge Computing Service Provider
  • step S301 the EAS provider or EAS user defines and configures the required EAS resources based on the satellite backhaul category information.
  • step S302 the EEC sends an EAS discovery request to the EES.
  • step S303 the EES sends an EAS discovery resource optimization request to the EAS.
  • step S304 the EAS configures the EAS resources based on the satellite backhaul category information.
  • step S305 the EAS sends an EAS discovery resource optimization response to the EES.
  • step S306 the EES performs authorization confirmation.
  • step S307 the EES sends an EAS discovery response to the EEC.
  • steps 1)-3) below may be performed.
  • the EES sends an EAS discovery resource optimization request to the EAS.
  • Table 3 shows an example of the IEs included in the EAS discovery resource optimization request.
  • the EAS discovery resource optimization request may include EAS SatelliteBackhaulCategory, an IE that indicates information about the EAS satellite backhaul category.
  • the EAS sends an EAS discovery resource optimization response to the EES.
  • Table 4 is an example of the IEs included in the EAS discovery resource optimization response.
  • the EAS discovery resource optimization response may include IEs indicating a success response, a failure response and the cause of the failure, an updated EAS profile, a proposed expiration time, a registration ID, and security credentials related to the EAS.
  • Table 5 shows each IE of the EAS service KPIs.
  • EAS service KPIs may include IEs indicating maximum request rate, maximum response time, availability, available compute resources, available graphical compute resources, available memory, available storage, and connection bandwidth.
  • the value of each IE in the EAS Service KPIs may be changed based on the value of the EAS SatelliteBackhaulCategory, which indicates information about the EAS satellite backhaul category.
  • the value to be changed may be set by the edge computing provider or specified by the user. The change may be performed in any of the EAS, EES, and EEC.
  • FIG. 15 is a sequence diagram illustrating an example of an EAS discovery and subscription request in an embodiment of the present invention.
  • the sequence in FIG. 15 may be based on the following prerequisites 1)-4).
  • the EEC already has the address (e.g., URI (Uniform Resource Identifier)) of the EES. 2) The EEC has already obtained the appropriate security credentials to enable communication with the EES. 3) The EES is configured with an Edge Computing Service Provider (ECSP) policy for EAS discovery. 4) The EEC may optionally obtain a notification target address to be used for subscribing to notifications.
  • URI Uniform Resource Identifier
  • step S401 the EAS provider or EAS user defines and configures the required EAS resources based on the satellite backhaul category information.
  • step S402 the EEC sends an EAS discovery subscription request to the EES.
  • step S403 the EES sends an EAS discovery subscription resource optimization request to the EAS.
  • step S404 the EAS configures the EAS resources based on the satellite backhaul category information.
  • step S405 the EAS sends an EAS discovery subscription resource optimization response to the EES.
  • step S406 the EES performs authorization verification.
  • step S407 the EES sends an EAS discovery subscription response to the EEC.
  • the EES sends an EAS discovery subscription resource optimization request to the EAS.
  • Table 3 is an example of the IE included in the EAS discovery subscription resource optimization request.
  • the EAS discovery subscription resource optimization request may include EAS SatelliteBackhaulCategory, an IE that indicates information about the EAS satellite backhaul category.
  • the EAS sends an EAS discovery subscription resource optimization response to the EES.
  • Table 4 is an example of the IEs included in the EAS discovery subscription resource optimization response.
  • the EAS discovery subscription resource optimization response may include IEs indicating a success response, a failure response and the cause of the failure, an updated EAS profile, a proposed expiration time, a registration ID, and security credentials related to the EAS.
  • Table 5 shows each IE of the EAS service KPIs.
  • EAS service KPIs may include IEs indicating maximum request rate, maximum response time, availability, available compute resources, available graphical compute resources, available memory, available storage, and connection bandwidth.
  • the value of each IE in the EAS Service KPIs may be changed based on the value of the EAS SatelliteBackhaulCategory, which indicates information about the EAS satellite backhaul category.
  • the value to be changed may be set by the edge computing provider or specified by the user. The change may be performed in any of the EAS, EES, and EEC.
  • the above-described embodiment will enable edge application services to be provided according to the satellite backhaul category in the future, when there will be a greater variety of types of satellite communications and the conditions for the edge computing environments placed on satellites connected to terminals will also become more diverse, resulting in both static and dynamic connections to satellites. Furthermore, in edge applications that realize edge computing using satellites, which are scarce and have limited resources, it will become possible to provide optimal resources according to the type of satellite.
  • the base station 10, network node 30, and terminal 20 include functions for performing the above-described embodiments. However, the base station 10, network node 30, and terminal 20 may each have only a portion of the functions of the embodiments.
  • the network node 30 may correspond to the above-described AC, EEC, EDN, EAS, EES, ECS, and core network.
  • FIG. 16 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30.
  • the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140.
  • the functional configuration shown in FIG. 16 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any.
  • the network node 30 may have the same functional configuration as the base station 10.
  • a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.
  • the transmitter 110 includes a function for generating signals to be transmitted to the terminal 20 or other network nodes 30, and transmitting the signals via wired or wireless communication.
  • the receiver 120 includes a function for receiving various signals transmitted from the terminal 20 or other network nodes 30, and for example, obtaining information of higher layers from the received signals.
  • a communication unit including the transmitter 110 and receiver 120 may be configured.
  • the setting unit 130 stores pre-set setting information and various setting information to be sent to the terminal 20 in a storage device, and reads it from the storage device as needed.
  • the setting information includes, for example, information related to edge applications.
  • control unit 140 performs processing related to edge applications in the network.
  • the control unit 140 also performs processing related to communication with the terminal 20.
  • the functional unit in the control unit 140 related to signal transmission may be included in the transmitting unit 110, and the functional unit in the control unit 140 related to signal reception may be included in the receiving unit 120.
  • FIG. 17 is a diagram showing an example of the functional configuration of the terminal 20.
  • the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240.
  • the functional configuration shown in FIG. 17 is merely an example. As long as the operations related to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any.
  • the communication device that becomes the resource holder 20 may have the same functional configuration as the terminal 20.
  • the transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly.
  • the receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals.
  • the receiver 220 also has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL control signals, reference signals, etc. transmitted from the network node 30.
  • a communication unit including the transmitter 210 and receiver 220 may be configured.
  • the setting unit 230 stores various setting information received from the network node 30 by the receiving unit 220 in a storage device, and reads it from the storage device as needed.
  • the setting unit 230 also stores setting information that is set in advance.
  • the content of the setting information may be, for example, information related to edge applications.
  • control unit 240 performs processing related to edge applications in the network.
  • Functional units related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and functional units related to signal reception in the control unit 240 may be included in the receiving unit 220.
  • each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (e.g., wired, wireless, etc.) and these multiple devices.
  • the functional block may be realized by combining the single device or the multiple devices with software.
  • Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment.
  • a functional block (component) that performs transmission functions is called a transmitting unit or transmitter.
  • transmitting unit or transmitter As mentioned above, there are no particular limitations on how these functions are implemented.
  • the network node 30, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure.
  • Figure 18 is a diagram showing an example of the hardware configuration of a base station 10 and terminal 20 in one embodiment of the present disclosure.
  • the network node 30 may have the same hardware configuration as the base station 10.
  • the above-mentioned base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.
  • the term "apparatus" can be interpreted as a circuit, device, unit, etc.
  • the hardware configuration of the base station 10 and terminal 20 may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.
  • the functions of the base station 10 and terminal 20 are realized by loading specific software (programs) onto hardware such as the processor 1001 and storage device 1002, causing the processor 1001 to perform calculations, control communications via the communication device 1004, and control at least one of the reading and writing of data from and to the storage device 1002 and auxiliary storage device 1003.
  • the processor 1001 for example, runs an operating system to control the entire computer.
  • the processor 1001 may be configured as a central processing unit (CPU) that includes an interface with peripheral devices, a control unit, an arithmetic unit, registers, etc.
  • CPU central processing unit
  • control unit 140, control unit 240, etc. may be realized by the processor 1001.
  • the processor 1001 reads programs (program code), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with these.
  • the programs used are those that cause a computer to execute at least some of the operations described in the above-mentioned embodiments.
  • the control unit 140 of the base station 10 shown in FIG. 16 may be stored in the storage device 1002 and implemented by a control program running on the processor 1001.
  • the control unit 240 of the terminal 20 shown in FIG. 17 may be stored in the storage device 1002 and implemented by a control program running on the processor 1001.
  • While the various processes described above have been described as being executed by a single processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001.
  • the processor 1001 may be implemented on one or more chips.
  • the programs may also be transmitted from a network via a telecommunications line.
  • the storage device 1002 is a computer-readable recording medium and may be composed of, for example, at least one of a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), a RAM (Random Access Memory), etc.
  • the storage device 1002 may also be called a register, a cache, a main memory, etc.
  • the storage device 1002 can store executable programs (program code), software modules, etc. for implementing a communication method according to one embodiment of the present disclosure.
  • Auxiliary storage device 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc.
  • the above-mentioned storage medium may be, for example, a database, a server, or other suitable medium that includes at least one of storage device 1002 and auxiliary 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 referred to as a network device, network controller, network card, or communication module, for example.
  • the communication device 1004 may be configured to include high-frequency switches, duplexers, filters, frequency synthesizers, etc. to implement at least one of frequency division duplex (FDD) and time division duplex (TDD).
  • FDD frequency division duplex
  • TDD time division duplex
  • the transmitting/receiving antenna, amplifier unit, transmitting/receiving unit, transmission path interface, etc. may be implemented by the communication device 1004.
  • the transmitting/receiving unit may be implemented as a physically or logically separated transmitting unit and receiving unit.
  • the input device 1005 is an input device (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts input from the outside.
  • the output device 1006 is an output device (e.g., a display, speaker, LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).
  • each device such as the processor 1001 and the storage device 1002, is connected by a bus 1007 for communicating information.
  • the bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
  • the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by this hardware.
  • the processor 1001 may be implemented using at least one of these pieces of hardware.
  • FIG. 19 shows an example configuration of a vehicle 2001.
  • the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013.
  • a communication device mounted on the vehicle 2001 and may be applied to the communication module 2013, for example.
  • the drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.
  • the steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and rear wheels based on the operation of the steering wheel operated by the user.
  • the electronic control unit 2010 is composed of a microprocessor 2031, memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided on the vehicle 2001.
  • the electronic control unit 2010 may also be called an ECU (Electronic Control Unit).
  • Signals from the various sensors 2021-2029 include a current signal from a current sensor 2021 that senses the motor current, a front and rear wheel rotation speed signal obtained by a rotation speed sensor 2022, a front and rear wheel air pressure signal obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.
  • the information service unit 2012 is composed of various devices, such as a car navigation system, audio system, speakers, television, and radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, as well as one or more ECUs that control these devices.
  • the information service unit 2012 uses information obtained from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001.
  • the information service unit 2012 may include input devices that accept input from the outside (e.g., a keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.), and may also include output devices that output to the outside (e.g., a display, speaker, LED lamp, touch panel, etc.).
  • the driving assistance system unit 2030 is composed of various devices that provide functions to prevent accidents and reduce the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices.
  • the driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.
  • the communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port.
  • the communication module 2013 transmits 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, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29, all of which are provided on the vehicle 2001.
  • 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 sends and receives various 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, a mobile station, etc.
  • the communications module 2013 may transmit, via wireless communication, to an external device at least one of the following: signals from the various sensors 2021-2028 input to the electronic control unit 2010; information obtained based on these signals; and information based on input from the outside (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 referred to as input units that accept input.
  • the PUSCH transmitted by the communications module 2013 may include information based on the above input.
  • the communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices 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 that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 2013).
  • the communication module 2013 also stores the various information received from external devices in memory 2032 that can be used by the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc. provided in the vehicle 2001.
  • a network node has a receiving unit that acquires information on a satellite backhaul category, and a control unit that configures resources of an Edge Application Server (EAS) based on the information on the satellite backhaul category.
  • EAS Edge Application Server
  • the above configuration makes it possible to provide optimal resources according to the type of satellite in edge applications that realize edge computing using satellites, which are scarce and limited resources. In other words, it is possible to provide optimal satellite edge computing in an NTN (Non-Terrestrial Network) environment.
  • NTN Non-Terrestrial Network
  • the device may further include a transmitter that transmits a message requesting EAS registration to an Edge Enabler Server (EES), and the receiver receives a response to the message from the EES.
  • EES Edge Enabler Server
  • the receiving unit may further include a transmitting unit that receives a message from an Edge Enabler Server (EES) requesting resource optimization for EAS discovery, including information on the satellite backhaul category, and transmits a response to the message to the EES.
  • EES Edge Enabler Server
  • the control unit may change each IE (Information Element) of KPIs (Key Performance Indicators) related to the EAS service based on the information of the satellite backhaul category.
  • This configuration makes it possible to provide optimal resources according to the type of satellite in edge applications that realize edge computing using satellites, which are scarce and have few resources.
  • a receiving unit that acquires satellite backhaul category information, a control unit that sets AC (Application Client) resources based on the satellite backhaul category information, and a transmitting unit that transmits a message requesting AC registration to an EEC (Edge Enabler Client), and the receiving unit is provided with a terminal that receives a response to the message from the EEC.
  • AC Application Client
  • the above configuration makes it possible to provide optimal resources according to the type of satellite in edge applications that realize edge computing using satellites, which are scarce and limited resources. In other words, it is possible to provide optimal satellite edge computing in an NTN (Non-Terrestrial Network) environment.
  • NTN Non-Terrestrial Network
  • a communication method in which a network node executes a procedure for acquiring satellite backhaul category information and a procedure for configuring EAS (Edge Application Server) resources based on the satellite backhaul category information.
  • EAS Electronic Application Server
  • the above configuration makes it possible to provide optimal resources according to the type of satellite in edge applications that realize edge computing using satellites, which are scarce and limited resources. In other words, it is possible to provide optimal satellite edge computing in an NTN (Non-Terrestrial Network) environment.
  • NTN Non-Terrestrial Network
  • the operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components.
  • the order of processing steps described in the embodiments may be reversed as long as there is no contradiction.
  • the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof.
  • the software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.
  • the notification of information is not limited to the aspects/embodiments described in the present disclosure, and may be performed using other methods.
  • the notification of information may be performed by 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), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination of these.
  • RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • SUPER 3G IMT-Advanced
  • 4G 4th generation mobile communication system
  • 5G 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • xG xG (x is, for example, an integer or decimal number)
  • FRA Full Radio Access Network
  • the present invention may be applied to at least one of systems using IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20 (Ultra-Wideband), Bluetooth (registered trademark), CDMA2000, NR (new 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 (registere
  • certain operations described as being performed by the base station 10 may also be performed by its upper node in some cases.
  • 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 may be performed by at least one of the base station 10 and other network nodes other than the base station 10 (such as, but not limited to, an MME or S-GW). While the above example illustrates a case where there is one other network node other than the base station 10, the other network node may also be a combination of multiple other network nodes (for example, an MME and an S-GW).
  • the information, signals, etc. 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/output via multiple network nodes.
  • Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.
  • the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • software, instructions, information, etc. may be transmitted and received via a transmission medium.
  • a transmission medium such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)
  • wired technology such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)
  • wireless technology such as infrared or microwave
  • the information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies.
  • data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
  • a channel and a symbol may be a signal (signaling).
  • a signal may be a message.
  • a component carrier CC may be called a carrier frequency, a cell, a frequency carrier, etc.
  • system and “network” are used interchangeably.
  • radio resources may be indicated by an index.
  • the names used for the parameters described above are not intended to be limiting in any way. Furthermore, the mathematical formulas using these parameters may differ from those explicitly disclosed in this disclosure.
  • the various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.
  • Base station BS
  • radio base station base station
  • base station device fixed station
  • NodeB nodeB
  • eNodeB eNodeB
  • gNodeB gNodeB
  • base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.
  • a base station can accommodate one or more (e.g., three) cells.
  • a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)).
  • RRH Remote Radio Head
  • the terms "cell” or “sector” refer to part or all of the coverage area of at least one of the base station and base station subsystem that provides communication services within this coverage area.
  • a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.
  • MS Mobile Station
  • UE User Equipment
  • a mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
  • At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc.
  • At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc.
  • the mobile object refers to an object that can move at any speed. Naturally, this also includes cases where the mobile object is stationary.
  • the mobile object examples include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon.
  • the mobile object may also be a mobile object that moves autonomously based on an operation command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned).
  • at least one of the base station and the mobile station may be a device that does not necessarily move during communication operations.
  • at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.
  • the base station in the present disclosure may be read as a user terminal.
  • the aspects/embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)).
  • the terminals 20 may be configured to have the functions possessed by the base station 10 described above.
  • terms such as “uplink” and “downlink” may be read as terms corresponding to communication between terminals (for example, "side”).
  • terms such as uplink channel and downlink channel may be read as side channel.
  • the user terminal in this disclosure may be interpreted as a base station.
  • the base station may be configured to have the functions possessed by the user terminal described above.
  • determining may encompass a wide variety of actions.
  • Determining and “determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching a table, database, or other data structure), and ascertaining something that is considered to be a “determination.”
  • Determining and “determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and so on.
  • judgment and “decision” can include regarding actions such as resolving, selecting, choosing, establishing, and comparing as having been “judgment” or “decision.” In other words, “judgment” and “decision” can include regarding some action as having been “judgment” or “decision.” Furthermore, “judgment (decision)” can be interpreted as “assuming,” “expecting,” “considering,” etc.
  • connection refers to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” to each other.
  • the coupling or connection between elements may be physical, logical, or a combination thereof.
  • “connected” may be read as "access.”
  • two elements may be considered to be “connected” or “coupled” to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.
  • the reference signal may also be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.
  • the phrase “based on” does not mean “based only on,” unless expressly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”
  • any reference to an element using a designation such as "first,” “second,” etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.
  • a and B are different may mean “A and B are different from each other.” Note that this term may also mean “A and B are each different from C.” Terms such as “separate” and “combined” may also be interpreted in the same way as “different.”
  • notification of specified information is not limited to being done explicitly, but may also be done implicitly (e.g., not notifying the specified information).
  • Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Astronomy & Astrophysics (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Theoretical Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Ce nœud de réseau comprend : une unité de réception qui acquiert des informations sur une catégorie de liaison terrestre par satellite ; et une unité de commande qui configure une ressource de serveur d'application périphérique (EAS) sur la base des informations sur la catégorie de liaison terrestre par satellite.
PCT/JP2024/007639 2024-02-29 2024-02-29 Nœud de réseau, terminal et procédé de communication Pending WO2025182045A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2024/007639 WO2025182045A1 (fr) 2024-02-29 2024-02-29 Nœud de réseau, terminal et procédé de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2024/007639 WO2025182045A1 (fr) 2024-02-29 2024-02-29 Nœud de réseau, terminal et procédé de communication

Publications (1)

Publication Number Publication Date
WO2025182045A1 true WO2025182045A1 (fr) 2025-09-04

Family

ID=96920804

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2024/007639 Pending WO2025182045A1 (fr) 2024-02-29 2024-02-29 Nœud de réseau, terminal et procédé de communication

Country Status (1)

Country Link
WO (1) WO2025182045A1 (fr)

Similar Documents

Publication Publication Date Title
WO2025182045A1 (fr) Nœud de réseau, terminal et procédé de communication
WO2025182044A1 (fr) Terminal et procédé de communication
WO2024150282A1 (fr) Nœud de réseau et procédé de commande
WO2024225233A1 (fr) Nœud de réseau et procédé de commande
WO2024201606A1 (fr) Nœud de réseau et procédé de commande
WO2024171467A1 (fr) Nœud de réseau et procédé de commande
WO2025062604A1 (fr) Nœud de réseau et procédé de commande
WO2024209502A1 (fr) Nœud de réseau et procédé de commande
WO2025234008A1 (fr) Nœud de réseau et procédé de communication
WO2025173270A1 (fr) Nœud de réseau, terminal et procédé de communication
WO2025215828A1 (fr) Nœud de réseau et procédé de communication
WO2025074606A1 (fr) Nœud de réseau, station de base et procédé de communication
WO2025258082A1 (fr) Nœud de réseau et station de base
WO2024201605A1 (fr) Nœud de réseau et procédé de commande
WO2025177456A1 (fr) Terminal, station de base, nœud de réseau et procédé de communication
WO2025062603A1 (fr) Nœud de réseau et procédé de commande
WO2025183047A1 (fr) Nœud de réseau et procédé de communication
WO2025062602A1 (fr) Nœud de réseau et procédé de commande
WO2025181995A1 (fr) Terminal, station de base, nœud de réseau et procédé de communication
WO2024185573A1 (fr) Nœud de réseau et procédé de commande
WO2025169394A1 (fr) Nœud de réseau et station de base
WO2025150205A1 (fr) Nœud de réseau, système de communication et procédé de communication
WO2024209503A1 (fr) Nœud de réseau et procédé de commande
WO2025173214A1 (fr) Terminal, nœud de réseau et procédé de communication
WO2025203577A1 (fr) Terminal, nœud de réseau et procédé de communication

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: 24927211

Country of ref document: EP

Kind code of ref document: A1