[go: up one dir, main page]

WO2024146146A1 - Service informatique dans des réseaux - Google Patents

Service informatique dans des réseaux Download PDF

Info

Publication number
WO2024146146A1
WO2024146146A1 PCT/CN2023/113909 CN2023113909W WO2024146146A1 WO 2024146146 A1 WO2024146146 A1 WO 2024146146A1 CN 2023113909 W CN2023113909 W CN 2023113909W WO 2024146146 A1 WO2024146146 A1 WO 2024146146A1
Authority
WO
WIPO (PCT)
Prior art keywords
computing
computing service
message
network
service
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/CN2023/113909
Other languages
English (en)
Inventor
Congchi ZHANG
Mingzeng Dai
Lizhuo ZHENG
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.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
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 Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2023/113909 priority Critical patent/WO2024146146A1/fr
Publication of WO2024146146A1 publication Critical patent/WO2024146146A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/303—Terminal profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/24—Negotiation of communication capabilities

Definitions

  • the present disclosure relates to wireless communications, and more specifically to methods and apparatuses to support a computing service in a network, for example, a computing power network.
  • a wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • Each network communication devices such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology.
  • the wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) .
  • 6G network is visioned to be a computing power network, wherein the computing capability of 6G network (including the computing capability of radio access network (RAN) , core network (CN) , mobile edge computing (MEC) , or cloud supported by the 6G network) is expected to be open to support computing tasks of third-party applications, also known as computing as a service.
  • RAN radio access network
  • CN core network
  • MEC mobile edge computing
  • cloud supported by the 6G network is expected to be open to support computing tasks of third-party applications, also known as computing as a service.
  • some implementations of the methods and apparatuses described herein may include: receiving, at a first apparatus and from a third apparatus, a first message for requesting a computing service; and transmitting a second message to the third apparatus, wherein the second message comprises address information for the computing service from a second apparatus capable of the computing service.
  • the condition comprises one of the following: whether the second apparatus has required computing resources; a communication quality between the second apparatus and the third apparatus; or computing service continuity of the second apparatus.
  • some implementations of the methods and apparatuses described herein may include: transmitting a discovery request message to an NRF to initiate a service discovery procedure for requesting information of at least one network function capable of a computing service.
  • the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20.
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • a UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink.
  • a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
  • a network entity 102 may support communications with the core network 106, or with another network entity 102, or both.
  • a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) .
  • the network entities 102 may communicate with each other directly (e.g., between the network entities 102) .
  • the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) .
  • a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, or any combination thereof.
  • CU central unit
  • DU distributed unit
  • RU radio unit
  • RIC RAN Intelligent Controller
  • RIC e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC)
  • SMO Service Management and Orchestration
  • the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
  • RRC Radio Resource Control
  • SDAP service data adaption protocol
  • PDCP Packet Data Convergence Protocol
  • the CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access
  • the core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway Packet Data Network gateway
  • UPF user plane function
  • the wireless communications system 100 may also include an MEC 120 provide computing services for a UE 104 and other entities.
  • the MEC 120 may communicate with the network entity 102 via a link 122 and communicate with the core network 106 via a link 124.
  • the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) .
  • the network entities 102 and the UEs 104 may support different resource structures.
  • the network entities 102 and the UEs 104 may support different frame structures.
  • the network entities 102 and the UEs 104 may support a single frame structure.
  • a time interval of a resource may be organized according to frames (also referred to as radio frames) .
  • Each frame may have a duration, for example, a 10 millisecond (ms) duration.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) .
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) .
  • FR1 410 MHz –7.125 GHz
  • FR2 24.25 GHz –52.6 GHz
  • FR3 7.125 GHz –24.25 GHz
  • FR4 (52.6 GHz –114.25 GHz)
  • FR4a or FR4-1 52.6 GHz –71 GHz
  • FR5 114.25 GHz
  • the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) .
  • FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
  • FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) .
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) .
  • FIG. 1B illustrates an exemplary diagram 130 of evolution to a computing power network.
  • the computing may be performed at the UE 104 and the application server 118, and the RAN 102 and the core network 106 may transfer computing tasks between the UE 104 and the application server 118.
  • the computing capability of the network (including the computing capability of RAN and CN, as well as the computing capability of MEC or cloud supported by the network) is expected to be open up to support computing tasks of third-party applications (APPs) .
  • APPs third-party applications
  • FIG. 1C illustrates an exemplary deployment 150 of computing task deployments in a computing power network.
  • the client and server sides of APP are running on the UE 104 and application server 118 as usual.
  • the UE 104 or application server 118 may request the network to provide the computing service.
  • the RAN 102 or CN 106 may create and deploy a dedicated container (that shares the same operating system and hardware as 6G network functions but running in a separate/isolated environment) to support the third party application computing tasks.
  • FIG. 1D illustrates an exemplary diagram of a network architecture 180 that supports a computing service in a computing power network, in accordance with aspects of the present disclosure.
  • the core network 106 may comprise an AF 203-2, a Network Exposure Function (NEF) 551, an Access and Mobility Management function (AMF) 351, a User Plane Function (UPF) 352, a Session Management Function (SMF) 353, an NRF 651 and an NF 202-2 at CN side that is capable of providing a computing service.
  • NEF Network Exposure Function
  • AMF Access and Mobility Management function
  • UPF User Plane Function
  • SMF Session Management Function
  • Some embodiments of the present disclosure propose to achieve the deployment by introducing a new Core Network Function built-in the 3GPP core network, which may be named as Computing Service Coordination Function (CSCF) .
  • the core network 106 may also comprise a CSCF 201.
  • CSCF Computing Service Coordination Function
  • the name of this function is provided for the purpose of illustration without suggesting any limitations, and this function may be named differently, such as a computing task coordination function, or the like.
  • the MEC 120 may comprise an NF 202-3 at MEC side that is capable of providing a computing service.
  • the RAN 102 may comprise an NF 202-1 at RAN side that is capable of providing a computing service.
  • the CSCF 201 may connect to the CN via an interface of Ncscf as an example.
  • the RAN 102 may also connect to the CN via an interface of Nran as an example.
  • Some embodiments of the present disclosure may apply to a 6G computing power network, and the name of each network function is only exemplary.
  • the network function providing the same functionality/service may be named differently.
  • the mentioned network functions provide at least the following concerned functionalities/services.
  • Packet inspection e.g. application detection based on service data flow template and the optional Packet Flow Detections (PFDs) received from the SMF 353 in addition
  • PFDs Packet Flow Detections
  • 4G/5G Network is orchestrated by OAM
  • Cloud is orchestrated by another system, saying cloud orchestrator.
  • the dynamic computing resources sharing between Network and Cloud are not supported.
  • the second apparatus 202 receives 217 the third message and transmits 218 a fourth message 219 to the first apparatus.
  • the second apparatus 202 may indicate an acceptance of the computing service and include address information for the computing service from the second apparatus in the fourth message.
  • the first apparatus 201 receives 220 the fourth message.
  • a computing session may be set up 224 between the second apparatus 202 and the third apparatus 203.
  • the third apparatus 203 may transmit a request message for a computing session setup to the second apparatus 202.
  • the request message may comprise an environment configuration related to the computing service.
  • the request message may be transmitted via a PDU session for the computing service.
  • the environment configuration may comprise a list of software dependencies, a list of required software packages, and/or an address to fetch an image file from an application server.
  • the first apparatus 201 may subscribe to a computing resource status of the at least one network function by transmitting a subscription message to the at least one network function.
  • the at least one network function e.g., the second apparatus 202
  • FIG. 3 illustrates an exemplary procedure 300 that supports a computing service in a computing power network, in accordance with aspects of the present disclosure.
  • the procedure 300 can be an example of the process 200 as shown in FIG. 2.
  • the procedure 300 may involve a CSCF 201, a UE 203-1, a RAN side NF 202-1, a CN side NF 202-2, an MEC side NF 202-3, an AMF 351, an UPF 352 and an SMF 353.
  • the CSCF 201 could be an example of the first apparatus 201 in FIG. 2;
  • the UE 203-1 could be an example of the third apparatus 203 in FIG. 2;
  • the RAN side NF 202-1, the CN side NF 202-2 and an MEC side NF 202-3 could be an example of the second apparatus 202 in FIG. 2, and they are capable of a computing service.
  • the computing service is requested by a UE.
  • a UE facing computing overload may request computing service from a computing power network by sending a Computing Service Request message (e.g., a non-access stratum (NAS) message) towards a dedicated NF, e.g., a CSCF.
  • a Computing Service Request message e.g., a non-access stratum (NAS) message
  • NAS non-access stratum
  • the CSCF will select a proper NF that can provide the requested computing service and informs the UE about the computing service NF address information.
  • the UE can establish a computing session towards the provided computing service NF address.
  • the selected computing service provider NF can be a NF at the RAN side, CN side or MEC side, the UE first establishes a regular PDU session towards the SMF, and the later messages to establish the computing session are routed by the UPF towards the computing service NF address or towards the UE.
  • NF at the RAN side could be a dedicated RAN Network Function for computing service, or could be a Network Function offered by RAN node, or service-based RAN Central Unit Control Plane (CU-CP) or service-based RAN Central Unit Computing Plane in case of split RAN architecture.
  • NF at the RAN side could be a sub Network Function of other RAN NFs.
  • the CSCF 201 may consider if the selected NF can serve the UE with good communication quality (e.g., high reliability, low latency) considering UE location and network condition. Alternatively, or additionally, the CSCF 201 may consider if the selected NF can ensure some level of computing service continuity, e.g., the CSCF 201 may select a RAN side NF for computing service if the UE is stationary, or the CSCF 201 may select a CN side NF or MEC side NF for computing service if the UE is in move.
  • the selected NF can serve the UE with good communication quality (e.g., high reliability, low latency) considering UE location and network condition.
  • the CSCF 201 may consider if the selected NF can ensure some level of computing service continuity, e.g., the CSCF 201 may select a RAN side NF for computing service if the UE is stationary, or the CSCF 201 may select a CN side NF or MEC side NF
  • steps 401 to 409 could be the same as steps 301 to 309 in procedure 300.
  • steps 401 to 409 will not be described repeatedly.
  • RAN node performs traffic filtering to understand if the traffic is for the RAN side NF 202-1 for computing service.
  • traffic filtering may be based on whether the target IP address is same as the IP address provided by the RAN side NF 202-1 for computing service at 406.
  • traffic filtering may be based on whether the network slice ID, QoS flow ID, or radio bearer ID associated with the uplink transmission is dedicated for the computing service.
  • FIG. 5 illustrates yet another exemplary procedure 500 that supports a computing service in a computing power network, in accordance with aspects of the present disclosure.
  • the procedure 500 can be an example of the process 200 as shown in FIG. 2.
  • the procedure 500 may involve a CSCF 201, a RAN side NF 202-1, a CN side NF 202-2, an MEC side NF 202-3, an NEF 551, an AF 203-2 and an APP server 552.
  • the CSCF 201 could be an example of the first apparatus 201 in FIG. 2;
  • the AF 203-2 could be an example of the third apparatus 203 in FIG. 2;
  • the RAN side NF 202-1, the CN side NF 202-2 and an MEC side NF 202-3 could be an example of the second apparatus 202 in FIG. 2, and they are capable of a computing service.
  • the CSCF 201 subscribes to the computing resource status information from NFs that capable of computing services, which will be described later by referring to FIG. 6.
  • An APP server running an application e.g., VR
  • the AF 203-2 associated with the APP server initiates the procedure to request computing service from the network.
  • the Computing Service Request (e.g., HTTP/HTTPS) message may be transferred to the NEF 551 first and then forwarded by the NEF 551 to the CSCF 201 only if the NEF 551 determines the AF 203-2 is authorized to request for computing service.
  • HTTP/HTTPS HyperText Transfer Protocol
  • the selected computing service NF node (e.g., the RAN side NF 202-1) generates and sends an Nnfname_ComputingService_Response message to the CSCF 201, which may further contain address information for the computing service from the computing service NF such as IP or FQDN.
  • some embodiments of the present disclosure provide a solution that supports dynamic computing service based on a request from a UE.
  • the UE mobility factor can be considered, e.g., RAN side computing service may be only used if the UE is rather stationary.
  • some embodiments of the present disclosure provide a solution that supports dynamic computing service based on a request from an AF.
  • the AF only knows the address information (e.g., IP address) providing the computing service, while they do not need to know where the computing service is located in the computing power network. Network does not need to expose sensitive information.
  • the NF 202 can be any of an NF at RAN side, an NF at CN side, or an NF at MEC side.
  • the NF at RAN side could be a dedicated RAN Network Function for computing service, or could be Network Function offered by RAN node, or service-based RAN Central Unit Control Plane (CU-CP) or service-based RAN Central Unit Computing Plane in case of split RAN architecture.
  • the NF at RAN side could be a sub Network Function of other RAN NFs.
  • the NF at CN side could be a dedicated Core Network Function for computing service, or a Sub Network Function offered by NWDAF, or AIML Function, or a Data Analysis Function, or a Data Processing Function.
  • the NF at MEC side could be a Network Function offered by MEC Node.
  • the NF 202 capable of computing service registers the computing service in the NRF 651 by sending an Nnrf_NFManagement_NFRegister_Request message to the NRF 651, wherein the message includes computing service capability information.
  • the computing service capability may be represented by absolute values such as: the supported computing type (s) , e.g., AIML DNN, AIML CNN, AIML GAN or non AIML; the supported operating system (s) , e.g., Linux, Debian, Ubuntu, CentOS; the CPU/GPU/DPU/FPGA capability, e.g., max number of CPUs/GPUs/DPUs/FPAGs, and versions of them; the storage capability, e.g., max storage space in unit of GibiByte or GigaByte; the memory capability, e.g., max memory space in unit of GibiByte or GigaByte; and/or the computing capability per second, e.g., FLOP
  • the computing service capability may be represented by abstractive values such as a level value N within [1, 100] reflecting the computing capability in general.
  • the Nnrf_NFManagement_NFRegister_Request may further contain information such as an NF type, NF instance ID, FQDN or IP address of NF.
  • the NRF 651 replies the CSCF 201 an Nnrf_NFDiscovery_Request_Response message, which includes information about the computing service capable NF (s) as requested by the CSCF 201.
  • the information may include a set of NF instances, and/or a validity period for the discovery result, and per NF instance may include an NF type, NF instance ID, FQDN or IP address (es) of the NF instance, and computing service capability information (as listed at 601) .
  • the CSCF 201 decides to subscribe to the computing resource status of a computing service capable NF by sending an Nnfname_ComputingResourcesStatusSubscribe_Request message to the concerned NF.
  • the NF 202 accepts the subscription by replying an Nnfname_ComputingResourcesStatusSubscribe_Response message.
  • the NF 202 notifies the CSCF 201 using an Nnfname_ComputingResourcesStatusNotify message, which may contain absolute values such as: the available/occupied number of CPUs/GPUs/DPUs/FPAGs, and versions of them; the available/occupied storage space in unit of GibiByte or GigaByte; the available/occupied memory space in unit of GibiByte or GigaByte; and/or the available/occupied FLOPS.
  • it may contain abstractive values representing available/occupied computing resource status such as a level value N within e.g. [1, 100] .
  • it may contain a percentage value N%which represents the available/occupied computing resource comparing to its maximal capability.
  • the NF 202 may trigger the computing resource status notification upon receiving an explicit request from the CSCF 201. Additionally, or alternatively, the NF 202 may trigger the computing resource status notification periodically upon a periodicity value provided by CSCF 201. Additionally, or alternatively, the NF 202 may trigger the computing resource status notification upon certain event, e.g., the level of the computing resource status changes.
  • FIG. 7 illustrates an example of a device 700 that supports a computing service in a computing power network in accordance with aspects of the present disclosure.
  • the device 700 may be an example of the first apparatus 201 (e.g., the CSCF 201) , the second apparatus 202 (e.g., the RAN side NF 202-1, the CN side NF 202-2, or the MEC side NF 202-3) or the third apparatus 203 (e.g., the UE 203-1 or the AF 203-2 or the APP server 552) as described herein.
  • the device 700 may support wireless communication with the first apparatus 201, the second apparatus 202, the third apparatus 203 and other entities, or any combination thereof.
  • the processor 702, the memory 704, the transceiver 706, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 702 and the memory 704 coupled with the processor 702 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704) .
  • the processor 702 may support wireless communication at the device 700 in accordance with examples as disclosed herein.
  • the processor 702 may be configured to operable to support a means for receiving, from a third apparatus, a first message for requesting a computing service; and a means for transmitting a second message to the third apparatus, wherein the second message comprises address information for the computing service from a second apparatus capable of the computing service.
  • the processor 702 may be configured to operable to support a means for receiving, from a first apparatus, a third message for requesting a computing service for a third apparatus; and a means for transmitting a fourth message to the first apparatus, wherein the fourth message indicates an acceptance of the computing service and address information for the computing service from the second apparatus.
  • the processor 702 may be configured to operable to support a means for transmitting, to a first apparatus, a first message for requesting a computing service; and a means for receiving a second message from the first apparatus, wherein the second message comprises address information for the computing service from a second apparatus capable of the computing service.
  • the I/O controller 708 may manage input and output signals for the device 700.
  • the I/O controller 708 may also manage peripherals not integrated into the device M02.
  • the I/O controller 708 may represent a physical connection or port to an external peripheral.
  • the I/O controller 708 may utilize an operating system such as or another known operating system.
  • the I/O controller 708 may be implemented as part of a processor, such as the processor 706.
  • a user may interact with the device 700 via the I/O controller 708 or via hardware components controlled by the I/O controller 708.
  • the device 700 may include a single antenna 710. However, in some other implementations, the device 700 may have more than one antenna 710 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 706 may communicate bi-directionally, via the one or more antennas 710, wired, or wireless links as described herein.
  • the transceiver 706 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 706 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 710 for transmission, and to demodulate packets received from the one or more antennas 710.
  • the transceiver 706 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 710 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • the processor 800 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • the controller 802 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein.
  • the controller 802 may operate as a control unit of the processor 800, generating control signals that manage the operation of various components of the processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 802 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 804 and determine subsequent instruction (s) to be executed to cause the processor 800 to support various operations in accordance with examples as described herein.
  • the controller 802 may be configured to track memory address of instructions associated with the memory 804.
  • the controller 802 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 802 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein.
  • the controller 802 may be configured to manage flow of data within the processor 800.
  • the controller 802 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 800.
  • ALUs arithmetic logic units
  • the memory 804 may include one or more caches (e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800) . In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800) .
  • caches e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800) . In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800) .
  • the processor 800 may be configured to or operable to support a means for transmitting, to a first apparatus, a first message for requesting a computing service; and a means for receiving a second message from the first apparatus, wherein the second message comprises address information for the computing service from a second apparatus capable of the computing service.
  • the method 900 may further include transmitting, to the second apparatus, a third message for requesting the computing service from the second apparatus.
  • the third message comprises an ID of the third apparatus.
  • the information of the at least one network function comprises one of the following: a set of network function instances, each of which comprises one of a network function type, a network function instance ID, an FQDN, an IP address, and computing service capability information; or a validity period for a discovery result.
  • the method 900 may further include: transmitting, to the at least one network function, a subscription message to subscribe to a computing resource status of the at least one network function; and receiving, from the at least one network function, a response message indicative of an acceptance of the subscription.
  • the method 900 may further include: receiving, from the at least one network function, a notification message in case of a change of the subscribed computing resource status.
  • the method may include receiving, from a first apparatus, a third message for requesting a computing service for a third apparatus.
  • the operations of receiving the first configuration may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of receiving the first configuration may be performed by a device as described with reference to FIG. 1D.
  • the method 1000 may further include: registering, using a register request message, computing service capability information to an NRF; receiving a response message from the NRF.
  • the method 1000 may further include: receiving, from the first apparatus, a subscription message for subscribing to a computing resource status of the second apparatus; and transmitting, to the first apparatus, a response message indicative of an acceptance of the subscription.
  • the method may include transmitting, to a first apparatus, a first message for requesting a computing service.
  • the operations of receiving the first configuration may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of receiving the first configuration may be performed by a device as described with reference to FIG. 1D.
  • the request message is transmitted via a PDU session for the computing service.
  • the environment configuration comprises one of the following: a list of software dependencies; a list of required software packages; or an address to fetch an image file from an application server.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation concernent des procédés et des appareils pour prendre en charge un service informatique dans un réseau, par exemple, un réseau énergétique informatique. Selon un aspect, un premier appareil reçoit un premier message pour demander un service informatique et transmet un second message comprenant des informations d'adresse pour le service informatique d'un second appareil capable d'exécuter le service informatique. Le second appareil peut être sélectionné parmi un réseau comprenant un réseau d'accès radio (RAN), un réseau central (CN), une informatique périphérique mobile (MEC) ou un nuage. De cette manière, une structure unifiée peut utiliser pleinement les ressources informatiques dans le réseau énergétique informatique et peut fournir un service informatique dynamique sur la base d'une demande.
