A terminal registration service communication method, device, equipment and storage medium

Abstract

The application relates to a terminal registration service communication method and device, equipment and a storage medium. The method is applied to a relay device and comprises the following steps: receiving a registration request message sent by a target terminal; querying registration information of the target terminal in a preset terminal registration information table according to an identifier of the target terminal to obtain the registration information; extracting a registration state from the registration information; judging whether the last registration request of the target terminal is successful according to the registration state; if it is judged that the last registration request of the target terminal is successful, extracting a registration period from the registration information; generating a response message of the registration request message according to the registration period; returning the response message to the target terminal; and forwarding the registration request message to a scheduling application program. Therefore, the application does not need the relay device to passively wait for a response message fed back by the scheduling application program, can effectively reuse the effective cache information of the historical successful registration of the terminal, greatly shortens the waiting time length of the terminal registration response, and further efficiently optimizes the utilization rate of air interface resources.

Description

Technical Field

[0001] This application relates to the conventional field of DMR, and more particularly to a terminal registration service communication method, apparatus, device and storage medium. Background Technology

[0002] In Digital Mobile Radio (DMR) communication systems, with the increasing adoption of conventional IP interconnection and enhanced virtual trunking (XPT) solutions combined with dispatch software, data services are becoming more widely used, such as positioning systems, text messaging systems, telemetry services, and data transmission services. These applications all require knowledge of whether a terminal is powered on or off. Radio Registration Services (RRS) provides a registration service that allows terminals to register, deregister, and check their online status. After powering on, a terminal proactively reports its online status to the IP interconnection or XPT system. Upon receiving this report, the IP interconnection or XPT system forwards it to the dispatch application, which then stores the registration information.

[0003] Currently, in the existing terminal registration service communication scheme, after the terminal starts up, it starts a timer periodically to report an RRS registration request to the repeater. This registration request is a packet data, consisting of one data header and two data blocks. After the terminal switches to the RRS channel, it checks whether the RRS channel is busy. If it is busy, it returns to the current channel and waits for retransmission; the RRS registration information is only transmitted when the RRS channel is idle. After the RRS registration information is successfully transmitted, the terminal will remain on the RRS channel for a period of time, waiting for a response from the console. If no response is received after the channel holding time, it will exit the RRS channel holding state. After receiving the packet data reported by the terminal, the repeater forwards the packet to the scheduling application and waits for a response from the scheduling application. When the scheduling application replies with an RRS registration response, the repeater determines whether the current repeater is idle or whether it allows the issuance of scheduling services. If not, the service is discarded; if allowed, a certain number of precarriers are first issued to the air interface, and then the RRS registration response from the scheduling application is converted into packet data (one data header and two data blocks) and sent to the air interface. Once the terminal receives the registration response, the RRS registration process is complete.

[0004] However, while the terminal is waiting for an RRS response, the repeater is idle and allows other terminals to access its services. If, during this waiting period, the repeater receives an RRS registration request from another terminal, and simultaneously receives an RRS response from the scheduling application in the same time slot, one terminal's RRS service will inevitably fail. This failure triggers a retransmission, further increasing air interface pressure and the probability of RRS services colliding with other services, resulting in a waste of air interface resources. Summary of the Invention

[0005] This application provides a terminal registration service communication method, apparatus, device, and storage medium, aiming to solve the technical problem in existing terminal registration service communication schemes where the terminal registration process takes too long, is easily interrupted by other services, causes registration failure, and thus leads to a waste of air interface resources.

[0006] In a first aspect, embodiments of this application provide a terminal registration service communication method, the method being applied to a relay device, the method comprising: Receive a registration request message sent by the target terminal, wherein the registration request message includes the identifier of the target terminal; Based on the identifier of the target terminal, the registration information of the target terminal is queried in a preset terminal registration information table to obtain the first registration information. The preset terminal registration information table includes at least one terminal identifier and at least one registration information, and the at least one terminal identifier corresponds one-to-one with the at least one registration information. Extract the first registration status from the first registration information; Based on the first registration status, determine whether the target terminal's previous registration request was successful; If it is determined that the previous registration request of the target terminal was successful, then the first registration period is extracted from the first registration information; A first response message is generated based on the first registration period to the registration request message; The first response message is returned to the target terminal; The registration request message is forwarded to the scheduling application.

