Holographic communication mobility management method and related devices

Abstract

The present disclosure provides a holographic communication mobility management method and related equipment, and relates to the technical field of communication. The method comprises the following steps: an edge network node receives mobile signaling sent by an initial access point, the initial access point is an access point accessed before a network entity moves, and the mobile signaling carries a target identifier of the network entity; the target identifier of the network entity is inquired from a name resolution system, a target network address corresponding to the target identifier of the network entity is acquired, and the target network address is a network address after the network entity moves; a mapping relationship between the target identifier of the network entity and the target network address is used to update an entity identifier-position mapping table of the edge network node; and data packets forwarded to the network entity are re-bound based on the entity identifier-position mapping table. The present disclosure can effectively cope with the growing demand for mobility and improve the performance of holographic communication.

Description

Technical Field

[0001] This disclosure relates to the field of network security technology, and in particular to a holographic communication mobile management method, a holographic communication mobile management device, a holographic communication mobile management system, an electronic device, a computer-readable storage medium, and a computer program product. Background Technology

[0002] With the widespread deployment and popularization of 5G technology, holographic communication is gradually developing. Holographic communication can not only achieve real-time transmission of three-dimensional images, but also transmit multi-sensory information such as sound and touch, greatly enriching people's remote communication experience. At the same time, with the rapid increase in the number of smartphones, tablets, and other portable smart devices, mobile data traffic is also growing exponentially. In this context, effectively managing these constantly changing terminal devices becomes particularly important.

[0003] In related technologies, the traditional Internet protocol architecture tightly binds the identity of a network entity to its physical address. However, this approach proves inadequate in the face of highly dynamic holographic communication environments. When a network entity changes its access point, traditional methods require reallocating a new network address and maintaining session continuity through complex redirection processes. These methods are unsuitable for the highly dynamic network environments of holographic communication, increasing system complexity and potentially leading to inefficiencies.

[0004] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0005] This disclosure provides a holographic communication mobile management method and related equipment, which at least to some extent overcomes the problem that the method of binding the identity of network entities to physical addresses in the Internet protocol architecture is not applicable to holographic communication, and that the system has problems of high complexity and low efficiency.

[0006] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0007] According to one aspect of this disclosure, a holographic communication mobility management method is provided, applied to an edge network node. The method includes: receiving mobility signaling sent by an initial access point, wherein the initial access point is an access point accessed by a network entity before its movement, and the mobility signaling carries a target identifier of the network entity; querying the target identifier of the network entity from a name resolution system to obtain a target network address corresponding to the target identifier of the network entity, wherein the target network address is the network address of the network entity after its movement; updating an entity identifier-location mapping table of the edge network node according to the mapping relationship between the target identifier of the network entity and the target network address; and rebinding data packets forwarded to the network entity based on the entity identifier-location mapping table.

[0008] In one embodiment of this disclosure, in the entity identifier-location mapping table, one network entity corresponds to one table entry, and one table entry includes the mapping relationship between the entity identifier field, network address field, and timestamp field of the network entity; before querying the target identifier of the network entity from the name resolution system to obtain the target network address corresponding to the target identifier of the network entity, the method further includes: establishing a table entry corresponding to the network entity in the entity identifier-location mapping table, configuring the entity identifier field of the table entry as the target identifier of the network entity, configuring the timestamp field of the table entry as the current system time when the table entry was established, and configuring the network address field of the table entry as a default initial value; after querying the target identifier of the network entity from the name resolution system to obtain the target network address corresponding to the target identifier of the network entity, the method further includes: modifying the network address field of the table entry from the default initial value to the target network address.

[0009] In one embodiment of this disclosure, the method further includes: if there is an entry in the entity identifier-location mapping table that is not matched within a preset time period, then the entry is deleted from the entity identifier-location mapping table.

[0010] In one embodiment of this disclosure, the method further includes: generating a mobility notification message based on the updated entity identifier-location mapping table of the edge network node, and propagating the mobility notification message through a first forwarding path to each intermediate network node on the first forwarding path, up to the terminating network node, so that each intermediate network node and the terminating network node update the entity identifier-location mapping table of the corresponding node according to the target identifier and the target network address of the network entity, wherein the first forwarding path is a path with the opposite transmission direction to the second forwarding path, and the second forwarding path is a path from the source network node to the path before the network entity moves.

[0011] In one embodiment of this disclosure, the terminating network node is the next network node after the fork node of the second forwarding path and the third forwarding path, the third forwarding path being the path from the source network node to the network entity after it has moved; the next network node after the fork node is the network node following the fork node along the transmission direction of the first forwarding path.

[0012] In one embodiment of this disclosure, the data packet includes an IPv6 header, an entity identifier header, and data, wherein the entity identifier header is an IPv6 extended header and contains the target identifier of the network entity.

[0013] According to another aspect of this disclosure, a holographic communication mobility management method is also provided, applied to an intermediate network node. The method includes: in response to the intermediate network node obtaining a data packet of a network entity, matching the target identifier of the network entity in an entity identifier-location mapping table corresponding to the intermediate network node, wherein the entity identifier-location mapping table is used to characterize the mapping relationship between the target network identifier and the target network address of the network entity stored by the intermediate network node; if the target identifier of the network entity is matched, determining the target network address corresponding to the target identifier, modifying the target network address field of the network address field to the destination network address of the data packet of the network entity, and forwarding the data packet of the network entity according to the target network address.

[0014] In one embodiment of this disclosure, the method further includes: if no target identifier of the network entity is matched, then forwarding the data packets of the network entity according to the routing table.

[0015] In one embodiment of this disclosure, the method further includes: receiving a mobility notification message propagated through a first forwarding path, the mobility notification message being generated based on an updated entity identifier-location mapping table of an edge network node, the entity identifier-location mapping table of the edge network node being used to characterize the mapping relationship between the target identifier of the moved network entity and the target network address, the first forwarding path being a path with the transmission direction opposite to that of a second forwarding path, the second forwarding path being a path that routes data packets from the source network node to the point before the network entity moved; if the intermediate network node is not a terminating network node, then updating the entity identifier-location mapping table of the intermediate network node according to the mobility notification message, and propagating the mobility notification message through the first forwarding path until reaching the terminating network node; if the intermediate network node is a terminating network node, then updating the entity identifier-location mapping table of the terminating network node according to the mobility notification message.

[0016] In one embodiment of this disclosure, the step of propagating the mobile notification message through the first forwarding path includes: querying an ingress port table to obtain the ingress port of the data packet of the network entity flowing through the intermediate network node; and forwarding the mobile notification message through the ingress port of the data packet of the network entity flowing through the intermediate network node.

[0017] In one embodiment of this disclosure, the terminating network node is the next network node after the fork node of the second forwarding path and the third forwarding path, the third forwarding path being the path from the source network node to the network entity after it has moved; the next network node after the fork node is the network node following the fork node along the transmission direction of the first forwarding path.

[0018] In one embodiment of this disclosure, the mobile notification message carries the initial network address and the target network address of the network entity, wherein the initial network address is the network address of the network entity before it moves, and the target network address is the network address of the network entity after it moves; wherein, after receiving the mobile notification message propagated through the first forwarding path, the method further includes: using the initial network address and the target network address of the network entity to look up a routing table to obtain the outgoing port corresponding to the initial network address and the outgoing port corresponding to the target network address; if the outgoing port of the target network address is the same as the outgoing port of the initial network address, then the intermediate network node is determined as the terminating network node, and the propagation of the mobile notification message is stopped; if the outgoing port of the target network address is different from the outgoing port of the initial network address, then the incoming port table or the routing table is queried, and the obtained port is used to forward the mobile notification message.