PCT/CN2023/113909 2023-08-18 2023-08-18 Service informatique dans des réseaux Pending WO2024146146A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/113909 WO2024146146A1 (fr) 2023-08-18 2023-08-18 Service informatique dans des réseaux

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/113909 WO2024146146A1 (fr) 2023-08-18 2023-08-18 Service informatique dans des réseaux

Publications (1)

Publication Number Publication Date
WO2024146146A1 true WO2024146146A1 (fr) 2024-07-11

Family

ID=91803484

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/113909 Pending WO2024146146A1 (fr) 2023-08-18 2023-08-18 Service informatique dans des réseaux

Country Status (1)

Country Link
WO (1) WO2024146146A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114073059A (zh) * 2019-03-29 2022-02-18 三星电子株式会社 用于在无线通信系统中提供边缘计算服务的设备和方法
CN115769615A (zh) * 2020-08-03 2023-03-07 英特尔公司 用于下一代蜂窝网络的计算服务实现
US20230132454A1 (en) * 2021-10-28 2023-05-04 Samsung Electronics Co., Ltd. Method and apparatus for supporting edge computing service for roaming ue in wireless communication system
US20230247418A1 (en) * 2020-09-30 2023-08-03 Huawei Technologies Co., Ltd. Network edge computing method and communication apparatus

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114073059A (zh) * 2019-03-29 2022-02-18 三星电子株式会社 用于在无线通信系统中提供边缘计算服务的设备和方法
CN115769615A (zh) * 2020-08-03 2023-03-07 英特尔公司 用于下一代蜂窝网络的计算服务实现
US20230247418A1 (en) * 2020-09-30 2023-08-03 Huawei Technologies Co., Ltd. Network edge computing method and communication apparatus
US20230132454A1 (en) * 2021-10-28 2023-05-04 Samsung Electronics Co., Ltd. Method and apparatus for supporting edge computing service for roaming ue in wireless communication system

