Communication method and device for computing power service

Abstract

The embodiment of the invention relates to a communication method and device for computing power service. The communication method comprises the following steps: determining an internet protocol IP address used by computing power service; and sending the message of the computing power service by using the IP address. In this way, the connection path between the terminal device and the computing power node can be optimized, so that the time delay is reduced.

Description

Technical Field

[0001] This disclosure relates to the field of communications, and more specifically to communication methods, apparatus, systems, computer-readable storage media, and computer program products for computing services. Background Technology

[0002] With the rise of commercial network deployments and industry applications, the demand for computing resources (computing power) is increasing. Currently, the actual deployment location of cloud edge computing nodes in wireless networks typically corresponds to the local user plane function (UPF) of the core network. Correspondingly, the connection between user equipment (UE) and cloud edge computing nodes is achieved through the UPF, which serves as the anchor point for the UE's Internet Protocol (IP) protocol. Under this mechanism, it is impossible to achieve the optimal connection path between the UE and the cloud edge computing node.

[0003] Some communication scenarios have high real-time requirements for computing tasks. In future-generation mobile communication systems, cloud edge computing nodes can be deployed closer to the network edge of the access side, thereby improving mobile network speed, reducing latency, and enhancing connection reliability. The connection between the UE and cloud edge computing nodes still requires further research and improvement to optimize its performance. Summary of the Invention

[0004] This disclosure provides an example embodiment of an IP address management scheme for computing power services, and relates to communication methods, apparatus, systems, computer-readable storage media, and computer program products.

[0005] In a first aspect of this disclosure, a communication method is provided, applicable to communication devices (e.g., terminal devices) and chips. The method includes: determining an Internet Protocol (IP) address for use as a computing power service; and sending a message for the computing power service using the IP address. This allows the terminal device to be assigned an IP address for the computing power service without needing to be anchored to a UPF (User-Defined Pointer). In this way, the connection path between the terminal device and the computing power node can be optimized, thereby reducing latency. In one possible implementation, the IP address is used exclusively for the computing power service.

[0006] In some embodiments, determining the IP address used for computing power services includes: determining the IP address for use by the computing power services based on at least one of the following: local configuration of the terminal device; or receiving a first message. The first message includes at least one of the following: an IP address; or first indication information indicating that the IP address is used for computing power services. In some implementations, the first message may be a broadcast message or a multicast message. In some implementations, the first message may be a unicast message. Different terminal devices may use the same IP address for computing power services. In this way, the IP address used for computing power services can be determined, thereby optimizing the connection path between the terminal device and the computing power node, thereby reducing latency. In one possible implementation, determining the IP address in this disclosure may also be enabling the IP address.

[0007] In some embodiments, the method further includes receiving a second message including an IP address. In some implementations, the second message may be a unicast message. The IP address may be device-specific. In other words, different terminal devices use different IP addresses for computing power services. In this way, the IP address of the terminal device used for computing power services can be obtained, thereby optimizing the connection path between the terminal device and the computing power node and reducing latency.

[0008] In some embodiments, determining the IP address used for the computing power service includes: determining the IP address for the computing power service based on at least one of the following: a second message including second indication information indicating that the IP address is used for the computing power service; local configuration of the terminal device; or the second message including the IP address. In this manner, the terminal device can determine that the received IP address is used for the computing power service, and thus can use the IP address in the computing power service.

[0009] In some embodiments, the method further includes sending a first request message. The first request message is used for at least one of the following: registering on the network, obtaining an IP address, or establishing a default connection used to transmit the first packet for the computing power service. In this manner, an IP address for the computing power service can be received based on sending the first request message.

[0010] In some embodiments, the first request message includes third indication information, which indicates a request for IP address allocation. In this way, the terminal device can explicitly request the allocation of an IP address for computing power services via the indication information.

[0011] In some embodiments, the IP address is a first IP address, and the method further includes: determining a second IP address for use by the computing power service based on the replacement of the access network equipment by the terminal device. In this way, the terminal device can access the computing power service using the newly allocated IP address after the access network equipment is replaced, without having to return to the anchor point of the original IP address, thereby optimizing the path and reducing latency.

[0012] In some embodiments, determining the second IP address for computing power services based on the replacement of the access network device by the terminal device includes: determining the acquisition of the second IP address when the terminal device replaces the access network device based on at least one of the following: a second message including fourth indication information, the fourth indication information indicating that the second IP address for computing power services should be acquired when the terminal device replaces the access network device; local configuration of the terminal device; or the second message including a first IP address. For example, based on receiving an IP address for computing power services, the terminal device can determine to replace (i.e., reacquire) the IP address for computing power services when the access network device is replaced. In this way, the terminal device can reacquire the IP address for computing power services after replacing the access network device.

[0013] In a second aspect of this disclosure, a method for communication is provided. This method can be applied to communication devices (e.g., network devices) and chips. The method includes: determining the Internet Protocol (IP) address used by a terminal device for computing power services; and sending at least one of the following to the terminal device: the IP address; or first indication information, the first indication information indicating that the IP address is used for computing power services. This allows the terminal device to access computing power services using the IP address used for computing power services, without having to be anchored at a UPF (User-Defined Node). In this way, the connection path between the terminal device and the computing power node can be optimized, thereby reducing latency.

[0014] In some embodiments, the method further includes: allocating an IP address to a terminal device or determining whether the terminal device is allowed to use an IP address for computing power services based on at least one of the following: determining that an IP address has not yet been allocated to the terminal device; determining that the terminal device is allowed to use computing power services; local configuration; the terminal device's subscription data; policy information; or receiving a first request message, the first request message being used for at least one of the following: registering to the network, obtaining an IP address for use in computing power services, or establishing a default connection, the default connection being used to transmit the first packet of computing power services. In this way, an IP address for computing power services can be allocated to the terminal device or the terminal device can be enabled to use an IP address for computing power services, thereby optimizing the connection path between the terminal device and the computing power node and reducing latency. In one possible implementation, using an IP address for computing power services in this disclosure can also be enabling an IP address for computing power services.

[0015] In some embodiments, the first request message includes third indication information, which indicates a request to allocate an IP address. In this way, the network device can allocate an IP address to the terminal device based on the indication information displayed by the terminal device requesting the allocation of an IP address for computing power services.

[0016] In some embodiments, the IP address is a first IP address, and the method further includes sending at least one of the following: fourth indication information, indicating that a second IP address for use in computing power services is obtained when the terminal device changes its access network equipment; or second indication information, indicating that the IP address is used for computing power services. The second indication information enables the terminal device to determine that the IP address is used for computing power services. The fourth indication information enables the terminal device to re-obtain the IP address for use in computing power services after changing the access network equipment. This optimizes the connection path between the terminal device and the computing power node, thereby reducing latency.

[0017] In some embodiments, the method further includes: sending fifth indication information, the fifth indication information indicating at least one of the following: replacing the source IP address in a message sent from the terminal device to the computing power node of the computing power service; or replacing the destination IP address in a message sent from the computing power node of the computing power service to the terminal device. Thus, the IP address of the terminal device used for computing power services can be replaced during message transmission. In this way, the IP address of the terminal device used for computing power services may not have an anchor point, thereby optimizing the connection path between the terminal device and the computing power node and reducing latency.

[0018] In some embodiments, the method further includes: receiving fifth indication information, the fifth indication information indicating at least one of the following: replacing the source IP address in a message sent from the terminal device to the computing power node; or replacing the destination IP address in a message sent from the computing power node to the terminal device. Thus, the IP address of the terminal device used for computing power services can be replaced during message transmission. In this way, the IP address of the terminal device used for computing power services may not have an anchor point, thereby optimizing the connection path between the terminal device and the computing power node and reducing latency.

[0019] In some embodiments, the method further includes: receiving a message from a terminal device, the message carrying an IP address; replacing the source IP address in the message with a third IP address associated with the terminal device; and sending the message including the third IP address to a computing power node providing the computing power service. This allows the IP address in the terminal device's message to be replaced at the network device. In this way, the IP address used by the terminal device for the computing power service may not have an anchor point, thereby optimizing the connection path between the terminal device and the computing power node and reducing latency.

[0020] In some embodiments, the method further includes: determining a third IP address associated with a terminal device; and storing a correspondence between the third IP address and at least one of the following: an identifier of the terminal device; information about computing power services; or an IP address. In this way, the IP address of the terminal device used for computing power services can be replaced with the allocated IP address of the terminal device, allowing different terminal devices to use the same IP address for computing power services. Therefore, the IP address of the terminal device used for computing power services may not have an anchor point, thereby optimizing the connection path between the terminal device and the computing power node and reducing latency.

[0021] In some embodiments, determining the third IP address associated with the terminal device includes: determining the third IP address based on received fifth indication information or based on received packets. The fifth indication information indicates at least one of the following: replacing the source IP address in a packet sent from the terminal device to the computing power node; or replacing the destination IP address in a packet sent from the computing power node to the terminal device. In this way, an IP address can be assigned to the terminal device for replacement with the IP address used for computing power services.

[0022] In some embodiments, determining a third IP address associated with a terminal device includes determining the third IP address based on the absence of a stored mapping associated with the terminal device. This avoids repeatedly assigning IP addresses to the terminal device for replacing IP addresses used for computing services. Furthermore, assigning IP addresses to the terminal device for replacing IP addresses used for computing services can be done with less signaling overhead. This reduces signaling overhead and resource consumption.

[0023] In some embodiments, the method further includes: receiving a downlink packet including a third IP address from a computing node; replacing the destination IP address in the downlink packet with an IP address based on a correspondence; and sending a downlink packet including the IP address to a terminal device. In this way, the connection path between the terminal device and the computing node used for the downlink packet can be optimized, thereby reducing latency.

[0024] In some embodiments, the terminal device switches from a first network device to a second network device. The method further includes: the first network device sending a sixth indication message or a seventh indication message to the second network device, the sixth indication message indicating permission for the terminal device to use computing power services, and the seventh indication message indicating the allocation of an IP address for the terminal device to use computing power services, wherein the first network device is a first access network device or a first core network device, and the second network device is a second access network device or a second core network device. In this manner, the terminal device can regain an IP address for use with computing power services.

[0025] In some embodiments, the IP address is a first IP address, and the terminal device switches from a first network device to a second network device. The method further includes: the second network device receiving a sixth indication message or a seventh indication message from the first network device, the sixth indication message indicating permission for the terminal device to use computing power services, and the seventh indication message indicating the allocation of an IP address for the terminal device to use computing power services; and sending a second message to the terminal device, the second message including a second IP address for the computing power services. In this manner, the terminal device can reacquire an IP address for the computing power services.

[0026] In some embodiments, the IP address is a first IP address, and the terminal device switches from a first access network device to a second access network device. The method further includes: the second access network device sending a second request message to a core network device, the second request message requesting the allocation of an IP address for computing power services for the terminal device; receiving a second message from the core network device, the second message including a second IP address for computing power services; and sending the second message to the terminal device. In this manner, the terminal device can reacquire an IP address for computing power services.

[0027] In some embodiments, the IP address is a first IP address. When a terminal device switches from a first access network device to a second access network device, the method further includes: the core network device receiving a second request message from the second access network device, the second request message being used to request the allocation of an IP address for computing power services for the terminal device; determining a second IP address for computing power services; and sending a second message to the second access network device, the second message including the second IP address. In this manner, the terminal device can regain an IP address for computing power services.