[0007] Optionally, the method further includes: A second response message is received from the registration request message returned by the scheduling application; Extract the identifier of the target terminal from the second response message; Based on the identifier of the target terminal, query the preset terminal registration information table to see if the registration information of the target terminal exists; If the target terminal's registration information is not found in the preset terminal registration information table, the second response message is returned to the target terminal via a packet data delivery method.

[0008] Optionally, the method further includes: If the target terminal's registration information exists in the preset terminal registration information table, then the data type of the registration request message is obtained; If the data type is a single-frame data type, then the second response message is converted into a third response message, and the data type of the third response message is a single-frame data type. The third response message is returned to the target terminal.

[0009] Optionally, after extracting the identifier of the target terminal from the second response message, the method further includes: Extract the second registration status and second registration period of the target terminal from the second response message; The registration information of the target terminal in the preset terminal registration information table is updated according to the identifier of the target terminal, the second registration status, and the second registration period.

[0010] Optionally, the method further includes: If the first registration period is different from the second registration period, then the second registration period is sent to the target terminal.

[0011] Optionally, the method further includes: Receive an offline request message sent by the target terminal, the offline request message including the identifier of the target terminal; Based on the identifier of the target terminal, delete the registration information of the target terminal from the preset terminal registration information table; The offline request message is forwarded to the scheduling application.

[0012] Optionally, the method further includes: If the first registration information is not found in the preset terminal registration information table, then the third registration status of the target terminal and the registration timestamp of the registration request message are obtained. Based on the third registration status and the registration timestamp, the second registration information of the target terminal is generated; The second registration information is stored in the preset terminal registration information table; Forward the registration request message to the scheduling application; Receive a fourth response message from the scheduling application in response to the registration request message. The fourth response message is returned to the target terminal.

[0013] Secondly, embodiments of this application also provide a terminal registration service communication device, which includes a unit for performing the above-described method.

[0014] Thirdly, embodiments of this application also provide a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the above-described method.

[0015] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the above-described method.

[0016] This application provides a terminal registration service communication method, apparatus, device, and storage medium. The method, applied to a relay device, includes: receiving a registration request message from a target terminal, the registration request message including an identifier of the target terminal; querying the target terminal's registration information in a preset terminal registration information table based on the target terminal's identifier to obtain first registration information, the preset terminal registration information table including at least one terminal identifier and at least one registration information, the at least one terminal identifier corresponding one-to-one with the at least one registration information; extracting a first registration status from the first registration information; determining whether the target terminal's previous registration request was successful based on the first registration status; if the target terminal's previous registration request was successful, extracting a first registration period from the first registration information; generating a first response message for the registration request message based on the first registration period; returning the first response message to the target terminal; and forwarding the registration request message to a scheduling application. Therefore, this application optimizes the interaction logic for terminal registration communication scenarios. When the relay device receives a registration request message from the target terminal and has the terminal's registration information cached in its local preset terminal registration information table, it can directly parse the terminal's registration status and first registration period from the first registration information and determine the terminal's previous registration result based on historical registration status. If the terminal's previous registration was successful, the relay device can directly generate a corresponding registration response message based on the cached first registration period and send it back to the target terminal, while forwarding the registration request message to the scheduling application to complete the subsequent process. This application eliminates the need for the relay device to passively wait for the scheduling application to provide a response message, effectively reusing the valid cached information from the terminal's previous successful registrations, and greatly shortening the terminal registration response waiting time. Furthermore, this solution effectively avoids registration failures caused by other services preempting or interrupting the terminal registration process, improving the stability and success rate of the terminal registration process, and thus efficiently optimizing the utilization rate of air interface resources. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0020] Figure 1a A flowchart illustrating a terminal registration service communication method provided in an embodiment of this application; Figure 1b A single-frame RRS signaling format provided in this application embodiment; Figure 1c A registration request signaling format provided for embodiments of this application; Figure 1d A signaling format for a registration response provided in this application embodiment; Figure 1e A signaling format for an offline request message provided in an embodiment of this application; Figure 1f A signaling format for an online detection request message provided in this application embodiment; Figure 1g A signaling format for a response message to an online detection request message provided in an embodiment of this application; Figure 1h A signaling format for a registration period update notification message provided in this application embodiment; Figure 1i A communication connection diagram of a terminal device provided in an embodiment of this application; Figure 1j This is one of the flowcharts for processing RRS messages by a relay device provided in an embodiment of this application; Figure 1q This is a second flowchart illustrating the processing of RRS messages by a relay device, as provided in an embodiment of this application. Figure 1k-1 This is an air interface timing diagram of the terminal sending a single-frame RRS registration request for the first time in an embodiment of this application; Figure 1k-2This is an air interface timing diagram of the single-frame RRS registration request sent after successful terminal registration in this embodiment of the application; Figure 2 A schematic block diagram of a terminal registration service communication device provided in an embodiment of this application; Figure 3 A computer device provided in an embodiment of this application. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, 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.

