Ip address acquisition method, apparatus, and related device

Abstract

The application provides an IP address acquisition method and device and related equipment, and relates to the technical field of wireless communication. The IP address acquisition method is applied to a first communication node. The method comprises the following steps: receiving a configuration update request message sent by a second communication node, wherein the configuration update request message is used for requesting to update an IP address of a target device; and sending a configuration update response message to the second communication node according to the configuration update request message, wherein the configuration update response message comprises an updated IP address of the target device. In this way, the IP address of the target device can be updated through the configuration update request message, so that the accuracy of the determined IP address of the target device is improved.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to an IP address acquisition method, apparatus, and related equipment. Background Technology

[0002] With the continuous development of wireless communication technology, communication has become increasingly important in people's lives. Currently, target devices can access servers via the network, but when the target device is powered off and restarted, its Internet Protocol (IP) address usually changes. Therefore, the accuracy of the currently determined IP address of the target device is relatively poor. Summary of the Invention

[0003] This application provides an IP address acquisition method, apparatus, and related equipment to solve the problem of poor accuracy of the IP address of the currently determined target device.

[0004] To solve the above problems, this application is implemented as follows:

[0005] In a first aspect, embodiments of this application provide an IP address acquisition method, applied to a first communication node, the method comprising:

[0006] Receive a configuration update request message sent by the second communication node, the configuration update request message being used to request an update of the Internet Protocol (IP) address of the target device;

[0007] According to the configuration update request message, a configuration update response message is sent to the second communication node, the configuration update response message including the updated IP address of the target device.

[0008] Secondly, embodiments of this application provide an IP address acquisition method, applied to a second communication node, the method comprising:

[0009] Send a configuration update request message to the first communication node, the configuration update request message being used to request the first communication node to update the Internet Protocol IP address of the target device;

[0010] The system receives a configuration update response message sent by the first communication node, the configuration update response message including the updated IP address of the target device.

[0011] Thirdly, embodiments of this application also provide an IP address acquisition device, applied to a first communication node, the device comprising:

[0012] The first receiving module is used to receive a configuration update request message sent by the second communication node, wherein the configuration update request message is used to request an update of the Internet Protocol IP address of the target device;

[0013] The first sending module is configured to send a configuration update response message to the second communication node according to the configuration update request message, wherein the configuration update response message includes the updated IP address of the target device.

[0014] Fourthly, embodiments of this application also provide an IP address acquisition device, applied to a second communication node, the device comprising:

[0015] The second sending module is used to send a configuration update request message to the first communication node, the configuration update request message being used to request the first communication node to update the Internet Protocol IP address of the target device;

[0016] The second receiving module is used to receive a configuration update response message sent by the first communication node, wherein the configuration update response message includes the updated IP address of the target device.

[0017] Fifthly, embodiments of this application also provide an electronic device, including: a memory, a processor, and a program stored in the memory and executable on the processor; the processor is configured to read the program in the memory to implement the steps in the method described in the first aspect above, or to read the program in the memory to implement the steps in the method described in the second aspect above.

[0018] In a sixth aspect, embodiments of this application also provide a readable storage medium for storing a program, which, when executed by a processor, implements the steps of the method described in the first aspect above, or implements the steps of the method described in the second aspect above.

[0019] In a seventh aspect, embodiments of this application also provide a computer program product, including computer instructions, which, when executed by a processor, implement the steps in the methods described in the first or second aspect above.

[0020] In this embodiment of the application, when the first communication node receives a configuration update request message sent by the second communication node, since the configuration update request message is used to request an update of the target device's IP address, the target device's IP address can be updated according to the configuration update request message, and the updated IP address of the target device can be sent to the second communication node along with the configuration update response message. In this way, the IP address of the target device can be updated through the configuration update request message, thereby improving the accuracy of the determined IP address of the target device. Attached Figure Description

[0021] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 This is a schematic diagram of the structure of a network system to which the embodiments of this application can be applied;

[0023] Figure 2 This is one of the flowcharts of the IP address acquisition method provided in the embodiments of this application;

[0024] Figure 3 This is a representation of the mapping information provided in the embodiments of this application;

[0025] Figure 4 This is a schematic diagram of ffmpeg commands provided in an embodiment of this application;

[0026] Figure 5 This is a schematic diagram of the IP address detection process for the target device provided in an embodiment of this application;

[0027] Figure 6 This is a schematic diagram of the structure of a TCP packet provided in an embodiment of this application;

[0028] Figure 7 This is a schematic diagram of the structure of the data portion of UDP provided in an embodiment of this application;

[0029] Figure 8 This is a schematic diagram of the message structure of the configuration update request message provided in the embodiments of this application;

[0030] Figure 9 This is a schematic diagram of the message structure of the configuration update response message provided in the embodiments of this application;

[0031] Figure 10 This is a schematic diagram of the message structure of the initial configuration transmission message provided in the embodiments of this application;

[0032] Figure 11 This is the second flowchart of the IP address acquisition method provided in the embodiments of this application;

[0033] Figure 12 This is the third flowchart of the IP address acquisition method provided in the embodiments of this application;

[0034] Figure 13 This is one of the structural schematic diagrams of the IP address acquisition device provided in the embodiments of this application;