[0028] In a third aspect of this disclosure, a communication apparatus is provided. The communication apparatus includes a unit or module for performing any method according to the first aspect and its implementation, or for performing any method according to the second aspect and its implementation.

[0029] In a fourth aspect of this disclosure, a communication apparatus is provided. The communication apparatus includes a processor configured to perform any method according to the first aspect and its implementation, or configured to perform any method according to the second aspect and its implementation.

[0030] In a fifth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when executed by a device, cause the device to perform any method according to the first aspect and its implementation, or cause the device to perform any method according to the second aspect and its implementation.

[0031] In a sixth aspect of this disclosure, a computer program product is provided. The computer program product includes instructions that, when executed by a device, cause the device to perform any method according to the first aspect and its implementation, or cause the device to perform any method according to the second aspect and its implementation.

[0032] In a seventh aspect of this disclosure, a chip is provided. The chip includes a processor and a communication interface, through which the processor reads instructions stored in memory to execute any method according to the first aspect and its implementation, or any method according to the second aspect and its implementation.

[0033] In a seventh aspect of this disclosure, a communication system is provided. The communication system includes communication means for performing any method according to the first aspect and its implementations, and communication means for performing any method according to the second aspect and its implementations.

[0034] It should be understood that the descriptions in this application are not intended to limit the key or essential features of this disclosure, nor are they intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0035] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Several implementations of this application are illustrated herein by way of example and not limitation, in the accompanying drawings:

[0036] Figure 1A A schematic diagram of the 5G network architecture is shown;

[0037] Figure 1B and Figure 1C The diagram illustrates some of the network topology modes to which embodiments of this disclosure can be applied;

[0038] Figure 1D A schematic diagram of a system architecture to which some embodiments of this disclosure may be applied is shown;

[0039] Figure 2 A schematic signaling diagram of a communication process according to some embodiments of the present disclosure is shown;

[0040] Figure 3 A schematic diagram of a user plane connection scenario according to some embodiments of the present disclosure is shown;

[0041] Figures 4A to 4D A schematic signaling diagram of a communication process for IP address management according to some embodiments of the present disclosure is shown;

[0042] Figure 5A schematic flowchart illustrating a method implemented at a terminal device according to an embodiment of the present disclosure is shown.

[0043] Figure 6 A schematic flowchart illustrating a method implemented at a network device according to an embodiment of the present disclosure is shown.

[0044] Figure 7 This is a block diagram of a device that can be used to implement some embodiments of this application.

[0045] Figure 8 This is a schematic diagram of the structure of an apparatus according to some embodiments of this application.

[0046] Figure 9 This is a schematic diagram of the structure of an apparatus according to some embodiments of this application.

[0047] In the various figures, the same or similar figure labels indicate the same or similar elements. Detailed Implementation

[0048] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0049] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "an embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc., may refer to different or the same objects. The term "and / or" indicates at least one of the two items associated therewith. For example, "A and / or B" means A, B, or A and B. Other explicit and implicit definitions may also be included below.

[0050] The embodiments of this disclosure can be applied to fourth-generation (4G) communication systems, such as long-term evolution (LTE) communication systems, as well as fifth-generation (5G) communication systems, such as 5G new radio (NR) communication systems, or future communication systems, such as sixth-generation (6G) communication systems. The embodiments of this disclosure can also be applied to Bluetooth systems, wireless fidelity (WiFi) systems, long-range radio (LoRa) systems, or vehicle-to-everything (V2X) systems. The embodiments of this disclosure can also be applied to satellite communication systems, wherein the satellite communication system can be integrated with the aforementioned communication systems.

[0051] In this disclosure, the term "core network equipment" or "core network element" can refer to a functional block located in the next-generation core network (NGC). The NGC may include, but is not limited to, any of the following: access and mobility management function (AMF), user plane function (UPF), gateway mobile location center (GMLC), user data management (UDM), location management function (LMF), and location retrieval function (LRF). The AMF primarily performs mobility management or access authentication / authorization functions. Additionally, the AMF can receive non-access stratum (NAS) signaling from terminal equipment and related signaling from access network equipment (e.g., next-generation (NG) 2 interface signaling at the base station granularity that interacts with the AMF). The NGC may also include units or modules for performing sensing processes (e.g., initiating sensing tasks, determining sensing configurations, and evaluating sensing measurement data).

[0052] In this disclosure, the term "access network equipment" refers to a network-side entity or node that can be used to communicate with terminal equipment, such as an access network device. An access network device can be a means deployed in a radio access network to provide wireless communication functionality for a mobile terminal. For example, an access network device can be a base station (BS), an evolved NodeB (eNodeB), a next-generation NodeB (gNB) in a 5G mobile communication system, a transmission reception point (TRP), a 3GPP subsequent evolution base station, an access node in a WiFi system, a wireless relay node, a wireless backhaul node, etc. An access network device can include one or more co-located or non-co-located transmission reception points. In some deployments of access network equipment, the access network device can include a central unit (CU), a distributed unit (DU), or both CU and DU. In other deployments of access network equipment, the CU can also be divided into a CU-control plane (CP) and a CU-user plane (UP), etc. In some deployments of access network equipment, the access network equipment can also be an open radio access network (ORAN) architecture. The ORAN architecture includes a near-real-time RAN intelligence controller (near-RT RIC), a control unit (CU), and a distribution unit (DU). The DU implements the functions of the physical (PHY) layer, media access control (MAC) layer, and radio link control (RLC) layer. The CU implements the functions of radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The near-real-time RIC implements the application layer functions. In the ORAN architecture, AI functions are implemented in the near-real-time RIC. The near-real-time RIC can include functions such as radio connection management, mobility management, QoS management, interference management, and AI training models. The CU and DU can be connected via an F1 interface, and the near-real-time RIC and CU can be connected via an E2 interface. This application does not limit the specific deployment method of the access network equipment. Multiple network function entities can be used to implement some functions of the radio access network equipment.These network function entities can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). For example, in vehicle-to-everything (V2X) technology, the access network device can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. Base stations can communicate with terminal devices or through relay stations. The access network device in this disclosure can also be a device with sensing capabilities, capable of emitting sensing signals or receiving and processing reflected signals from targets in the environment. In embodiments of this disclosure, the communication device used to implement the access network device's functions can be the access network device itself, an access network device with some base station functions, or a device capable of supporting the access network device in implementing these functions, such as a chip system, which can be installed within the access network device.

[0053] In this disclosure, the term "terminal device" refers to a user-side device with wireless transceiver capabilities, which can be a fixed device, mobile device, handheld device (e.g., mobile phone), wearable device, in-vehicle device, Internet of Things (IoT) device, device for providing voice or data connectivity to a user, or a wireless device (e.g., communication module, modem, or chip system, etc.) built into the aforementioned devices. Terminal devices are used to connect people, things, machines, etc., and can be widely used in various scenarios, such as: cellular communication, device-to-device (D2D) communication, V2X communication, machine-to-machine / machine-type communications (M2M / MTC) communication, Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, drones, robots, etc. For example, the terminal device may be a handheld terminal in cellular communication, a communication device in D2D, an IoT device in MTC, a surveillance camera in intelligent transportation and smart cities, or a communication device on a drone, etc. More specifically, terminal devices can include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), in-vehicle equipment (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), virtual reality (VR) devices, augmented reality (AR) devices, smart point-of-sale (POS) machines, customer-premises equipment (CPE), wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), smart robots, robotic arms, workshop equipment, wireless terminals in autonomous driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, and flying equipment (such as smart robots, hot air balloons, drones, airplanes), etc.The terminal device can also be other devices with terminal functions. For example, it can be a device that performs terminal functions in D2D communication. Terminal devices are sometimes referred to as user equipment (UE), user terminal, user device, user unit, user station, terminal, access terminal, access station, UE station, remote station, mobile device, mobile station (MS), mobile terminal (MT), or wireless communication device, etc. In this application, terminal devices with wireless transceiver functions and chips that can be disposed in the aforementioned terminal devices are collectively referred to as terminal devices. The embodiments of this application do not limit the device form of the terminal.

[0054] In this disclosure, the term "computing node" refers to a computing function node used to provide specific computing services or computing power services, providing users with connectivity, computing, and data storage functions. A computing node may also be referred to as a computing function, computing node, computing resource, edge computing resource, computing power resource, or other names. A computing node can include various types and forms of computing resources, memory resources, or storage resources. A computing node can be a resource integrated into a terminal device, network device, access network, core network, transmission network, or data network. A computing node can also include independently deployed resources of various forms, such as MEC, edge cloud, public cloud, industry private cloud, or on-premises resources, or a combination of these types. The physical device of a computing node can be based on a general-purpose central processing unit (CPU), such as an advanced RISC machine (ARM) or x86. The physical devices of computing nodes can also be based on heterogeneous computing capabilities such as artificial intelligence (AI) chips, graphics processing unit (GPU) chips, and field-programmable gate arrays (FPGAs). The supply of computing nodes is based on the virtual partitioning of computing resources of various forms and granularities. For example, computing nodes include clusters, hosts, virtual machines (VMs), containers, virtual nodes (PODs), or other finer-grained resources. These resources are resources capable of running a piece of logical code or a function, such as cloud-native serverless systems. A virtual node may contain a group of containers, i.e., one or more containers. Computing nodes can be used to complete computing tasks using computing resources. These computing tasks can be requested by terminal devices or applications. Communication is required when executing computing tasks between terminal devices and applications on computing nodes. In this embodiment, data transmission is completed through a computing bearer between the terminal device and the application. A computing task is a manifestation of an application running on a computing node. In this embodiment, a computing task can also be simply referred to as a task. An application can correspond to one or more tasks.

[0055] In this disclosure, the term "communication signal" refers to a signal transmitted between communication devices for the purpose of communication, such as signals transmitted between network devices and terminal devices. A communication signal may, for example, be a signal carried on a physical downlink shared channel (PDSCH).

[0056] In this disclosure, the term "downlink" refers to transmission from a network device or data network to a terminal device.

[0057] In this disclosure, the term "uplink" refers to a transmission from a terminal device to a network device or data network.

[0058] Figure 1A A schematic diagram of the 5G network architecture 100A is shown. 5G systems are also known as new wireless communication systems, new radio (NR) technologies, or next-generation mobile communication systems. Figure 1A As shown, this network architecture can include a UE, an access network (AN), a core network (CN), and a data network (DN). The access network primarily implements radio physical layer functions, resource scheduling and radio resource management, radio access control, and mobility management. The core network may include management devices and gateway devices. Management devices are mainly used for terminal device registration, security authentication, mobility management, and location management. Gateway devices are mainly used to establish channels with terminal devices and forward data packets between terminal devices and external data networks on these channels. The data network may include network devices (such as servers and routers). The data network primarily provides various data services to terminal devices, such as carrier services, internet access, or third-party services.

[0059] The access network can be a radio access network ((R)AN). The main function of the access network is to provide wireless connectivity for the UE, and it is located between the UE and the core network. The (R)AN equipment can be composed of multiple 5G-(R)AN nodes, which can include: non-3GPP access networks, such as access points (APs) of WiFi networks, next-generation base stations (collectively referred to as next-generation radio access network nodes (NG-RAN nodes), WiMAX BS, where next-generation base stations include new radio interface base stations (NR nodeB, gNB), next-generation evolved NB (NG-eNB), gNBs in a separate form of central unit (CU) and distributed unit (DU), etc.), transmission receivepoints (TRPs), transmission points (TPs), or other nodes.