[0019] According to another aspect of this disclosure, a holographic communication mobility management device is provided, applied to an edge network node. The device includes: a signaling receiving module, configured to receive mobility signaling sent by an initial access point, wherein the initial access point is the access point accessed by the network entity before its movement, and the mobility signaling carries a target identifier of the network entity; an address acquisition module, configured to query the target identifier of the network entity from a name resolution system and obtain a target network address corresponding to the target identifier of the network entity, wherein the target network address is the network address of the network entity after its movement; a first update module, configured to update the entity identifier-location mapping table of the edge network node according to the mapping relationship between the target identifier of the network entity and the target network address; and a rebinding module, configured to rebind data packets forwarded to the network entity based on the entity identifier-location mapping table.

[0020] According to another aspect of this disclosure, a holographic communication mobility management device is provided, applied to an intermediate network node. The device includes: an identifier matching module, configured to, in response to the intermediate network node obtaining a data packet of a network entity, match a target identifier of the network entity in an entity identifier-location mapping table corresponding to the intermediate network node, the entity identifier-location mapping table being used to characterize the mapping relationship between the target network identifier and the target network address of the network entity stored by the intermediate network node; and an address binding module, configured to, if a target identifier of the network entity is matched, determine the target network address corresponding to the target identifier, modify the target network address in the network address field to the destination network address of the data packet of the network entity, and forward the data packet of the network entity according to the target network address.

[0021] According to another aspect of this disclosure, a holographic communication mobile management system is provided, comprising a name resolution system, an edge network node, and an intermediate network node, wherein: the name resolution system is used to store target identifiers and corresponding target network addresses of network entities before and after their movement; the edge network entity is used to receive mobility signaling sent by an initial access point, the initial access point being the access point accessed by the network entity before its movement, the mobility signaling carrying the target identifier of the network entity; querying the target identifier of the network entity from the name resolution system to obtain the target network address corresponding to the target identifier of the network entity, the target network address being the network address of the network entity after its movement; and updating the edge network node according to the mapping relationship between the target identifier of the network entity and the target network address. The entity identifier-location mapping table is used to rebind and forward data packets to the network entity. The intermediate network node, in response to receiving a data packet from the network entity, matches the target identifier of the network entity in the entity identifier-location mapping table corresponding to the intermediate network node. The entity identifier-location mapping table represents the mapping relationship between the target network identifier and the target network address of the network entity stored by the intermediate network node. If a target identifier of the network entity is matched, the target network address corresponding to the target identifier is determined, the target network address in the network address field is modified to the destination network address of the data packet of the network entity, and the data packet of the network entity is forwarded according to the target network address.

[0022] According to another aspect of this disclosure, an electronic device is provided, comprising: a processor and a memory, the memory being used to store executable instructions of the processor; wherein the processor is configured to perform the above-described holographic communication mobility management method by executing the executable instructions.

[0023] According to another aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the above-described holographic communication mobility management method.

[0024] According to another aspect of this disclosure, a computer program product is provided, the computer program product comprising a computer program or computer instructions, the computer program or computer instructions being loaded and executed by a processor to enable a computer to implement the above-described holographic communication mobile management method.

[0025] In this embodiment, the edge network node receives a mobility signaling message sent by an initial access point (the access point the network entity accessed before its movement). The initial access point carries the target identifier of the network entity. The node queries the name resolution system to obtain the target network address corresponding to the target identifier of the network entity. The target network address is the network address after the network entity's movement. Based on the mapping relationship between the target identifier and the target network address, the edge network node updates its entity identifier-location mapping table. Based on the entity identifier-location mapping table, the data packets forwarded to the network entity are re-bound. This disclosure records the latest mapping relationship between the network entity's identifier and network address through the entity identifier-location mapping table. The network node dynamically re-binds the data packets forwarded to the moving network entity with the new network address according to the entity identifier-location mapping table. This provides a more flexible and scalable holographic communication mobility management method that can effectively cope with the increasing mobility demands and significantly improve the overall performance of holographic communication applications.

[0026] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0027] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0028] Figure 1 A schematic diagram of an exemplary architecture of a holographic communication mobility management method according to an embodiment of the present disclosure is shown.

[0029] Figure 2 A flowchart of a holographic communication mobility management method according to an embodiment of this disclosure is shown.

[0030] Figure 3This diagram illustrates the structure of a holographic communication mobile management system according to an embodiment of the present disclosure.

[0031] Figure 4 This diagram illustrates the state changes of a network entity's forwarding path before and after movement, as shown in an embodiment of this disclosure.

[0032] Figure 5 A flowchart of another holographic communication mobility management method is shown in an embodiment of this disclosure.

[0033] Figure 6 A flowchart of another holographic communication mobility management method is shown in this embodiment.

[0034] Figure 7 A flowchart of another holographic communication mobility management method is shown in an embodiment of this disclosure.

[0035] Figure 8 A schematic diagram of the structure of a holographic communication mobility management device according to an embodiment of the present disclosure is shown.

[0036] Figure 9 This illustration shows a schematic diagram of another holographic communication mobility management device in an embodiment of the present disclosure.

[0037] Figure 10 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0038] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0039] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0040] The specific implementation methods of the embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0041] Figure 1A schematic diagram of an exemplary system architecture applicable to the holographic communication mobility management method of embodiments of this disclosure is shown. Figure 1 As shown, the system architecture 100 may include terminal device 101, network 102 and network-side device 103.

[0042] Network 102 is a medium used to provide a communication link between terminal device 101 and network-side device 103, and can be a wired network or a wireless network.

[0043] Optionally, the aforementioned wireless or wired networks use standard communication technologies and / or protocols. The network is typically the Internet, but can also be any network, including but not limited to Local Area Networks (LANs), Metropolitan Area Networks (MANs), Wide Area Networks (WANs), mobile, wired or wireless networks, private networks, or any combination of virtual private networks. In some embodiments, technologies and / or formats including Hyper Text Markup Language (HTML), Extensible Markup Language (XML), etc., are used to represent data exchanged over the network. Furthermore, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Networks (VPNs), and Internet Protocol Security (IPSec) can be used to encrypt all or some links. In other embodiments, custom and / or dedicated data communication technologies can be used to replace or supplement the aforementioned data communication technologies.

[0044] Optionally, the terminal device 101 in this embodiment of the present disclosure may also be referred to as UE (User Equipment) or a network entity. In specific implementation, the terminal device 101 may be a mobile phone, a tablet computer, a laptop computer, a personal digital assistant (PDA), a mobile internet device (MID), a wearable device, or an in-vehicle device, etc. It should be noted that the specific type of the terminal device 101 is not limited in the embodiments of the present invention.

[0045] The network-side device 103 can be a base station, relay, or access point, etc. The base station can be a 5G or later version base station (e.g., 5G NR NB), or a base station in other communication systems (e.g., eNB base station). It should be noted that the specific type of network-side device is not limited in this embodiment of the disclosure.

[0046] Those skilled in the art will know that Figure 1 The number of terminal devices, networks, and network-side devices shown is merely illustrative; any number of terminals, networks, and network-side devices can be included as needed. This disclosure does not limit the scope of the embodiments.

[0047] With the widespread deployment and popularization of 5G technology, holographic communication is gradually developing. Holographic communication can not only achieve real-time transmission of three-dimensional images, but also transmit multi-sensory information such as sound and touch, greatly enriching people's remote communication experience. However, holographic communication also faces many challenges in practical applications, especially ensuring high-quality information transmission. Because holographic communication involves massive amounts of data and is extremely sensitive to latency, it is highly susceptible to various factors during data transmission, such as noise interference, network jitter, and data packet loss. These factors can severely impact user experience and even lead to image distortion or interruption.

[0048] At the same time, with the explosive growth in the number of smartphones, tablets, and other portable smart devices, mobile data traffic has also grown exponentially. In this context, effectively managing these constantly changing terminal devices has become particularly important.