[0035] Figure 14This is a second schematic diagram of the structure of the IP address acquisition device provided in the embodiments of this application;

[0036] Figure 15 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0037] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0038] The terms "first," "second," etc., used in the embodiments of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products, or devices. Additionally, the use of "and / or" in this application indicates at least one of the connected objects, such as A and / or B and / or C, representing seven possibilities: including A alone, B alone, C alone, and the presence of both A and B, both B and C, both A and C, and the presence of A, B, and C.

[0039] Please see Figure 1 , Figure 1 This is a structural diagram of a network system to which the embodiments of this application can be applied, such as... Figure 1 As shown, it includes a first communication node 11, a second communication node 12, and a third communication node 13.

[0040] The first communication node 11 and the second communication node 12 can communicate with each other, the first communication node 11 and the third communication node 13 can communicate with each other, and the second communication node 12 and the third communication node 13 can also communicate with each other.

[0041] Optionally, the first communication node 11 can be a base station, and the second communication node 12 and the third communication node 13 can both be servers. The functions of the servers corresponding to the second communication node 12 and the third communication node 13 can be different. For example, the second communication node 12 can be called a traffic distribution server or a local traffic distribution server, and the third communication node 13 can be called a heartbeat server.

[0042] The specific type of target device is not limited here. Optionally, the target device may include Customer Premise Equipment (CPE) or electronic devices. Electronic devices may include mobile phones, tablet computers, laptop computers, personal digital assistants (PDAs), mobile internet devices (MIDs), wearable devices, or in-vehicle devices, etc. Target components in the target device may include at least one of the following: cameras, LiDAR, etc.

[0043] The IP address acquisition method provided in the embodiments of this application will be described in detail below.

[0044] See Figure 2 , Figure 2 This is a flowchart illustrating the IP address acquisition method provided in the embodiments of this application. Figure 2 The IP address acquisition method shown can be executed by the first communication node.

[0045] like Figure 2 As shown, the method for obtaining an IP address may include the following steps:

[0046] Step 201: Receive a configuration update request message sent by the second communication node. The configuration update request message is used to request an update of the IP address of the target device.

[0047] The first communication node can establish a connection with the target device based on the target device's IP address, and the first communication node can communicate with the target device based on the information transmission channel corresponding to the connection. Optionally, the first communication node can obtain information collected or stored on the target device based on the information transmission channel corresponding to the connection. For example, when the target device is a CPE, the first communication node can obtain image information collected by the camera mounted on the CPE.

[0048] When the target device is powered off and restarted, its IP address changes. At this time, the first communication node cannot continue to obtain information from the target device based on the previous IP address. Therefore, it needs to obtain the changed IP address of the target device to continue to establish a connection with the target device. Thus, the second communication node can send a configuration update request message to the first communication node to request the updated IP address of the target device.

[0049] Step 202: Send a configuration update response message to the second communication node according to the configuration update request message. The configuration update response message includes the updated IP address of the target device.

[0050] Upon receiving the configuration update request message, the first communication node can obtain or update the updated IP address of the target device and send the updated IP address of the target device along with the configuration update response message to the second communication node.

[0051] In this embodiment of the application, through steps 201 to 202, when the first communication node receives the configuration update request message sent by the second communication node, since the configuration update request message is used to request an update of the target device's IP address, the target device's IP address can be updated according to the configuration update request message, and the updated IP address of the target device is sent to the second communication node along with the configuration update response message. In this way, the IP address of the target device can be updated through the configuration update request message, thereby improving the accuracy of the determined IP address of the target device.

[0052] In addition, when the target device in this application embodiment is a terminal, the terminal does not need to integrate additional functions, is plug-and-play, avoids the problem of the dynamic domain name system (DNS) requiring terminal development permissions, and reduces the cost of using the terminal.

[0053] It should be noted that the specific method by which the first communication node obtains the updated IP address of the target device is not limited here. Optionally, the first communication node can directly obtain the updated IP address of the target device, and the updated IP address of the target device can be stored in a data table, which can be used to store the IP addresses of various devices.

[0054] As an optional implementation, sending a configuration update response message to the second communication node according to the configuration update request message includes:

[0055] Upon receiving the configuration update request message, the IP information of the uplink data packet is parsed;

[0056] Based on the IP information, the target data packet with the destination IP address being the first IP address is determined;

[0057] The updated IP address of the target device is determined based on the source IP address of the target data packet, and the configuration update response message is sent to the second communication node.

[0058] Optionally, the first IP address may include the address of the heartbeat server, or alternatively, the first IP address may also include the address of other servers, such as servers used to store communication information or media information.

[0059] It should be noted that, optionally, the aforementioned uplink data packet can be a heartbeat data packet, and the heartbeat data packet can also be called a heartbeat packet. That is, the aforementioned uplink data packet can be a data packet sent every preset period. The aforementioned uplink data packet can be sent by the target device every preset period, or the aforementioned uplink data packet can also be actively obtained by the first communication node. The specifics are not limited here.