[0060] The core network may include multiple functional units such as user plane function (UPF) network elements, authentication server function (AUSF) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, service communication proxy (SCP) network elements, network data analytics function (NWDAF) network elements, network exposure function (NEF) network elements, network repository function (NRF) network elements, policy control function (PCF) network elements, unified data management (UDM) network elements, and application function (AF) network elements.

[0061] The UPF network element is primarily responsible for connecting to the data network (DN) and handling packet routing and forwarding. It also acts as a session anchor, an uplink classifier to support routing traffic to the local data network, and a branch point to support multi-homed PDU sessions. The AUSF network element is primarily responsible for terminal device authentication. The AMF network element is primarily responsible for managing user registration, reachability detection, SMF node selection, and mobility state transition management. The SMF network element is primarily responsible for session management, UE address management and allocation, dynamic host configuration protocol functions, and user plane function selection and control. The SCP network element can evolve the original mesh-based fully connected networking mode into a star topology, significantly simplifying the signaling network architecture. The NWDAF network element automatically senses and analyzes the network based on network data, providing network data collection and analysis functions based on big data and artificial intelligence technologies. It participates in the entire lifecycle of network planning, construction, operation and maintenance, network optimization, and operation, making the network easier to maintain and control, improving network resource utilization efficiency, and enhancing user service experience. The NEF (Network Element) is responsible for the exposure and management of publicly accessible network data, allowing external systems to obtain network configuration, status, and other relevant information. It can also communicate with other network elements to obtain necessary data or provide data services. The NRF (Network Request Element) is responsible for registering and managing NFs (Network Functions) and providing a communication interface between NFs and UDMs (User Device Managers). It stores and manages network resource information and provides resource discovery and configuration functions. The NRF also supports integration and interaction with other systems. The PCF (Network Component Element) is primarily responsible for providing a unified policy framework for network behavior management, providing policy rules for control plane functions, and obtaining registration information related to policy decisions. The UDM (User Device Manager) is responsible for storing user data, such as subscription information and authentication / authorization information, and providing data access interfaces to other NFs. The UDM also supports data interaction and integration with external systems. The AF (Active AF) can interact with the core network to provide services; its functions include accessing network open functions and interacting with the policy framework for policy control. Trusted AFs can directly access the functions of internal network elements in the 5G core network. It should be noted that these functional units can work independently or be combined to implement certain control functions, such as access control and mobility management functions for terminal devices, including access authentication, security encryption, and location registration, as well as session management functions such as the establishment, release, and modification of user plane transmission paths.

[0062] In 5GC, some functional units can communicate with each other through the next generation (NG) interface. For example, the UE can transmit control plane messages with the AMF network element through NG interface 1 (N1), the (R)AN device can establish a user plane data transmission channel with the UPF network element through NG interface 3 (N3), the (R)AN device can establish a control plane signaling connection with the AMF network element through NG interface 2 (N2), the UPF can exchange information with the SMF network element through NG interface 4 (N4), and the UPF can exchange user plane data with the data network DN through NG interface 6 (N6).

[0063] In service-oriented interface scenarios, some network elements in the core network are connected via a bus, such as... Figure 1A As shown, AUSF, AMF, SMF, SCP, NWDAF, NEF, NRF, PCF, UDM, and AF network elements are interconnected via a bus. When these network elements are interconnected via the bus, they use service-oriented interfaces. For example, AUSF network elements connect to the bus via a Nausf interface, AMF network elements connect via a Namf interface, SMF network elements connect via a Nsmf interface, AF network elements connect via a NAF interface, UDM connects via a Nudm interface, PCF network elements connect via an NPCF interface, NRF connects via an Nnrf interface, NEF connects via an Nnef interface, and NWDAF connects via an Nnwdaf interface. It should be noted that... Figure 1A This is merely an illustrative architecture diagram, except... Figure 1A In addition to the functional units shown, the network architecture may also include other functional units, and the network architecture is not limited to a service-oriented interface-based network architecture, but may also adopt a reference point-based network architecture.