[0049] In the traditional internet architecture, the identity of a network entity is tightly bound to its corresponding physical address. This design can meet the needs of most application scenarios, but it falls short when facing highly dynamic holographic communication network environments. Specifically, when a mobile terminal device changes its access point, in the traditional internet architecture, a new IP address needs to be reassigned to the terminal device, and a complex redirection process is required to maintain session continuity. This method increases system complexity and leads to low communication efficiency.

[0050] In related technologies, various IP-based mobility management schemes have been proposed, such as Mobile IP and Proxy Mobile IP. These methods all attempt to achieve seamless handover by introducing a centralized anchor point to track the location changes of each mobile terminal device. However, this centralized architecture often leads to suboptimal path selection problems; that is, to ensure uninterrupted connectivity, data forwarding must be routed via detours, which can easily sacrifice network performance. Furthermore, as the user base grows, a single control point may face enormous load pressure, thus affecting the stability and scalability of the entire holographic communication system.

[0051] To at least partially address the aforementioned technical problems, this disclosure proposes a holographic communication mobility management method based on a post-binding mechanism. By decoupling the relationship between the identity of a network entity and its actual location, efficient data transmission can be maintained even when the network topology changes. Specifically, in the holographic communication mobility management method provided by this disclosure, the edge network node receives mobility signaling sent by the initial access point, which is the access point the network entity accessed before its movement. The mobility signaling carries the target identifier of the network entity. The target identifier of the network entity is queried from the name resolution system to obtain the target network address corresponding to the target identifier of the network entity. The target network address is the network address after the network entity's movement. The network address is used to update the entity identifier-location mapping table of the edge network node according to the mapping relationship between the target identifier and the target network address of the network entity; based on the entity identifier-location mapping table, the data packets forwarded to the network entity are rebound. This disclosure records the latest mapping relationship between the identifier and the network address of the network entity through the entity identifier-location mapping table. The network node dynamically rebinds the data packets forwarded to the mobile network entity with the new network address according to the entity identifier-location mapping table. This provides a more flexible and scalable holographic communication mobility management method, which can not only effectively cope with the increasing mobility demand, but also significantly improve the overall performance of holographic communication applications.

[0052] The following detailed description of this exemplary implementation method is provided in conjunction with the accompanying drawings and embodiments.

[0053] First, this disclosure provides a holographic communication mobility management method, which can be executed by any electronic device with computing capabilities. In some embodiments, the method can be executed by an edge network node; in some embodiments, the method can be executed by an intermediate network node.

[0054] Figure 2 A flowchart of a holographic communication mobility management method according to an embodiment of this disclosure is shown. Figure 2 As shown, in one embodiment, the holographic communication mobility management method provided in this disclosure is applied to an edge network node and includes the following steps:

[0055] S202. Receive the mobility signaling sent by the initial access point, which is the access point that the network entity accessed before moving, and the mobility signaling carries the target identifier of the network entity.

[0056] In one embodiment, the network entity is a mobile terminal device, router, data, etc., in the holographic communication system.

[0057] like Figure 3 As shown, in one embodiment, a network entity is split into a locator and an identifier. The identifier ID is a globally unique identifier for the network entity, and the network address is used as the locator to locate the network entity. For example, using an IP address as the network address is backward compatible with current routing and forwarding devices. The target identifier and target network address of the network entity are included in the data packets exchanged through the network entity.

[0058] Mobility signaling is used to propagate information about the movement of network entities. After a network entity moves, the initial access point to which the entity previously connected sends mobility signaling carrying the destination identifier of the network entity to the edge router, thereby quickly notifying the network entity of the movement event.

[0059] S204. Query the target identifier of the network entity from the name resolution system, and obtain the target network address corresponding to the target identifier of the network entity. The target network address is the network address of the network entity after it is moved.

[0060] Before moving, a network entity accesses the network through its initial access point; after moving, it accesses the network through its destination access point. The mapping between the destination identifier and the destination network address of a network entity is maintained in the name resolution system.

[0061] S206. Update the Entity Identifier-Location Mapping Table (ELMT) of the edge network node according to the mapping relationship between the target identifier and the target network address of the network entity.

[0062] In one embodiment, each network node (e.g., a router) maintains an entity identifier-network address mapping table to record the latest mapping relationship between the target identifier and the target network address of a moving network entity. In the entity identifier-location mapping table of an edge network node, one network entity corresponds to one table entry, and one table entry includes the mapping relationship between the network entity's entity identifier field, network address field, and timestamp field.

[0063] As shown in Table 1, the entity identifier-location mapping table contains three entries, where the new IP corresponding to the target identifier ID1 is IP1 and the timestamp is T1.

[0064] Table 1. Structure of Entity Identifier-Location Mapping Table

[0065] ID New IP Timestamp ID1 IP1 T1 ID2 IP2 T2 ID3 IP3 T3 … … …

[0066] S208. Based on the entity identifier-location mapping table, rebind the data packets forwarded to the network entity.

[0067] Edge network nodes can dynamically rebind packets forwarded to mobile network entities with new network addresses based on entity identifier-location mapping tables.

[0068] When a network entity's data packet flows through an edge network node, the edge network node first matches it against the entity identifier-location mapping table. If the data packet matches the entity identifier-location mapping table, the edge network node modifies the destination network address of the data packet; otherwise, the router forwards the data packet directly according to the IP forwarding table.

[0069] If an entry in the entity identifier-location mapping table of an edge network node does not match for an extended period of time, the edge network node determines that the network entity corresponding to the target identifier in that entry is idle, has not established a session, or has left the nearby area. The edge network node will then delete the entry, thereby improving scalability.

[0070] like Figure 4 As shown in (a), before network entity 0 moves, the source network node CN routes the data packet to network entity 0 via the third forwarding path (indicated by the green line in the figure). The third forwarding path is source network node CN-R1-R2-R4-R6-network entity 0. When network entity 0 moves to 1, the initial access point that network entity 0 accessed before moving sends a movement signaling message to the edge network node R6, which carries the destination identifier of network entity 0. The edge network node R6 queries the name resolution system based on the destination identifier of network entity 0 to determine the target network address corresponding to the destination identifier of the network entity, and updates the entity identifier-address mapping table of the edge network node. The edge network node modifies the destination network address of the data packet and routes it to the moved network entity 1 via the second forwarding path. At this time, the second forwarding path is source network node CN-R1-R2-R6-R6-R4-R2-R5-network entity 0.

[0071] In this embodiment, the edge network node receives a mobility signaling message sent by an initial access point (the access point the network entity accessed before its movement). The initial access point carries the target identifier of the network entity. The node queries the name resolution system to obtain the target network address corresponding to the target identifier of the network entity. The target network address is the network address after the network entity's movement. Based on the mapping relationship between the target identifier and the target network address, the edge network node updates its entity identifier-location mapping table. Based on the entity identifier-location mapping table, the data packets forwarded to the network entity are re-bound. This disclosure records the latest mapping relationship between the network entity's identifier and network address through the entity identifier-location mapping table. The network node dynamically re-binds the data packets forwarded to the moving network entity with the new network address according to the entity identifier-location mapping table. This provides a more flexible and scalable holographic communication mobility management method that can effectively cope with the increasing mobility demands and significantly improve the overall performance of holographic communication applications.

[0072] In one embodiment, in the entity identifier-location mapping table, one network entity corresponds to one table entry. Each table entry includes the mapping relationship between the network entity's entity identifier field, network address field, and timestamp field. Specifically, the value of the entity identifier field corresponds to the target identifier of the network entity, the value of the network address field corresponds to the network address of the network entity after it has moved, and the timestamp field corresponds to the creation time of the entry.