[0060] Optionally, the aforementioned uplink data packet may refer to all uplink data packets obtained by the first communication node. Alternatively, the aforementioned uplink data packet may also refer to uplink data packets that meet preset conditions among all uplink data packets obtained by the first communication node. The aforementioned preset conditions may include: the C-RNTI associated with the corresponding uplink data packet is a new C-RNTI, that is, a C-RNTI that was not previously associated with a certain device information in the mapping information table in the following text. The aforementioned device information can be understood as the information of the target device, which may include at least one of the following: mapping port, IP address, and identifier.

[0061] The number of uplink data packets can be multiple. The IP information of each uplink data packet can be parsed, and the IP information can include the destination IP address of each uplink data packet. When the destination IP address of a certain uplink data packet is the address corresponding to the heartbeat server, the uplink data packet can be identified as the target data packet, and the source IP address of the target data packet can be identified as the updated IP address of the target device.

[0062] Optionally, the aforementioned IP information may include IP header information, which may also be referred to as the IP header.

[0063] It should be noted that the destination IP address can be understood as the IP address corresponding to the final destination transmission location of the target data packet, while the source IP address of the target data packet can be understood as the IP address corresponding to the source location.

[0064] In this embodiment of the application, the updated IP address of the target device can be determined based on the source IP address of the target data packet, thus making the accuracy of the determined updated IP address of the target device higher.

[0065] It should be noted that the specific method for determining the updated IP address of the target device based on the source IP address of the target data packet is not limited here. Optionally, the source IP address of the target data packet can be directly determined as the updated IP address of the target device; alternatively, the source IP address of the target data packet can be modified, and then the modified source IP address of the target data packet can be determined as the updated IP address of the target device.

[0066] As an optional implementation, before receiving the configuration update request message sent by the second communication node, the method further includes:

[0067] Receive the initial configuration transmission message sent by the second communication node;

[0068] The mapping information table of the target device is updated according to the initial configuration transmission message. The mapping information table includes: the mapping port corresponding to the target device, the IP address of the target device, and the Cell-Radio Network Temporary Identifier (C-RNTI) corresponding to the target device.

[0069] When the first communication node receives the initial configuration transmission message, if no mapping information table exists, it can first create a mapping information table and store the mapping port corresponding to the target device, the IP address of the target device, and the C-RNTI corresponding to the target device in the corresponding positions in the mapping information table.

[0070] When a mapping information table exists, only the information that is updated in the mapping information table can be updated. For example, the information stored in the location used to store the C-RNTI corresponding to the target device can be updated to the latest C-RNTI information.

[0071] For example, see Figure 3 As shown, Figure 3 This is a structural diagram of the mapping information table, and Figure 3 The target device shown can be a CPE, since the camera is mounted on the CPE. Figure 3 The camera mapping port shown can be understood as the mapping port corresponding to the target device, the CPE IP can be understood as the IP address of the target device, and the C-RNTI can be understood as the C-RNTI corresponding to the target device.

[0072] In this embodiment, upon receiving an initial configuration transmission message from the second communication node, the mapping information table of the target device can be updated based on the initial configuration transmission message, thereby improving the accuracy of the mapping information table update and avoiding erroneous updates. Furthermore, the mapping information table includes the mapping port corresponding to the target device, the IP address of the target device, and the C-RNTI corresponding to the target device, thus increasing the richness and diversity of the content included in the mapping information table.

[0073] For example, the steps for the first communication node to update the mapping information table can be described as follows:

[0074] 1. The initial configuration information of the CPE (i.e., the target device) is set in the local split server (i.e., the second communication node). After each manual adjustment, the updated information is transmitted to the base station (i.e., the first communication node) through the local split server.

[0075] 2. After receiving the initial configuration information transmission message (i.e., the initial configuration transmission message), the base station will update the terminal information table (i.e., the mapping information table) and add the corresponding C-RNTI.

[0076] 3. Upon successful stream acquisition (i.e., successful request from the second communication node to obtain information from the target device), the base station will begin recording the IP-C-RNTI (which can be a globally recognized User Equipment Identifier (UE ID)) key-value pair of the currently stream-acquiring CPE (i.e., the target device), and simultaneously record the C-RNTI of the currently connected CPE. A queue data structure can be used for recording, performing a storage operation every X seconds, following a first-in, first-out (FIFO) principle. The value of X is not limited here; for example, it can be 1.

[0077] 4. If the streaming operation is interrupted or fails (i.e., the second communication node fails to obtain information from the target device), the base station will begin recording the C-RNTI of newly entered connection CPEs (i.e., the target device) and unpack the destination IP addresses of each newly entered connection. If the destination IP address is the configuration server address (which can be understood as the first IP address, and the first IP address may include the address of the heartbeat server), the captured corresponding source IP address will be forwarded to the local splitter server to re-stream.

[0078] It should be noted that when there are multiple target devices, there is a problem that the IP addresses of the target devices are difficult to identify accurately. To solve this problem, the following implementation method is proposed:

[0079] As an optional implementation, the number of target devices is multiple, and the step of determining the destination IP address of the target data packet as the first IP address based on the IP information includes:

[0080] Based on the IP information, multiple target data packets with a destination IP address of the first IP address are determined;

[0081] Determining the updated IP address of the target device based on the source IP address of the target data packet includes:

[0082] Obtain the source IP address of each target data packet;

[0083] Send a port status detection request to each of the target devices, and determine the updated IP address of each target device based on the port connectivity detection result received from each of the target devices and the source IP address of each target data packet;