[0022] The following disclosure provides numerous different embodiments or examples for implementing various structures of this application. To simplify the disclosure, specific examples and arrangements are described below. These are merely examples and are not intended to limit the scope of this application. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.

[0023] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0024] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of the application. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0025] It should also be further understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0026] As used in this specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrases "if determined" or "if [the described condition or event] is detected" may be interpreted, depending on the context, as "once determined," "in response to determination," "once [the described condition or event] is detected," or "in response to detection of [the described condition or event]."

[0027] To address the technical problem in existing terminal registration service communication schemes where the terminal registration process is too long and easily interrupted by other services, leading to registration failure and wasted air interface resources, this application provides a terminal registration service communication device that can shorten the registration process and prevent the terminal from failing to register due to interruption by other services, thereby effectively improving the utilization rate of air interface resources.

[0028] Figure 1a This is a flowchart illustrating a terminal registration service communication method provided in an embodiment of this application. In one embodiment, the method is applied to a relay device, and the method includes: S101-S108.

[0029] S101. Receive the registration request message sent by the target terminal.

[0030] The registration request message includes the identifier of the target terminal. The identifier of the target terminal can be the target terminal's ID.

[0031] It should be noted that the transfer equipment can be a transfer station or a vehicle-mounted transfer station.

[0032] Please see Figure 1b , Figure 1b This application provides a single-frame RRS signaling format for its embodiments. It should be noted that the registration request message in this application uses a single-frame RRS signaling format, as shown below. Figure 1b As shown, single-frame RRS and single-frame location information reporting share the same DataType. In this embodiment, ServiceType is used to distinguish between location information reporting and RRS. Specifically, the ServiceType of RRS is 0xD, and the Opcode is used to distinguish the specific operation of RRS.

[0033] Please see Figure 1c , Figure 1c This application provides a registration request signaling format. The Opcode is 0x0, used to identify the signaling as a registration request signaling. Bytes 1-4 are filled with the terminal identifier (i.e., terminal ID), and bytes 5-9 are reserved bits.

[0034] S102. Based on the identifier of the target terminal, query the registration information of the target terminal in the preset terminal registration information table to obtain the first registration information.

[0035] The preset terminal registration information table includes at least one terminal identifier and at least one registration information, with at least one terminal identifier corresponding to at least one registration information.

[0036] The first registration information is the registration information of the target terminal. The registration information of the target terminal includes, but is not limited to, the registration request timestamp, the registration status, and the registration period.

[0037] S103. Extract the first registration status from the first registration information.

[0038] The first registration status refers to the registration status of the target terminal. The target terminal has only two registration statuses, indicating whether the previous registration request was successful.

[0039] S104. Determine whether the target terminal's previous registration request was successful based on the first registration status.

[0040] S105. If it is determined that the previous registration request of the target terminal was successful, the first registration period is extracted from the first registration information.

[0041] The first registration period is the registration period of the target terminal, which is used to characterize the latest registration period of the target terminal.

[0042] S106. Generate the first response message of the registration request message according to the first registration cycle.

[0043] The first response message is the response message to the registration request message.