[0073] Figure 5 A flowchart of another holographic communication mobility management method according to an embodiment of this disclosure is shown. Figure 5 As shown, in one embodiment, before S204 queries the target identifier of the network entity from the name resolution system to obtain the target network address corresponding to the target identifier of the network entity, the method further includes:

[0074] S203. Create a table entry corresponding to the network entity in the entity identifier-location mapping table, configure the entity identifier field of the table entry as the target identifier of the network entity, configure the timestamp field of the table entry as the current system time when the table entry is created, and configure the network address field of the table entry as the default initial value.

[0075] After S204 queries the name resolution system for the target identifier of the network entity and obtains the target network address corresponding to the target identifier of the network entity, the method further includes:

[0076] S205. Change the network address field of the table entry from the default initial value to the target network address.

[0077] It should be noted that for edge network nodes, the entity identifier-location mapping table is initially empty, with no entries. Upon receiving mobility signaling, the edge network node can add an entry to the entity identifier-location mapping table based on the target identifier of the network entity carried in the mobility signaling. The entity identifier field of this entry is configured to the target identifier, the timestamp field is configured to the current system time at the time of entry creation, and the network address field is configured to the default initial value. The default initial value can be determined according to actual needs, and its value is not limited. The default initial value indicates that the table entry has not been fully updated and that data packets to be sent to the network entity are temporarily stored.

[0078] After the edge network node retrieves the target network address corresponding to the target identifier from the name resolution system, the network address field of the table entry can be modified from the default initial value to the target network address.

[0079] In one embodiment, when an entry containing a target identifier already exists in the entity identifier-location mapping table, the timestamp field can be configured to the current system time, the network address field of the entry can be modified to the default initial value, and then the default initial value can be replaced with the target network address queried from the name resolution system, thereby enabling the edge network node to update the entity identifier-location mapping table.

[0080] When a network entity's data packet flows through the edge network node, the edge network node matches the destination identifier of the network entity corresponding to the data packet in the entity identifier-location mapping table. If a table entry is matched and the network address field of the entry is not the default initial value, the data packet will undergo late binding, i.e., the destination network address of the data packet will be modified to the destination network address (new IP address) of the table entry's network address field, and then forwarded according to the destination network address. If a table entry is matched but the network address field of the entry is the default initial value, the data packet will be temporarily stored in the edge router to avoid packet loss, and the entity identifier-location mapping table will be queried periodically until the network address field of the table entry is modified from the default initial value to the destination network address, and then forwarded according to the destination network address. If no table entry corresponding to the destination identifier is matched, it indicates that the network entity has not moved, and the data packet will be forwarded directly according to the IP routing table.

[0081] The routing table is stored in the network node. The routing table includes the destination address, mask, and next information, which guides the selection of the path for data packets from the source address to the destination address.

[0082] In this embodiment of the disclosure, updating the entity identifier-address mapping table of the edge network node through mobile signaling enables late binding of data packets routed to the network entity, ensuring that the network entity can maintain an uninterrupted session during movement and guaranteeing session continuity.

[0083] In one embodiment, the method further includes: if an entry in the entity identifier-location mapping table does not match within a preset time period, then deleting an entry from the entity identifier-location mapping table.

[0084] It should be noted that the preset time period can be pre-configured in the edge network nodes, and the value of the preset time period can be determined according to actual needs, such as 24 hours.

[0085] Based on the timestamp field of the entity identifier-location mapping table. When a data packet flows through an edge network node, if the table entry matches, the timestamp field of that entry is updated to the current system time. If the timestamp field of an entry has not been updated for a long time, it indicates that the network entity corresponding to the target identifier of that entry is in an idle state and has not established a session, or that the network entity has been away from the nearby network for a long time. Therefore, the edge network node deletes the entry.

[0086] In addition, the decision to delete a table entry can be made based on the number of times the entry is matched within a preset time period. For example, if the number of matches for a table entry is less than a preset threshold within 24 hours, the entry will be deleted.

[0087] In this embodiment of the disclosure, timeout deletion of table entries is used to delete unnecessary table entries in the entity identifier-location mapping table, thereby improving the scalability of the entity identifier-location mapping table.

[0088] Figure 6 A flowchart illustrating yet another holographic communication mobility management method according to an embodiment of this disclosure is shown. Figure 6 As shown, in one embodiment, the method further includes:

[0089] S210. Generate a mobility notification message based on the updated entity identifier-location mapping table of the edge network node, and propagate the mobility notification message to each intermediate network node on the first forwarding path through the first forwarding path until the termination network node, so that each intermediate network node and the termination network node update the entity identifier-location mapping table of the corresponding node according to the target identifier and target network address of the network entity. The first forwarding path is a path with the opposite transmission direction to the second forwarding path. The second forwarding path is a path from the source network node to the path before the network entity moves.

[0090] In one embodiment, the first forwarding path is the path in the opposite direction to the transmission direction of the data packet before the network entity moves. For example... Figure 4 As shown in (a), the data packet is routed from the source network node CN to network entity 0 via the second forwarding path, which is source network node CN-R2-R4-R6-network entity 0. After the network entity moves, the edge network node generates a mobility notification message, which is then forwarded to all intermediate network nodes before the edge network node via the first forwarding path. This allows the intermediate network nodes before the edge network node to know the new mapping relationship between the target identifier and the target network address of the network node, thereby triggering each intermediate network node to perform late binding and modify the forwarding path of the data packet. The first forwarding path is R6-R4-R2-R1. The propagation of the mobility notification message has a special characteristic, forming an invisible one-to-many propagation.

[0091] Intermediate network nodes are network nodes between the source network node and the network entity. The number of intermediate network nodes is greater than or equal to one and can be determined according to actual needs. The destination of the mobile notification message is every intermediate network node in the propagation path, not just the terminating network node.

[0092] In this embodiment, the propagation of the mobility notification message affects the entity identifier-address mapping table stored in the edge router. This mapping table triggers late binding of the data packet at the edge router and even at each intermediate network node along the first forwarding path, thus affecting the forwarding path of the data packet. If the edge router stops propagating the mobility notification after learning of the entity's movement time, the edge router becomes a temporary anchor point. The data packet will not be late-bound until it reaches the edge router. The new path of the data packet will be particularly long, resulting in high overall network overhead. In this disclosure, the mobility notification message propagates along the reverse forwarding path of the data packet. Each intermediate network node through which the mobility notification message flows performs late binding on the data packet. As the mobility notification message propagates, the forwarding path of the data packet is greatly shortened.

[0093] In one embodiment, the terminating network node is the next network node after the fork node of the second and third forwarding paths, where the third forwarding path is the path from the source network node to the network entity after the data packet has moved; the next network node after the fork node is the network node after the fork node along the transmission direction of the first forwarding path.

[0094] Continue to refer to Figure 4 As mobile notification messages propagate, many data packets will have temporary paths during mobility handover. For example... Figure 4As shown in (b), after the mobility notification message flows through the intermediate network node R4, the intermediate network node R4 modifies the data packet and forwards it to the target network address of the network entity, i.e., the new IP address. At this time, the temporary path of the data packet is CN-R1-R2-R4-R2-R5-MN. Figure 4 In (c), the mobility notification message flows through intermediate network node R2. Intermediate network node R2 is the branching node of the two paths (forming a Y shape) from the initial position and the target position of CN to MN. At this time, the new temporary path of the data packet will be CN-R1-R2-R5-MN, and subsequent data packets sent by CN to MN will follow the path shown in the diagram. Figure 4 (d) shows forwarding along the CN-R1-R2-R5-MN path. Figure 4 The CN-R1-R2-R5-MN path in (d) is the third forwarding path mentioned above. The next network node after the fork node is... Figure 4 The intermediate node R1 in the network. Clearly, as the mobile notification message propagates, the forwarding path of the data packets is shortened, and the new path is often optimal, which reduces overall network overhead.