[0084] Alternatively, obtain parameter information for each target data packet, and determine the updated IP address of each target device based on the parameter information and the source IP address of each target data packet. The parameter information includes timestamp interval information or packet payload length information.

[0085] The method of sending a port status detection request to each target device and determining the updated IP address of each target device based on the port connectivity detection result received from each target device and the source IP address of each target data packet can be referred to as Method 1; while the method of obtaining parameter information of each target data packet and determining the updated IP address of each target device based on the parameter information and the source IP address of each target data packet, wherein the parameter information includes timestamp interval information or packet payload length information, can be referred to as Method 2.

[0086] It should be noted that the above method of determining the updated IP address of each target device based on the port connectivity detection result received from each target device and the source IP address of each target data packet can be understood as follows: if the port connectivity detection result indicates connectivity, the source IP address of the corresponding target data packet can be directly determined as the updated IP address of the target device; if the port connectivity detection result indicates disconnection, the updated IP address of the target device can be determined as not being the source IP address of the corresponding target data packet.

[0087] For example, in Method 1, the number of target devices can be two, and each target device can be a CPE. These two target devices can be represented as CPE1 and CPE2, respectively. Each target device can be connected to two target components, which can be cameras. Therefore, the two cameras connected to CPE1 are mapped to ports 551 and 552, respectively, while the two cameras connected to CPE2 are mapped to ports 553 and 554. To verify port connectivity, this implementation uses the ffmpeg tool or the telnet command tool for port status detection. ffmpeg commands can be found in [link to ffmpeg command documentation]. Figure 4 As shown, when using ffmpeg to perform port connectivity testing, if the return code is 0 after command execution, it indicates that the port connection is successful, and it can be inferred that IP address IP1 belongs to CPE1; conversely, if the return code is not 0, it indicates that the port connection has failed, and it can be inferred that IP address IP1 does not belong to CPE1. Additionally, a schematic diagram of the detection method 1 can be found in [reference needed]. Figure 5 As shown.

[0088] It should be noted that, optionally, the information transmitted between the target device and the first communication node can be streaming media information, and the streaming media transmission can adopt the Real Time Streaming Protocol (RTSP), whose Uniform Resource Locator (URL) format is rtsp: / / username:password@CPE_IP:camera mapping port / streaming / channels / 1.

[0089] Specifically, determining the updated IP address of each target device based on the parameter information and the source IP address of each target data packet can be understood as follows: based on the different parameter information, the source IP address of each target data packet can be accurately determined, and the source IP address corresponding to each target data packet can be determined as the updated IP address of each target device.

[0090] For example, in Method 2, different CPEs can be identified by recording the timestamp interval information or message payload length of the heartbeat packets. For instance, if the heartbeat packet sending period for CPE1 is set to 30 seconds and that for CPE2 to 40 seconds, analyzing the timestamp interval information can effectively distinguish the communication flows from these two CPEs, and accurately identify the IP address of the CPE based on the communication flow (i.e., determine the updated IP address of each target device based on the source IP address of each target data packet). The timestamp interval information can be understood as the interval period, and the message payload length can be understood as the length of the maximum message payload.

[0091] In this embodiment, when multiple target devices exist, the updated IP address of each target device can be determined according to the above method, thereby increasing the diversity and flexibility of the method for determining the updated IP address of the target device. Simultaneously, multiple CPEs can be distinguished by timestamp interval information or packet payload length information, and the mapping information table can be automatically maintained without manual binding, solving the problem of large-scale deployment management.

[0092] It should be noted that, optionally, when the first communication node communicates with the second communication node, for example, when the first communication node sends the updated IP address of the target device in the configuration update response message to the second communication node, they can communicate directly through Transmission Control Protocol (TCP) messages or User Datagram Protocol (UDP) messages, thereby bypassing the core network, reducing communication latency, and improving communication efficiency.

[0093] TCP is a connection-oriented, reliable, byte-stream-based transport layer communication protocol designed to adapt to and support layered protocol architectures for multiple network applications. In different but interconnected computer communication networks, paired processes within a host computer use TCP to achieve reliable communication services.

[0094] A TCP message segment is divided into a TCP header and a data portion, where the TCP header must conform to the TCP / IP protocol format specifications. For example... Figure 6 As shown, the TCP header consists of the following parts in sequence:

[0095] 1. 16-bit source port: The port number of the application on the sending host.

[0096] 2. 16-bit destination port: The port number of the application on the destination host.

[0097] 3. 32-bit TCP sequence number: Represents the number of the first byte of data sent in this segment.

[0098] 4. 4-bit TCP Data Offset: The data offset refers to the byte offset of the starting position of the data field relative to the beginning of the entire segment within a TCP segment. This parameter is used to determine the length of the header, thereby explicitly indicating the starting position of the data payload to the receiving application.

[0099] 5. 6-bit reserved field: Reserved for future TCP development; currently, all bits must be 0.

[0100] 6. 6-bit flags: There are 6 flags in total, and each flag occupies 1 bit.

[0101] 7. 16-bit window size: This field indicates the amount of bytes of data that the receive window of the TCP packet sender and receiver can still hold. Its function is to implement the flow control mechanism in the TCP protocol.