[0064] UPFs and data networks (or data services) are typically connected via a mesh network, meaning different UPFs are connected to different data networks, and different UPFs can connect to the same data network. In the current 5G architecture, the UE's IP address is anchored to a UPF (e.g., UPF#1) (i.e., the UPF serves as the UE's IP anchor point), and the UPF is responsible for forwarding the UE's service messages. Even if the UE moves, the connection between the UE and the data network server must still be established through the UE's IP anchor point (i.e., UPF#1). In other words, the UE's IP address is bound to its location attribute when it registered with the network; that is, the UE's IP address reflects its location when it registered (the UE's location at registration is under the corresponding UPF). However, this mechanism cannot achieve the optimal connection path between the UE and the data network server, especially when the UE moves, which may increase transmission latency and consume network bandwidth.

[0065] Some communication scenarios have high real-time requirements for computing tasks. In future generations of mobile communication systems, cloud edge computing nodes can be deployed closer to the network edge near the access side or further down to the network access node (i.e., the base station side), thereby improving mobile network speed, reducing latency, and enhancing connection reliability. For example, the access network can further undertake some computing functions, which can be internal functional nodes of the base station or external independent functional nodes separate from the logical functions of the base station. Figure 1B A schematic diagram of a networking mode 100B to which some embodiments of this disclosure may be applied is shown. Networking mode 100B involves a UE 110, a base station 120, and a computing function node 130. The computing function node 130 may also be referred to as a computing power node, a computing node, or an independent intelligent unit. Figure 1B As shown, the computing function node 130 is close to the base station 120. The UE 110 accesses the wireless network through the base station 120 and accesses the computing function node 130 through the base station 120.

[0066] After the computing function nodes are moved down, a star topology can be adopted. That is, the base station can be connected to different computing function nodes, and the base station can provide access services for multiple UEs. Therefore, from the perspective of the base station, the system architecture is a star topology. Figure 1C A schematic diagram of a networking mode 100C to which some embodiments of this disclosure may be applied is shown. Networking mode 100C involves UEs 110a, 110b, 110c, 110d, 110e, and 110f (collectively referred to as UE 110), base stations 120a and 120b (collectively referred to as base station 120), and computing function nodes 130a, 130b, 130c, 130d, 130e, and 130f (collectively referred to as computing function node 130). Figure 1CAs shown, computing function nodes 130a, 130b, and 130c are located near base station 120a. UEs 110a, 110b, and 110c access the wireless network through base station 120a and access computing function nodes 130a, 130b, and 130c through base station 120a. Computing function nodes 130d, 130e, and 130f are located near base station 120a. UEs 130d, 130e, and 130f access the wireless network through base station 120b and access computing function nodes 130d, 130e, and 130f through base station 120b.

[0067] Figure 1B and Figure 1C The network topology shown is merely an example; other network topologies are also possible. Figure 1B and Figure 1C Although the computing function node 130 is shown as an external, independent function node separate from the base station 120, it can be understood that the computing function node 130 may also be located inside the base station 120. Although the base station 120 and the computing function node 130 are shown as directly connected without intermediate network nodes, it can be understood that a UPF network element close to the base station 120 may be deployed between the base station 120 and the computing function node 130, or some functions of the base station 120 may be implemented on the UPF network element.

[0068] Figure 1D A schematic diagram of a system architecture 100D to which some embodiments of the present disclosure may be applied is shown. System architecture 100D involves a UE 110, a base station 120, a computing function node 130, a core network 140, a general-purpose computing server, and operation, administration and maintenance (OAM), etc. It should be understood that system architecture 100D may also include additional boxes not shown and / or omit some boxes shown, and the scope of this disclosure is not limited thereto. System architecture 100D may include... Figure 1A The 5G network architecture 100D shown here contains some network elements and architectures that are the same as or have the same functions as those in the 5G network architecture 100A, and detailed descriptions of them will be omitted here. It should be understood that system architecture 100D is for illustrative purposes only and does not imply any limitations. The embodiments of this disclosure can also be applied to other possible system architectures. For example, a UPF can be deployed at the edge of a base station, or some functions of the base station can be implemented in the UPF.

[0069] The computing function node 130 can be implemented as an independent intelligent unit to provide specific computing services and computing power services, such as providing low-latency, short-connection services to the UE. Through this service, the computing function node 130 can provide users with connectivity, computing, and data storage functions. The computing function node 130 can be managed by the intelligent unit control entity function 142, including registration management, distribution, and configuration of relevant information of the independent intelligent unit to other nodes. A protocol reference point can exist between the computing function node 130 and the computing power service on the UE 110, which can support the computing power service module on the UE to call computing power services. A communication reference point can exist between the computing function node 130 and the base station 120, which can be based on L2 switch forwarding, L3 IP routing, or tunneling transmission protocols. Computing power service refers to a type of service, such as rendering service. Computing power service can be provided by one or more computing power nodes.

[0070] The intelligent unit control entity 142 is responsible for managing independent intelligent units, including receiving registration, address allocation, and QoS information from independent intelligent units. Furthermore, the intelligent unit control entity 142 can also be used to configure information about independent intelligent units to the base station.

[0071] Base station 120 can interface with computing nodes and is responsible for routing uplink and downlink packets. In some implementations, base station 120 can also be responsible for establishing the connection between UE 110 and base station 120, such as processing AS requests from UE 110, implementing authentication and authorization, and establishing the connection between UE 110 and base station 120. In some implementations, base station 120 can be composed of a remote unit (RU), a distributed unit (DU), and a central unit (CU), where the CU in base station 120 can interface with computing nodes.

[0072] Core network 140 may include a core network control plane functional entity xCF 141. xCF 141 may contain a core network control plane that implements network connectivity. In some implementations, xCF 141 may be responsible for establishing a connection between UE 110 and base station 120, such as handling NAS requests from UE 110, implementing authentication and authorization, and establishing a connection between UE 110 and base station 120. In some implementations, xCF 141 may assist in the overall management of deployment strategies for various computing power tasks on computing power nodes and may coordinate the selection of computing power nodes. It is understood that xCF 141 may be implemented by one or more of the AMF, SMF, and PCF network elements in core network 140.

[0073] As mentioned earlier, since the UE's IP address is anchored at the UPF, the optimal connection path between the UE and the data network server cannot be achieved. When the compute node is deployed to the network edge closer to the access side or further down to or near the access side, it is necessary to design the source IP of the user plane packets. That is, it is necessary to design the source IP in the uplink packets generated when the UE accesses the compute function node, in order to further improve the mobile network speed, reduce latency, and enhance connection reliability.

[0074] Some embodiments of this disclosure provide a management scheme for IP addresses used for computing services, enabling UEs to send computing service packets using IP addresses designated for computing services. In other words, IP addresses for computing services are assigned to the UE without needing to be anchored at a UPF (User Platform Function). For example, the IP address used for computing services may not have an anchor point, or it may be anchored at or near a base station. This optimizes the connection path between the UE and the data network server, thereby reducing latency.

[0075] Figure 2 A schematic signaling diagram of a communication process 200 according to some embodiments of the present disclosure is shown. The communication process 200 can be applied to... Figure 1B , Figure 1C and Figure 1D The network topology or system architecture shown herein, or other possible network topology or system architectures, will be referenced for ease of understanding. Figures 1B to 1D To describe Figure 2 The communication process 200 may involve an access terminal device 210, a network device 220, and a computing node 230. The terminal device 210 can be implemented as... Figures 1B to 1D UE 110 in the example. In some embodiments, network device 220 can be implemented as an access network device, such as... Figures 1B to 1D Base station 120. Alternatively, network equipment 220 can be implemented as core network equipment, for example... Figure 1D xCF 141 in the context. Computing node 230 can be implemented as... Figures 1B to 1D The computational function node 130 is included. It should be understood that the communication process 200 may also include additional boxes not shown and / or omit some boxes shown, and the scope of this disclosure is not limited thereto.

[0076] refer to Figure 2Terminal device 210 determines (218) the Internet Protocol IP address 206 used for the computing power service and uses IP address 206 to send (222) a message 224 for the computing power service. In other words, the source IP address of the message used by the terminal device to access the computing power service can be the IP address used for the computing power service. The access network device can receive message 224 from terminal device 210 and send message 224 to computing power node 230 of the computing power service based on the destination IP address of message 224. Accordingly, computing power node 230 can receive (226) the message 224.

[0077] In some embodiments, terminal device 210 may receive (208) IP address 206 from network device 220. For example, network device 220 may determine (202) the IP address 206 used by terminal device 210 for computing services and send (204) IP address 206 to terminal device 210. In this disclosure, "IP address used for computing services" refers to the IP address used by messages for computing services.

[0078] In some embodiments, terminal device 210 may send a first request message to network device 220, and network device 220, in response to receiving the first request message, may send a response message to terminal device 210, which may include IP address 206. In one example, the first request message may be used for network registration. Network device 220 may send IP address 206 to terminal device 210 in the registration response. In another example, the first request message may be used to request the establishment of a default connection for transmitting the first packet of the computing power service. Network device 220 may send IP address 206 to terminal device 210 in the default connection establishment response. In yet another example, the first request message may be used to obtain an IP address. In other words, terminal device 210 may send a request message to request an IP address.

[0079] In some embodiments, the first request message may include indication information requesting the allocation of an IP address, such as Indicator-1. Network device 220 may determine that terminal device 210 requests the allocation of an IP address based on Indicator-1 in the first request message, and thus send a response message including the IP address to terminal device 210. In some alternative embodiments, the first request message may not include the indication information requesting the allocation of an IP address, and network device 220 may send a response message including the IP address to terminal device 210 based on local configuration, subscription data of terminal device 210, or policy information. For example, if the first request message contains DNN / S-NSSAI, and at least one of the local configuration of network device 220, subscription data of terminal device 210, or policy information from PCF indicates that an IP address for computing power service needs to be allocated to the DNN / S-NSSAI, or indicates that the DNN / S-NSSAI is allowed to access computing power service, then network device 220 may send a response message including the IP address to terminal device 210. In another example, if at least one of the following indicates that the UE is allowed to access computing services, or indicates that an IP address for computing services needs to be assigned to the UE, then the network device 220 may send a response message including the IP address to the terminal device 210.

[0080] In some embodiments, if network device 220 determines that an IP address for computing power service has not yet been allocated to terminal device 210, and allows terminal device 210 to use computing power service, then network device 220 may send a message including the IP address to terminal device 210. In some examples, the message including the IP address may be a response message to a first request message. In some alternative examples, network device 220 may send a message including the IP address even without receiving a request message. For example, after completing the registration of terminal device 210 or establishing a default connection between terminal device 210 and access network device, network device 220 may determine whether to allow terminal device 210 to use computing power service and whether to allocate an IP address for computing power service to terminal device 210. If an IP address for computing power service has not yet been allocated to terminal device 210, and terminal device 210 is allowed to use computing power service, network device 220 may send a response message including the IP address to terminal device 210 based on local configuration, terminal device 210's subscription data, or policy information. Network device 220 can determine whether to allow terminal device 210 to use computing power services based on local configuration, subscription data of terminal device 210, or policy information. In this disclosure, "allowing terminal device to use computing power services" can be understood as allowing terminal device to use a specific data network name (DNN) and / or use specific single network slice selection assistance information (S-NSSAI).

[0081] In some embodiments, based on the replacement of the access network device by the terminal device 210, the terminal device 210 can determine a second IP address for use in computing power services. In some examples, when receiving IP address 206, the terminal device 210 can receive indication information indicating that the terminal device will obtain a second IP address for use in computing power services when replacing the access network device. Alternatively or additionally, the terminal device 210 can determine the acquisition of the second IP address when using the access network device based on its local configuration. Alternatively or additionally, the terminal device 210 can determine the acquisition of the second IP address when using the access network device based on receiving IP address 206 for computing power services. It is understood that "replacing the access network device" mentioned in the embodiments of this disclosure can be replaced with replacing the user plane function network element. For example, the user plane function network element can be deployed down to or near the access network device. In this case, the actions of the access network device can be described as being performed by the user plane function network element. The same substitution can be made in other places in this application, which will not be repeated hereafter.

[0082] In some embodiments, when terminal device 210 changes access network equipment, terminal device 210 can determine a second IP address for use with computing power services. For example, IP address 206 is a first IP address, network device 220 is a first network device, and when terminal device 210 changes from the first network device to the second network device, terminal device 210 can receive the second IP address for use with computing power services from the second network device. In some examples, the first network device is a first access network device (e.g., a source base station), and the second network device is a second access network device (e.g., a target base station). When terminal device 210 changes from the first access network device to the second access network device, the first access network device can send indication information to the second access network device. This indication information is used to indicate that terminal device 210 is allowed to use computing power services. Alternatively or additionally, this indication information is used to indicate that an IP address for use with computing power services is allocated to terminal device 210. Alternatively or additionally, this indication information is used to instruct terminal device 210 to access computing power services. The second access network device may, in response to receiving the indication information, send a second IP address for use with the computing power service to the terminal device 210. In some alternative examples, the first network device is a first core network device (e.g., a source xCF), and the second network device is a second core network device (e.g., a destination xCF). When the terminal device 210 is switched from the first core network device to the second core network device, the first core network device may send an indication information to the second core network device. This indication information is used to indicate that the terminal device 210 is allowed to use the computing power service. Alternatively or additionally, this indication information is used to indicate that an IP address for use with the computing power service be assigned to the terminal device 210. Alternatively or additionally, this indication information is used to instruct the terminal device 210 to access the computing power service. The second core network device may, in response to receiving the indication information, send a second IP address for use with the computing power service to the terminal device 210. It is understood that the first network device and the second network device may be the same. When the first network device determines that the terminal device 210 has been switched from the first access network device to the second access network device, the first network device sends the second IP address for use in computing power services to the terminal device 210.

[0083] In some embodiments, when terminal device 210 changes access network equipment, terminal device 210 can determine a second IP address for use in computing power services. For example, IP address 206 is a first IP address. When terminal device 210 switches from a first access network equipment (e.g., a source base station) to a second access network equipment (e.g., a target base station), terminal device 210 can receive the second IP address for use in computing power services from the core network equipment associated with the second access network equipment. The second access network equipment can send a request message to the core network equipment requesting the allocation of an IP address for use in computing power services for terminal device 210. It is understood that the request message can also be described as indicating that terminal device 210 has switched to the second access network equipment (i.e., the target base station). For example, the request message can be represented by a path switching request message in the prior art. The core network equipment can determine the second IP address for use in computing power services for terminal device 210 in response to receiving the request message and send the second IP address to terminal device 210. In some examples, network equipment 230 can be a core network equipment associated with the second access network equipment. In other words, when terminal device 210 switches from the first access network device to the second access network device, a core network device switchover may not occur. Network device 230 can reallocate an IP address for computing power services to terminal device 210 based on a request message sent by the second access network device. In an alternative example, network device 230 may be a first core network device (e.g., a source xCF) associated with the first access network device, and the core network device associated with the second access network device may be a second core network device (e.g., a target xCF). In other words, when terminal device 210 switches from the first access network device to the second access network device, a core network device switchover occurs, and the second network device can reallocate an IP address for computing power services to terminal device 210 based on a request message sent by the second access network device.

[0084] Therefore, in some embodiments of this disclosure, different terminal devices use different IP addresses when accessing computing power nodes. Figure 3 A schematic diagram of a user plane connection scenario 300 according to some embodiments of the present disclosure is shown. Scenario 300 may be... Figure 2 This is a specific example implementation of the steps in the communication process 200 where the terminal device sends a message to the computing node. For example... Figure 3As shown, UE-1 310a and UE-2 310b can communicate with computing nodes 330-1, 330-2, ..., 330-n via xNB 320. The IP address used by UE-1 310a for computing services is UE IP-1, and the IP address used by UE-2 310b for computing services is UE IP-2. Accordingly, the source IP address of uplink packets sent by UE-1 310a to the computing nodes is UE IP-1, and the source IP address of uplink packets sent by UE-2 310b to the computing nodes is UE IP-2. The IP addresses used by UE-1 310a and UE-2 310b for computing services can be assigned by xNB 320. Alternatively, the IP addresses used by UE-1 310a and UE-2 310b for computing services can be assigned by core network equipment (e.g., xCF) associated with xNB 320. The IP addresses of computing power nodes 330-1, 330-2, ..., 330-n are the IP addresses of Independent Intelligent Unit-1, Independent Intelligent Unit-2, ..., Independent Intelligent Unit-n, respectively. The xNB 320 forwards packets to the corresponding computing power nodes based on the destination IP address of the uplink packets sent by the UE. The destination IP address of the downlink packets sent by the computing power nodes to the UE is the IP address used by the corresponding UE for computing power services. The xNB 320 forwards packets to the corresponding UE based on the destination IP address of the downlink packets sent by the computing power nodes. The IP address used for computing power services can be an IPv4 address or an IPv6 prefix. When the UE changes base stations, the UE can reacquire the IP address used for computing power services according to the indication information or its local configuration.

[0085] Figure 4A A schematic signaling diagram of a communication process 400A for IP address management according to some embodiments of the present disclosure is shown. For ease of understanding, reference will be made to... Figures 1B to 1D To describe Figure 4A Communication process 400A may involve UE 410, xNB 420, xCF 440, and computing node #1 430. In some embodiments, communication process 400A may also involve target xNB 420'. UE 410 may be implemented as... Figures 1B to 1D UE 110. xNB 420 and target xNB 420' can be implemented as Figures 1B to 1D Base station 120 in the xCF 440 can be implemented as Figure 1D xCF 141 in the context. Computing node #1 430 can be implemented as Figures 1B to 1D The computing function node 130 in the middle. The communication process 400A can be regarded as Figure 2This is a specific example of the communication process 200. It should be understood that the communication process 400A may also include additional boxes not shown and / or omit some boxes shown, and the scope of this disclosure is not limited thereto.

[0086] like Figure 4A As shown, at step 401, computing power information is configured on at least one of xNB 420 and xCF 440, including configuring the address of the computing power node and the QoS corresponding to the computing power node or computing power service. This computing power information configuration process can be implemented by the network management system or by the intelligent unit control entity. At step 402, UE 410 initiates a registration process to register and join the network. The registration process of UE 410 can be implemented by interaction between UE 410 and xCF 440, or by interaction between UE 410 and xNB 420.

[0087] In some implementations, the registration process for UE 410 is carried out through interaction between UE 410 and xCF 440. At 402, UE 410 sends a registration request to xCF 440 via xNB 420. Optionally, the registration request may carry Indicator-1, which instructs xCF 440 to allocate a UE IP related to computing power services for UE 410, or indicates that UE 410 requests a UE IP related to computing power services. At 403, xCF 440 allocates a UE IP to UE 410 for use by the computing power services. In some examples, xCF 440 allocates a UE IP for computing power services to UE 410 based on the Indicator-1 carried in the registration request. In some examples, the registration request may not carry Indicator-1. The xCF 440 can assign a UEIP for computing services to UE 410 based on its local configuration, and / or UE 410's subscription data, and / or policy information from the PCF. For example, the xCF 440's local configuration, and / or UE 410's subscription data, and / or policy information from the PCF may indicate that UE 410 is allowed to access computing services (or that UE 410 is allowed to access computing services directly through xNB 420). In another example, the xCF 440 only assigns a UEIP for computing services to UE 410 when it determines that UE 410 is allowed to use computing services based on its local configuration, and / or UE 410's subscription data, and / or policy information from the PCF. In some examples, the UEIP may not have an anchor point. In another example, the UE IP can be anchored to xNB 420, or to xCF 440, or to other centralized network elements, such as the IP address pool management network element. In other words, the IP address pool can be located in xNB 420, xCF 440, or other centralized network elements. In this disclosure, "determining that UE 410 is allowed to use computing power services" can also be described as determining that UE 410 is allowed to use computing power services or access computing power services. In this disclosure, "using computing power services" or "accessing computing power services" can specifically refer to using or accessing a specific DNN and / or a specific slice.

[0088] At step 404, xCF 440 sends a registration response to the UE via xNB 420. This registration response may carry the UE IP assigned in step 403. Optionally, the registration response may carry Indicator-2. Indicator-2 is used to instruct the UE to reacquire the UE IP when changing base stations, i.e., to reacquire the source IP corresponding to the computing power service. In some examples, when UE 410 does not receive Indicator-2, UE 410 may decide to reacquire the UE IP when changing base stations based on its local configuration. In some examples, when UE 410 receives the UE IP in the registration response, UE 410 may decide to reacquire the UE IP when changing base stations. Optionally, the registration response may carry Indicator-3. Indicator-3 is used to indicate that the UE IP is available for use by the computing power service. In other words, UE 410 will only use the UE IP as the source IP of the message when UE 410 invokes the computing power service. In some examples, when UE 410 does not receive Indicator-3, UE 410 can determine that the UE IP is available for use by the computing power service based on its local configuration. In some examples, when UE 410 receives the UE IP in the registration response, UE 410 can determine that the UE IP is available for use by the computing power service. Optionally, at 405, UE 410 can save the received UE IP. Optionally, UE 410 can save Indicator-2 and / or Indicator-3. In this disclosure, when terminal device 210 invokes the computing power service, it refers to terminal device 210 sending and / or receiving messages corresponding to the computing power service.

[0089] In some implementations, the registration process for UE 410 is carried out through interaction between UE 410 and xNB 420. At 402, UE 410 sends a registration request to xNB 420. Optionally, the registration request may carry Indicator-1, which instructs xNB 420 to allocate a UE IP related to computing power services for UE 410, or indicates that UE 410 requests a UE IP related to computing power services. At 403, xNB 420 allocates a UE IP for UE 410 for use by the computing power services. In some examples, xNB 420 allocates a UE IP for computing power services to UE 410 based on Indicator-1 carried in the registration request. In some examples, the registration request may not carry Indicator-1, and xNB 420 may allocate a UE IP for computing power services to UE 410 based on xNB 420's local configuration, and / or UE 410's subscription data, and / or policy information from the PCF. For example, the local configuration of xNB420, and / or the subscription data of UE 410, and / or policy information from the PCF indicate that UE 410 is allowed to access computing services (or that UE 410 is allowed to access computing services directly through xNB 420). In another example, xNB 420 allocates a UE IP for computing services to UE 410 only when it determines that UE 410 is allowed to use computing services based on the local configuration of xNB 420, and / or the subscription data of UE 410, and / or the policy information from the PCF. In some examples, the UE IP may not have an anchor point. In other examples, the UE IP may be anchored to xNB 420, or to xCF 440, or anchored to other centralized network elements, such as the IP address pool management network element. In other words, the IP address pool may be located in xNB 420, xCF 440, or other centralized network elements. At step 404, xNB 420 sends a registration response to the UE, which may carry the UE IP assigned in step 403. Optionally, the registration response may carry Indicator-2. Optionally, the registration response may carry Indicator-3. At step 405, UE 410 may save the received UE IP. Optionally, UE 410 may save Indicator-2 and / or Indicator-3.

[0090] Although the above steps illustrate obtaining the UE IP for computing services during the registration process, in some implementations, the UE uses a separate process to obtain the UE IP for computing services. For example, UE 410 can send an IP address allocation request to xNB 420 or via xNB 420 to xCF 440, the IP address allocation request may carry Indicator-1. xNB 420 or xCF 440 can respond to the IP address allocation request by performing step 403 and sending the UE IP to UE 410 in an IP address allocation message. Optionally, the IP address allocation message may carry Indicator-2. Optionally, the IP address allocation message may carry Indicator-3.

[0091] Optionally, at 406, a default connection is established between UE 410 and xNB 420. This default connection is used to transmit the first message for the computing service. In some examples, the default connection also includes a connection between xNB 420 and the computing node for transmitting the first message for the computing service. The default connection establishment process can be combined with the registration process or performed separately.

[0092] At 407, UE 410 triggers the computing service. UE 410 can generate the first packet corresponding to this computing service, with the source IP of the packet being the UE IP. At 408, UE 410 sends the first packet corresponding to the computing service to xNB 420. This packet (the first packet of the computing service) is carried on the default connection. If step 406 is executed to establish the default connection, the default connection can be a data radio bearer (DRB). If step 406 is not executed, the first packet of the computing service can be carried on a signal radio bearer (SRB), i.e., the default connection is an SRB. At 409, based on the destination IP address of the packet, xNB 420 sends the packet to computing node #1 430. At 411, computing node #1 430 returns a downlink packet to xNB 420, with the destination IP of the downlink packet being the UE IP. In step 412, xNB 420 sends the downlink packet to UE 410 according to the destination IP of the downlink packet. In step 413, xNB 420 can establish a dedicated connection for this computing power service. Specifically, xNB 420 can trigger a dedicated connection corresponding to the QoS of the computing power service initiated by the UE based on the configuration information in step 401 (e.g., the QoS corresponding to the computing power service / computing power node). In some examples, step 413 can be executed in parallel with step 412. In step 414, UE 410 can continue to send packets for this computing power service (no longer the first packet), which can be carried on the dedicated connection.

[0093] In step 415, when UE 410 switches from xNB 420 to target xNB 420' (e.g., due to mobility), UE 410 can reacquire the UE IP corresponding to the computing service. In some examples, when UE 410 switches to target xNB 420', UE 410 can send an IP address allocation request to target xNB 420' or through target xNB 420' to the xCF associated with target xNB 420'. For example, the IP address allocation request can carry Indicator-1. In other words, UE 410 can initiate an IP reallocation process. Target xNB 420' or the xCF associated with target xNB 420' can respond to the IP address allocation request by performing an operation similar to step 403 and sending the UE IP to UE 410 in the IP address allocation message. Optionally, the IP address allocation message can carry Indicator-2. Optionally, the IP address allocation message can carry Indicator-3.

[0094] In some embodiments, the xNB assigns a UE IP address for computing services to the UE (i.e., step 403 is performed by xNB 420), and when the UE switches from the source xNB to the target xNB, the target xNB initiates the IP reallocation process. For example, when UE 410 switches to the target xNB 420', xNB 420 can send indication information to the target xNB 420' to indicate that UE 410 is allowed to use computing services, or to indicate that UE 410 requires IP reallocation. The target xNB 420' can reallocate a UE IP address for computing services to UE 410 according to the indication information and send the reallocated UE IP address to UE 410. When UE 410 invokes computing services again, UE 410 can use the reallocated UE IP address as the source IP address for uplink packets.

[0095] In some embodiments, the xCF assigns a UE IP address for computing services to the UE (i.e., step 403 is performed by xCF 440), and when the UE switches from the source xNB to the target xNB, the xCF associated with the target xNB initiates an IP reallocation process. The xCF associated with the target xNB 420' can be xCF 440 or another xCF. For example, when UE 410 switches to the target xNB 420', the target xNB 420' can send a path switching request to the xCF associated with the target xNB 420'. The xCF associated with the target xNB 420' reallocates a UE IP address for computing services to UE 410 based on the UE 410's switch from xNB 420 to the target xNB 420', and sends the reallocated UE IP address to UE 410. When UE 410 invokes computing services again, UE 410 can use the reallocated UE IP address as the source IP address for uplink packets. In another example, the xCF associated with the target xNB 420' can be a different xCF than xCF 440 (referred to as the target xCF). When UE 410 switches to the target xNB 420', xCF 440 can send a path switch request to the target xCF. The target xCF, based on UE 410's switch from xNB 420 to the target xNB 420', reassigns a UE IP for UE 410 to use for computing services and sends the reassigned UE IP to UE 410. When UE 410 invokes computing services again, UE 410 can use the reassigned UE IP as the source IP address for uplink packets.

[0096] In this way, during the registration process (or the IP address allocation process initiated by the UE), the xNB or xCF can allocate a UE IP address to the UE. This UE IP address is used for computing services; that is, when the UE calls the computing service, it uses this UE IP address as the source IP address of the corresponding message. When the UE changes base stations, the xNB or xCF needs to reallocate a UE IP address to the UE. In other words, when the UE changes base stations, it can use the newly allocated UE IP address to access the computing service. The newly allocated UE IP address can be anchored to the current serving base station or a network element communicating with the current serving base station. The anchor point corresponding to the newly allocated UE IP address can be different from the anchor point corresponding to the original UE IP address. In this case, the user plane path does not need to return to the anchor point corresponding to the original UE IP address, thus achieving path optimization.

[0097] Figure 4BA schematic signaling diagram of a communication process 400B for IP address management according to some embodiments of the present disclosure is shown. The communication process 400B may involve UE 410, xNB 420, xCF 440, and computing node #1 430. The same reference numerals are used to denote... Figure 4A The elements or components described herein have the same operation Figure 4B The components, parts, or steps described herein will be omitted, and their detailed descriptions will be omitted. Communication process 400B can be considered as... Figure 2 This is a specific example of the communication process 200. It should be understood that the communication process 400B may also include additional boxes not shown and / or omit some boxes shown, and the scope of this disclosure is not limited thereto.

[0098] like Figure 4B As shown, at 421, the registration process for UE 410 is performed. At 422, xCF 440 or xNB 420 can determine, based on at least one of the following: local configuration, and / or UE 410's subscription data, and / or policy information from the PCF, to allocate a UE IP for computing services to UE 410. xCF 440 or xNB 420 can allocate a UE IP for computing services to UE 410 based on the determination that a UE IP for computing services has not yet been allocated to UE 410, and based on the determination that UE 410 is allowed to use computing services. At 423, xCF 440 or xNB 420 sends the UE IP, (optional) Indicator-2, and (optional) Indicator-3 to the UE. Indicator-2 and Indicator-3 can be the same or similar indication information as Indicator-2 and Indicator-3 in communication procedure 400A.

[0099] In step 424, when UE 410 switches from xNB 420 to target xNB 420' (e.g., due to mobility), UE 410 can reacquire the UE IP corresponding to the computing service. In some embodiments, the xNB actively allocates a UE IP for the UE to use for the computing service (i.e., step 422 is performed by xNB 420), and when the UE switches from the source xNB to the target xNB, the target xNB initiates the IP reallocation process. For example, when UE 410 switches to target xNB 420', xNB 420 can send indication information (e.g., context information) to target xNB 420' to indicate that UE 410 is allowed to use the computing service, or to indicate that UE 410 needs IP reallocation, or to indicate that UE 410 accesses the computing service. Target xNB 420' can reallocate a UE IP for UE 410 to use for the computing service according to the indication information and send the reallocated UE IP to UE 410. When UE 410 invokes the computing service again, UE 410 can use the reassigned UE IP as the source IP address of the uplink packet.

[0100] In some embodiments, the xCF actively allocates a UE IP address for computing services to the UE (i.e., step 422 is performed by xCF 440), and when the UE switches from the source xNB to the target xNB, the xCF associated with the target xNB initiates an IP reallocation process. The xCF associated with the target xNB 420' can be xCF 440 or another xCF. For example, when UE 410 switches to the target xNB 420', the target xNB 420' can send a path switching request to the xCF associated with the target xNB 420'. The xCF associated with the target xNB 420' reallocates a UE IP address for computing services to UE 410 based on the UE 410 switching from xNB 420 to the target xNB 420', and sends the reallocated UE IP address to UE 410. When UE 410 invokes computing services again, UE 410 can use the reallocated UE IP address as the source IP address for uplink packets. In another example, the xCF associated with the target xNB 420' can be a different xCF than xCF 440 (referred to as the target xCF). When UE 410 switches to the target xNB 420', xCF 440 can send a path switch request to the target xCF. The target xCF, based on UE 410's switch from xNB 420 to the target xNB 420', reassigns a UE IP for UE 410 to use for computing services and sends the reassigned UE IP to UE 410. When UE 410 invokes computing services again, UE 410 can use the reassigned UE IP as the source IP address for uplink packets.

[0101] It should be understood that although steps 422, 423, and 405 are shown as following the registration process (step 421), this is merely exemplary and not intended to be limiting. In some examples, steps 422, 423, and 405 may also occur between steps 406 and 407. In this way, the xNB or xCF can proactively assign a UE IP address to the UE for use with computing services. When the UE changes base stations, the xNB or xCF needs to reassign a UE IP address to the UE. That is, when the UE changes base stations, it can access computing services using the reassigned UE IP address, and the user plane path does not need to return to the anchor point corresponding to the original UE IP address, thereby achieving path optimization.

[0102] Figure 4C A schematic signaling diagram of a communication process 400C for IP address management according to some embodiments of this disclosure is shown. The communication process 400C may involve UE 410, xNB 420, xCF 440, and computing node #1 430. The same reference numerals are used to denote... Figure 4A and Figure 4B The elements or components described herein have the same operation Figure 4C The components, parts, or steps described herein will be omitted, and their detailed descriptions will be omitted. The communication process 400C can be considered as... Figure 2 This is a specific example of the communication process 200. It should be understood that the communication process 400C may also include additional boxes not shown and / or omit some boxes shown, and the scope of this disclosure is not limited thereto.

[0103] like Figure 4CAs shown, at 421, the registration process for UE 410 is performed. At 431, UE 410 initiates a default connection establishment process. UE 410 sends a default connection establishment request to xNB 420 or xCF 440 to establish a default connection between UE 410 and xNB 420, which is used to transmit the first packet of computing power services. Optionally, the default connection establishment request may carry Indicator-1. Indicator-1 may be the same as or similar to the Indicator-1 in communication procedure 400A. At 432, xNB 420 or xCF 440 assigns a UE IP for computing power services to UE 410 based on the Indicator-1 carried in the default connection establishment request. In some examples, the default connection establishment request may not carry Indicator-1. The xNB 420 or xCF 440 may assign a UE IP for computing services to UE 410 based on local configuration, and / or UE 410's subscription data, and / or policy information from the PCF. In some examples, the xNB 420 or xCF 440 may assign a UE IP for computing services to UE 410 based on the determination that a UE IP for computing services has not yet been assigned to UE 410, and based on the determination that UE 410 is allowed to use computing services. At 433, the xCF 440 or xNB 420 sends the UE IP, (optional) Indicator-2, and (optional) Indicator-3 to the UE. Indicator-2 and Indicator-3 may be the same or similar indication information as Indicator-2 and Indicator-3 in communication procedure 400A.

[0104] In this way, during the default connection establishment process, the xNB or xCF can assign a UE IP to the UE, which is then used for computing services. When the UE changes base stations, the xNB or xCF needs to reassign a UE IP. In other words, when the UE changes base stations, it can use the reassigned UE IP to access computing services, and the user plane path does not need to return to the anchor point corresponding to the original UE IP, thus achieving path optimization.

[0105] Return to reference Figure 2In some embodiments, when determining (218) the IP address used for computing power services, terminal device 210 may use the IP address for computing power services based on its local configuration. Alternatively or additionally, when determining (218) the IP address used for computing power services, terminal device 210 may use the IP address used for computing power services based on the received IP address. Alternatively or additionally, when determining (218) the IP address used for computing power services, terminal device 210 may use the IP address used for computing power services based on received indication information indicating that the IP address is used for computing power services.

[0106] In some embodiments, terminal device 210 may send a first request message to network device 220, and network device 220, in response to receiving the first request message, sends a response message to terminal device 210. The response message may include at least one of an IP address 206 and indication information indicating that the IP address is used for computing power services. Terminal device 210 may use the IP address for computing power services based on the response message. In one example, the first request message may be used for network registration. Network device 220 may send at least one of an IP address 206 and indication information indicating that the IP address is used for computing power services to terminal device 210 in a registration response. In another example, the first request message may be used to request the establishment of a default connection for transmitting the first packet of the computing power service. Network device 220 may send at least one of an IP address 206 and indication information indicating that the IP address is used for computing power services to terminal device 210 in a default connection establishment response. In yet another example, the first request message may be used to request an IP address. In other words, terminal device 210 may send a request message for requesting an IP address.

[0107] In some embodiments, the first request message may include indication information requesting the allocation of an IP address, such as Indicator-1. Network device 220 may determine that terminal device 210 requests an IP address based on Indicator-1 in the first request message, and thus send a response message including the IP address to terminal device 210. In some alternative embodiments, the first request message may not include the indication information requesting the acquisition of an IP address, and network device 220 may send a response message including the IP address to terminal device 210 based on local configuration, terminal device 210's subscription data, or policy information.

[0108] In some alternative embodiments, network device 220 may send at least one of IP address 206 and indication information indicating that the IP address is used for computing power services to terminal device 210 based on local configuration, subscription data, or policy information of terminal device 210, to instruct terminal device 210 to use the IP address. In some alternative examples, network device 220 may send at least one of IP address 206 and indication information indicating that the IP address is used for computing power services without receiving a request message. For example, after completing the registration and network access of terminal device 210, or after establishing a default connection between terminal device 210 and access network device, network device 220 may determine whether to allow terminal device 210 to use computing power services, and whether terminal device 210 has determined the IP address to be used for computing power services. If the terminal device 210 has not yet determined the IP address for use in the computing power service, and the terminal device 210 is allowed to use the computing power service, the network device 220 may send at least one of the following to the terminal device 210: IP address 206 and indication information indicating that the IP address is used for the computing power service, based on local configuration, the terminal device 210's subscription data, or policy information.

[0109] In some embodiments, the core network device may send an indication message to the access network device, which instructs the access network device to replace the source IP address in a message sent from the terminal device 210 to the computing power node 230 providing computing power services. Alternatively or additionally, the indication message instructs the access network device to replace the destination IP address in a message sent from the computing power node 230 providing computing power services to the terminal device 210.

[0110] In some embodiments, when terminal device 210 sends message 224 (222), access network device can receive the message from terminal device 210, which carries an IP address. Access network device can replace the source IP address in the message with a third IP address associated with terminal device 210, and send the message including the third IP address to computing node 230 of computing power service.

[0111] In some embodiments, the access network device may determine a third IP address associated with a terminal device and store a correspondence between the third IP address and at least one of the following: the identifier of the terminal device; information about the computing power service; or an IP address used by the computing power service. For example, the access network device may receive indication information from a core network device instructing the replacement of the source IP address in a message sent from the terminal device 210 to the computing power node 230 of the computing power service and / or the replacement of the destination IP address in a message sent from the computing power node 230 of the computing power service to the terminal device 210. The access network device may determine the third IP address in response to receiving this indication information. More specifically, the access network device may determine the third IP address upon receiving the indication information based on the absence of a stored correspondence associated with the terminal device 210, and store a correspondence between the third IP address and at least one of the following: the identifier of the terminal device; information about the computing power service; or an IP address used by the computing power service. In another example, the access network device may determine the third IP address based on a received message. More specifically, when the access network device receives a message from the terminal device 210, it can determine the third IP address based on the absence of a stored correspondence associated with the terminal device 210, and save the correspondence between the third IP address and at least one of the following: the identifier of the terminal device; information of the computing power service; or the IP address used by the computing power service.

[0112] In some embodiments, the access network device may also receive downlink packets including a third IP address from the computing node 230. Based on the mapping relationship of the third IP address, the access network device may replace the destination IP address in the downlink packet with the IP address used by the terminal device 21 for computing services, and send a downlink packet including the IP address to the terminal device 210.

[0113] Therefore, in some embodiments of this disclosure, different terminal devices can use the same IP address to send messages for computing power services. Before sending the message to the computing power node, the base station can replace the source IP address of the message; and before sending the downlink message for computing power services to the terminal device, it can replace the destination IP address of the message. Thus, the IP address used by the terminal device for computing power services may not have an anchor point. In a specific example, the specific IP address used for computing power services can be a specific IP address, such as "1.1.1.1". Different UEs can use the same specific IP address to send and receive messages for computing power services. This specific IP address is used only to fill the source IP field in the IP header of the computing power service message. Therefore, this message format is compatible with existing IP header designs. This specific IP address is unrelated to the UE's serving base station and core network element; in other words, the UE's serving base station or corresponding core network element cannot be determined through this specific IP address. Therefore, this specific IP address no longer has location meaning, i.e., it does not have an anchor point function. When a UE changes base stations, it does not need to reacquire the IP address used for computing power services, and the user plane path does not need to return to the anchor point, thus enabling path optimization.

[0114] Figure 4D A schematic signaling diagram of a communication process 400D for IP address management according to some embodiments of the present disclosure is shown. The communication process 400D may involve UE 410, xND 420, xCF 440, and computing node #1 430. The same reference numerals are used to denote... Figure 4A The elements or components described herein have the same operation Figure 4D The components, parts, or steps described herein will be omitted, and their detailed descriptions will be omitted. Communication process 400D can be considered as... Figure 2 This is a specific example of the communication process 200. It should be understood that the communication process 400D may also include additional boxes not shown and / or omit some boxes shown, and the scope of this disclosure is not limited thereto.

[0115] like Figure 4DAs shown, UE 410 sends a registration request to xNB 420 or via xNB 420 to xCF 440. Optionally, the registration request may carry Indicator-1, which indicates that UE 410 requests a specific IP for use with computing services. In some embodiments, different UEs may use the same specific IP as the source IP for computing service packets. In some embodiments, xNB 420 or xCF 440 may determine whether to allow UE 410 to use the specific IP as the source IP for computing service packets, or determine whether to allocate a specific IP for computing services to UE 410, based on at least one of Indicator-1, local configuration, UE 410's subscription data, and policy information from PCF. In some embodiments, xNB 420 or xCF 440 may allocate a specific IP to UE 410 based on determining that UE 410 is allowed to access computing services.

[0116] In some embodiments, at 423, xNB 420 sends an Indicator-to-UE to UE 410. In some embodiments, at 422, xCF 440 sends an Indicator-to-xNB and an Indicator-to-UE to xNB 420, and xNB 420 sends the Indicator-to-UE received from xCF 440 to UE 410. In some examples, the Indicator-to-UE is used to indicate that the UE is allowed to use a specific IP as the source IP for computing service messages. After receiving the Indicator-to-UE, UE 410 determines to use the specific IP for computing services. When the UE invokes computing services, the UE uses the specific IP as the source IP for the message. Alternatively, the Indicator-to-UE is used to indicate that a corresponding specific IP is available for use by computing services. After UE 410 receives the specific IP and the Indicator-to-UE, when UE 410 invokes computing services, UE 410 uses the specific IP as the source IP for the message.

[0117] In some embodiments, if UE 410 does not receive an Indicator-to-UE, UE 410 may determine, based on its local configuration, to use a specific IP when sending a message corresponding to the computing power service, or to determine that the received specific IP is a specific IP used by the computing power service.

[0118] In some embodiments, the Indicator-to-xNB sent by xCF 440 to xNB 420 indicates that the source IP address of the uplink packet for the computing power service is replaced with an IP address. Alternatively or concurrently, the Indicator-to-xNB indicates that the destination IP address of the downlink packet for the computing power service is replaced with an IP address.

[0119] In alternative embodiments, the transmission of specific IP, indicator-to-UE, and indicator-to-xNB (if any) can occur during the default connection establishment process. Alternatively or additionally, the transmission of specific IP, indicator-to-UE, and indicator-to-xNB (if any) can be independent processes. Alternatively or additionally, the transmission of specific IP, indicator-to-UE, and indicator-to-xNB (if any) can be actively triggered by xNB 420 or xCF 440 without requiring a request message from UE 410.

[0120] At 408, UE 410 uses the specific IP as the source IP for the computing service message. At 444, after receiving the uplink message, xNB 420 replaces the source IP of the uplink message with the IP address (IP@xNB) assigned by xNB 420, based on the Indicator-to-xNB received at 442 or according to its local configuration. The computing service message can be the first message used for computing services.

[0121] In some embodiments, the UE IP address allocated by xNB 420 may be allocated by xNB 420 in response to receiving an "Indicator-to-xNB" message in step 442, or by xNB 420 in response to receiving an uplink message (e.g., the first packet) for the computing power service. In some embodiments, xNB 420 may maintain a mapping between specific IP addresses, the IP addresses allocated by xNB 420, UE identifiers (e.g., DRB, C-RNTI), and (optionally) computing power services. In some implementations, xNB 420 allocates an IP address to UE 410 only if it determines that an IP address has not yet been allocated to UE 410 (e.g., when xNB 420 has not maintained the aforementioned mapping). In some implementations, xNB 420 may allocate a port to UE 410, meaning that xNB allocates the same IP address and different ports to different UEs. This depends on the existence of network layer and transport layer connections between xNB and the computing power node.

[0122] After receiving an uplink message from UE 410, xNB 420 can identify whether the uplink message corresponds to a computing service. If xNB 420 determines that the uplink message corresponds to a computing service, it proceeds to step 444.

[0123] In the first example, the xNB 420 can identify whether an uplink packet corresponds to a computing service based on the destination IP address. For example, if the destination IP address of the uplink packet is "anycast," then the packet corresponds to a computing service. In the second example, when establishing an air interface connection, if the air interface connection is used to transmit packets for computing services, the xNB 420 stores the mapping between the air interface connection identifier and the computing service identifier (flag). The air interface connection identifier can include DRB ID, SRB ID, C-RNTI, etc. When the xNB 420 receives an uplink packet from the corresponding air interface connection, the xNB 420 can determine that the uplink packet corresponds to a computing service. In the third example, the xNB 420 can parse the content of the received packet; if the packet content carries computing power, the xNB 420 can determine that the packet corresponds to a computing service. In the fourth example, the xNB 420 can identify whether an uplink packet corresponds to a computing service based on the source IP address of the uplink packet. For example, if the source IP of the uplink packet is a specific IP, the xNB420 can determine the computing power service corresponding to the packet.

[0124] At 444, xNB 420 replaces the source IP of the uplink message corresponding to the computing power service from the specific IP to the IP address assigned by xNB 420. At 445, based on the destination IP address of the message, xNB 420 sends the message to computing node #1 430. At 446, computing node #1 430 returns a downlink message to xNB 420, the destination IP of which is the IP address assigned by xNB 420. At 447, xNB 420 replaces the destination IP from the IP address assigned by xNB 420 with the specific IP based on the Indicator-to-xNB received at 442, or based on local configuration and stored mappings. Furthermore, xNB 420 can determine that the destination of the downlink message is UE 410. At 412, xNB 420 sends the downlink message to UE 410.

[0125] Understandably, during communication process 400D, the UE uses a specific IP as the source IP for packets. This specific IP does not need to be bound to the address pool of the xNB 420. Therefore, even if the UE moves and undergoes xNB handover, it does not need to reacquire the specific IP. In this way, the source IP of the packet is no longer anchored to a fixed node, so when the UE moves, the user plane path does not need to be anchored to a fixed node, thus achieving path optimization.

[0126] Some embodiments of this disclosure relate to IP address management schemes for computing power services, supporting UEs to use IP addresses designated for computing power services to send computing power service packets. On one hand, some embodiments of this disclosure can support the reallocation of UE IP addresses for computing power services when a UE changes base stations. When transmitting computing power service packets, the user plane path does not need to return to the anchor point corresponding to the original UE IP, thereby optimizing the path. On the other hand, some embodiments of this disclosure can support UEs to use IP addresses without anchor points to send computing power service packets. When the UE moves, the user plane path does not need to be anchored to a fixed node, thereby optimizing the path. In this way, communication latency can be reduced. Although this disclosure has been described with reference to illustrative embodiments, it is not intended to be interpreted in a limiting sense. It will be understood that various modifications and combinations of the illustrative embodiments, as well as other embodiments of this disclosure, will be apparent to those skilled in the art. Those skilled in the art can combine these various embodiments and variations without demonstrating any ingenuity.

[0127] Figure 5 A schematic flowchart of a method 500 implemented at a terminal device according to an embodiment of the present disclosure is shown. In one possible implementation, method 500 may be implemented by UE 110 or terminal device 210. In other possible implementations, method 500 may also be implemented by other communication devices. As an example, method 500 will be described below as being implemented by terminal device 210.

[0128] In box 510, UE 110 determines the Internet Protocol (IP) address to be used for computing services. In box 520, UE 110 uses the IP address to send messages for computing services.

[0129] Understandably, Method 500 may also include references in this article. Figures 1A to 4D Any other operations or actions performed by the UE in some embodiments of this application as described herein will not be repeated here.

[0130] Figure 6A schematic flowchart illustrating a method 600 implemented at a network device according to an embodiment of the present disclosure is shown. In one possible implementation, method 600 may be implemented by network device 220. In other possible implementations, method 600 may also be implemented by other communication devices. As an example, method 600 will be described below as being implemented by network device 220.

[0131] In block 610, network device 220 determines the Internet Protocol (IP) address used by the UE for computing services. In block 620, network device 220 sends at least one of the following to the UE: the IP address; or first indication information indicating that the IP address is used for computing services.

[0132] It is understandable that method 600 may also include, with reference to Figures 1 to 12 of this document. Figure 4D Any other operations or actions performed by the base station or xCF in some embodiments of this application as described herein will not be repeated here.

[0133] Figure 7This is a block diagram that can be used to implement device 700 according to some embodiments of this application. In some embodiments, device 700 may be a component of a communication network infrastructure, such as a base station (e.g., a NodeB, an evolved NodeB (eNodeB or eNB), a next-generation NodeB (sometimes called a next-generation NodeB, gNodeB or gNB), a home subscriber server (HSS), a gateway (GW), such as a packet gateway (PGW) or a serving gateway (SGW), or various other nodes or functions within a core network (CN) or a Public Land Mobility Network (PLMN). In other embodiments, device 700 may be a device connected to the network infrastructure via a wireless interface, such as a mobile phone, a smartphone, or other such device that can be classified as User Equipment (UE). In some embodiments, device 700 may be a Machine Type Communications (MTC) device (also known as a machine-to-machine (M2M) device), or another such device that, although not providing direct service to a user, can be classified as a UE. In some embodiments, device 700 may be a roadside unit. The device 700 can be classified as a mobile unit (RSU), vehicle UE (V-UE), pedestrian UE (P-UE), or infrastructure UE (I-UE). In some scenarios, the device 700 may also be referred to as a mobile device, a term intended to reflect a device connected to a mobile network, regardless of whether the device itself is designed for or capable of being mobile. A particular device may utilize all or only a subset of the components shown, and the level of integration may vary depending on the device. Furthermore, the device 700 may contain multiple instances of components, such as multiple processors, memory, transmitters, receivers, etc.

[0134] Device 700 typically includes a processor 702, such as a central processing unit (CPU), and may further include a dedicated processor, such as a graphics processing unit (GPU) or other such processor, memory 704, a network interface 706, and a bus 708 for connecting the components of device 700. Optionally, device 700 may also include components such as a mass storage device 710, a video adapter 712, and an I / O interface 716 (shown in dashed lines).

[0135] Memory 704 may include any type of non-transitory system memory readable by processor 702, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or combinations thereof. In one embodiment, memory 704 may include more than one type of memory, such as ROM used at startup and DRAM used for program and data storage during program execution. Bus 708 may be one or more of a plurality of bus architectures of any type, including a memory bus or memory controller, a peripheral bus, or a video bus.

[0136] The device 700 may also include one or more network interfaces 706, which may include at least one of a wired network interface and a wireless network interface. For example... Figure 7 As shown, network interface 706 may include a wired network interface for connecting to network 722, and may also include a wireless access network interface 720 for connecting to other devices via a wireless link. When device 700 is a network infrastructure element, the wireless access network interface 720 may be omitted for nodes or functions that are elements of a PLMN rather than elements at the wireless edge. When device 700 is infrastructure at the wireless edge of the network, it may include both wired and wireless network interfaces. When device 700 is a wirelessly connected device, such as a user equipment, the wireless access network interface 720 may be present, and may be supplemented by other wireless interfaces such as a WiFi network interface. Network interface 706 allows device 700 to communicate with remote entities such as those connected to network 722.

[0137] Mass storage 710 may include any type of non-transitory storage device configured to store data, programs, and other information and make the data, programs, and other information accessible via bus 708. Mass storage 710 may include, for example, one or more of a solid-state drive, hard disk drive, disk drive, or optical disk drive. In some embodiments, mass storage 710 may be located remotely from device 700 and may be accessed using a network interface such as interface 706. In the illustrated embodiment, mass storage 710 is distinct from the memory 704 that includes it, and mass storage 710 typically performs storage tasks compatible with higher latency but typically provides low or no fluctuation. In some embodiments, mass storage 710 may be integrated with heterogeneous memory 704.

[0138] Optional video adapter 712 and I / O interface 716 (shown in dashed lines) provide interfaces for coupling device 700 to external input and output devices. Examples of input and output devices include a display 66 coupled to video adapter 712 and an I / O device 718, such as a touchscreen, coupled to I / O interface 716. Other devices may be coupled to device 700 and may utilize additional or fewer interfaces. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide interfaces for external devices. Those skilled in the art will understand that in embodiments where device 700 is part of a data center, I / O interface 716 and video adapter 712 may be virtualized and provided via network interface 706.

[0139] Figure 8 This is a schematic diagram of the structure of a device 800 according to some embodiments of this application. For example... Figure 8 As shown, device 800 includes a determining unit 802 and a transmitting unit 804. Device 800 can be applied to the communication system shown in FIG. 1 and can implement any of the methods provided in the embodiments above. Optionally, the physical manifestation of device 800 can be a communication device, such as a network device or UE. Alternatively, device 800 can be other devices capable of implementing the functions of a communication device, such as a processor or chip inside the communication device. Specifically, device 800 can be a programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system on a chip (SOC).

[0140] In some embodiments, the determining unit 802 may be configured to determine the Internet Protocol (IP) address used for the computing power service. The sending unit 804 may be configured to send messages for the computing power service using the IP address.

[0141] In some other embodiments, apparatus 800 may include various other units or modules that can be configured to perform the various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated here.

[0142] Figure 9 This is a schematic diagram of the structure of a device 900 according to some embodiments of this application. For example... Figure 9 As shown, the device 900 includes a determining unit 902 and a transmitting unit 904. The device 900 can be applied to the communication system shown in FIG. 1 and can implement any of the methods provided in the embodiments described above. Optionally, the physical manifestation of the device 900 can be a communication device, such as a network device or a UE. Alternatively, the device 900 can be other devices capable of implementing the functions of a communication device, such as a processor or chip within the communication device. Specifically, the device 900 can be a programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system on a chip (SOC).

[0143] In some embodiments, the determining unit 902 may be configured to determine the Internet Protocol (IP) address used by the terminal device for computing power services. The sending unit 904 may be configured to send at least one of the following to the terminal device: the IP address; or first indication information indicating that the IP address is used for computing power services.

[0144] In some other embodiments, the apparatus 900 may include various other units or modules that can be configured to perform the various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated here.

[0145] It should be noted that the module division in the above embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical units, or be integrated into one unit by two or more units. The integrated units described above can be implemented in hardware or as software functional units.

[0146] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, or all or part of it, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0147] Based on the above embodiments, this application also provides a computer program that, when run on a computer, causes the computer to execute any of the methods provided in the above embodiments.

[0148] Based on the above embodiments, this application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a computer, it causes the computer to perform any of the methods provided in the above embodiments. The storage medium can be any available medium that can be accessed by a computer. By way of example, but not limited to, a computer-readable medium may include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code having the form of instructions or data structures and that can be accessed by a computer.

[0149] Based on the above embodiments, this application also provides a chip for reading a computer program stored in a memory and implementing any of the methods provided in the above embodiments.

[0150] Based on the above embodiments, this application provides a chip system including a processor for supporting a computer device in implementing the functions involved in the communication devices in the above embodiments. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete components.

[0151] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0152] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0153] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0154] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0155] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of protection of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method, characterized in that, include: Determine the Internet Protocol (IP) address used to provide computing power services; as well as Send the message for the computing power service using the IP address.