[0044] Please see Figure 1d , Figure 1d This application provides a signaling format for a registration response. The registration response is the response message to the registration request message. In the signaling format of the registration response, bytes 1-4 of the valid information carry the terminal ID. Byte 5 carries the registration result (i.e., registration status), where 0 indicates successful terminal registration and 1 indicates registration failure. Bytes 6-9 are filled with the RRS period interval (i.e., the registration period). The registration period can be modified on the program interface of the scheduling application.

[0045] Specifically, in this embodiment of the application, a first response message to the registration request message is generated based on the first registration period, the identifier of the target terminal, and the registration result.

[0046] S107. Return the first response message to the target terminal.

[0047] S108. Forward the registration request message to the scheduling application.

[0048] It should be noted that there is no fixed execution order between S107 and S108; S108 can be executed first, followed by S107.

[0049] Furthermore, in this embodiment, the relay device can return a self-constructed first response message to the target terminal without waiting for the scheduling application to return a response message to the registration request message. This mechanism can effectively reduce the time required for the target terminal to wait for the scheduling application to return a response message to the registration request message, greatly shortening the target terminal's registration response waiting time. At the same time, this solution can effectively avoid registration failures caused by other services preempting or interrupting the terminal registration process, improving the stability and success rate of the terminal registration process, and thus efficiently optimizing the utilization rate of air interface resources.

[0050] This application provides a terminal registration service communication method. The method is applied to a relay device and includes: receiving a registration request message sent by a target terminal, the registration request message including an identifier of the target terminal; querying the registration information of the target terminal in a preset terminal registration information table based on the identifier of the target terminal to obtain first registration information, the preset terminal registration information table including at least one terminal identifier and at least one registration information, the at least one terminal identifier corresponding one-to-one with the at least one registration information; extracting a first registration status from the first registration information; determining whether the target terminal's previous registration request was successful based on the first registration status; if the target terminal's previous registration request was successful, extracting a first registration period from the first registration information; generating a first response message for the registration request message based on the first registration period; returning the first response message to the target terminal; and forwarding the registration request message to a scheduling application. Therefore, this application optimizes the interaction logic for terminal registration communication scenarios. When the relay device receives a registration request message from a target terminal and the terminal's registration information is cached in the local preset terminal registration information table, it can directly parse the terminal registration status and the first registration period from the first registration information and determine the terminal's previous registration result based on historical registration statuses. If the terminal successfully registered previously, the relay device can directly generate a corresponding registration response message based on the cached first registration cycle and send it back to the target terminal. Simultaneously, it forwards the registration request message to the scheduling application to complete subsequent processes. This application eliminates the need for the relay device to passively wait for response messages from the scheduling application, effectively reusing cached information from successful terminal registrations and significantly reducing terminal registration response waiting time. Furthermore, this solution effectively avoids registration failures caused by other services interrupting or preempting the registration process, improving the stability and success rate of the terminal registration process, and thus efficiently optimizing the utilization rate of air interface resources.

[0051] In one embodiment, the method further includes: S109-S112.

[0052] S109. Receive the second response message of the registration request message returned by the scheduling application.

[0053] The second response message is a response message to the registration request message.

[0054] S110. Extract the identifier of the target terminal from the second response message.

[0055] S111. Based on the identifier of the target terminal, query the preset terminal registration information table to see if the registration information of the target terminal exists.

[0056] S112. If the target terminal's registration information is not found in the preset terminal registration information table, a second response message is returned to the target terminal via a packet data delivery method.

[0057] It should be noted that S109-S112 will be explained in detail below.

[0058] In this embodiment, when multiple terminals simultaneously initiate registration requests, the registration information corresponding to the target terminal may be deleted due to the capacity limitation of the preset terminal registration information table. Therefore, after the scheduling application returns a response message to the target terminal, it needs to check whether the target terminal's registration information exists in the preset terminal registration information table. If the target terminal's registration information does not exist in the preset terminal registration information table, a second response message is returned to the target terminal via packet data delivery.

[0059] In one embodiment, the method further includes: S113-S115.

[0060] S113. If the target terminal's registration information exists in the preset terminal registration information table, then obtain the data type of the registration request message.

[0061] The registration request message has two data types: a single-frame data type and a group data type.

[0062] S114. If the data type is a single-frame data type, then convert the second response message into a third response message.

[0063] The data type of the third response message is a single-frame data type.