[0102] 8. 16-bit Checksum Field: To ensure the integrity of transmitted data, the sending end calculates and generates a checksum value based on the data content, while the receiving end performs the corresponding checksum operation on the received data to generate a corresponding value. If the two values ​​match, it indicates that the data has not been corrupted and is valid; if they do not match, the data is considered invalid, and the corresponding data packet will be discarded. The checksum calculation is based on three parts of information: the pseudo-header, the TCP header, and the TCP data segment.

[0103] 9. 16-bit Urgent Pointer Field: This field is only meaningful when the URG flag in the Flags field is set to 1. Its function is to indicate the number of bytes of urgent data in the payload. Once the urgent data has been processed, TCP will notify the application to return to normal operating mode. Even with a zero receiver window size, the transmission of urgent data is still possible because the urgent data does not require buffering.

[0104] 10. Options field: Length is variable, but must be an integer multiple of 32 bits and not exceed 40 bytes. Content is variable, therefore a header length must be used to distinguish the specific length of the options.

[0105] The UDP data portion can be found in [reference needed]. Figure 7 As shown, the specifics will not be elaborated here.

[0106] It should be noted that the above can be understood as meaning that the configuration update request message, configuration update response message, and initial configuration transmission message can all be in the form of UDP or TCP, and the specific message structure of the configuration update request message, configuration update response message, and initial configuration transmission message can be constructed independently according to different use cases.

[0107] As an optional implementation, the configuration update request message includes at least one of the following:

[0108] The first message type identifier is used to indicate the message category to which the configuration update request message belongs;

[0109] First quantity information, used to indicate the quantity of the target devices;

[0110] The first identifier of the target device is used to identify the target device whose IP address is to be updated.

[0111] The message type corresponding to the configuration update request message can be referred to as message type 1. The message structure of the configuration update request message can be found above. In addition, the configuration update request message may also include a first reserved bit, which can be used to reserve space for future development of data packets. Currently, all of them must be set to 0.

[0112] The first message type identifier and the first reserved bit can both be 8 bits, and the first quantity information and the first identifier of the target device can both be 16 bits. The first quantity information is used to indicate the number of target devices. If the first quantity information is 0, it means that there are no target devices. For example, when the target device is a CPE and the first quantity information is 0, it means that there are no CPEs. The first identifier of the target device is used to indicate the identification information of the target device whose IP address is to be updated. The specific type of the above identification information is not limited here. Optionally, the above identification information can be a serial number.

[0113] It should be noted that the message structure of the above configuration update request message can be found in [reference needed]. Figure 8 As shown.

[0114] In this embodiment of the application, since the configuration update request message includes at least one of the above messages, the diversity and flexibility of the content included in the configuration update request message are increased.

[0115] As an optional implementation, the configuration update response message includes at least one of the following:

[0116] The second message type identifier is used to indicate the message category to which the configuration update response message belongs;

[0117] The second quantity information is used to indicate the quantity of the target devices;

[0118] The second identifier of the target device is used to identify the target device whose IP address is to be updated.

[0119] The third quantity information is used to indicate the data offset of the field corresponding to the IP address of the next target device;

[0120] The first IP address is used to represent the updated IP address, which is the IP address of the target device.

[0121] Optionally, the aforementioned data offset may include a header offset.

[0122] The message type corresponding to the configuration update response message can be referred to as message type 2. The message structure of the configuration update response message can be found above. In addition, the configuration update response message may also include a second reserved bit, which can be used to reserve space for future development of data packets. Currently, all of them must be set to 0.

[0123] The second message type identifier and the second reserved bit can both be 8 bits, the second quantity information, the second identifier of the target device, and the third quantity information can all be 16 bits, and the first IP address can be 32 bits. The second quantity information is used to indicate the number of target devices. If the second quantity information is 0, it means that no target device exists. For example, if the target device is a CPE and the second quantity information is 0, it means that no CPE exists. The second identifier of the target device is used to indicate the identification information of the target device whose IP address is to be updated. The specific type of the above identification information is not limited here. Optionally, the above identification information can be a sequence number. The third quantity information is used to indicate the data offset of the 32-bit IP address field of the next target device (such as a CPE). If all are zero, it indicates that there is no subsequent CPE connection.

[0124] It should be noted that the message structure corresponding to the configuration update response message can be found in [link to relevant documentation]. Figure 9 As shown.

[0125] In this embodiment of the application, since the configuration update response message includes at least one of the above messages, the diversity and flexibility of the content included in the configuration update response message are increased.

[0126] As an optional implementation, the initial configuration transmission message further includes at least one of the following:

[0127] The third message type identifier is used to indicate the message category to which the initial configuration transmission message belongs;

[0128] The fourth quantity information is used to indicate the quantity of the target devices;

[0129] The third identifier of the target device is used to represent the identification information of a single target device;

[0130] The fifth quantity information is used to indicate the number of target components corresponding to a single target device;

[0131] The sixth quantity information is used to indicate the data offset of the field corresponding to the IP address of the next target device;

[0132] The second IP address is used to represent the IP address of a single target device;

[0133] Mapped port information is used to represent the information of the mapped port corresponding to the target device.