2. The method according to claim 1, characterized in that, The IP address used to provide computing power services includes: The IP address is determined for use by the computing power service based on at least one of the following: Local configuration of the terminal device; or Receive a first message, the first message including at least one of the following: The IP address; or The first indication information indicates that the IP address is used for the computing power service.

3. The method according to claim 1, characterized in that, Also includes: Receive a second message including the IP address.

4. The method according to claim 3, characterized in that, The IP address used to provide computing power services includes: The IP address is determined to be used for the computing power service based on at least one of the following: The second message includes a second indication, which indicates that the IP address is used for the computing power service; Local configuration of the terminal device; or The second message includes the IP address.

5. The method according to any one of claims 2 to 4, characterized in that, Also includes: Sending a first request message, wherein the first request message is used for at least one of the following: Register and join the network. Obtain the IP address, or Establish a default connection, which is used to transmit the first packet of the computing power service.

6. The method according to claim 5, characterized in that, The first request message includes third indication information, which indicates a request to allocate the IP address.

7. The method according to claim 3 or 4, characterized in that, The IP address is the first IP address, and the method further includes: Based on the replacement of the access network equipment by the terminal device, a second IP address is determined for use by the computing power service.

8. The method according to claim 7, characterized in that, The step of determining the second IP address for the computing power service based on the replacement of the access network equipment by the terminal equipment includes: The second IP address is determined based on at least one of the following: The second message includes a fourth indication, which indicates that when the terminal device changes its access network equipment, it obtains a second IP address for use by the computing power service. The local configuration of the terminal device; or The second message includes the first IP address.