[0064] It should be noted that, in order to improve data transmission efficiency, the second response message of the packet data type is converted into the third response message of the single-frame data type.

[0065] S115. Return a third response message to the target terminal.

[0066] In one embodiment, after S110, the method further includes: S115-S116.

[0067] S115. Extract the second registration status and second registration period of the target terminal from the second response message; S116. Update the registration information of the target terminal in the preset terminal registration information table according to the target terminal's identifier, second registration status, and second registration period.

[0068] It should be noted that S115-S116 will be explained in detail below.

[0069] In this embodiment, the latest registration information of the target terminal also needs to be extracted from the second response message and updated to the preset terminal registration information table. When the target terminal sends a registration request message to the relay device in the next registration cycle, the relay device can extract the latest registration information of the target terminal from the preset terminal registration information table and return it to the target terminal.

[0070] In one embodiment, the method further includes: S117.

[0071] S117. If the first registration period and the second registration period are different, the second registration period is sent to the target terminal.

[0072] It should be noted that when the relay device detects a change in the registration period of the target terminal, it can promptly send the latest registration period to the target terminal. Alternatively, the latest registration period can be returned to the target terminal when it initiates a registration request in the next registration period.

[0073] In one embodiment, the method further includes: S118-S120.

[0074] S118. Receive an offline request message sent by the target terminal. The offline request message includes the identifier of the target terminal.

[0075] Please see Figure 1e , Figure 1e This application provides a signaling format for an offline request message. In this signaling format, bytes 1-4 are filled with the terminal ID, and bytes 5-9 are reserved bits.

[0076] S119. Delete the registration information of the target terminal in the preset terminal registration information table according to the identifier of the target terminal.

[0077] S120: Forward the offline request message to the scheduling application.

[0078] It should be noted that S118-S120 will be explained in detail below.

[0079] When a target terminal is about to go offline, it sends an offline request message to the relay device. Upon receiving the offline request message, the relay device extracts the target terminal's identifier from the message and, based on this identifier, deletes the target terminal's registration information from the preset terminal registration information table. Finally, it forwards the offline request message to the scheduling application.

[0080] In one embodiment, the method further includes: S121-S126.

[0081] S121. If the first registration information is not found in the preset terminal registration information table, then obtain the third registration status of the target terminal and the registration timestamp of the registration request message.

[0082] S122. Generate the second registration information of the target terminal based on the third registration status and the registration timestamp.

[0083] S123. Store the second registration information in the preset terminal registration information table.

[0084] S124. Forward the registration request message to the scheduling application.

[0085] S125, Receive the fourth response message of the registration request message returned by the scheduling application.

[0086] S126. Return the fourth response message to the target terminal.

[0087] It should be noted that S121-S126 will be explained in detail below.

[0088] When the target terminal initiates a registration request for the first time, its registration information does not exist in the preset terminal registration information table. In this case, this embodiment first needs to obtain the target terminal's third registration status and the registration timestamp of the registration request message. Next, based on the third registration status and the registration timestamp, the target terminal's second registration information is generated. Then, the second registration information is stored in the preset terminal registration information table. Next, the registration request message is forwarded to the scheduling application, and the system waits for the scheduling application to return a response message to the registration request message. Finally, the response message is returned to the target terminal.

[0089] It should be noted that if the preset terminal registration information table has a capacity limit and is full, the terminal registration information with the smallest timestamp can be retrieved from the preset terminal registration information table and deleted. Then, the second registration information is stored in the preset terminal registration information table. Alternatively, this application embodiment can also provide a registration information aging and deletion mechanism. Specifically, the timestamp corresponding to each registration information in the preset terminal registration information table is checked periodically. When the timestamp corresponding to the registration information exceeds a preset threshold compared to the current timestamp, the registration information is deleted, thereby clearing expired terminal registration information.

[0090] Please see Figure 1f-1g , Figure 1f This application provides a signaling format for an online detection request message. Figure 1gThis application provides a signaling format for a response message to an online detection request message. When a scheduling application needs to actively detect the online status of a terminal, it can send an online detection request message to a relay device. The online detection request message includes a terminal ID. After receiving the online detection request message, the relay device queries the online status of the terminal based on the terminal ID and returns the online status of the terminal to the scheduling application.