[0095] In this embodiment, a mobile notification propagation scheme is used to establish and update the entity identifier-location mapping table, and to promptly notify the network of mobile events. The mobile notification propagation mechanism enables data packets to be quickly forwarded to the new network address after a network entity moves, and the new path is close to the optimal one, reducing the detour of data packets, reducing network overhead, and improving transmission efficiency.

[0096] In one embodiment, the data packet includes an IPv6 header, an entity identifier header, and data. The entity identifier header is an IPv6 extended header that contains the target identifier of the network entity.

[0097] Table 2 Data Packet Format

[0098] IPv6 header ID header upper-level header data

[0099] Table 2 shows the packet format. As shown in Table 2, a packet consists of an IPv6 header, an ID header, an upper-layer header, and data. The IPv6 header is for backward compatibility with current IP networks. The ID header is an IPv6 extended header that contains the destination identifier of the network entity. This allows the actual location of the network entity to be determined by rebinding the immutable destination identifier with a variable and routable IP address.

[0100] Figure 7 A flowchart illustrating another holographic communication mobility management method according to an embodiment of this disclosure is shown. Figure 7As shown, in one embodiment, this disclosure also provides a holographic communication mobility management method applied to an intermediate network node. The method mainly includes the following steps:

[0101] S702. In response to the intermediate network node obtaining the data packet of the network entity, the target identifier of the network entity is matched in the entity identifier-location mapping table corresponding to the intermediate network node. The entity identifier-location mapping table is used to represent the mapping relationship between the target network identifier and the target network address of the network entity stored by the intermediate network node.

[0102] In one embodiment, the source network node routes data packets of a network entity through multiple intermediate network nodes to that network entity. Figure 3 In this process, the source network node routes the data packet to the network entity MN through R4-R3-R2-R1, where R1 to R4 are four intermediate nodes.

[0103] It should be noted that each intermediate network node maintains and updates an entity identifier-location mapping table. The entries in the entity identifier-location mapping tables of different intermediate network nodes can be the same or different. However, the value of the same entry is the same in different network nodes.

[0104] An entity identifier-location mapping table represents the mapping relationship between the target identifier of a network entity and the target network address.

[0105] S704. If a target identifier of a network entity is matched, determine the target network address corresponding to the target identifier, modify the target network address in the network address field to the destination network address of the network entity's data packet, and forward the network entity's data packet according to the target network address.

[0106] When a data packet from a network entity flows through an intermediate network node, the intermediate network node matches the destination identifier of the network entity corresponding to the data packet in the entity identifier-location mapping table. When a table entry containing the destination identifier is matched, the data packet undergoes late binding, which modifies the destination network address of the data packet to the destination network address (new IP address) in the network address field of that table entry, and then forwards the packet according to the destination network address.

[0107] In one embodiment, the method further includes: if no target identifier of the network entity is matched, forwarding the network entity's data packet according to the routing table.

[0108] When no table entry corresponding to the target identifier can be found, it indicates that the network entity has not moved, and the data packet will be forwarded directly according to the IP routing table.

[0109] The routing table is stored in the network node. The routing table includes the destination address, mask, and next information, which guides the selection of the path for data packets from the source address to the destination address.

[0110] It should be noted that each entry in the entity identifier-location mapping table of each intermediate network node has a timestamp field. When a data packet flows through an intermediate network node, if the entry in the entity identifier-location mapping table matches, the timestamp field of the entry is updated to the current system time. If the timestamp field of a certain entry has not been updated for a long time, the intermediate network node determines that the network entity corresponding to the target identifier in that entry is in an idle state, has not established a session, or has left the nearby network for a long time. The intermediate network node will then delete the less frequently used entry.

[0111] In this embodiment, in response to receiving a data packet from a network entity, an intermediate network node matches the target identifier of the network entity in the entity identifier-location mapping table corresponding to the intermediate network node. The entity identifier-location mapping table is used to represent the mapping relationship between the target network identifier and the target network address of the network entity stored by the intermediate network node. If a target identifier of the network entity is matched, the target network address corresponding to the target identifier is determined, and the target network address in the network address field is modified to the destination network address of the data packet of the network entity. The data packet of the network entity is forwarded according to the target network address. This disclosure records the latest mapping relationship between the identifier and the network address of the network entity through the entity identifier-location mapping table. The network node dynamically rebinds the data packet forwarded to the moving network entity with the new network address according to the entity identifier-location mapping table, providing a more flexible and scalable holographic communication mobile management method. It can not only effectively cope with the increasing mobile demand, but also significantly improve the overall performance of holographic communication applications.

[0112] In one embodiment, the method further includes: receiving a mobility notification message propagated through a first forwarding path, the mobility notification message being generated based on an updated entity identifier-location mapping table of an edge network node, the entity identifier-location mapping table of the edge network node being used to characterize the mapping relationship between the target identifier and the target network address of the moved network entity, the first forwarding path being a path with the transmission direction opposite to that of a second forwarding path, the second forwarding path being a path that routes data packets from the source network node to the point before the network entity moved; if the intermediate network node is not the terminating network node, updating the entity identifier-location mapping table of the intermediate network node according to the mobility notification message, and propagating the mobility notification message through the first forwarding path until reaching the terminating network node; if the intermediate network node is the terminating network node, updating the entity identifier-location mapping table of the terminating network node according to the mobility notification message.

[0113] In one embodiment, propagating a mobile notification message through a first forwarding path includes: querying an ingress port table to obtain the ingress port of the network entity's data packets flowing through the intermediate network node; and forwarding the mobile notification message through the ingress port of the intermediate network node via the network entity's data packets.

[0114] In one embodiment, the mobility notification message propagates along the reverse forwarding path of the data packet (i.e., the first forwarding path). Network nodes can use an Ingress Port Table (IPT) to guide the propagation of the mobility notification message. The IPT records the port through which data packets enter the network node. Intermediate network nodes obtain the ingress port of the data packet by querying the IPT and use that ingress port as the egress port for the mobility notification message, forwarding the message accordingly.

[0115] In this embodiment of the disclosure, the most intuitive way to select the reverse next hop is to leave "breadcrumbs" at each intermediate network node during the packet forwarding process to prepare for the propagation of mobile notification messages.

[0116] In one embodiment, the terminating network node is the next network node after the fork node of the second and third forwarding paths, where the third forwarding path is the path from the source network node to the network entity after the data packet has moved; the next network node after the fork node is the network node after the fork node along the transmission direction of the first forwarding path.

[0117] In one embodiment, the mobility notification message carries the initial network address and the destination network address of the network entity, where the initial network address is the network address of the network entity before its movement, and the destination network address is the network address of the network entity after its movement. After receiving the mobility notification message propagated through the first forwarding path, the method further includes: using the initial network address and the destination network address of the network entity to look up a routing table to obtain the outgoing port corresponding to the initial network address and the outgoing port corresponding to the destination network address; if the outgoing port of the destination network address is the same as the outgoing port of the initial network address, then the intermediate network node is determined as the terminating network node, and the propagation of the mobility notification message is stopped; if the outgoing port of the destination network address is different from the outgoing port of the initial network address, then the incoming port table or the routing table is queried, and the obtained port is used to forward the mobility notification message.

[0118] The routing table is stored in the network node. The routing table includes the destination address, mask, and next information, which guides the selection of the path for data packets from the source address to the destination address.

[0119] In this embodiment of the disclosure, by selecting the next node after the fork node of the old and new data packet paths as the propagation termination point, the data packet forwarding path is made closer to the optimal one, and the signaling overhead is reduced.

