Communication method, apparatus, system and storage medium
In the edge computing deployment scenario, the first network element receives and sends IP address ranges, ensuring that the edge migration target EAS is within the authorization scope, solving the problem of low edge migration efficiency and achieving efficient service flow migration.
Patent Information
- Application Number
- PCT/CN2024/091544
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-12
- Filing Date
- 2024-05-07
- Publication Date
- 2024-11-21
AI Technical Summary
In edge computing deployment scenarios, edge migration efficiency is low, and the existing technology is difficult to effectively solve the problem of failure in business flow migration caused by terminal mobility and edge application server load balancing.
The first network element receives the IP address range that allows the terminal to route to the VPLMN, and sends the first IP address range to the third network element to ensure that the target EAS is within the authorization range, thereby successfully completing edge migration and improving migration efficiency.
It implements the IP address range of the authorized terminal access to the V-SMF during the session establishment, during the establishment process, or after the establishment, ensuring the efficiency and success rate of edge migration, and avoiding resource waste and multiple denial issues.
Smart Images

Figure CN2024091544_21112024_PF_FP_ABST
Abstract
Description
Communication method, device, system and storage medium
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 12, 2023, with application number 202310539711.5 and invention name “Communication Method, Device, System and Storage Medium”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communication technology, and in particular to a communication method, device, system and storage medium. Background Art
[0003] In edge computing (EC) deployment scenarios, due to terminal mobility and edge application server (EAS) load balancing, service flows need to be migrated to the EAS to ensure service continuity. In home routed with session breakout (HR-SBO) roaming scenarios, to maintain control of the home PLMN (HPLMN) over locally offloaded services, the home-session management function (H-SMF) indicates to the visited-session management function (V-SMF) the IP address range authorized for access in the visited public land mobile network (VPLMN) during, during, or after session establishment.
[0004] In the prior art, edge migration is prone to failure, that is, edge migration efficiency is low.
[0005] Summary of the Invention
[0006] The present application provides a communication method, device, system and storage medium to improve the efficiency of edge migration.
[0007] In a first aspect, a communication method is provided. The method may be performed by a first network element, or by a module (e.g., a processor, a chip, or a chip system) applied to the first network element. The method may also be implemented by a logical node, a logical module, or software that implements all or part of the functions of the first network element. Exemplarily, the first network element may be a V-SMF.
[0008] The method includes: a first network element receives a second Internet Protocol (IP) address range from a second network element that allows a terminal to be routed to a local data network of a VPLMN; the first network element sends a first IP address range to a third network element based on the second IP address range; and the first network element receives first indication information from the third network element, where the first indication information is used to instruct the first network element to migrate a service flow between the terminal and a source EAS to a target EAS, where the IP address of the target EAS belongs to the first IP address range.
[0009] In this aspect, the first network element sends a first IP address range that allows the terminal to be routed to the local data network of the VPLMN to the third network element, so that when the third network element is triggered to perform edge migration, the target EAS is determined according to the first IP address range, and the service flow between the terminal and the source EAS is migrated to the target EAS according to the instruction of the third network element, so that the target EAS is authorized, thereby enabling successful migration and improving the efficiency of edge migration.
[0010] Exemplarily, the first IP address range is determined based on the second IP address range. The first IP address range may be smaller than or equal to the second IP address range.
[0011] In a possible implementation, the source EAS includes the EAS that serves the terminal before the migration, and the target EAS includes the EAS that serves the terminal after the migration.
[0012] In another possible implementation, the first network element sends the first IP address range to the third network element based on the second IP address range, including: the first network element receives a subscription request from the third network element, and the subscription request is used to request subscription to the first IP address range corresponding to at least one terminal; and the first network element sends a notification message to the third network element, and the notification message includes the first IP address range corresponding to the at least one terminal.
[0013] In this implementation, the first network element may send the first IP address range that allows the terminal to be routed to the local data network of the VPLMN to the third network element through a subscription process.
[0014] In another possible implementation, before the first network element sends the first IP address range to the third network element based on the second IP address range, the method also includes: the first network element receives second indication information from the third network element, and the second indication information is used to instruct the first network element to replace the IP address of the user message; and the first network element sends a rejection information to the third network element, and the rejection information is used to instruct the first network element to refuse to replace the IP address of the user message.
[0015] In this implementation, after receiving an instruction from the third network element instructing the first network element to migrate the service flow between the terminal and the source EAS to the first target EAS, if the first network element finds that the first target EAS is not within the first IP address range of the local data network that allows the terminal to be routed to the VPLMN, the first network element sends a rejection message to the third network element, and the third network element sends the first IP address range, so that the third network element can select the second target EAS within the first IP address range, so that the third network element can instruct the first network element and L-PSA to successfully complete the edge migration, thereby improving the efficiency of edge migration.
[0016] In another possible implementation, the rejection information includes the first IP address range.
[0017] In this implementation, the first IP address range may be included in the rejection information. Additionally, the first IP address range and the rejection information may be in different messages.
[0018] In another possible implementation, after the first network element receives the first indication information from the third network element, the method further includes: the first network element instructing the fourth network element to replace the IP address of the user message.
[0019] In another possible implementation, the first indication information includes the IP address of the target EAS.
[0020] In another possible implementation, the first indication information further includes at least one of the following information: the port number of the target EAS, the IP address of the source EAS, and the port number of the source EAS.
[0021] In another possible implementation, the first network element is a session management network element of the VPLMN, and the first network element is configured to obtain the second IP address range from the session management network element of the HPLMN.
[0022] In a second aspect, a communication method is provided. The method may be performed by a third network element, or by a module (e.g., a processor, chip, or chip system) applied to the third network element. The method may also be implemented by a logical node, logical module, or software that implements all or part of the functions of the third network element. Exemplarily, the third network element may be an application function (AF).
[0023] The method includes: a third network element obtains a first IP address range of a local data network that allows the terminal to be routed to a VPLMN; and the third network element sends first indication information to the first network element, where the first indication information is used to instruct the first network element to migrate the service flow between the terminal and the source EAS to the target EAS, and the IP address of the target EAS belongs to the first IP address range.
[0024] In a possible implementation, the source EAS includes the EAS that serves the terminal before the migration, and the target EAS includes the EAS that serves the terminal after the migration.
[0025] In another possible implementation, the third network element obtains the first IP address range of the local data network that allows the terminal to be routed to the VPLMN, including: the third network element sends a subscription request to the first network element, and the subscription request is used to request subscription to the first IP address range corresponding to at least one terminal; and the third network element receives a notification message from the first network element, and the notification message includes the first IP address range corresponding to the at least one terminal.
[0026] In another possible implementation, the third network element obtains a first IP address range of a local data network that allows the terminal to be routed to the VPLMN, including: the third network element instructs the first network element to replace the IP address of the user message; the third network element receives rejection information from the first network element, and the rejection information is used to instruct the first network element to refuse to replace the IP address of the user message; and the third network element receives the first IP address range from the first network element.
[0027] In another possible implementation, the first IP address range is storage information of the third network element.
[0028] In another possible implementation, before the third network element sends the first indication information to the first network element, the method further includes: the third network element determining that the service flow is a first type of service flow.
[0029] In another possible implementation, the method further includes: the third network element selecting a target EAS corresponding to the target IP address in the first IP address range according to the location of the terminal and / or a load condition of at least one EAS corresponding to the first IP address range.
[0030] In another possible implementation, the first indication information includes the IP address of the target EAS.
[0031] In another possible implementation, the first indication information further includes at least one of the following information: the port number of the target EAS, the IP address of the source EAS, and the port number of the source EAS.
[0032] In a third aspect, a communication method is provided. The method may be performed by a first network element, or by a module (e.g., a processor, a chip, or a chip system) applied to the first network element. The method may also be implemented by a logical node, a logical module, or software that implements all or part of the functions of the first network element. Exemplarily, the first network element may be a V-SMF.
[0033] The method includes: a first network element receives a second IP address range from a second network element that allows the terminal to be routed to a local data network of a VPLMN; the first network element receives first information from a third network element, the first information including a correspondence between at least one EAS and at least one weight factor; the first network element determines, based on the first information, a target EAS belonging to a first IP address range, the first IP address range being related to the second IP address range; the first network element sends first indication information to the third network element, the first indication information being used to indicate the target EAS; and the first network element receives second indication information from the third network element, the second indication information being used to indicate the first network element to migrate the service flow between the terminal and the source EAS to the target EAS.
[0034] In this aspect, V-SMF can accurately determine the target EAS based on the correspondence between at least one EAS and at least one weight factor provided by AF, according to the first IP address range and the correspondence, thereby improving the success rate of migrating business flows to the target EAS and improving the efficiency of edge migration.
[0035] In a possible implementation, the source EAS includes the EAS that serves the terminal before the migration, and the target EAS includes the EAS that serves the terminal after the migration.
[0036] In another possible implementation, the first network element determines the target EAS belonging to the first IP address range based on the first information, including: the first network element determines all EASs in the first information that belong to the first IP address range, and selects the EAS with the largest weight factor as the target EAS among the determined EASs based on the correspondence between the at least one EAS and the at least one weight factor.
[0037] In another possible implementation, the second indication information includes the IP address of the target EAS.
[0038] In another possible implementation, the second indication information further includes at least one of the following information: the port number of the target EAS, the IP address of the source EAS, and the port number of the source EAS.
[0039] In another possible implementation, after the first network element receives the second indication information from the third network element, the method further includes: the first network element instructing the fourth network element to replace the IP address of the user message.
[0040] In another possible implementation, the first network element is a session management network element of the VPLMN, and the first network element is configured to obtain the second IP address range from the session management network element of the HPLMN.
[0041] In a fourth aspect, a communication method is provided. The method may be performed by a third network element, or by a module (e.g., a processor, chip, or chip system) applied to the third network element. The method may also be implemented by a logical node, logical module, or software that implements all or part of the third network element's functions. Exemplarily, the third network element may be an AF.
[0042] The method includes: a third network element sends first information to a first network element, the first information including a correspondence between at least one EAS and at least one weight factor; the third network element receives first indication information from the first network element, the first indication information is used to indicate a target EAS; and the third network element sends second indication information to the first network element, the second indication information is used to instruct the first network element to migrate the service flow between the terminal and the source EAS to the target EAS, the IP address of the target EAS belongs to a first IP address range, and the first IP address range is the IP address range corresponding to the EAS that the terminal is authorized by the home public land mobile network HPLMN to roam to the visited public land mobile network VPLMN to access.
[0043] In a possible implementation, the method further includes: the third network element determining that the service flow is a first type of service flow.
[0044] In another possible implementation, the source EAS includes the EAS that serves the terminal before the migration, and the target EAS includes the EAS that serves the terminal after the migration.
[0045] In another possible implementation, the second indication information includes the IP address of the target EAS.
[0046] In another possible implementation, the second indication information further includes at least one of the following information: the port number of the target EAS, the IP address of the source EAS, and the port number of the source EAS.
[0047] In a fifth aspect, a communication device is provided, configured to implement the communication method in the first aspect or any one of its implementations; or configured to implement the communication method in the third aspect or any one of its implementations. The device may be a first network element, a module (e.g., a processor, a chip, or a chip system) applied to the first network element, or a logical node, a logical module, or software capable of implementing all or part of the functions of the first network element.
[0048] In a sixth aspect, a communication device is provided, configured to implement the communication method in the second aspect or any one of its implementations; or configured to implement the communication method in the fourth aspect or any one of its implementations. The device may be a third network element, a module (e.g., a processor, a chip, or a chip system) applied to a third network element, or a logical node, a logical module, or software capable of implementing all or part of the functions of a third network element.
[0049] In a possible implementation, the communication device in the fifth to sixth aspects includes a module for respectively executing the method in any one of the first to fourth aspects or any one of the implementations.
[0050] In another possible implementation, the communication device in the fifth to sixth aspects includes a processor coupled to a memory; the processor is configured to enable the device to perform the corresponding functions in the above-mentioned communication method. The memory is used to couple with the processor and store the necessary programs (instructions) and / or data for the device. Optionally, the communication device may further include a communication interface for enabling communication between the device and other network elements. Optionally, the memory may be located inside or outside the communication device.
[0051] In another possible implementation, the communication device in the fifth to sixth aspects includes a processor and a transceiver, the processor being coupled to the transceiver, and the processor being used to execute a computer program or instruction to control the transceiver to receive and send information; when the processor executes the computer program or instruction, the processor is also used to implement the above method through a logic circuit or execution code instruction. The transceiver may be a transceiver, a transceiver circuit, or an input / output interface, configured to receive signals from other communication devices other than the communication device and transmit them to the processor, or to send signals from the processor to other communication devices other than the communication device. When the communication device is a chip, the transceiver is a transceiver circuit or an input / output interface.
[0052] When the communication device in the fifth and sixth aspects is a chip, the transmitting unit may be an output unit, such as an output circuit or a communication interface; and the receiving unit may be an input unit, such as an input circuit or a communication interface. When the communication device is a terminal, the transmitting unit may be a transmitter or a transmitter; and the receiving unit may be a receiver or a receiver.
[0053] In a seventh aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When the computer program or instruction is executed, the methods described in the above aspects are implemented.
[0054] In an eighth aspect, a computer program product comprising instructions is provided, which, when executed on a communication device, causes the communication device to execute the methods described in the above aspects.
[0055] In a ninth aspect, a communication system is provided, which includes a second network element, the communication device described in the fifth aspect, and the communication device described in the sixth aspect. BRIEF DESCRIPTION OF THE DRAWINGS
[0056] FIG1 is a simplified schematic diagram of a wireless communication system provided by an embodiment of the present application;
[0057] FIG2 is a schematic diagram of a non-roaming 5G edge computing offload architecture provided in an embodiment of the present application;
[0058] FIG3 is a schematic diagram of an edge migration process provided in an embodiment of the present application;
[0059] FIG4 is a schematic diagram of the architecture of session-separated home routing roaming provided in an embodiment of the present application;
[0060] FIG5 is a flow chart of a communication method provided in an embodiment of the present application;
[0061] FIG6 is a flow chart of another communication method provided in an embodiment of the present application;
[0062] FIG7 is a flow chart of another communication method provided in an embodiment of the present application;
[0063] FIG8 is a flow chart of another communication method provided in an embodiment of the present application;
[0064] FIG9 is a schematic structural diagram of a communication device provided in an embodiment of the present application;
[0065] FIG10 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0066] The embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application.
[0067] The following at least one (item) involved in this application indicates one (item) or more (items). More than one (item) refers to two (items) or more than two (items). "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. In addition, it should be understood that although the terms first, second, etc. may be used to describe each object in this application, these objects should not be limited to these terms. These terms are only used to distinguish each object from each other.
[0068] The terms "including" and "having" and any variations thereof mentioned in the following description of this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices. It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any method or design described in this application as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other methods or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way.
[0069] The technology provided by this application can be applied to various communication systems. For example, the communication system can be a fourth generation (4G) th generation, 4G) communication systems (such as long term evolution (LTE) systems), fifth generation (5 thThe 5G communication system may also be referred to as a new radio (NR) system.
[0070] A network element in a communication system can send signals to or receive signals from another network element. The signals may include information, signaling, or data. The network element may also be replaced by an entity, a network entity, a device, a communication device, a communication module, a node, a communication node, etc. The present application uses the network element as an example for description. For example, a communication system may include at least one terminal and at least one access network device. The access network device may send downlink signals to the terminal, and / or the terminal may send uplink signals to the access network device. In addition, it is understood that if the communication system includes multiple terminals, the multiple terminals may also send signals to each other, that is, the signal sending network element and the signal receiving network element may both be terminals.
[0071] Referring to Figure 1, Figure 1 is a simplified schematic diagram of a wireless communication system provided in an embodiment of the present application. As shown in Figure 1, the wireless communication system includes a wireless access network 100. The wireless access network 100 can be a next-generation (e.g., 6G or higher) wireless access network, or a traditional (e.g., 5G or 4G) wireless access network. One or more communication devices (120a-120j, collectively referred to as 120) can be connected to each other or to one or more network devices (110a, 110b, collectively referred to as 110) in the wireless access network 100. Figure 1 is only a schematic diagram, and the wireless communication system may also include other devices, such as core network devices, wireless relay devices and / or wireless backhaul devices, which are not shown in Figure 1.
[0072] For example, in actual applications, the wireless communication system may include multiple network devices (also called access network devices) at the same time, or may include multiple communication devices at the same time. A network device may serve one or more communication devices at the same time. A communication device may also access one or more network devices at the same time. The embodiments of the present application do not limit the number of communication devices and network devices included in the wireless communication system.
[0073] The network device may be an entity on the network side for transmitting or receiving signals. The network device may be an access device for a communication device to access the wireless communication system in a wireless manner, such as a base station. The base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), access network equipment in open radio access network (O-RAN), relay station, access point, transmission point (TRP), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard wireless node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), radio unit (RU), centralized unit control plane (CU-CP) node, centralized unit user plane (CU user The base station may be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The network device may also refer to a communication module, a modem or a chip provided in the aforementioned device or apparatus. The network device may also be a mobile switching center and a device to device (D2D), vehicle-to-everything (V2X), a device that performs the base station function in machine-to-machine (M2M) communications, a network side device in a 6G network, a device that performs the base station function in a future communication system, etc. The network device may support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.
[0074] All or part of the functions of the network device in this application may also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform). The network device in this application may also be a logical node, logical module, or software that can implement all or part of the network device functions.
[0075] Network devices can be fixed or mobile. For example, base stations 110a and 110b are stationary and are responsible for wireless transmission and reception in one or more cells from communication device 120. The helicopter or drone 120i shown in Figure 1 can be configured to act as a mobile base station, and one or more cells can move according to the location of the mobile base station 120i. In other examples, the helicopter or drone (120i) can be configured to act as a communication device communicating with base station 110b.
[0076] In this application, the communication device used to implement the above-mentioned access network function can be an access network device, a network device having some of the access network functions, or a device capable of supporting the implementation of the access network function, such as a chip system, a hardware circuit, a software module, or a hardware circuit and a software module. The device can be installed in the access network device or used in combination with the access network device. In the method of this application, the communication device used to implement the access network device function is described as an access network device.
[0077] A communication device may be an entity on the user side for receiving or transmitting signals, such as a mobile phone. A communication device may be used to connect people, objects, and machines. A communication device may communicate with one or more core networks through a network device. Communication devices include handheld devices with wireless connection capabilities, other processing devices connected to a wireless modem, or vehicle-mounted devices. A communication device may be a portable, pocket-sized, handheld, computer-built-in, or vehicle-mounted mobile device. The communication device 120 may be widely used in various scenarios, such as cellular communication, device-to-device, vehicle-to-everything (V2X), point-to-point (P2P), machine-to-machine (M2M), machine type communication (MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, etc. Some examples of communication devices 120 are: the 3rd Generation Partnership Project rdThe 3GPP standard covers user equipment (UE), fixed devices, mobile devices, handheld devices, wearable devices, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers, smart books, vehicles, satellites, Global Positioning System (GPS) devices, target tracking devices, drones, helicopters, aircraft, ships, remote control devices, smart home devices, industrial devices, personal communication service (PCS) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), wireless network cameras, tablets, PDAs, mobile internet devices (MIDs), wearable devices such as smart watches, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, terminals in vehicle networking systems, wireless terminals in self-driving cars, wireless terminals in smart grids, wireless terminals in transportation safety, and smart cities. The communication device 120 may be a wireless device in the above various scenarios or a device for being set up in a wireless device, for example, a communication module, a modem or a chip in the above device. The communication device may also be referred to as a terminal, a terminal device, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc. The communication device may also be a communication device in a future wireless communication system. The communication device may be used in a dedicated network device or a general device. The embodiments of the present application do not limit the specific technology and specific device form adopted by the communication device.
[0078] For example, a communication device can function as a base station. For example, a UE can function as a dispatching entity, providing sidelink signals between UEs in V2X, D2D, or P2P scenarios. As shown in Figure 1 , a cell phone 120a and a car 120b communicate with each other using sidelink signals. Cell phone 120a and smart home device 120e communicate without relaying the communication signals through base station 110b.
[0079] In this application, the communication device used to implement the functions of the communication device can be a terminal, or a terminal with some of the functions of the above communication device, or a device that can support the implementation of the functions of the above communication device, such as a chip system, which can be installed in the terminal or used in conjunction with the terminal. In this application, the chip system can be composed of chips, or it can include chips and other discrete devices. In the technical solution provided in this application, the communication device is described as a terminal or UE as an example.
[0080] For example, a wireless communication system is typically composed of cells, with a base station providing cell management and communication services to multiple mobile stations (MS) in the cell. The base station includes a baseband unit (BBU) and a remote radio unit (RRU). The BBU and RRU can be placed in different locations, for example: the RRU is remotely located in an area with high traffic volume, while the BBU is placed in a central computer room. The BBU and RRU can also be placed in the same computer room. The BBU and RRU can also be different components under the same rack. For example, a cell can correspond to a carrier or component carrier.
[0081] It can be understood that the present application can be applied between a network device and a communication device, between a network device and a network device, or between a communication device and a communication device, that is, between a primary device and a secondary device. The primary device can be a network device or a communication device. When the primary device is a network device, the secondary device can be another network device or a communication device. When the primary device is a communication device, the secondary device can be another communication device.
[0082] The communication between the access network device and the terminal follows a certain protocol layer structure. The protocol layer structure may include a control plane protocol layer structure and a user plane protocol layer structure. For example, the control plane protocol layer structure may include the functions of protocol layers such as the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the medium access control (MAC) layer, and the physical layer. For example, the user plane protocol layer structure may include the functions of protocol layers such as the PDCP layer, the RLC layer, the MAC layer, and the physical layer. In one possible implementation, a service data adaptation protocol (SDAP) layer may also be included above the PDCP layer.
[0083] Exemplarily, the protocol layer structure between the access network device and the terminal may further include an artificial intelligence (AI) layer for transmitting data related to AI functions.
[0084] Taking data transmission between access network equipment and terminals as an example, data transmission needs to pass through the user plane protocol layers, such as the SDAP layer, PDCP layer, RLC layer, MAC layer, and physical layer. The SDAP layer, PDCP layer, RLC layer, MAC layer, and physical layer can also be collectively referred to as the access layer. Data transmission is divided into sending or receiving based on the direction of transmission, and each of these layers is further divided into a sending part and a receiving part. Taking downlink data transmission as an example, after the PDCP layer obtains data from the upper layer, it transmits the data to the RLC layer and MAC layer. The MAC layer then generates a transport block, which is then wirelessly transmitted through the physical layer. Data is encapsulated accordingly in each layer. For example, data received by a layer from the layer above it is considered a service data unit (SDU) of that layer. After encapsulation by that layer, it becomes a protocol data unit (PDU) and is then passed to the next layer.
[0085] For example, a terminal may also have an application layer and a non-access layer. The application layer can be used to provide services to applications installed in the terminal. For example, downlink data received by the terminal can be sequentially transmitted from the physical layer to the application layer, and then provided to the application by the application layer. For another example, the application layer can obtain data generated by the application and sequentially transmit the data to the physical layer for transmission to other communication devices. The non-access layer can be used to forward user data, such as forwarding uplink data received from the application layer to the SDAP layer, or forwarding downlink data received from the SDAP layer to the application layer.
[0086] The access network equipment may include a centralized unit (CU) and a distributed unit (DU). Multiple DUs may be centrally controlled by one CU. As an example, the interface between the CU and the DU may be referred to as an F1 interface. Among them, the control plane (CP) interface may be F1-C, and the user plane (UP) interface may be F1-U. The CU and DU may be divided according to the protocol layers of the wireless network: for example, the functions of the PDCP layer and above protocol layers are set in the CU, and the functions of the protocol layers below the PDCP layer (such as the RLC layer and the MAC layer, etc.) are set in the DU; for another example, the functions of the protocol layers above the PDCP layer are set in the CU, and the functions of the protocol layers below the PDCP layer are set in the DU.
[0087] It is understandable that the above division of the processing functions of CU and DU according to the protocol layer is only an example, and can also be divided in other ways, for example, the CU or DU can be divided into functions with more protocol layers, and for example, the CU or DU can also be divided into partial processing functions with the protocol layer. In one design, some functions of the RLC layer and the functions of the protocol layers above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the functions of the protocol layers below the RLC layer are set in the DU. In another design, the functions of the CU or DU can also be divided according to the service type or other system requirements, for example, by delay, the functions whose processing time needs to meet the delay requirements are set in the DU, and the functions that do not need to meet the delay requirements are set in the CU. In another design, the CU can also have one or more functions of the core network. For example, the CU can be set on the network side to facilitate centralized management. In another design, the RU of the DU is set remotely. Among them, the RU has a radio frequency function.
[0088] Exemplarily, DU and RU can be divided at the physical layer (PHY). For example, DU can implement high-level functions in the PHY layer, and RU can implement low-level functions in the PHY layer. When used for sending, the functions of the PHY layer may include adding cyclic redundancy check (CRC) code, channel coding, rate matching, scrambling, modulation, layer mapping, precoding, resource mapping, physical antenna mapping, and / or RF transmission functions. When used for receiving, the functions of the PHY layer may include CRC, channel decoding, rate matching, descrambling, demodulation, layer mapping, channel detection, resource demapping, physical antenna demapping, and / or RF receiving functions. The high-level functions in the PHY layer may include a part of the functions of the PHY layer, for example, the part of the functions is closer to the MAC layer, and the low-level functions in the PHY layer may include another part of the functions of the PHY layer, for example, the part of the functions is closer to the RF function. For example, the high-level functions in the PHY layer may include adding CRC codes, channel coding, rate matching, scrambling, modulation, and layer mapping, and the low-level functions in the PHY layer may include precoding, resource mapping, physical antenna mapping, and RF transmission functions; or, the high-level functions in the PHY layer may include adding CRC codes, channel coding, rate matching, scrambling, modulation, layer mapping, and precoding, and the low-level functions in the PHY layer may include resource mapping, physical antenna mapping, and RF transmission functions.
[0089] For example, the functions of the CU can be implemented by one entity, or by different entities. For example, the functions of the CU can be further divided, that is, the control plane and the user plane are separated and implemented by different entities, namely the control plane CU entity (i.e., CU-CP entity) and the user plane CU entity (i.e., CU-UP entity). The CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the functions of the access network device.
[0090] In the above architecture, signaling generated by the CU can be sent to the terminal via the DU, and vice versa. For example, RRC or PDCP layer signaling is ultimately processed into physical layer signaling and sent to the terminal, or converted from received physical layer signaling. In this architecture, the RRC or PDCP layer signaling can be considered to be sent via the DU, or via the DU and RU.
[0091] For example, any of the above-mentioned DU, CU, CU-CP, CU-UP, and RU can be a software module, a hardware structure, or a software module + hardware structure, without limitation. The existence forms of different entities can be different and are not limited. For example, DU, CU, CU-CP, and CU-UP are software modules, and RU is a hardware structure. These modules and their execution methods are also within the scope of protection of this application.
[0092] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meanings. For example, in the O-RAN system, CU may be called O-CU (Open CU), DU may be called O-DU, CU-CP may be called O-CU-CP, CU-UP may be called O-CU-UP, and RU may be called O-RU.
[0093] It should be understood that the number and type of each device in the communication system shown in Figure 1 are for illustration only, and the present application is not limited to this. In actual applications, the communication system may also include more terminals, more access network devices, and other network elements, such as core network devices, and / or network elements for implementing artificial intelligence functions.
[0094] It is understandable that all or part of the functions implemented by one or more of the terminals, access network devices, core network devices, or network elements for implementing artificial intelligence functions can be virtualized, that is, implemented by one or more of the proprietary processors or general-purpose processors and the corresponding software modules. Among them, since the terminal and the access network device involve an interface for air interface transmission, the transceiver function of the interface can be implemented by hardware. Core network equipment, such as operation administration and maintenance (OAM) network elements, can be virtualized. Exemplarily, one or more functions of the virtualized terminal, access network device, core network device, or network elements for implementing artificial intelligence functions can be implemented by cloud devices, such as cloud devices in an over the top (OTT) system.
[0095] The method provided in this application can be used for communication between access network equipment and terminals, and can also be used for communication between other communication devices, such as communication between macro base stations and micro base stations in wireless backhaul links, and communication between two terminals in side links (SL), etc., without limitation.
[0096] In this application, "sending information to... (e.g., a terminal)" or the related illustrations in the accompanying drawings can be understood as the destination end of the information being the terminal. This can include sending information to the terminal directly or indirectly. "Receiving information from... (e.g., a terminal)" or "receiving information from... (e.g., a terminal)", or the related illustrations in the accompanying drawings can be understood as the source end of the information being the terminal, which can include receiving information from the terminal directly or indirectly. The information may be processed as necessary between the source end and the destination end of the information transmission, such as format changes, etc., but the destination end can understand the valid information from the source end. Similar expressions in this application can be understood similarly and will not be repeated here.
[0097] In traditional mobile network architecture and deployment prior to 4G, user-plane equipment generally follows a tree topology. Uplink user packets pass through base stations and backhaul networks, ultimately accessing the data network through centrally deployed anchor gateways. These anchor gateways are typically located higher in the network, such as in regional central equipment rooms. This relatively simple topology facilitates centralized service control and packet processing at the anchor points.
[0098] With the explosive growth of mobile service traffic, this deployment model is increasingly unable to support this rapidly increasing mobile service traffic model. On the one hand, in a network with centralized anchor gateway deployment, the increasing traffic ultimately concentrates at the gateway and core equipment room, placing increasingly high demands on backhaul network bandwidth, equipment room throughput, and gateway specifications. On the other hand, the long-distance backhaul network and complex transmission environment from access points to anchor gateways also lead to significant latency and jitter in user message transmission.
[0099] Based on the above background, the industry has proposed the concept of edge computing. As shown in Figure 2, the non-roaming 5G edge computing offload architecture provided in the embodiment of this application is a schematic diagram. By moving the user plane function (UPF) and business processing capabilities to the edge of the network, local processing of distributed business traffic is achieved, avoiding excessive concentration of traffic, thereby greatly reducing the specification requirements for core computer rooms and centralized gateways. At the same time, the distance of the backhaul network is shortened, and the end-to-end (E2E) delay and jitter of user messages are reduced, making the deployment of ultra-low latency services possible.
[0100] The functions of each network element are as follows:
[0101] (1) Access node (AN): Its main function is to provide wireless connection and it is located between UE and core network node.
[0102] (2) User plane function (UPF): This function is primarily responsible for processing user messages, such as forwarding and billing statistics. The UPF directly connected to the data network (DN) via N6 in a session is called a PDU session anchor (PSA). The anchor point UPF for local traffic diversion is called a local PDU session anchor (L-PSA). The UPF that serves as a diversion point is called a branching point (BP) or an uplink classifier (ULCL).
[0103] ULCL offloads traffic based on the destination IP address of uplink packets, for example, IP range 1 is sent to the C-PSA and IP range 2 is sent to the L-PSA. BP offloads traffic based on the source IP address of uplink packets, for example, IP range 1 is sent to the C-PSA and IP range 2 to the L-PSA. BP offloads traffic based on the source IP address of uplink packets, for example, IP range 1 is sent to the C-PSA and IP range 2 to the L-PSA. BP offloads traffic to the UE and requires UE awareness and cooperation. This means that the UE is aware of the services to be offloaded and uses IP range 2 as the source address when accessing offloaded services and IP range 1 as the source address when accessing remote services. ULCL offloads traffic to the UE without UE awareness.
[0104] (3) DN: such as operator services, Internet access or third-party services.
[0105] (4) Edge application server (EAS): It is a server that provides application services to UE.
[0106] (5) Access and mobility function (AMF): The main functions include managing user registration, reachability detection, session management function (SMF) selection, and mobility state transition management.
[0107] (6)SMF: Mainly responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning IP addresses to users and selecting UPFs that provide packet forwarding functions.
[0108] In roaming scenarios, SMF can be divided into the following categories:
[0109] Visited-session management function (V-SMF): The visited domain SMF that serves users when they roam.
[0110] Home-session management function (H-SMF): The home domain SMF that serves users during roaming. Currently, only home-routed (HR) roaming architectures have an H-SMF. Local breakout (LBO) roaming users do not have an H-SMF.
[0111] (7) Policy control function (PCF): The main function is to serve as a policy decision point, providing rules based on service data flow and application detection, gating, quality of service (QoS), and flow-based charging control.
[0112] It supports unified policy management of network behavior; provides policy rules to the control plane function for execution; and obtains contract-related information from the unified data repository (UDR) to make policy decisions.
[0113] In roaming scenarios, PCF can be divided into the following categories:
[0114] Visited-Policy Control Function (V-PCF): The visited-domain PCF that serves users during roaming. In existing architectures, only LBO roaming architectures have V-PCFs. HR roaming users do not have V-PCFs.
[0115] Home-policy control function (H-PCF): The home domain PCF that serves users when they roam.
[0116] (8) AF: The main function is to cooperate with the Third Generation Partnership Project (3 rd The 3GPP core network interacts with the 3GPP to provide services, affecting traffic routing, access network capability exposure, and policy control.
[0117] (9) Network exposure function (NEF): securely exposes services and capabilities provided by 3GPP network functions, such as third parties, edge computing, and AF.
[0118] By moving the UPF and service processing capabilities to the network edge, the UE can access the EAS through the application layer after obtaining the EAS IP address. The core network helps the UE find a suitable EAS (nearby in terms of geographic location or network topology). The UE then establishes a connection with the EAS through the application layer IP address and accesses applications.
[0119] The AF and EAS can be considered control plane and user plane network element instances of the same server. Application service providers establish edge hosting environments (EHEs), which can be understood as computer rooms. Each EHE can contain an AF and multiple EASs. The AF is aware of the status of all EASs within the EHE, such as EAS load status and the IP addresses of all UEs accessing the EAS. (The scope of AF control is not necessarily limited to a single EHE / computer room; it can be a larger area.)
[0120] The basis for AF to select the target EAS varies in different scenarios. For example, if EAS load balancing triggers edge migration, the AF selects the target EAS based on the EAS load (i.e., the one with the lowest load). If UE mobility triggers edge migration, the AF needs to select the target EAS based on the target data network access identifier (DNAI) provided by the SMF (i.e., the selected target EAS needs to be within the target DNAI).
[0121] In EC deployment scenarios, due to UE mobility and EAS load balancing, sessions need to be migrated to EAS to ensure business continuity. The following details the edge migration process:
[0122] The standard defines multiple edge migration scenarios and processes. The most typical AF-supported IP replacement process is as follows:
[0123] FIG3 is a schematic diagram of an edge migration process provided by an embodiment of the present application. The edge migration process includes the following steps:
[0124] S101. PDU session establishment process: For example, the UE may request to establish a PDU session.
[0125] S102. After the session is established, the UE can obtain an EAS IP address through local configuration or EAS discovery process. In the subsequent migration process, this EAS can be considered as the source EAS.
[0126] S103. The UE communicates with the source EAS.
[0127] For uplink communication, the UE sends an uplink service data packet to the source EAS through the L-PSA. The uplink service data packet includes: source IP address (UE's IP address), destination IP address (source EAS's IP address), source port number (UE's port number) and destination port number (source EAS's port number).
[0128] For downlink communication, the source EAS sends a downlink service data packet to the UE through the L-PSA. The downlink service data packet includes: source IP address (IP address of the source EAS), destination IP address (IP address of the UE), source port number (port number of the source EAS) and destination port number (port number of the UE).
[0129] S104.AF or the fifth generation communication system core network (5 th generation core, 5GC) (SMF, UPF) triggers the EAS IP replacement process (also known as EAS migration).
[0130] One situation is that the EAS IP replacement process is triggered by AF. When the load of multiple EASs controlled by AF is unbalanced, AF will first select the target EAS and perform real-time context mirroring on the source / target EAS. After that, AF will notify SMF to perform IP replacement. The notification includes: target EAS IP address, target EAS port number, source EAS IP address, and source EAS port number. After receiving the AF indication, SMF instructs the local anchor point UPF (L-PSA) through which the session passes, and UPF replaces the uplink destination address and downlink source address of the service flow. The indication includes: target EAS IP address, target EAS port number, source EAS IP address, and source EAS port number. The replacement process includes: uplink destination address: source EAS IP→destination EAS IP, downlink source address: destination EAS IP→source EAS IP. After completing the above process, the EAS IP replacement is completed.
[0131] In another scenario, the EAS IP replacement process is triggered by the 5GC. When the UE moves, the AMF notifies the SMF of the UE mobility event, which triggers the EAS IP replacement process. The SMF notifies the AF of the target DNAI. This DNAI is used to identify the access point of the DN network. The subsequent steps are the same as the above EAS IP replacement process triggered by the AF, except that the AF selects the target EAS within the DNAI range.
[0132] Furthermore, the local anchor point UPF (L-PSA) replaces the IP address of the relevant service flow according to the instructions of the SMF to enable communication between the UE and the target EAS:
[0133] S105a. For uplink communication, when L-PSA receives an uplink message from the UE (whose source IP address is the UE's IP address and the destination IP address is the source EAS's IP address), L-PSA replaces the destination IP address from the source EAS's IP address to the target EAS's IP address and sends the uplink message to the target EAS.
[0134] S105b. For downlink communication, when L-PSA receives a downlink message from the source EAS (whose source IP address is the IP address of the source EAS and the destination IP address is the IP address of the UE), L-PSA replaces the source IP address from the IP address of the source EAS with the IP address of the target EAS and sends the downlink message to the UE.
[0135] The existing HR roaming architecture does not support edge computing, and roaming edge computing has not been proposed yet. As shown in Figure 4, a new edge computing scenario is proposed (relative to the non-roaming 5G edge computing offload architecture shown in Figure 2): home routed with session breakout (HR-SBO) roaming. For HR roaming UEs, the UE can access the edge environment through the VPLMN. However, unlike the non-roaming edge computing scenario, in order to maintain the HPLMN's control over local offload services, the local-session management function (H-SMF) can indicate to the V-SMF when the session is established that the HPLMN authorizes the UE to roam to the IP address range corresponding to the EAS accessed by the VPLMN (included in the VPLMN Specific Offloading Policy / Information). For example, the IP address range can be represented by a full qualified domain name (FQDN) or an IP segment.
[0136] However, in this edge computing scenario, the following problems arise:
[0137] 1) In the HR-SBO architecture, traffic can only be offloaded to the VPLMN based on authorization provided by the HPLMN using the VPLMN-specific offload policy / information. However, when selecting the target EAS for edge migration, the AF does not consider the HPLMN's authorization information and may select an EAS that is not authorized by the HPLMN.
[0138] 2) After the AF selects a target EAS that is not authorized by the HPLMN and notifies the V-SMF. If the V-SMF instructs the UPF to perform IP replacement as required by the AF, the UE will access the EAS that is not authorized by the HPLMN. If the V-SMF rejects the AF's request, the AF needs to reselect the target EAS. The real-time context mirroring that the AF has completed will be deleted, resulting in a waste of resources. Moreover, the target EAS selected by the AF again may not be within the HPLMN authorized scope, which may lead to multiple rejections and waste of signaling.
[0139] As can be seen, there is currently no mechanism or solution for edge migration based on HPLMN authorization in roaming scenarios. As a result, the AF does not consider the HPLMN's authorization information when selecting a target EAS based on existing rules. When edge migration is required for a service flow roaming to a VPLMN in the HR-SBO architecture, the AF may select a target EAS that is not within the HPLMN's authorization range.
[0140] To this end, the present application provides a communication solution, in which the AF obtains a first IP address range that allows the terminal to be routed to the local data network of the VPLMN through subscription. When the AF is triggered to perform edge migration, the target EAS is determined based on the first IP address range, and the V-SMF is instructed to migrate the service flow between the terminal and the source EAS to the target EAS, so that the target EAS is authorized, thereby enabling successful migration and improving the efficiency of edge migration.
[0141] The following describes in detail various method embodiments of the present application:
[0142] It should be noted that the IP addresses mentioned in the various embodiments of the present application may be IPv4 addresses, IPv6 prefixes, or media access control (MAC) addresses.
[0143] It is understandable that this application uses the first network element (e.g., V-SMF), the second network element (e.g., H-SMF), the third network element (e.g., AF), and the fourth network element (e.g., UPF) as examples of the execution entities of the interaction diagram, but this application does not limit the execution entities of the interaction diagram. For example, the first / second / third / fourth network element in the method provided in this application may also be a chip, chip system, or processor applied to the first / second / third / fourth network element, or a logical node, logic module, or software that can implement all or part of the first / second / third / fourth network element.
[0144] As shown in Figure 5, a flow chart of a communication method provided in an embodiment of the present application is shown. Exemplarily, the method may include the following steps:
[0145] S200. AF sends a subscription request to V-SMF. Correspondingly, V-SMF receives the subscription request.
[0146] Among them, the subscription request can be used to request subscription to a first IP address range corresponding to at least one UE. The subscription request may include the data network name (DNN) of the session / single network slice selection assistance information (S-NSSAI) / group ID / generic public subscription identifier (GPSI). That is, the AF requests subscription to the first IP address range corresponding to at least one UE in DNN / S-NSSAI / group ID / GPSI.
[0147] Alternatively, the UE may include multiple sessions. The subscription request may be used to request subscription to a first IP address range corresponding to at least one session. The subscription request may include the UE IP address of the session.
[0148] The first IP address range is the IP address range that the AF is authorized to perform edge migration (ie, the IP address range of the target EAS).
[0149] Exemplarily, this step can be a separate subscription process, or it can be merged with the existing subscription process, that is, while subscribing to other information (for example, taking the first IP address range as a type of user plane path management events (UP path management events)), the V-SMF can also be instructed to provide the above-mentioned first IP address range. Of course, the present application is not limited to the subscription process, and the V-SMF can also be notified of the address of this AF and that this AF wants to obtain the first IP address range in other ways. The present application does not limit the method of obtaining the first IP address range.
[0150] For example, the AF sends an Nnef_TrafficInfluence_Create message to the V-SMF through the NEF / UDR / PCF, which is used to request subscription to the first IP address range corresponding to the UE IP, or the message is used to request subscription to the first IP address range corresponding to at least one UE of the DNN / S-NSSAI / group ID / GPSI.
[0151] Exemplarily, the AF may send the subscription request before the session is established (e.g., step S200), during the session, or after the session is established (after step S203). It is understandable that when the subscription request includes the UE IP of the session, the subscription request may be sent during or after the session is established (after step S203).
[0152] S201. The H-SMF sends a second IP address range to the V-SMF, allowing the terminal to be routed to the local data network of the VPLMN. Correspondingly, the V-SMF receives the second IP address range.
[0153] Exemplarily, during the session establishment process, the H-SMF sends a PDU session update request (Nsmf_PDUSession_Update Request) to the V-SMF. The PDU session update request includes VPLMN-specific offload information. The VPLMN-specific offload information includes the aforementioned second IP address range. The second IP address range is the IP address range that the HPLMN allows the terminal to route to the local data network of the VPLMN. "The second IP address range that allows the terminal to route to the local data network of the VPLMN" can also be understood as "the second IP address range that the terminal is allowed to route to the local data network of the VPLMN."
[0154] The HPLMN is the home public land mobile network (PLMN) to which the terminal subscribes.
[0155] S202. The V-SMF determines the first IP address range based on the second IP address range.
[0156] For example, the first IP address range may be based on the second IP address range. In other words, the first IP address range is determined based on the second IP address range. The first IP address range is related to the second IP address range. The first IP address range may be smaller than or equal to the second IP address range.
[0157] Exemplarily, after receiving the second IP address range, the V-SMF may process the second IP address range according to the V-SMF local logic (eg, reduce the range or modify the information format) to obtain the first IP address range, which is smaller than the second IP address range.
[0158] Since the first IP address range may be the second IP address range, this step is optional and is indicated by a dotted line in the figure.
[0159] S203. The V-SMF sends the first IP address range to the AF based on the second IP address range. Correspondingly, the AF receives the first IP address range.
[0160] Exemplarily, after receiving the subscription request, the V-SMF sends a notification message (Nsmf_EventExposure_Notify) to the AF, where the notification message includes the first IP address range corresponding to at least one terminal or at least one session. It is understandable that, corresponding to step S200, if the AF sends the subscription request before the session is established, the V-SMF notifies the AF at step S203; if the AF sends the subscription request during or after the session is established, the V-SMF notifies the AF upon receiving the subscription request.
[0161] For example, if the first IP address range is equal to the second IP address range, this step can be understood as V-SMF transparently forwarding the second IP address range sent by H-SMF to AF; or V-SMF can parse the second IP address range and then forward the second IP address range to AF.
[0162] S204. After the session is established, the UE can obtain an EAS IP address through local configuration or EAS discovery process. In the subsequent migration process, this EAS can be considered as the source EAS.
[0163] S205. The UE communicates with the source EAS according to the IP address of the source EAS.
[0164] For uplink communication, the UE sends an uplink service data packet to the source EAS through the L-PSA. The uplink service data packet includes: source IP address (UE's IP address), destination IP address (source EAS's IP address), source port number (UE's port number) and destination port number (source EAS's port number).
[0165] For downlink communication, the source EAS sends a downlink service data packet to the UE through the L-PSA. The downlink service data packet includes: source IP address (IP address of the source EAS), destination IP address (IP address of the UE), source port number (port number of the source EAS) and destination port number (port number of the UE).
[0166] The source EAS generates a context about the UE during the communication process.
[0167] Edge migration may be triggered due to excessive load on the source EAS or UE movement. In this case, perform one of the following steps:
[0168] Option 1:
[0169] S206a. Since the source EAS load is too high, the AF triggers edge migration.
[0170] In this solution, when the AF finds that the source EAS is overloaded, edge migration is required, which triggers the subsequent steps.
[0171] In addition, AF can also trigger edge migration based on its own policies. For example, if AF maintains multiple servers (EAS), and one EAS has a relatively high load while the other EASs have relatively low loads, edge migration may also be triggered.
[0172] Option 2:
[0173] S206b-1. Due to the movement of the UE, the V-SMF or L-PSA triggers edge migration.
[0174] S206b-2. V-SMF notifies AF of target DNAI.
[0175] In this solution, the V-SMF finds that the L-PSA needs to be changed due to UE mobility, for example. After the L-PSA is changed, the V-SMF notifies the AF of the target DNAI, that is, the DNAI to which the new L-PSA belongs.
[0176] S207. The AF selects a target EAS corresponding to the target IP address in the first IP address range according to the location of the terminal and / or the load of at least one EAS.
[0177] For example, corresponding to solution 1, if edge migration is triggered by excessive load of the source EAS, the AF can select a target EAS corresponding to the target IP address in the first IP address range based on the load of at least one EAS, and the target EAS has a lower load.
[0178] For example, corresponding to solution 2, if edge migration is triggered by UE mobility, the AF can select a target EAS corresponding to the target IP address in the first IP address range according to the location of the terminal, and the target EAS is located within the target DNAI.
[0179] In other embodiments, the AF may also select a target EAS corresponding to the target IP address in the first IP address range according to the location of the terminal and the load of at least one EAS corresponding to the first IP address range.
[0180] Since the target EAS is selected from the first IP address range, the target EAS is authorized.
[0181] S208. The AF instructs the source EAS and the target EAS to perform real-time context mirroring.
[0182] After selecting the target EAS, the AF can instruct the source EAS to perform real-time context mirroring with the target EAS.
[0183] Exemplarily, the AF establishes a data channel between the source EAS and the target EAS. The source EAS can send the context related to the UE to the target EAS via a data channel or network routing path. Furthermore, since the source EAS is still communicating with the UE, whenever the context related to the UE changes, the source EAS sends the updated context related to the UE to the target EAS via the data channel in real time, ensuring that the context related to the UE on the source and target EAS is synchronized in real time (remaining identical at all times). Consequently, after step S208 is completed, both the source EAS and the target EAS have stored a real-time context image of the UE.
[0184] S209. The AF sends a first instruction message to the V-SMF. The first instruction message is used to instruct the V-SMF to migrate the service flow between the terminal and the source EAS to the target EAS. Correspondingly, the V-SMF receives the first instruction message.
[0185] After the AF instructs the source EAS and the target EAS to complete real-time context mirroring, it instructs the V-SMF to migrate the service flow between the terminal and the source EAS to the target EAS. The first instruction information includes the IP address of the target EAS. For example, the AF sends AF influence information to the V-SMF, and the AF influence information includes EAS IP replacement information. The EAS IP replacement information can be the IP address of the target EAS.
[0186] Furthermore, the first indication information may also include the port number of the target EAS, the IP address of the source EAS, and the port number of the source EAS.
[0187] The source EAS includes the EAS serving the terminal before the migration, and the target EAS includes the EAS serving the terminal after the migration. The target EAS belongs to the first IP address range. The source EAS address is the IP address discovered by the UE for the edge computing service. The source EAS IP address and port number are the destination IP address and port number of the edge computing service uplink traffic generated by the UE.
[0188] S210. The V-SMF instructs the local anchor point UPF (L-PSA) to replace the IP address of the user message. Correspondingly, the local anchor point UPF (L-PSA) receives the instruction. Exemplarily, the V-SMF can instruct the UPF through the N4 session.
[0189] S211. The local anchor UPF (L-PSA) replaces the IP address of the relevant service flow according to the instructions of the V-SMF to enable communication between the UE and the target EAS:
[0190] For uplink communication, when L-PSA receives an uplink message from UE (whose source IP address is the UE's IP address and the destination IP address is the source EAS's IP address), L-PSA replaces the destination IP address from the source EAS's IP address to the target EAS's IP address and sends the uplink message to the target EAS.
[0191] For downlink communication, when the L-PSA receives a downlink message from the source EAS (whose source IP address is the IP address of the source EAS and the destination IP address is the IP address of the UE), the L-PSA replaces the source IP address from the IP address of the source EAS to the IP address of the target EAS and sends the downlink message to the UE.
[0192] Furthermore, after the UE communicates with the target EAS, the context related to the UE on the source EAS may be deleted.
[0193] According to a communication method provided by an embodiment of the present application, the AF obtains a first IP address range that allows the terminal to be routed to the local data network of the VPLMN through subscription. When the AF is triggered to perform edge migration, the target EAS is determined based on the first IP address range, and the V-SMF is instructed to migrate the service flow between the terminal and the source EAS to the target EAS, so that the target EAS is authorized, thereby enabling successful migration and improving the efficiency of edge migration.
[0194] The above embodiment describes that the AF can obtain the first IP address range through the subscription process. In another embodiment, the AF can also provide the first IP address range to the AF after an attempt to migrate the edge fails, thereby reducing the number of attempts and improving the efficiency of edge migration:
[0195] As shown in Figure 6, it is a flowchart of another communication method provided in an embodiment of the present application. Exemplarily, the method may include the following steps:
[0196] S300. The H-SMF sends a second IP address range to the V-SMF, allowing the terminal to be routed to the local data network of the VPLMN. Correspondingly, the V-SMF receives the second IP address range.
[0197] The specific implementation of this step can refer to step S201 of the embodiment shown in FIG5 , and will not be described in detail here.
[0198] S301. V-SMF determines the first IP address range based on the second IP address range.
[0199] For the specific implementation of this step, reference may be made to step S202 of the embodiment shown in FIG5 , and details thereof will not be repeated here.
[0200] S302. After the session is established, the UE can obtain an EAS IP address through local configuration or EAS discovery process. In the subsequent migration process, this EAS can be considered as the source EAS.
[0201] The specific implementation of this step can refer to step S204 of the embodiment shown in FIG5 , and will not be described in detail here.
[0202] S303. The UE communicates with the source EAS according to the IP address of the source EAS.
[0203] For the specific implementation of this step, reference may be made to step S205 of the embodiment shown in FIG5 , which will not be described in detail here.
[0204] When EAS load is too high or UE moves, edge migration may be triggered. Perform one of the following steps:
[0205] Option 1:
[0206] S304a. Since the source EAS load is too high, the AF triggers edge migration.
[0207] In this solution, when the AF finds that the source EAS load is too high and edge migration is required, the subsequent steps are triggered.
[0208] In addition, AF can also trigger edge migration based on its own policies. For example, if AF maintains multiple servers (EAS), and one EAS has a relatively high load while the other EASs have relatively low loads, edge migration may also be triggered.
[0209] Option 2:
[0210] S304b-1. Due to the movement of the UE, the V-SMF or L-PSA triggers edge migration.
[0211] S304b-2. V-SMF notifies AF of target DNAI.
[0212] In this solution, the V-SMF finds that the L-PSA needs to be changed due to UE mobility, for example. After the L-PSA is changed, the V-SMF notifies the AF of the target DNAI, that is, the DNAI to which the new L-PSA belongs.
[0213] S305. The AF sends a second instruction message to the V-SMF, where the second instruction message is used to instruct the V-SMF to migrate the service flow between the terminal and the source EAS to the first target EAS. Correspondingly, the V-SMF receives the second instruction message.
[0214] The second indication information includes the IP address of the first target EAS.
[0215] Since the AF does not know the first IP address range, the IP address of the first target EAS selected by the AF may not be within the first IP address range.
[0216] S306. After receiving the second indication information, V-SMF determines that the IP address of the first target EAS is not within the above-mentioned first IP address range. Therefore, V-SMF sends a rejection information to AF, which is used to instruct V-SMF to refuse to replace the IP address of the user message.
[0217] S307. V-SMF sends the first IP address range to AF.
[0218] In step S301, the V-SMF has determined a first IP address range that allows the terminal to be routed to the local data network of the VPLMN. Therefore, after receiving an instruction from the AF instructing the V-SMF to migrate the service flow between the terminal and the source EAS to the first target EAS, the V-SMF can send the first IP address range to the AF. In this way, the frequent migration failures of the AF described in the background art can be avoided.
[0219] Exemplarily, the first IP address range may be included in the above-mentioned rejection information, or the V-SMF may also send the first IP address range separately.
[0220] S308. The AF selects a second target EAS corresponding to the target IP address in the first IP address range according to the location of the terminal and / or the load of at least one EAS.
[0221] The specific implementation of this step can refer to step S207 of the embodiment shown in Figure 5, and will not be repeated here. The difference is that in this embodiment, the AF finally selects the second target EAS.
[0222] S309. The AF instructs the source EAS to perform real-time context mirroring with the second target EAS.
[0223] For the specific implementation of this step, reference may be made to step S208 of the embodiment shown in FIG5 , and details thereof will not be repeated here.
[0224] S310. The AF sends first instruction information to the V-SMF, where the first instruction information is used to instruct the V-SMF to migrate the service flow between the terminal and the source EAS to the second target EAS. Correspondingly, the V-SMF receives the first instruction information.
[0225] After the AF instructs the source EAS to complete real-time context mirroring with the second target EAS, it instructs the V-SMF to migrate the service flow between the terminal and the source EAS to the second target EAS. The first instruction information includes the IP address of the second target EAS. For example, the AF sends AF impact information to the V-SMF, and the AF impact information includes EAS IP replacement information. The EAS IP replacement information can be the IP address of the second target EAS.
[0226] The source EAS includes the EAS serving the terminal before the migration, and the second target EAS includes the EAS serving the terminal after the migration. The second target EAS belongs to the first IP address range. The source EAS address is the IP address discovered by the UE for the edge computing service. The source EAS IP address and port number are the destination IP address and port number of the edge computing service uplink traffic generated by the UE.
[0227] The first indication information includes the IP address of the second target EAS.
[0228] Furthermore, the first indication information may also include the port number of the second target EAS, the IP address of the source EAS, and the port number of the source EAS.
[0229] S311. The V-SMF instructs the local anchor point UPF (L-PSA) to replace the IP address of the user message. Correspondingly, the UPF receives the instruction.
[0230] S312. The local anchor point UPF (L-PSA) replaces the IP address of the relevant service flow according to the instruction of the V-SMF to enable communication between the UE and the second target EAS.
[0231] For the specific implementation of this step, reference may be made to step S211 of the embodiment shown in FIG5 , and details thereof will not be repeated here.
[0232] According to a communication method provided by an embodiment of the present application, after the V-SMF receives an instruction from the AF instructing the V-SMF to migrate the service flow between the terminal and the source EAS to the first target EAS, if it finds that the first target EAS is not within the first IP address range of the local data network that allows the terminal to be routed to the VPLMN, the V-SMF sends a rejection message to the AF, and the AF sends the first IP address range, so that the AF can select the second target EAS within the first IP address range, so that the AF can instruct the V-SMF and L-PSA to successfully complete the edge migration, thereby improving the efficiency of the edge migration.
[0233] The above embodiment describes that the V-SMF provides the first IP address range to the AF, thereby enabling the AF to obtain the first IP address range. In fact, the AF can also store the first IP address range itself to avoid transmitting the first IP address range on the network, thereby improving network security:
[0234] As shown in FIG7 , a flow chart of another communication method provided in an embodiment of the present application is shown. Exemplarily, the method may include the following steps:
[0235] S400. AF obtains the stored first IP address range.
[0236] For example, the AF may determine a first IP address range through a negotiation agreement (e.g., a service level agreement (SLA)) between a service provider and an operator, and store the first IP address range. The first IP address range is the IP address range for which the AF is authorized to perform edge migration (i.e., the IP address range of the target EAS).
[0237] For example, if PLMN1 is a HPLMN, the IP address range corresponding to the EAS configured for users of PLMN1 to access when roaming to different PLMNs is shown in Table 1 below:
[0238] Table 1
[0239] According to Table 1 above, the first IP address range corresponding to the EAS accessed by the terminal authorized by PLMN1 to roam to PLMN2 is IP range1; the first IP address range corresponding to the EAS accessed by the terminal authorized by PLMN1 to roam to PLMN3 is IP range2; and so on.
[0240] For another example, if PLMN2 is a HPLMN, the IP address range corresponding to the EAS configured for users of PLMN2 to access when roaming to different PLMNs is as shown in Table 2 below:
[0241] Table 2
[0242] According to Table 2 above, the first IP address range corresponding to the EAS that PLMN2 authorizes the terminal to roam to PLMN1 is IP range3; the first IP address range corresponding to the EAS that PLMN2 authorizes the terminal to roam to PLMN3 is IP range4; and so on.
[0243] The AF can obtain the first IP address range through its own stored information without obtaining it from the network, thereby improving the security of the IP information and being able to obtain the first IP address range in a timely manner.
[0244] S401. Session establishment.
[0245] S402. After the session is established, the UE can obtain an EAS IP address through local configuration or EAS discovery process. In the subsequent migration process, this EAS can be considered as the source EAS.
[0246] S403. The UE communicates with the source EAS according to the IP address of the source EAS.
[0247] For the specific implementation of this step, reference may be made to step S205 of the embodiment shown in FIG5 , which will not be described in detail here.
[0248] Due to EAS load imbalance or UE mobility, edge migration may be triggered. Perform one of the following steps:
[0249] Option 1:
[0250] S404a. Since the source EAS load is too high, the AF triggers edge migration.
[0251] In this solution, when the AF finds that the source EAS load is too high and edge migration is required, the subsequent steps are triggered.
[0252] Option 2:
[0253] S404b-1. Due to the movement of the UE, the V-SMF and L-PSA trigger edge migration.
[0254] S404b-2.V-SMF notifies AF of the target DNAI.
[0255] In this solution, the V-SMF finds that the L-PSA needs to be changed due to UE mobility. After the L-PSA is changed, the V-SMF notifies the AF of the target DNAI, that is, the DNAI to which the new L-PSA belongs.
[0256] S405. AF determines that the service flow is a first type of service flow.
[0257] The first type of service flow may refer to a service flow accessing services through an HR-SBO session. The AF may also be unaware that the first type of service flow accesses services through an HR-SBO session. Specifically, the AF determines, based on the following exemplary judgment, that a service flow of the first type is accessed through an HR-SBO session. The AF is unaware of the type of session used to access the service flow.
[0258] Exemplarily, the AF determines that the current service flow is an HR-SBO session based on the UE IP and the L-PSA of the access source EAS, if the UE IP and the L-PSA are from different PLMNs.
[0259] Alternatively, the AF determines the UE's roaming status based on the UE account identifier, such as the phone number, and the information provided to the AF when the account was registered. Specifically, when registering the account, the AF determines the UE's HPLMN based on the phone number. Through the agreement between the AF and the HPLMN, the AF determines the roaming type (such as HR-SBO) used by the UE when accessing the service. The AF can then determine the UE's roaming status based on the account.
[0260] S406. The AF selects a target EAS corresponding to the target IP address in the first IP address range according to the location of the terminal and / or the load of at least one EAS.
[0261] When the AF is triggered to perform edge migration and the AF determines that the service flow is the first type of service flow, for example, when the UE is in the HR-SBO session state, the AF can obtain the first IP address range stored in itself and select the target EAS corresponding to the target IP address in the first IP address range based on the location of the terminal and / or the load of at least one EAS.
[0262] For the specific implementation of this step, reference may be made to step S207 of the embodiment shown in FIG5 , and details thereof will not be repeated here.
[0263] S407. The AF instructs the source EAS and the target EAS to perform real-time context mirroring.
[0264] For the specific implementation of this step, reference may be made to step S208 of the embodiment shown in FIG5 , and details thereof will not be repeated here.
[0265] S408. The AF sends first instruction information to the V-SMF, where the first instruction information is used to instruct the V-SMF to migrate the service flow between the terminal and the source EAS to the target EAS. Correspondingly, the V-SMF receives the first instruction information.
[0266] For the specific implementation of this step, reference may be made to step S209 of the embodiment shown in FIG5 , and details thereof will not be repeated here.
[0267] S409. The V-SMF instructs the local anchor point UPF (L-PSA) to replace the IP address of the user message. Correspondingly, the UPF receives the instruction.
[0268] S410. The local anchor point UPF (L-PSA) replaces the IP address of the relevant service flow according to the instruction of the V-SMF to enable communication between the UE and the target EAS.
[0269] For the specific implementation of this step, reference may be made to step S211 of the embodiment shown in FIG5 , and details thereof will not be repeated here.
[0270] According to a communication method provided in an embodiment of the present application, the AF can determine, through a negotiation agreement between the service provider and the operator, a first IP address range of the local data network that allows the terminal to be routed to the VPLMN, and store the first IP address range. When the AF is triggered to perform edge migration and determines that the service flow is a first type of service flow, it can obtain the first IP address range stored in itself, determine the target EAS based on the first IP address range, and instruct the V-SMF to migrate the service flow between the terminal and the source EAS to the target EAS, thereby achieving successful migration and improving the efficiency of edge migration.
[0271] The above embodiment describes that the AF indicates the target EAS to the V-SMF. The following embodiment will describe that the V-SMF can also determine the target EAS by itself:
[0272] As shown in FIG8 , a flow chart of another communication method provided in an embodiment of the present application is shown. Exemplarily, the method may include the following steps:
[0273] S500. The H-SMF sends a second IP address range to the V-SMF, allowing the terminal to be routed to the local data network of the VPLMN. Correspondingly, the V-SMF receives the second IP address range.
[0274] The specific implementation of this step can refer to step S201 of the embodiment shown in FIG5 , and will not be described in detail here.
[0275] S501. V-SMF determines the first IP address range based on the second IP address range.
[0276] This step is optional and is indicated by a dotted line in the figure.
[0277] For the specific implementation of this step, reference may be made to step S202 of the embodiment shown in FIG5 , and details thereof will not be repeated here.
[0278] S502. After the session is established, the UE can obtain an EAS IP address through local configuration or EAS discovery process. In the subsequent migration process, this EAS can be considered as the source EAS.
[0279] The specific implementation of this step can refer to step S204 of the embodiment shown in FIG5 , and will not be described in detail here.
[0280] S503. The UE communicates with the source EAS according to the IP address of the source EAS.
[0281] For the specific implementation of this step, reference may be made to step S205 of the embodiment shown in FIG5 , which will not be described in detail here.
[0282] Due to EAS load imbalance or UE mobility, edge migration may be triggered. Perform one of the following steps:
[0283] Option 1:
[0284] S504a. Since the source EAS load is too high, the AF triggers edge migration.
[0285] In this solution, when the AF finds that the source EAS load is too high and edge migration is required, the subsequent steps are triggered.
[0286] Option 2:
[0287] S504b-1. Due to the movement of the UE, the V-SMF and L-PSA trigger edge migration.
[0288] S504b-2. V-SMF notifies AF of target DNAI.
[0289] In this solution, the V-SMF finds that the L-PSA needs to be changed due to UE mobility. After the L-PSA is changed, the V-SMF notifies the AF of the target DNAI, that is, the DNAI to which the new L-PSA belongs.
[0290] S505. AF sends the first information to V-SMF. Correspondingly, V-SMF receives the first information.
[0291] The first information includes a correspondence between at least one EAS and at least one weighting factor.
[0292] In an example, the above correspondence is shown in Table 3:
[0293] Table 3
[0294] Exemplarily, the weight factor is used to indicate the AF's preference for at least one EAS. For example, the larger the weight factor, the higher the AF's preference for that EAS. The weight factor can be determined based on the EAS's load, location, and so on. For example, due to an unbalanced EAS load, the AF is triggered to determine all possible alternative EASs and assign a weight factor to each EAS based on the load of these EASs. These EASs and their corresponding weight factors constitute the aforementioned Table 3.
[0295] The weight factor is a weight value representing AF preference. For example, when edge migration is triggered due to excessive EAS load, the lower the load of these alternative EASs, the higher the weight of the weight factor; when edge migration is triggered due to UE movement, the weight factor is determined according to the location, and the closer the location of the alternative EAS is to the UE, the higher the weight of the weight factor.
[0296] The AF can provide the above-mentioned correspondence to the V-SMF at any time, not limited to when the AF is triggered to perform edge migration. The AF can also provide the above-mentioned correspondence to the V-SMF when determining that the service flow is a first-type service flow. Furthermore, before step S505, the following step may be included: the AF determines that the service flow is a first-type service flow. The specific implementation of this step can be referenced to step S405 of the embodiment shown in Figure 7 and will not be repeated here.
[0297] S506. The V-SMF determines the target EAS based on the first information and the first IP address range.
[0298] The target EAS belongs to the first IP address range.
[0299] For example, the first IP address range may be based on the second IP address range. In other words, the first IP address range is determined based on the second IP address range. The first IP address range may be smaller than or equal to the second IP address range.
[0300] Exemplarily, the V-SMF may determine all EASs in the first information that belong to the first IP address range, and select the EAS with the largest weight factor as the target EAS among the determined EASs based on a correspondence between at least one EAS and at least one weight factor.
[0301] The AF's preference for EASs may be due to its load balancing strategy. AF prefers that all EASs it controls have low load, or have similar load levels. Therefore, when an EAS is highly loaded and requires edge migration of its users, the AF will try to select the EAS with the lowest load to receive these migrated users, ensuring that the load levels of all EASs controlled by the AF are as close as possible. This also minimizes the risk of the EAS receiving users after edge migration becoming overloaded.
[0302] For example, the V-SMF first determines which EASs in the above correspondence are within the first IP address range. Those within the range are selectable EASs. After determining the selectable EASs, the V-SMF selects the one with the highest AF preference weight as the target EAS based on the weight factors of these EASs. When selecting the target EAS, some local logic of the V-SMF may also affect the selection result.
[0303] S507. The V-SMF sends first indication information to the AF. Correspondingly, the AF receives the first indication information.
[0304] The first indication information is used to indicate a target EAS, and the IP address of the target EAS is authorized.
[0305] S508. The AF instructs the source EAS and the target EAS to perform real-time context mirroring.
[0306] For the specific implementation of this step, reference may be made to step S208 of the embodiment shown in FIG5 , and details thereof will not be repeated here.
[0307] S509. The AF sends the second indication information to the V-SMF. Correspondingly, the V-SMF receives the second indication information.
[0308] The second indication information is used to instruct the V-SMF to migrate the service flow between the terminal and the source EAS to the target EAS.
[0309] S510. The V-SMF instructs the local anchor point UPF (L-PSA) to replace the IP address of the user message. Correspondingly, the local anchor point UPF (L-PSA) receives the instruction.
[0310] The specific implementation of this step can refer to step S210 of the embodiment shown in FIG5 , and will not be described in detail here.
[0311] S511. The local anchor point UPF (L-PSA) replaces the IP address of the relevant service flow according to the instruction of the V-SMF to enable communication between the UE and the target EAS.
[0312] For the specific implementation of this step, reference may be made to step S211 of the embodiment shown in FIG5 , and details thereof will not be repeated here.
[0313] According to a communication method provided in an embodiment of the present application, the V-SMF can accurately determine the target EAS based on the correspondence between at least one EAS provided by the AF and at least one weight factor, according to the first IP address range and the correspondence, thereby improving the success rate of migrating the service flow to the target EAS and improving the efficiency of edge migration.
[0314] It should be noted that the EAS in the above embodiment can be replaced by DNAI, which is defined by 3GPP to identify the DN network access point. DNN represents the name of the DN, and DNAI represents the specific network access point of the DN, with certain physical properties. For example, a DN is planned in the network, and its DNN is abc. The DN has two access points in City A and City B. The DNAI corresponding to City A and City B can be named abc.A and abc.B. In the UL CL diversion scenario, DNAI is used to identify the PDU session anchor point on the edge side, that is, the auxiliary anchor point UPF. A simple way to understand DNAI is to think that a DNAI contains multiple PSAs and multiple EASs. AF selects the target EAS based on the target DNAI provided by V-SMF, that is, AF needs to select an EAS within the target DNAI. The same method can also be used for edge migration at the DNAI granularity. AF can instruct V-SMF to migrate the service flow between the terminal and the source DNAI to any EAS in the target DNAI; or V-SMF can also determine on its own to migrate the service flow between the terminal and the source DNAI to any EAS in the target DNAI.
[0315] Based on the same concept, referring to FIG9 , an embodiment of the present application further provides a communication device 900, which includes a processing unit 901 and an interface unit 902. The communication device 900 may be a first network element, or a communication device applied to the first network element, or used in conjunction with the first network element, and capable of implementing a communication method executed on the first network element side; or the communication device 900 may be a third network element, or a communication device applied to the third network element, or used in conjunction with the third network element, and capable of implementing a communication method executed on the third network element side.
[0316] The interface unit may also be referred to as a communication interface, interface module, transceiver module, transceiver, transceiver, or transceiver device. The processing unit may also be referred to as a processor, processing board, processing unit, or processing device. Optionally, the interface unit is configured to perform the sending and receiving operations on the first network element side or the third network element side in the above method. The device in the interface unit that implements the receiving function may be considered a receiving unit, and the device in the interface unit that implements the sending function may be considered a sending unit. That is, the interface unit includes a receiving unit and a sending unit.
[0317] When the communication device 900 is applied to a first network element, the processing unit 901 can be used to implement the processing functions of the first network element (e.g., V-SMF) in the examples of Figures 5 to 8 , and the interface unit 902 can be used to implement the transceiver functions of the first network element in the examples of Figures 5 to 8 . Alternatively, the communication device can also be understood with reference to the first and third aspects of the invention and the possible designs of the first and third aspects.
[0318] When the communication device 900 is applied to a third network element, the processing unit 901 can be used to implement the processing functions of the third network element (e.g., AF) in the examples of Figures 5 to 8, and the interface unit 902 can be used to implement the transceiver functions of the third network element in the examples of Figures 5 to 8. Alternatively, the communication device can also be understood with reference to the second and fourth aspects of the invention and the possible designs of the second and fourth aspects.
[0319] In addition, it should be noted that the aforementioned interface unit and / or processing unit can be implemented through virtual modules, for example, the processing unit can be implemented through a software function unit or a virtual device, and the interface unit can be implemented through a software function or a virtual device. Alternatively, the processing unit or interface unit can also be implemented through a physical device. For example, if the device is implemented using a chip / chip circuit, the interface unit can be an input / output circuit and / or a communication interface that performs input operations (corresponding to the aforementioned receiving operations) and output operations (corresponding to the aforementioned sending operations); the processing unit is an integrated processor or microprocessor or integrated circuit.
[0320] The division of modules in this application is illustrative and represents only a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the examples of this application may be integrated into a single processor, exist physically as separate modules, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in either hardware or software functional modules.
[0321] Based on the same technical concept, the embodiment of the present application further provides a communication device 1000. For example, the communication device 1000 can be a chip or a chip system. Optionally, in the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices.
[0322] The communication device 1000 can be used to implement the functions of any network element in the communication system described in the above examples. The communication device 1000 may include at least one processor 1010. Optionally, the processor 1010 is coupled to a memory, and the memory may be located within the device, or the memory may be integrated with the processor, or the memory may be located outside the device. For example, the communication device 1000 may also include at least one memory 1020. The memory 1020 stores the necessary computer programs, computer programs or instructions and / or data for implementing any of the above examples; the processor 1010 may execute the computer program stored in the memory 1020 to complete the method in any of the above examples.
[0323] The communication device 1000 may also include a communication interface 1030, and the communication device 1000 can exchange information with other devices through the communication interface 1030. Exemplarily, the communication interface 1030 can be a transceiver, a circuit, a bus, a module, a pin, or other types of communication interfaces. When the communication device 1000 is a chip-type device or circuit, the communication interface 1030 in the device 1000 can also be an input-output circuit that can input information (or receive information) and output information (or send information). The processor is an integrated processor or microprocessor or integrated circuit or logic circuit, and the processor can determine output information based on the input information.
[0324] Coupling in this application refers to an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. Processor 1010 may operate in conjunction with memory 1020 and communication interface 1030. This application does not limit the specific connection medium between the processor 1010, memory 1020, and communication interface 1030.
[0325] Optionally, referring to FIG10 , the processor 1010, the memory 1020, and the communication interface 1030 are interconnected via a bus 1040. Bus 1040 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, for example. Buses can be categorized as address buses, data buses, control buses, and the like. For ease of illustration, FIG10 shows only one thick line, but this does not imply that there is only one bus or only one type of bus.
[0326] In this application, a processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in this application. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in this application may be directly executed by a hardware processor, or by a combination of hardware and software modules within the processor.
[0327] In the present application, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or a volatile memory, such as a random-access memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in the present application may also be a circuit or any other device that can implement a storage function, for storing program instructions and / or data.
[0328] In one possible implementation, the communication device 1000 can be applied to a first network element. Specifically, the communication device 1000 can be the first network element, or it can be a device that can support the first network element and implement the functions of the first network element in any of the above-mentioned examples. The memory 1020 stores a computer program (or instruction) and / or data that implements the functions of the first network element in any of the above-mentioned examples. The processor 1010 can execute the computer program stored in the memory 1020 to complete the method executed by the first network element in any of the above-mentioned examples. Applied to the first network element, the communication interface in the communication device 1000 can be used to interact with a third network element, send information to the third network element, or receive information from the third network element.
[0329] In another possible implementation, the communication device 1000 can be applied to a third network element. Specifically, the communication device 1000 can be a third network element, or a device that can support a third network element and implement the functions of the third network element in any of the above-mentioned examples. The memory 1020 stores a computer program (or instruction) and / or data that implements the functions of the third network element in any of the above-mentioned examples. The processor 1010 can execute the computer program stored in the memory 1020 to complete the method performed by the third network element in any of the above-mentioned examples. Applied to the third network element, the communication interface in the communication device 1000 can be used to interact with the first network element, send information to the first network element, or receive information from the first network element.
[0330] Since the communication device 1000 provided in this example can be applied to a first network element to perform the method performed by the first network element, or applied to a third network element to perform the method performed by the third network element, the technical effects that can be achieved can refer to the above method examples and will not be repeated here.
[0331] Based on the above examples, the present application provides a communication system including a first network element and a third network element, wherein the first network element can implement the function of V-SMF in the communication method provided in the examples shown in Figures 5-8, and the third network element can implement the function of AF in the communication method provided in the examples shown in Figures 5-8.
[0332] The technical solutions provided in this application can be implemented in whole or in part through software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to this application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a terminal, an access network device, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media. The available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, digital video discs (DVDs)), or semiconductor media, etc.
[0333] In this application, under the premise of no logical contradiction, the examples can reference each other, for example, the methods and / or terms between method embodiments can reference each other, for example, the functions and / or terms between device embodiments can reference each other, for example, the functions and / or terms between device examples and method examples can reference each other.
[0334] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.
Claims
1. A communication method, It is characterized in that The method comprises: The first network element receives from the second network element a second Internet Protocol IP address range that allows the terminal to be routed to a local data network of a visited public land mobile network VPLMN; The first network element sends the first IP address range to the third network element according to the second IP address range; The first network element receives first indication information from the third network element, where the first indication information is used to instruct the first network element to migrate the service flow between the terminal and the source edge application server EAS to a target EAS, where the IP address of the target EAS belongs to the first IP address range.
2. The method according to claim 1, It is characterized in that The source EAS includes the EAS serving the terminal before the migration, and the target EAS includes the EAS serving the terminal after the migration.
3. The method according to claim 1 or 2, It is characterized in that The first network element sends the first IP address range to the third network element according to the second IP address range, including: The first network element receives a subscription request from the third network element, where the subscription request is used to request subscription to a first IP address range corresponding to at least one terminal; The first network element sends a notification message to the third network element, where the notification message includes a first IP address range corresponding to the at least one terminal.
4. The method according to any one of claims 1 to 3, It is characterized in that Before the first network element sends the first IP address range to the third network element according to the second IP address range, the method further includes: The first network element receives second indication information from the third network element, where the second indication information is used to instruct the first network element to replace the IP address of the user message; The first network element sends rejection information to the third network element, where the rejection information is used to instruct the first network element to reject replacement of the IP address of the user message.
5. The method according to claim 4, It is characterized in that The rejection information includes the first IP address range.
6. The method according to any one of claims 1 to 5, It is characterized in that After the first network element receives the first indication information from the third network element, the method further includes: the first network element instructs the fourth network element to replace the IP address of the user message.
7. The method according to any one of claims 1 to 6, It is characterized in that The first indication information includes the IP address of the target EAS.
8. The method according to claim 7, It is characterized in that The first indication information further includes at least one of the following information: the port number of the target EAS, the IP address of the source EAS, and the port number of the source EAS.
9. The method according to any one of claims 1 to 8, It is characterized in that The first network element is a session management network element of the VPLMN, and the first network element is used to obtain the second IP address range from the session management network element of the HPLMN.
10. A communication method, It is characterized in that The method comprises: The third network element obtains a first Internet Protocol IP address range that allows the terminal to be routed to a local data network of a visited public land mobile network VPLMN; The third network element sends first indication information to the first network element, where the first indication information is used to instruct the first network element to migrate the service flow between the terminal and the source edge application server EAS to the target EAS, and the IP address of the target EAS belongs to the first IP address range.
11. The method according to claim 10, It is characterized in that The source EAS includes the EAS serving the terminal before the migration, and the target EAS includes the EAS serving the terminal after the migration.
12. The method according to claim 10 or 11, It is characterized in that The third network element obtains a first IP address range that allows the terminal to be routed to the local data network of the VPLMN, including: The third network element sends a subscription request to the first network element, where the subscription request is used to request subscription to a first IP address range corresponding to at least one terminal; The third network element receives a notification message from the first network element, where the notification message includes a first IP address range corresponding to the at least one terminal.
13. The method according to claim 10 or 11, It is characterized in that The third network element obtains a first IP address range that allows the terminal to be routed to the local data network of the VPLMN, including: The third network element instructs the first network element to replace the IP address of the user message; The third network element receives rejection information from the first network element, where the rejection information is used to instruct the first network element to reject the replacement of the IP address of the user message; The third network element receives the first IP address range from the first network element.
14. The method according to claim 10 or 11, It is characterized in that The first IP address range is storage information of the third network element.
15. The method according to claim 14, It is characterized in that Before the third network element sends the first indication information to the first network element, the method further includes: The third network element determines that the service flow is a first type of service flow.
16. The method according to any one of claims 10 to 15, It is characterized in that The method further comprises: The third network element selects a target EAS corresponding to a target IP address in the first IP address range according to the location of the terminal and / or a load condition of at least one EAS corresponding to the first IP address range.
17. The method according to any one of claims 11 to 16, It is characterized in that The first indication information includes the IP address of the target EAS.
18. The method according to claim 17, It is characterized in that The first indication information further includes at least one of the following information: the port number of the target EAS, the IP address of the source EAS, and the port number of the source EAS.
19. A communication method, It is characterized in that The method comprises: The first network element receives from the second network element a second Internet Protocol IP address range that allows the terminal to be routed to a local data network of a visited public land mobile network VPLMN; The first network element receives first information from a third network element, where the first information includes a correspondence between at least one edge application server EAS and at least one weight factor; The first network element determines, based on the first information, a target EAS belonging to a first IP address range, the first IP address range being related to the second IP address range; The first network element sends first indication information to the third network element, where the first indication information is used to indicate the target EAS; The first network element receives second indication information from the third network element, where the second indication information is used to instruct the first network element to migrate the service flow between the terminal and the source EAS to the target EAS.
20. The method according to claim 19, It is characterized in that The source EAS includes the EAS serving the terminal before the migration, and the target EAS includes the EAS serving the terminal after the migration.
21. The method according to claim 19 or 20, It is characterized in that The first network element determines, according to the first information, a target EAS belonging to the first IP address range, including: The first network element determines all EASs in the first information that belong to the first IP address range, and selects an EAS with a maximum weight factor as a target EAS among the determined EASs according to a correspondence between the at least one EAS and the at least one weight factor.
22. The method according to any one of claims 19 to 21, It is characterized in that The second indication information includes the IP address of the target EAS.
23. The method according to claim 22, It is characterized in that The second indication information further includes at least one of the following information: the port number of the target EAS, the IP address of the source EAS, and the port number of the source EAS.
24. The method according to any one of claims 19 to 23, It is characterized in that After the first network element receives the second indication information from the third network element, the method further includes: The first network element instructs the fourth network element to replace the IP address of the user message.
25. The method according to any one of claims 19 to 24, It is characterized in that The first network element is a session management network element of the VPLMN, and the first network element is used to obtain the second IP address range from the session management network element of the HPLMN.
26. A communication method, It is characterized in that The method comprises: The third network element sends first information to the first network element, where the first information includes a correspondence between at least one edge application server EAS and at least one weight factor; The third network element receives first indication information from the first network element, where the first indication information is used to indicate a target EAS; The third network element sends second indication information to the first network element, and the second indication information is used to instruct the first network element to migrate the service flow between the terminal and the source EAS to the target EAS, and the IP address of the target EAS belongs to the first IP address range, and the first IP address range is an IP address range that allows the terminal to be routed to the local data network of the visited public land mobile network VPLMN.
27. The method according to claim 26, It is characterized in that The method further comprises: The third network element determines that the service flow is a first type of service flow.
28. The method according to claim 26 or 27, It is characterized in that The source EAS includes the EAS serving the terminal before the migration, and the target EAS includes the EAS serving the terminal after the migration.
29. The method according to any one of claims 26 to 28, It is characterized in that The second indication information includes the IP address of the target EAS.
30. The method according to any one of claims 27 to 29, It is characterized in that The second indication information further includes at least one of the following information: the port number of the target EAS, the IP address of the source EAS, and the port number of the source EAS.
31. A communication method, It is characterized in that The method comprises: The second network element sends to the first network element a second Internet Protocol IP address range that allows the terminal to be routed to a local data network of a visited public land mobile network VPLMN; The first network element sends the first IP address range to the third network element according to the second IP address range; The third network element sends first indication information to the first network element, where the first indication information is used to instruct the first network element to migrate the service flow between the terminal and the source EAS to a target EAS, and the IP address of the target EAS belongs to the first IP address range.
32. A communication method, It is characterized in that The method comprises: The second network element sends to the first network element a second Internet Protocol IP address range that allows the terminal to be routed to a local data network of a visited public land mobile network VPLMN; The third network element sends first information to the first network element, where the first information includes a correspondence between at least one edge application server EAS and at least one weight factor; The first network element determines, based on the first information, a target EAS belonging to a first IP address range, the first IP address range being related to the second IP address range; The first network element sends first indication information to the third network element, where the first indication information is used to indicate the target EAS; The third network element sends second indication information to the first network element, where the second indication information is used to instruct the first network element to migrate the service flow between the terminal and the source EAS to the target EAS.
33. A communication device, It is characterized in that The communication device is used to execute the method according to any one of claims 1-30.
34. A communication system, It is characterized in that It comprises a visited location-session management network element V-SMF and an application function network element AF, wherein the V-SMF is used to execute the method according to any one of claims 1 to 9, and the AF is used to execute the method according to any one of claims 10 to 18.
35. A communication system, It is characterized in that It comprises a visited location-session management network element V-SMF and an application function network element AF, the V-SMF is used to execute the method as described in any one of claims 19-25, and the AF is used to execute the method as described in any one of claims 26-30.
36. A communication device, It is characterized in that The device comprises a processor, wherein the processor is coupled to a memory, wherein the memory is used to store instructions. When the program or instructions are executed by the processor, the device performs the method according to any one of claims 1 to 30.
37. A computer readable storage medium, It is characterized in that The storage medium stores a computer program or instruction, and when the computer program or instruction is executed by the communication device, the method according to any one of claims 1 to 30 is implemented.
Citation Information
Patent Citations
Application relocation method and device, electronic equipment and storage medium
CN113676977A
Information transmission method and device
CN115884155A
Coordination of edge application server reselection using edge client subnet
WO2022033832A1
Communication method and apparatus
WO2023051427A1
Cited By
IP address change
WO2026218597A1