[0091] Please see Figure 1h , Figure 1h This application provides a signaling format for a registration period update notification message. It should be noted that the user can configure the terminal's registration period on the application interface of the scheduling application. Then, the scheduling application notifies the relay device of the changed registration period via a registration period update notification message, which is then forwarded to the terminal by the relay device to make the terminal configuration effective.

[0092] Please see Figures 1i-1j .in, Figure 1i This is a communication connection diagram of a terminal device provided in an embodiment of this application. Figure 1j This is one of the flowcharts for processing RRS messages by a relay device, provided in an embodiment of this application. The terminal remains on the digital channel of the relay device. After powering on, it periodically reports RRS registration messages to the scheduling application through the local relay device or the IP interconnection relay device, and obtains the response from the scheduling application via the relay device.

[0093] like Figure 1j As shown, after the terminal powers on, it begins reporting RRS messages. Upon receiving the RRS message, the relay device parses it and determines the request type. There are three request types: RRS offline request, RRS registration request, and online detection response.

[0094] An RRS offline request is a request message actively reported by the terminal when it is powered off. After receiving the RRS offline request message, the relay device forwards it to the scheduling application and checks whether the relay device has registration information for the terminal locally. If the relay device has the terminal's registration information stored locally, it clears the terminal's registration information.

[0095] RRS registration requests are periodic requests submitted by terminals after power-on. Upon receiving an RRS registration request message, the relay device determines whether it is a single-frame RRS. If it is, it decompresses the message and forwards it to the scheduling application. If it is not a single-frame RRS registration request, it forwards it directly to the scheduling application. After forwarding, it checks if the terminal's registration information is stored locally. If it exists, it checks if the terminal's previous submission was successful. If successful, it maintains the channel, constructs an RRS registration response, and forwards it to the air interface so the terminal can receive the response. If the previous submission was unsuccessful, it indicates that the registration response received for this request should be forwarded to the air interface. Alternatively, if the relay device does not find the terminal's registration information stored locally, it extracts the terminal's registration information from the RRS registration request message, saves it locally, and indicates that the registration response received for this request needs to be forwarded to the air interface, then waits for a response from the scheduling application.

[0096] The online detection response is the online status replied by the terminal after receiving the online detection request. Upon receiving this response, the relay device, if it is a single-frame RRS, decompresses it and forwards it to the scheduling application.

[0097] Please see Figure 1q , Figure 1q This is a second flowchart illustrating the processing of RRS messages by a relay device, provided in an embodiment of this application. The relay device receives an RRS message from the scheduling application, extracts the terminal's identifier from the RRS message, and queries a local preset terminal registration information table based on the terminal's identifier to determine if the terminal's registration information is stored locally. If the relay device does not have the terminal's registration information cached locally, it directly constructs a packet data package according to the original process and forwards it to the air interface. If the relay device has the terminal's registration information cached locally, it further determines whether the RRS message is an online response. If it is an online response, the relay device updates the RRS reporting cycle and the current service status, then determines whether the identifier cached during the registration request needs to be forwarded to the air interface. If so, it decides whether to forward packet data or a single-frame RRS to the terminal based on the RRS type reported by the terminal.

[0098] Please see Figure 1k-1 as well as Figure 1k-2 . Figure 1k-1 This is an air interface timing diagram of the terminal sending a single-frame RRS registration request for the first time in an embodiment of this application. Figure 1k-2This is an air interface timing diagram of the single-frame RRS registration request sent by the terminal after successful registration in this embodiment of the application. It can be seen that when the terminal receives the RRS online registration request service again after successful registration, its air interface occupancy time is significantly reduced. This reduces the number of times the terminal retransmits due to channel congestion after hopping to the RRS channel, and also increases the success rate of the terminal's online registration service and the terminal capacity reporting RRS within the same period.