[0120] This disclosure provides a novel communication mobility management method based on the backplane top. Compared with the centralized management method, the distributed architecture has lower heat, higher reliability and better resource utilization. It can be widely used in a variety of network environments and is not limited by specific topologies. It is one of the important directions for the future development of holographic communication networks.

[0121] Based on the same inventive concept, this disclosure also provides a holographic communication mobility management device, as shown in the following embodiments. Since the principle by which this device embodiment solves the problem is similar to that of the above-described method embodiments, the implementation of this device embodiment can refer to the implementation of the above-described method embodiments, and repeated details will not be elaborated further.

[0122] Figure 8 This diagram illustrates the structure of a holographic communication mobility management device according to an embodiment of the present disclosure. Figure 8 As shown, this holographic communication mobility management device is applied to an edge network node. The device includes a signaling receiving module 810, an address acquisition module 820, a first update module 830, and a rebinding module 840, wherein:

[0123] The signaling receiving module 810 is used to receive mobility signaling sent by the initial access point, wherein the initial access point is the access point accessed by the network entity before it moves, and the mobility signaling carries the target identifier of the network entity.

[0124] Address acquisition module 820 is used to query the target identifier of the network entity from the name resolution system and obtain the target network address corresponding to the target identifier of the network entity, wherein the target network address is the network address of the network entity after it has moved.

[0125] The first update module 830 is used to update the entity identifier-location mapping table of the edge network node according to the mapping relationship between the target identifier of the network entity and the target network address;

[0126] The rebinding module 840 is used to rebind data packets forwarded to the network entity based on the entity identifier-location mapping table.

[0127] In one embodiment, in the entity identifier-location mapping table, one network entity corresponds to one table entry, and one table entry includes the mapping relationship between the network entity's entity identifier field, network address field, and timestamp field. The first update module 830 is used to create a table entry corresponding to the network entity in the entity identifier-location mapping table before querying the target identifier of the network entity from the name resolution system to obtain the target network address corresponding to the target identifier of the network entity. The first update module 830 configures the entity identifier field of the table entry to the target identifier of the network entity, configures the timestamp field of the table entry to the current system time when the table entry is created, and configures the network address field of the table entry to the default initial value. After querying the target identifier of the network entity from the name resolution system to obtain the target network address corresponding to the target identifier of the network entity, the first update module 830 configures the network address field of the table entry to the target network address instead of the default initial value.

[0128] In one embodiment, the first update module is further configured to delete an entry from the entity identifier-location mapping table if an entry in the entity identifier-location mapping table does not match within a preset time period.

[0129] In one embodiment, the apparatus further includes a message sending module (not shown in the figures), which generates a mobility notification message based on the updated entity identifier-location mapping table of the edge network nodes, and propagates the mobility notification message through a first forwarding path to each intermediate network node on the first forwarding path, up to the terminating network node, so that each intermediate network node and the terminating network node update the entity identifier-location mapping table of the corresponding node according to the target identifier and target network address of the network entity. The first forwarding path is a path with the transmission direction opposite to that of the second forwarding path, and the second forwarding path is a path from the source network node to the path before the network entity moves.

[0130] In one embodiment, the terminating network node is the next network node after the fork node of the second and third forwarding paths, where the third forwarding path is the path from the source network node to the network entity after the data packet has moved; the next network node after the fork node is the network node after the fork node along the transmission direction of the first forwarding path.

[0131] In one embodiment, the data packet includes an IPv6 header, an entity identifier header, and data. The entity identifier header is an IPv6 extended header that contains the target identifier of the network entity.

[0132] In this embodiment, the edge network node receives a mobility signaling message sent by an initial access point (the access point the network entity accessed before its movement). The initial access point carries the target identifier of the network entity. The node queries the name resolution system to obtain the target network address corresponding to the target identifier of the network entity. The target network address is the network address after the network entity's movement. Based on the mapping relationship between the target identifier and the target network address, the edge network node updates its entity identifier-location mapping table. Based on the entity identifier-location mapping table, the data packets forwarded to the network entity are re-bound. This disclosure records the latest mapping relationship between the network entity's identifier and network address through the entity identifier-location mapping table. The network node dynamically re-binds the data packets forwarded to the moving network entity with the new network address according to the entity identifier-location mapping table. This provides a more flexible and scalable holographic communication mobility management method that can effectively cope with the increasing mobility demands and significantly improve the overall performance of holographic communication applications.

[0133] Figure 9 This illustration shows a schematic diagram of another holographic communication mobility management device structure in an embodiment of this disclosure, such as... Figure 9 As shown, this holographic communication mobility management device is applied to an intermediate network node. The device includes an identifier matching module 910 and an address bonding module 920, wherein:

[0134] The identifier matching module 910 is used to match the target identifier of the network entity in the entity identifier-location mapping table corresponding to the intermediate network node in response to the data packet of the network entity obtained by the intermediate network node. The entity identifier-location mapping table is used to represent the mapping relationship between the target network identifier and the target network address of the network entity stored by the intermediate network node.

[0135] The address binding module 920 is used to determine the target network address corresponding to the target identifier if a target identifier of a network entity is matched, modify the target network address in the network address field to the destination network address of the data packet of the network entity, and forward the data packet of the network entity according to the target network address.

[0136] In one embodiment, the address binding module 920 is used to forward the network entity's data packets according to the routing table if no target identifier of the network entity is matched.

[0137] In one embodiment, the apparatus further includes a second update module (not shown in the figures), which receives a mobility notification message propagated through a first forwarding path. The mobility notification message is generated based on an updated entity identifier-location mapping table of the edge network node. The entity identifier-location mapping table of the edge network node is used to characterize the mapping relationship between the target identifier and the target network address of the moved network entity. The first forwarding path is a path with the transmission direction opposite to that of the second forwarding path, which is a path that routes data packets from the source network node to the point before the network entity moves. If the intermediate network node is not the terminating network node, the entity identifier-location mapping table of the intermediate network node is updated according to the mobility notification message, and the mobility notification message is propagated through the first forwarding path until it reaches the terminating network node. If the intermediate network node is the terminating network node, the entity identifier-location mapping table of the terminating network node is updated according to the mobility notification message.

[0138] In one embodiment, the apparatus further includes a notification transceiver module (not shown in the figures), which is used to query an ingress port table to obtain the ingress ports through which data packets of network entities flow via intermediate network nodes; and to forward mobile notification messages through the ingress ports of intermediate network nodes via the data packets of network entities.

[0139] In one embodiment, the terminating network node is the next network node after the fork node of the second and third forwarding paths, where the third forwarding path is the path from the source network node to the network entity after the data packet has moved; the next network node after the fork node is the network node after the fork node along the transmission direction of the first forwarding path.

[0140] In one embodiment, the mobile notification message carries the initial network address and the destination network address of the network entity. The initial network address is the network address of the network entity before it moves, and the destination network address is the network address of the network entity after it moves. The notification transceiver module is used to, after receiving the mobile notification message propagated through the first forwarding path, use the initial network address and the destination network address of the network entity to look up the routing table and obtain the outgoing port corresponding to the initial network address and the outgoing port corresponding to the destination network address. If the outgoing port of the destination network address is the same as the outgoing port of the initial network address, the intermediate network node is determined as the terminating network node, and the propagation of the mobile notification message is stopped. If the outgoing port of the destination network address is different from the outgoing port of the initial network address, the ingoing port table or the routing table is queried, and the obtained port is used to forward the mobile notification message.