[0134] The message type corresponding to the initial configuration transmission message can be referred to as message type 0. The message structure of the initial configuration transmission message can be found in the above content. In addition, the initial configuration transmission message may also include a third reserved bit, which can be used to reserve space for future development of data packets. Currently, all of them must be set to 0.

[0135] The third message type identifier, third reserved bit, fifth quantity information, and sixth quantity information can all be 8 bits. The fourth quantity information, target device third identifier, and mapping port information can all be 16 bits. The second IP address can be 32 bits. The fourth quantity information is used to indicate the number of target devices. If the fourth quantity information is 0, it means that no target device exists. For example, when the target device is a CPE and the fourth quantity information is 0, it means that no CPE exists. The target device third identifier is used to indicate the identification information of a single target device. The specific type of the above identification information is not limited here. Optionally, the above identification information can be a serial number. The fifth quantity information is used to indicate the number of target components (cameras) corresponding to a single target device (such as a CPE). The sixth quantity information is used to indicate the data offset of the 32-bit IP address field of the next target device (such as a CPE). If all are zero, it means that there is no subsequent CPE connection. The mapping port information is used to indicate the information of the mapping port corresponding to the target device. For example, when the target device is a CPE, the mapping port information can be used to indicate the mapping ports of all cameras connected to the CPE. If all are 0, it means that there are no additional camera connections.

[0136] It should be noted that the message structure corresponding to the initial configuration transmission message can be found in [reference needed]. Figure 10 As shown.

[0137] In this embodiment of the application, since the initial configuration transmission message includes at least one of the above messages, the diversity and flexibility of the content included in the initial configuration transmission message are increased.

[0138] It should be noted that, in order to more fully explain the above configuration update request message, configuration update response message and initial configuration transmission message, please refer to Table 1. Table 1 is used to show the message sequence number, message name, transmission direction and message structure of the configuration update request message, configuration update response message and initial configuration transmission message.

[0139] It should be noted that, optionally, as shown in Table 1, the target device can be a CPE, the first communication node can be a base station, and the second communication node can be a local distribution server.

[0140] Table 1

[0141]

[0142] See Figure 11 , Figure 11 This is a flowchart illustrating an IP address acquisition method provided in an embodiment of this application. This IP address acquisition method can be executed by a second communication node.

[0143] like Figure 11 As shown, the method for obtaining an IP address includes the following steps:

[0144] Step 1101: Send a configuration update request message to the first communication node, wherein the configuration update request message is used to request the first communication node to update the IP address of the target device;

[0145] Step 1102: Receive the configuration update response message sent by the first communication node, wherein the configuration update response message includes the updated IP address of the target device.

[0146] The method for obtaining the IP address in this embodiment of the application is as follows: Figure 2 The embodiment corresponding to the IP address acquisition method shown above, the embodiment of this application is the same as the one described above. Figure 2 The difference between the IP address acquisition methods shown lies in the executing entity, namely... Figure 2 The execution entity of the IP address acquisition method shown is the first communication node, while the execution entity of this application embodiment is the second communication node. Therefore, this application embodiment can be compared with... Figure 2 The embodiments shown have the same beneficial technical effects, and the various technical features in the embodiments of this application can be found in the above description. Figure 2 The corresponding descriptions in the illustrated embodiments will not be repeated here.

[0147] As an optional implementation, sending a configuration update request message to the first communication node includes:

[0148] If the second communication node fails to retrieve streaming media data from the target device, the configuration update request message is sent to the first communication node.

[0149] In this embodiment, a configuration update request message is sent to the first communication node only when the second communication node fails to retrieve the streaming media data of the target device. This improves the accuracy of the configuration update request message and avoids the phenomenon of sending the wrong configuration update request message.

[0150] It should be noted that the specific method for determining that the second communication node has failed to retrieve the streaming media data of the target device is not limited here. Optionally, if the identification data of the streaming media data of the target device retrieved by the second communication node fails to match the identification data of the target device received in advance, it can be determined that the second communication node has failed to retrieve the streaming media data of the target device.

[0151] Alternatively, if the second communication node fails to retrieve streaming media data from the target device, the following description may also be helpful:

[0152] 1. The local split server (i.e., the second communication node) sends an RTSP streaming request command (i.e., a request command to pull streaming media data from the target device) to the camera connected to the CPE (i.e., the target device).

[0153] 2. After receiving the RTSP streaming request instruction, the camera connected to the CPE will respond within a predetermined time (T1) and directly transmit the camera streaming media data to the local distribution server.

[0154] 3. If the local split server receives the relevant instruction when the T1 timer expires, it indicates that the streaming process has been interrupted or failed, which means that the second communication node has failed to retrieve the streaming media data from the target device.

[0155] To more fully illustrate the above embodiments, a specific embodiment is given below as an example. For details, please refer to [link / reference needed]. Figure 12 The steps shown are as follows. It should be noted that, optionally, as... Figure 12 As shown in Table 2 below, when the target device is a CPE, the first communication node is a base station, the second communication node is a local traffic splitting server, and the third communication node is a heartbeat server, the roles, responsibilities, and authority of each of the above components can be found in the table below:

[0156] Table 2

[0157]