9. A communication method, characterized in that, include: Determine the Internet Protocol (IP) address used by the terminal device to provide computing power services; as well as Send at least one of the following to the terminal device: The IP address; or The first indication information indicates that the IP address is used for the computing power service.

10. The method according to claim 9, characterized in that, Also includes: The IP address is assigned to the terminal device or the terminal device is allowed to use the IP address for the computing power service based on at least one of the following: It has been determined that the IP address has not yet been assigned to the terminal device; Determine whether to allow the terminal device to use the computing power service; Local configuration; The contract data of the terminal device; Strategy information; or The first request message received is used for at least one of the following: registering to the network, obtaining an IP address for use by the computing power service, or establishing a default connection, wherein the default connection is used to transmit the first packet of the computing power service.

11. The method according to claim 10, characterized in that, The first request message includes third indication information, which indicates a request to allocate the IP address.

12. The method according to any one of claims 9 to 11, characterized in that, The IP address is a first IP address, and the method further includes sending at least one of the following: The fourth indication information indicates that when the terminal device changes its access network equipment, it should obtain a second IP address for use in the computing power service; or The second indication information indicates that the IP address is used for the computing power service.

13. The method according to any one of claims 9 to 12, characterized in that, Also includes: Send a fifth instruction message, which indicates at least one of the following: Replace the source IP address in the message sent from the terminal device to the computing power node of the computing power service; or Replace the destination IP address in the message sent from the computing power node of the computing power service to the terminal device.