[0141] In this embodiment, in response to receiving a data packet from a network entity, an intermediate network node matches the target identifier of the network entity in the entity identifier-location mapping table corresponding to the intermediate network node. The entity identifier-location mapping table is used to represent the mapping relationship between the target network identifier and the target network address of the network entity stored by the intermediate network node. If a target identifier of the network entity is matched, the target network address corresponding to the target identifier is determined, and the target network address in the network address field is modified to the destination network address of the data packet of the network entity. The data packet of the network entity is forwarded according to the target network address. This disclosure records the latest mapping relationship between the identifier and the network address of the network entity through the entity identifier-location mapping table. The network node dynamically rebinds the data packet forwarded to the moving network entity with the new network address according to the entity identifier-location mapping table, providing a more flexible and scalable holographic communication mobile management method. It can not only effectively cope with the increasing mobile demand, but also significantly improve the overall performance of holographic communication applications.

[0142] like Figure 3 As shown, in one embodiment, this disclosure also provides a holographic communication mobile management system, including a name resolution system, an edge network node, and an intermediate network node, wherein: the name resolution system is used to store the target identifier and corresponding target network address of the network entity before and after its movement; the edge network entity is used to receive mobile signaling sent by an initial access point, the initial access point being the access point accessed before the network entity moves, and the mobile signaling carrying the target identifier of the network entity; the target identifier of the network entity is queried from the name resolution system to obtain the target network address corresponding to the target identifier of the network entity, the target network address being the network address of the network entity after its movement; and the mapping relationship between the target identifier and the target network address of the network entity is updated according to the mapping relationship between the target identifier and the target network address of the network entity. The system uses an entity identifier-location mapping table for network nodes. Based on this table, data packets are re-bound and forwarded to the network entity. Intermediate network nodes, in response to receiving data packets from network entities, match the target identifier of the network entity in their corresponding entity identifier-location mapping table. This table represents the mapping relationship between the target network identifier and the target network address of the network entity stored in the intermediate network node. If a target identifier is matched, the corresponding target network address is determined, and the target network address in the network address field is modified to the destination network address of the network entity's data packets. The data packets of the network entity are then forwarded based on the target network address.

[0143] Those skilled in the art will understand that various aspects of this disclosure can be implemented as a system, method, or program product. Therefore, various aspects of this disclosure can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, collectively referred to herein as a "circuit," "module," or "system."

[0144] The following reference Figure 10 To describe an electronic device 1000 according to such an embodiment of the present disclosure. Figure 10 The electronic device 1000 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.

[0145] like Figure 10 As shown, the electronic device 1000 is manifested in the form of a general-purpose computing device. The components of the electronic device 1000 may include, but are not limited to: at least one processing unit 1010, at least one storage unit 1020, and a bus 1030 connecting different system components (including storage unit 1020 and processing unit 1010).

[0146] The storage unit stores program code, which can be executed by the processing unit 1010, causing the processing unit 1010 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of this disclosure. For example, the processing unit 1010 can perform, as follows: Figure 2 The method embodiment in the text includes the following steps: The edge network node receives a mobility signaling sent by an initial access point, which is the access point accessed before the network entity moves. The mobility signaling carries the target identifier of the network entity. The target identifier of the network entity is queried from the name resolution system to obtain the target network address corresponding to the target identifier of the network entity. The target network address is the network address of the network entity after its move. The entity identifier-location mapping table of the edge network node is updated according to the mapping relationship between the target identifier and the target network address of the network entity. Based on the entity identifier-location mapping table, the data packets forwarded to the network entity are re-bound.

[0147] For example, the processing unit 1010 may also perform the following: Figure 7The method embodiment in the text includes the following steps: In response to the intermediate network node obtaining the data packet of the network entity, the intermediate network node matches the target identifier of the network entity in the entity identifier-location mapping table corresponding to the intermediate network node. The entity identifier-location mapping table is used to represent the mapping relationship between the target network identifier and the target network address of the network entity stored by the intermediate network node. If the target identifier of the network entity is matched, the target network address corresponding to the target identifier is determined, the target network address in the network address field is modified to the destination network address of the data packet of the network entity, and the data packet of the network entity is forwarded according to the target network address.

[0148] Storage unit 1020 may include readable media in the form of volatile storage units, such as random access memory (RAM) 10201 and / or cache memory 10202, and may further include read-only memory (ROM) 10203.

[0149] Storage unit 1020 may also include a program / utility 10204 having a set (at least one) program module 10205, such program module 10205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0150] Bus 1030 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the multiple bus structures.

[0151] Electronic device 1000 can also communicate with one or more external devices 1040 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with the electronic device 1000, and / or with any device that enables the electronic device 1000 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 1050. Furthermore, electronic device 1000 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 1060. Figure 10 As shown, network adapter 1060 communicates with other modules of electronic device 1000 via bus 1030. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with electronic device 1000, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0152] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0153] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, which may be a readable signal medium or a readable storage medium. In exemplary embodiments of this disclosure, a computer program product is also provided, comprising a computer program or computer instructions, which are loaded and executed by a processor to cause a computer to implement the steps of the methods disclosed in the above embodiments.

[0154] In this disclosure, a computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of transmitting, propagating, or transmitting a program for use by or in connection with an instruction execution system, apparatus, or device.

[0155] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0156] Furthermore, although the steps of the method in this disclosure are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or a step may be broken down into multiple steps.

[0157] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the appended claims.

Claims

1. A holographic communication mobility management method, applied to edge network nodes, characterized in that, The method includes: Receive mobility signaling sent by an initial access point, wherein the initial access point is the access point accessed by the network entity before it moves, and the mobility signaling carries the target identifier of the network entity; The target identifier of the network entity is queried from the name resolution system, and the target network address corresponding to the target identifier of the network entity is obtained. The target network address is the network address of the network entity after it has moved. Update the entity identifier-location mapping table of the edge network node according to the mapping relationship between the target identifier of the network entity and the target network address; Based on the entity identifier-location mapping table, rebind and forward data packets to the network entity; A mobility notification message is generated based on the updated entity identifier-location mapping table of the edge network node. This message is then propagated through a first forwarding path to each intermediate network node along that path, up to the terminating network node. This allows each intermediate and terminating network node to update their respective entity identifier-location mapping tables based on the target identifier and target network address of the network entity. The first forwarding path is the path with the transmission direction opposite to that of the second forwarding path. The second forwarding path routes data packets from the source network node to the point before the network entity moves. The terminating network node is the next network node after the branch node of the second and third forwarding paths. The third forwarding path routes data packets from the source network node to the point after the network entity moves. The next network node after the branch node is the network node following the branch node along the transmission direction of the first forwarding path.

2. The holographic communication mobility management method according to claim 1, characterized in that, In the entity identifier-location mapping table, one network entity corresponds to one table entry, and one table entry includes the mapping relationship between the entity identifier field, network address field, and timestamp field of the network entity; Before querying the target identifier of the network entity from the name resolution system to obtain the target network address corresponding to the target identifier of the network entity, the method further includes: Create a table entry corresponding to the network entity in the entity identifier-location mapping table, configure the entity identifier field of the table entry as the target identifier of the network entity, configure the timestamp field of the table entry as the current system time when the table entry is created, and configure the network address field of the table entry as the default initial value. After querying the target identifier of the network entity from the name resolution system and obtaining the target network address corresponding to the target identifier of the network entity, the method further includes: Modify the network address field of the table entry from the default initial value to the target network address.

3. The holographic communication mobility management method according to claim 2, characterized in that, The method further includes: If an entry in the entity identifier-location mapping table does not match within a preset time period, then that entry is deleted from the entity identifier-location mapping table.

4. The holographic communication mobility management method according to claim 1, characterized in that, The data packet includes an IPv6 header, an entity identifier header, and data. The entity identifier header is an IPv6 extended header and contains the target identifier of the network entity.