[0158] It should be noted that the CPE can periodically send heartbeat packets and data collection packets to the heartbeat server. The heartbeat server is responsible for receiving these data packets and sending corresponding policy messages to the CPE. If the CPE fails to receive the expected policy message response within a predetermined time threshold (e.g., 30 seconds), after verification by the retry mechanism, the CPE will determine that the heartbeat server is unreachable and accordingly close the connection.

[0159] It should be noted that, optionally, the local offloading server can also be a local offloading container deployed within the base station.

[0160] See Figure 13 , Figure 13 This is a structural diagram of the IP address acquisition device provided in this application embodiment. The IP address acquisition device 1300 is applied to a first communication node. The IP address acquisition device 1300 includes:

[0161] The first receiving module 1301 is used to receive a configuration update request message sent by the second communication node, wherein the configuration update request message is used to request an update of the IP address of the target device;

[0162] The first sending module 1302 is used to send a configuration update response message to the second communication node according to the configuration update request message, wherein the configuration update response message includes the updated IP address of the target device.

[0163] As an optional implementation, the first transmitting module 1302 includes:

[0164] The parsing submodule is used to parse the IP information of the uplink data packet when the configuration update request message is received;

[0165] The first determining submodule is used to determine the target data packet whose destination IP address is the first IP address based on the IP information;

[0166] The second determining submodule is used to determine the updated IP address of the target device based on the source IP address of the target data packet, and send the configuration update response message to the second communication node.

[0167] As an optional implementation, it also includes:

[0168] The third receiving module is used to receive the initial configuration transmission message sent by the second communication node;

[0169] The update module is used to update the mapping information table of the target device according to the initial configuration transmission message. The mapping information table includes: the mapping port corresponding to the target device, the IP address corresponding to the target device, and the C-RNTI corresponding to the target device.

[0170] As an optional implementation, the number of target devices is multiple, and the first determining submodule is further configured to determine multiple target data packets whose destination IP address is the first IP address based on the IP information;

[0171] The second determination submodule includes:

[0172] The first acquisition unit is used to acquire the source IP address of each target data packet;

[0173] The sending unit is configured to send a port status detection request to each of the target devices, and determine the updated IP address of each target device based on the port connectivity detection result received from each of the target devices and the source IP address of each target data packet.

[0174] Alternatively, the second acquisition unit is used to acquire parameter information for each of the target data packets, and determine the updated IP address of each target device based on the parameter information and the source IP address of each target data packet. The parameter information includes timestamp interval information or packet payload length information.

[0175] As an optional implementation, the configuration update request message includes at least one of the following:

[0176] The first message type identifier is used to indicate the message category to which the configuration update request message belongs;

[0177] First quantity information, used to indicate the quantity of the target devices;

[0178] The first identifier of the target device is used to identify the target device whose IP address is to be updated.

[0179] As an optional implementation, the configuration update response message includes at least one of the following:

[0180] The second message type identifier is used to indicate the message category to which the configuration update response message belongs;

[0181] The second quantity information is used to indicate the quantity of the target devices;

[0182] The second identifier of the target device is used to identify the target device whose IP address is to be updated.

[0183] The third quantity information is used to indicate the data offset of the field corresponding to the IP address of the next target device;

[0184] The first IP address is used to represent the updated IP address, which is the IP address of the target device.

[0185] As an optional implementation, the initial configuration transmission message further includes at least one of the following:

[0186] The third message type identifier is used to indicate the message category to which the initial configuration transmission message belongs;

[0187] The fourth quantity information is used to indicate the quantity of the target devices;

[0188] The third identifier of the target device is used to represent the identification information of a single target device;

[0189] The fifth quantity information is used to indicate the number of target components corresponding to a single target device;

[0190] The sixth quantity information is used to indicate the data offset of the field corresponding to the IP address of the next target device;

[0191] The second IP address is used to represent the IP address of a single target device;

[0192] Mapped port information is used to represent the information of the mapped port corresponding to the target device.

[0193] The IP address acquisition device 1300 can achieve the functionality described in the embodiments of this application. Figure 2 The various processes in the method embodiments, and the ways to achieve the same beneficial effects, will not be repeated here to avoid repetition.

[0194] See Figure 14 , Figure 14 This is a structural diagram of the IP address acquisition device provided in this application embodiment. The IP address acquisition device 1400 is applied to a second communication node and includes:

[0195] The second sending module 1401 is used to send a configuration update request message to the first communication node, the configuration update request message being used to request the first communication node to update the IP address of the target device;

[0196] The second receiving module 1402 is used to receive a configuration update response message sent by the first communication node, wherein the configuration update response message includes the updated IP address of the target device.

[0197] As an optional implementation, the second sending module 1401 is further configured to send the configuration update request message to the first communication node when the second communication node fails to retrieve the streaming media data of the target device.

[0198] The IP address acquisition device 1400 can achieve the functionality described in the embodiments of this application. Figure 11 The various processes in the method embodiments, and the ways to achieve the same beneficial effects, will not be repeated here to avoid repetition.