[0099] See Figure 2 , Figure 2 This is a schematic block diagram of a terminal registration service communication device provided in an embodiment of this application. Corresponding to the above-described terminal registration service communication method, this application also provides a terminal registration service communication device. This terminal registration service communication device includes a unit for executing the above-described terminal registration service communication method, and can be configured in a terminal such as a desktop computer, tablet computer, or laptop computer. Specifically, the terminal registration service communication device includes: The receiving unit 201 is configured to receive a registration request message sent by the target terminal, wherein the registration request message includes the identifier of the target terminal; The query unit 202 is used to query the registration information of the target terminal in a preset terminal registration information table according to the identifier of the target terminal, and obtain the first registration information. The preset terminal registration information table includes at least one terminal identifier and at least one registration information, and the at least one terminal identifier corresponds one-to-one with the at least one registration information. The first extraction unit 203 is used to extract the first registration status from the first registration information; The judgment unit 204 is used to determine whether the previous registration request of the target terminal was successful based on the first registration status; The second extraction unit 205 is used to extract the first registration period from the first registration information if it is determined that the previous registration request of the target terminal was successful. Generation unit 206 is configured to generate a first response message to the registration request message according to the first registration period; Return unit 207 is used to return the first response message to the target terminal; Forwarding unit 208 is used to forward the registration request message to the scheduling application.

[0100] In one embodiment, the receiving unit 201 is further configured to: receive a second response message of the registration request message returned by the scheduling application; The first extraction unit 203 is further configured to: extract the identifier of the target terminal from the second response message; The query unit 202 is further configured to: query whether the registration information of the target terminal exists in the preset terminal registration information table based on the identifier of the target terminal; The return unit 207 is further configured to: if the registration information of the target terminal is not found in the preset terminal registration information table, return the second response message to the target terminal through a packet data delivery method.

[0101] In one embodiment, the device further includes: The acquisition unit 209 is used to acquire the data type of the registration request message if the registration information of the target terminal exists in the preset terminal registration information table. The conversion unit 210 is used to convert the second response message into a third response message if the data type is a single-frame data type, wherein the data type of the third response message is a single-frame data type. The return unit 207 is also used to: return the third response message to the target terminal.

[0102] In one embodiment, after extracting the identifier of the target terminal from the second response message, the method further includes: The second extraction unit 205 is further configured to: extract the second registration status and the second registration period of the target terminal from the second response message; The device further includes: The update unit 211 is used to update the registration information of the target terminal in the preset terminal registration information table according to the identifier of the target terminal, the second registration status, and the second registration period.

[0103] In one embodiment, the device further includes: The sending unit 212 is used to send the second registration period to the target terminal if the first registration period is different from the second registration period.

[0104] In one embodiment, the receiving unit 201 is further configured to: receive an offline request message sent by the target terminal, the offline request message including the identifier of the target terminal; The device further includes a deletion unit 213, used to delete the registration information of the target terminal in the preset terminal registration information table according to the identifier of the target terminal; The forwarding unit 208 is further configured to: forward the offline request message to the scheduling application.

[0105] In one embodiment, the acquisition unit 209 is further configured to: if the first registration information is not found in the preset terminal registration information table, acquire the third registration status of the target terminal and the registration timestamp of the registration request message; The generation unit 206 is further configured to: generate second registration information of the target terminal based on the third registration status and the registration timestamp; The device further includes a storage unit 214 for storing the second registration information in the preset terminal registration information table; The forwarding unit 208 is further configured to: forward the registration request message to the scheduling application; The receiving unit 201 is further configured to: receive a fourth response message of the registration request message returned by the scheduling application; The return unit 207 is further configured to: return the fourth response message to the target terminal.

[0106] like Figure 3 As shown, this application provides a computer device including a processor 31, a communication interface 32, a memory 33, and a communication bus 34. The processor 31, the communication interface 32, and the memory 33 communicate with each other through the communication bus 34. The memory 33 is used to store computer programs. In one embodiment of this application, when the processor 31 executes the program stored in the memory 33, it implements the terminal registration service communication method provided in any of the foregoing method embodiments.

[0107] It will be understood by those skilled in the art that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program may be stored in a storage medium, which is a computer-readable storage medium. The computer program is executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.

[0108] Therefore, embodiments of this application also provide a computer-readable storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements the steps of the terminal registration service communication method provided in any of the foregoing method embodiments.