5. A holographic communication mobility management method, applied to intermediate network nodes, characterized in that, The method includes: In response to the intermediate network node obtaining a data packet of a network entity, the target identifier of the network entity is matched in the entity identifier-location mapping table corresponding to the intermediate network node. The entity identifier-location mapping table is used to characterize the mapping relationship between the target network identifier and the target network address of the network entity stored by the intermediate network node. If a target identifier of the network entity is matched, the target network address corresponding to the target identifier is determined, the target network address in the network address field is modified to the destination network address of the data packet of the network entity, and the data packet of the network entity is forwarded according to the target network address; Receive a mobility notification message propagated through a first forwarding path. The mobility notification message is generated based on an updated entity identifier-location mapping table of the edge network node. The entity identifier-location mapping table of the edge network node is used to characterize the mapping relationship between the target identifier of the moved network entity and the target network address. The first forwarding path is a path with the transmission direction opposite to that of the second forwarding path. The second forwarding path is a path that routes data packets from the source network node to the path before the network entity moved. If the intermediate network node is not the terminating network node, then the entity identifier-location mapping table of the intermediate network node is updated according to the mobility notification message, and the mobility notification message is propagated through the first forwarding path until it reaches the terminating network node. The terminating network node is the next network node after the fork node of the second and third forwarding paths. The third forwarding path is the path that routes the data packet from the source network node to the network entity after it has moved. The next network node after the fork node is the network node after the fork node along the transmission direction of the first forwarding path. If the intermediate network node is a terminating network node, then the entity identifier-location mapping table of the terminating network node is updated according to the mobile notification message.

6. The holographic communication mobility management method according to claim 5, characterized in that, The method further includes: If no target identifier of the network entity is matched, the data packet of the network entity is forwarded according to the routing table.

7. The holographic communication mobility management method according to claim 5, characterized in that, The propagation of the mobile notification message through the first forwarding path includes: Query the ingress port table to obtain the ingress ports through which the data packets of the network entity flow through the intermediate network nodes; The data packets from the network entity are forwarded to the mobile notification message through the ingress port of the intermediate network node.

8. The holographic communication mobility management method according to claim 5, characterized in that, The mobile notification message carries the initial network address and the target network address of the network entity. The initial network address is the network address of the network entity before it moves, and the target network address is the network address of the network entity after it moves. The method further includes, after receiving the mobile notification message propagated through the first forwarding path: Use the initial network address and the target network address of the network entity to look up the routing table and obtain the outgoing port corresponding to the initial network address and the outgoing port corresponding to the target network address; If the outgoing port of the target network address is the same as the outgoing port of the initial network address, then the intermediate network node is determined as the termination network node, and the propagation of the mobile notification message is stopped. If the outgoing port of the target network address is different from the outgoing port of the initial network address, then the incoming port table or routing table is queried, and the port obtained from the query is used to forward the mobile notification message.

9. A holographic communication mobility management device, applied to an edge network node, characterized in that, The device includes: The signaling receiving module is used to receive mobility signaling sent by the initial access point, which is the access point that the network entity accesses before moving, and the mobility signaling carries the target identifier of the network entity. The address acquisition module is used to query the target identifier of the network entity from the name resolution system and obtain the target network address corresponding to the target identifier of the network entity. The target network address is the network address of the network entity after it has moved. The first update module is used to update the entity identifier-location mapping table of the edge network node according to the mapping relationship between the target identifier of the network entity and the target network address; The rebinding module is used to rebind data packets forwarded to the network entity based on the entity identifier-location mapping table; The message sending module is configured to generate a mobility notification message based on the updated entity identifier-location mapping table of the edge network node, and propagate the mobility notification message to each intermediate network node on the first forwarding path through the first forwarding path, up to the terminating network node, so that each intermediate network node and the terminating network node update the entity identifier-location mapping table of the corresponding node according to the target identifier and the target network address of the network entity. The first forwarding path is a path with the transmission direction opposite to that of the second forwarding path. The second forwarding path is a path that routes data packets from the source network node to the point before the network entity moves. The terminating network node is the next network node after the fork node of the second and third forwarding paths. The third forwarding path is a path that routes data packets from the source network node to the point after the network entity moves. The next network node after the fork node is a network node following the fork node along the transmission direction of the first forwarding path.

10. A holographic communication mobility management device, applied to an intermediate network node, characterized in that, The device includes: The identifier matching module is used to match the target identifier of the network entity in the entity identifier-location mapping table corresponding to the intermediate network node in response to the data packet of the network entity obtained by the intermediate network node. The address binding module is used to determine the target network address corresponding to the target identifier if the target identifier of the network entity is matched, modify the target network address in the network address field to the destination network address of the data packet of the network entity, and forward the data packet of the network entity according to the target network address; The second update module is used to receive a mobility notification message propagated through the first forwarding path. The mobility notification message is generated based on the updated entity identifier-location mapping table of the edge network node. The entity identifier-location mapping table of the edge network node is used to represent the mapping relationship between the target identifier and the target network address of the moved network entity. The first forwarding path is a path with the opposite transmission direction to the second forwarding path. The second forwarding path is the path from the source network node to the point before the network entity moves. If the intermediate network node is not the terminating network node, the entity identifier-location mapping table of the intermediate network node is updated according to the mobility notification message, and the mobility notification message is propagated through the first forwarding path until it reaches the terminating network node. If the intermediate network node is the terminating network node, the entity identifier-location mapping table of the terminating network node is updated according to the mobility notification message. The terminating network node is the next network node after the fork node of the second and third forwarding paths. The third forwarding path is the path from the source network node to the point after the network entity moves. The next network node after the fork node is the network node after the fork node along the transmission direction of the first forwarding path.

11. A holographic communication mobile management system, characterized in that, This includes a name resolution system, edge network nodes, and intermediate network nodes, among which: The name resolution system is used to store the target identifiers and corresponding target network addresses of network entities before and after their movement; The edge network node is configured to receive mobility signaling sent by an initial access point (the access point the network entity accessed before its movement), the mobility signaling carrying the target identifier of the network entity; query the target identifier of the network entity from the name resolution system to obtain the target network address corresponding to the target identifier of the network entity, the target network address being the network address of the network entity after its movement; update the entity identifier-location mapping table of the edge network node according to the mapping relationship between the target identifier and the target network address of the network entity; and rebind data packets forwarded to the network entity based on the entity identifier-location mapping table, according to the updated entity identifier-location mapping table of the edge network node. An identifier-location mapping table generates a mobility notification message, which is then propagated through a first forwarding path to each intermediate network node on that path, up to the terminating network node. The first forwarding path is the path with the transmission direction opposite to that of the second forwarding path. The second forwarding path routes data packets from the source network node to the point before the network entity moves. The terminating network node is the next network node after the fork node of the second and third forwarding paths. The third forwarding path routes data packets from the source network node to the point after the network entity moves. The next network node after the fork node is the network node following the fork node along the transmission direction of the first forwarding path. The intermediate network node is configured to, in response to the intermediate network node obtaining a data packet of a network entity, match the target identifier of the network entity in the entity identifier-location mapping table corresponding to the intermediate network node; if a target identifier of the network entity is matched, determine the target network address corresponding to the target identifier, modify the target network address in the network address field to the destination network address of the data packet of the network entity, and forward the data packet of the network entity according to the target network address.

12. An electronic device, characterized in that, include: A processor and a memory, wherein the memory is used to store executable instructions of the processor; The processor is configured to execute the holographic communication mobility management method according to any one of claims 1 to 4, or to execute the holographic communication mobility management method according to any one of claims 5 to 8, by executing the executable instructions.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the holographic communication mobility management method according to any one of claims 1 to 4, or the holographic communication mobility management method according to any one of claims 5 to 8.

14. A computer program product having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the holographic communication mobility management method according to any one of claims 1 to 4, or the holographic communication mobility management method according to any one of claims 5 to 8.

Images