[0199] This application also provides an electronic device. Please refer to [link to relevant documentation]. Figure 15 The electronic device may include a processor 1501, a memory 1502, and a program 15021 stored in the memory 1502 and executable on the processor 1501. When the electronic device is a first communication node, the program 15021, when executed by the processor 1501, can achieve... Figure 2 The corresponding steps in the method embodiments and the achievement of the same beneficial effects will not be repeated here; when the electronic device is the second communication node, when program 15021 is executed by processor 1501, it can realize the corresponding functions on the server mentioned above. Figure 11 Any steps in the method embodiments shown, and the same beneficial effects achieved, will not be repeated here.

[0200] Those skilled in the art will understand that all or part of the steps of the methods described in the above embodiments can be implemented by hardware related to program instructions, and the program can be stored in a readable medium. This application also provides a readable storage medium storing a computer program, which, when executed by a processor, can implement the above-described methods. Figure 2 or Figure 11 Any step in the corresponding method embodiment can achieve the same technical effect, and will not be repeated here to avoid repetition.

[0201] The storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0202] This application also provides a computer program product, including computer instructions, which, when executed by a processor, can perform the above-described functions. Figure 2 or Figure 11 Any step in the corresponding method embodiment can achieve the same technical effect, and will not be repeated here to avoid repetition.

[0203] The above description represents the preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles described in this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for obtaining an IP address, characterized in that, Applied to a first communication node, the method includes: Receive a configuration update request message sent by the second communication node, the configuration update request message being used to request an update of the Internet Protocol IP address of the target device; According to the configuration update request message, a configuration update response message is sent to the second communication node, the configuration update response message including the updated IP address of the target device; Sending a configuration update response message to the second communication node according to the configuration update request message includes: Upon receiving the configuration update request message, the IP information of the uplink data packet is parsed; Based on the IP information, the target data packet with the destination IP address being the first IP address is determined; The updated IP address of the target device is determined based on the source IP address of the target data packet, and the configuration update response message is sent to the second communication node.

2. The method according to claim 1, characterized in that, Before receiving the configuration update request message sent by the second communication node, the method further includes: Receive the initial configuration transmission message sent by the second communication node; The mapping information table of the target device is updated according to the initial configuration transmission message. The mapping information table includes: the mapping port corresponding to the target device, the IP address corresponding to the target device, the cell radio network temporary identifier (C-RNTI) corresponding to the target device, and the target device identifier.

3. The method according to claim 1, characterized in that, The number of target devices is multiple, and the step of determining the destination IP address of the target data packet as the first IP address based on the IP information includes: Based on the IP information, multiple target data packets with a destination IP address of the first IP address are determined; Determining the updated IP address of the target device based on the source IP address of the target data packet includes: Obtain the source IP address of each target data packet; Send a port status detection request to each of the target devices, and determine the updated IP address of each target device based on the port connectivity detection result received from each of the target devices and the source IP address of each target data packet; Alternatively, obtain parameter information for each target data packet, and determine the updated IP address of each target device based on the parameter information and the source IP address of each target data packet. The parameter information includes timestamp interval information or packet payload length information.

4. The method according to any one of claims 1 to 3, characterized in that, The configuration update request message includes at least one of the following: The first message type identifier is used to indicate the message category to which the configuration update request message belongs; First quantity information, used to indicate the quantity of the target devices; The first identifier of the target device is used to identify the target device whose IP address is to be updated.

5. The method according to any one of claims 1 to 3, characterized in that, The configuration update response message includes at least one of the following: The second message type identifier is used to indicate the message category to which the configuration update response message belongs; The second quantity information is used to indicate the quantity of the target devices; The second identifier of the target device is used to identify the target device whose IP address is to be updated. The third quantity information is used to indicate the data offset of the field corresponding to the IP address of the next target device; The first IP address is used to represent the updated IP address, which is the IP address of the target device.

6. The method according to claim 2, characterized in that, The initial configuration transmission message also includes at least one of the following: The third message type identifier is used to indicate the message category to which the initial configuration transmission message belongs; The fourth quantity information is used to indicate the quantity of the target devices; The third identifier of the target device is used to represent the identification information of a single target device; The fifth quantity information is used to indicate the number of target components corresponding to a single target device; The sixth quantity information is used to indicate the data offset of the field corresponding to the IP address of the next target device; The second IP address is used to represent the IP address of a single target device; Mapped port information is used to represent the information of the mapped port corresponding to the target device.

7. A method for obtaining an IP address, characterized in that, Applied to a second communication node, the method includes: Send a configuration update request message to the first communication node, the configuration update request message being used to request the first communication node to update the Internet Protocol IP address of the target device; The first communication node receives a configuration update response message, which includes the updated IP address of the target device. The configuration update response message is a message sent by the first communication node to the second communication node after receiving the configuration update request message, parsing the IP information of the uplink data packet, determining the target data packet with the destination IP address as the first IP address based on the IP information, determining the updated IP address of the target device based on the source IP address of the target data packet, and sending the message to the second communication node.

8. The method according to claim 7, characterized in that, Sending a configuration update request message to the first communication node includes: If the second communication node fails to retrieve streaming media data from the target device, the configuration update request message is sent to the first communication node.

9. An electronic device, comprising: A memory, a processor, and a program stored in the memory and executable on the processor; characterized in that the processor is configured to read the program in the memory to implement the steps in the IP address acquisition method as described in any one of claims 1 to 6; or to implement the steps in the IP address acquisition method as described in claim 7 or 8.

Images