[0109] The storage medium is a physical, non-transient storage medium, such as a USB flash drive, external hard drive, read-only memory (ROM), magnetic disk, or optical disk, or any other physical storage medium capable of storing program code. The computer-readable storage medium can be non-volatile or volatile.

[0110] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0111] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0112] The steps in the methods of this application embodiment can be adjusted, merged, or deleted according to actual needs. The units in the apparatus of this application embodiment can be merged, divided, or deleted according to actual needs. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0113] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0114] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0115] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Since these modifications and variations fall within the scope of the claims and their equivalents, this application also intends to include these modifications and variations.

[0116] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A terminal registration service communication method, characterized in that, The method is applied to a transfer device, and the method includes: Receive a registration request message sent by the target terminal, wherein the registration request message includes the identifier of the target terminal; Based on the identifier of the target terminal, the registration information of the target terminal is queried in a preset terminal registration information table to obtain the first registration information. The preset terminal registration information table includes at least one terminal identifier and at least one registration information, and the at least one terminal identifier corresponds one-to-one with the at least one registration information. Extract the first registration status from the first registration information; Based on the first registration status, determine whether the target terminal's previous registration request was successful; If it is determined that the previous registration request of the target terminal was successful, then the first registration period is extracted from the first registration information; A first response message is generated based on the first registration period to the registration request message; The first response message is returned to the target terminal; The registration request message is forwarded to the scheduling application.

2. The method according to claim 1, characterized in that, The method further includes: A second response message is received from the registration request message returned by the scheduling application; Extract the identifier of the target terminal from the second response message; Based on the identifier of the target terminal, query the preset terminal registration information table to see if the registration information of the target terminal exists; If the target terminal's registration information is not found in the preset terminal registration information table, the second response message is returned to the target terminal via a packet data delivery method.

3. The method according to claim 2, characterized in that, The method further includes: If the target terminal's registration information exists in the preset terminal registration information table, then the data type of the registration request message is obtained; If the data type is a single-frame data type, then the second response message is converted into a third response message, and the data type of the third response message is a single-frame data type. The third response message is returned to the target terminal.

4. The method according to claim 2, characterized in that, After extracting the identifier of the target terminal from the second response message, the method further includes: Extract the second registration status and second registration period of the target terminal from the second response message; The registration information of the target terminal in the preset terminal registration information table is updated according to the identifier of the target terminal, the second registration status, and the second registration period.

5. The method according to claim 4, characterized in that, The method further includes: If the first registration period is different from the second registration period, then the second registration period is sent to the target terminal.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Receive an offline request message sent by the target terminal, the offline request message including the identifier of the target terminal; Based on the identifier of the target terminal, delete the registration information of the target terminal from the preset terminal registration information table; The offline request message is forwarded to the scheduling application.

7. The method according to claim 1, characterized in that, The method further includes: If the first registration information is not found in the preset terminal registration information table, then the third registration status of the target terminal and the registration timestamp of the registration request message are obtained. Based on the third registration status and the registration timestamp, the second registration information of the target terminal is generated; The second registration information is stored in the preset terminal registration information table; Forward the registration request message to the scheduling application; Receive a fourth response message from the scheduling application in response to the registration request message. The fourth response message is returned to the target terminal.

8. A terminal registration service communication device, characterized in that, The device is used in transfer equipment, and the device includes: A receiving unit is configured to receive a registration request message sent by a target terminal, wherein the registration request message includes the identifier of the target terminal; The query unit is used to query the registration information of the target terminal in a preset terminal registration information table based on the identifier of the target terminal to obtain the first registration information. The preset terminal registration information table includes at least one terminal identifier and at least one registration information, and the at least one terminal identifier corresponds one-to-one with the at least one registration information. The first extraction unit is used to extract the first registration status from the first registration information; The judgment unit is used to determine whether the previous registration request of the target terminal was successful based on the first registration status; The second extraction unit is used to extract the first registration period from the first registration information if it is determined that the previous registration request of the target terminal was successful. The generation unit is configured to generate a first response message to the registration request message according to the first registration period; The return unit is used to return the first response message to the target terminal; The forwarding unit is used to forward the registration request message to the scheduling application.

9. A computer device, characterized in that, The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, can implement the method as described in any one of claims 1 to 7.

Images