14. The method according to any one of claims 9 to 12, characterized in that, Also includes: Receive a fifth instruction message, which indicates at least one of the following: Replace the source IP address in the message sent from the terminal device to the computing node; or Replace the destination IP address in the message sent from the computing node to the terminal device.

15. The method according to any one of claims 9 to 12 or 14, characterized in that, Also includes: Receive a message from the terminal device, the message carrying the IP address; Replace the source IP address in the message with a third IP address associated with the terminal device; as well as Send the message including the third IP address to the computing power node of the computing power service.

16. The method according to claim 15, characterized in that, Also includes: Determine the third IP address associated with the terminal device; and Save the correspondence between the third IP address and at least one of the following: The identifier of the terminal device; Information about the computing power service; or The IP address.

17. The method according to claim 16, characterized in that, The determination of the third IP address associated with the terminal device includes: The third IP address is determined based on the received fifth indication information or based on the received message. The fifth indication information indicates at least one of the following: Replace the source IP address in the message sent from the terminal device to the computing node; or Replace the destination IP address in the message sent from the computing node to the terminal device.

18. The method according to claim 17, characterized in that, The determination of the third IP address associated with the terminal device includes: The third IP address is determined based on the absence of a stored correspondence associated with the terminal device.

19. The method according to any one of claims 16 to 18, characterized in that, Also includes: Receive downlink packets including the third IP address from the computing node; Based on the aforementioned correspondence, the destination IP address in the downlink message is replaced by the IP address instead of the third IP address; as well as Send the downlink message including the IP address to the terminal device.