Similar Documents

Publication Publication Date Title
WO2024079365A1 (fr) Gestion de notification pour activation d'apprentissage fédéré vertical
WO2025145681A1 (fr) Évitement de collision d'id temporaires d'as pour dispositifs aiot
WO2024183312A1 (fr) Procédés et appareils pour des procédures ltm intra-bs et inter-bs
WO2024146146A1 (fr) Service informatique dans des réseaux
WO2024156388A1 (fr) Support d'enregistrement pour activation d'apprentissage fédéré vertical
US20250358726A1 (en) Techniques for indirect network sharing
WO2025030889A1 (fr) Double connectivité dans une architecture basée sur un service
WO2024109166A1 (fr) Changement de trajet indirect dans un trajet multiple
WO2025060464A1 (fr) Procédé et appareil de prise en charge d'applications d'intelligence artificielle (ia) dans des communications sans fil
WO2024109199A1 (fr) Détermination de fonction de réseau
WO2025035789A1 (fr) Détection et mise à jour de dispositif aiot
WO2025107663A1 (fr) Procédés et appareils d'un mécanisme d'optimisation de robustesse de mobilité (mro) pour une procédure ultérieure conditionnelle d'ajout ou de changement de cellule de groupe de cellules secondaires primaires (pscell) (cpac)
WO2025241556A1 (fr) Procédé et appareil de prise en charge de l'internet des objets ambiant (aiot)
WO2024139379A1 (fr) Établissement d'une connexion de plan utilisateur à des fins de détection
WO2025118648A1 (fr) Sélection de fonction de plan utilisateur
WO2025218260A1 (fr) Gestion de mobilité d'ue de détection
WO2024098839A1 (fr) Ajout de trajet indirect pour communication u2n
WO2024093439A1 (fr) Ajout ou libération de trajet dans un trajet multiple inter-gnb
WO2024198474A1 (fr) Atténuation de conflit dans un ric proche-rt
WO2024119887A1 (fr) Commande de règle et de facturation pour réseau électrique informatique
WO2025213788A1 (fr) Établissement d'une session informatique
WO2025077264A1 (fr) Procédé et appareil de prise en charge de rapport de faisceau
WO2025148426A1 (fr) Procédés et appareils de gestion de communication entre un ue distant et un ue relais à sauts multiples
US20250141753A1 (en) Interfacing services of an application data analytics enabler server
WO2024109130A1 (fr) Prise en charge de l'établissement de rapport de mesure de rendement clé (kpm) multicellulaire

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

Country of ref document: EP

Kind code of ref document: A1