20. The method according to any one of claims 9 to 12, characterized in that, The method further includes: (The terminal device is switched from the first network device to the second network device.) The first network device sends a sixth instruction message or a seventh instruction message to the second network device. The sixth instruction message indicates that the terminal device is allowed to use the computing power service, and the seventh instruction message indicates that an IP address is allocated to the terminal device for use by the computing power service. The first network device is a first access network device or a first core network device, and the second network device is a second access network device or a second core network device.

21. The method according to any one of claims 9 to 12, characterized in that, The IP address is a first IP address, and the terminal device is switched from the first network device to the second network device. The method further includes: The second network device receives a sixth indication message or a seventh indication message from the first network device, wherein the sixth indication message indicates that the terminal device is allowed to use the computing power service, and the seventh indication message indicates that an IP address is allocated to the terminal device for use by the computing power service; and A second message is sent to the terminal device, the second message including a second IP address for use by the computing power service.

22. The method according to any one of claims 9 to 12, characterized in that, The IP address is a first IP address, and the terminal device is switched from a first access network device to a second access network device. The method further includes: The second access network device sends a second request message to the core network device, the second request message being used to request the allocation of an IP address for the terminal device to use for the computing power service; Receive a second message from the core network device, the second message including a second IP address for use by the computing power service; and The second message is sent to the terminal device.

23. The method according to any one of claims 9 to 12, characterized in that, The IP address is a first IP address, and the terminal device is switched from a first access network device to a second access network device. The method further includes: The core network device receives a second request message from the second access network device. The second request message is used to request that the terminal device be allocated an IP address for use by the computing power service. Determine the second IP address to be used by the computing power service; and Send a second message to the second access network device, the second message including the second IP address.

24. A communication device, characterized in that, Includes one of the following: Units or modules used to perform the method according to any one of claims 1 to 8, or Units or modules for performing the method according to any one of claims 9 to 23.

25. A communication device, characterized in that, include: The processor is configured to perform one of the following: The method according to any one of claims 1 to 8, or The method according to any one of claims 9 to 23.

26. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed by the device, cause the device to perform one of the following: The method according to any one of claims 1 to 8, or The method according to any one of claims 9 to 23.

27. A computer program product, characterized in that, The computer program product includes instructions that, when executed by a device, cause the device to perform one of the following: The method according to any one of claims 1 to 8, or The method according to any one of claims 9 to 23.

28. A chip, characterized in that, Includes a processor and a communication interface, the processor reading instructions stored in memory via the communication interface to execute one of the following: The method according to any one of claims 1 to 8, or The method according to any one of claims 9 to 23.

29. A communication system, characterized in that, include: A communication device for performing the method according to any one of claims 1 to 8, and A communication device for performing the method according to any one of claims 9 to 23.

Images