Iot terminal registration process optimization method and device, and electronic equipment

Abstract

This application discloses a method, apparatus, and electronic device for optimizing the registration process of IoT terminals. The method includes: during the non-access stratum signaling interaction phase, sending mobility management information to the core network via a radio resource control connection; receiving a location area update result from the core network after authentication and security mode negotiation with the core network; releasing the radio resource control connection based on the location area update result; after releasing the radio resource control connection, sending a registration request message to the IoT platform within the frequency band corresponding to the uplink and downlink frequency resources; and receiving a registration acceptance message from the IoT platform in response to the registration request message. This application solves the technical problems of increased air interface signaling load, prolonged registration time, and low satellite channel bandwidth utilization caused by repeated transmission of non-access stratum signaling due to separate registration by the core network and the IoT platform.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and more specifically, to a method, apparatus, and electronic device for optimizing the registration process of Internet of Things (IoT) terminals. Background Technology

[0002] Satellite mobile communication systems (such as the Tiantong IoT communication system) typically employ a two-phase mechanism involving separate registration of the core network circuit-switched (CS) domain and the IoT platform. Terminals must first complete CS domain registration before registering with the IoT platform. However, this mechanism has the following drawbacks:

[0003] Significant signaling redundancy exists: During both the CS domain registration and IoT platform registration phases, terminals must perform Non-Access Stratum (NAS) signaling interactions, including mobility management, two-way authentication, and identity recognition processes. The lack of unified coordination leads to the repeated transmission of critical signaling.

[0004] The registration process is time-consuming: repeated signaling interactions increase the signaling processing steps, and combined with the inherent transmission delay of satellite communication, this significantly prolongs the total registration time for the terminal, affecting the timeliness of services.

[0005] Low bandwidth utilization and prone to congestion: Redundant signaling occupies valuable satellite channel bandwidth, reducing the effective data transmission rate; in scenarios with multiple terminals registering concurrently, it is prone to signaling congestion, leading to registration failure or a decline in communication quality.

[0006] There is currently no effective solution to the above problems. Summary of the Invention

[0007] This application provides a method, apparatus, and electronic device for optimizing the registration process of Internet of Things (IoT) terminals, in order to at least solve the technical problems of increased air interface signaling load, prolonged registration time, and low satellite channel bandwidth utilization caused by repeated transmission of non-access stratum signaling due to separate registration by the core network and the IoT platform.

[0008] According to one aspect of this application, an optimized method for IoT terminal registration process is provided, comprising: establishing a radio resource control connection with a base station; during the non-access stratum signaling interaction phase, sending mobility management information to the core network through the radio resource control connection, wherein the mobility management information includes: a location area update request and extended fields, the extended fields including: IoT platform registration information, security authentication information, and device permission information; the IoT platform registration information is used to instruct the IoT platform to initiate a verification process, the verification process including: verifying the IoT terminal according to the security authentication information and device permission information, and obtaining a pre-verification result; and, after completing authentication and security mode negotiation with the core network, receiving the location information sent by the core network. The location area update result includes: a temporary mobile subscriber identification number (TMI) and dedicated uplink and downlink frequency resources for IoT services; based on the location area update result, the radio resource control connection is released; after releasing the radio resource control connection, a registration request message is sent to the IoT platform within the frequency band corresponding to the uplink and downlink frequency resources. The registration request message includes: a TMI and a registration identifier, which together indicate that the registration request message is a registration request based on the pre-verification result; the registration acceptance message sent by the IoT platform in response to the registration request message is received, wherein the registration acceptance message is sent after the registration operation is completed based on the pre-verification result.

[0009] Optionally, receiving the location area update result sent by the core network includes: receiving a radio resource control direct transmission message sent by the core network, wherein the radio resource control direct transmission message includes at least: a location area update acceptance message; a temporary mobile subscriber identification code; and an information cell field in the location area update acceptance message where uplink and downlink frequency resources are located.

[0010] Optionally, based on the location area update result, the radio resource control connection is released, including: verifying whether the temporary mobile subscriber identification code and uplink / downlink frequency resources in the location area update result meet preset requirements; if the verification is successful, receiving a radio resource control release message sent by the base station via a dedicated access control channel; wherein, the radio resource control release message is triggered by the base station after completing the release of the interface connection with the core network; after receiving the radio resource control release message, returning a radio resource control release completion message to the base station to complete the release of the radio resource control connection.

[0011] Optionally, within the frequency bands corresponding to the uplink and downlink frequency resources, a registration request message is sent to the IoT platform, including: performing radio frequency link synchronization locking based on the uplink and downlink frequency resources so that the IoT terminal and the IoT access point of the IoT platform are in frequency alignment; establishing a dedicated IoT channel matching the IoT platform based on the channel bandwidth requirements corresponding to the uplink and downlink frequency resources; and sending a registration request message to the IoT platform through the dedicated IoT channel.

[0012] Optionally, before establishing a radio resource control connection with the base station, the method further includes: configuring the hardware module of the IoT terminal to an active state by executing a function configuration instruction; performing a cell search to obtain synchronization information of the base station in the active state; and establishing a radio resource control connection with the base station, including: sending a radio resource control connection request to the base station on a random access channel; receiving a radio resource control connection establishment message sent by the base station on an access permission channel; and sending a radio resource control connection establishment completion message to the base station through a dedicated access control channel to establish a radio resource control connection with the base station.

[0013] Optionally, the security authentication information includes: a pre-assigned authentication key; the device permission information includes at least one of the following: the frequency of data uploaded by the IoT terminal to the IoT platform and the range of data that the IoT terminal is allowed to access.

[0014] Optionally, after receiving the registration acceptance message sent by the IoT platform in response to the registration request message, the method further includes: sending a service activation confirmation message to the IoT platform, wherein the service activation confirmation message includes: the operating status parameters of the IoT terminal; starting a heartbeat timer, and performing keep-alive signaling interaction with the IoT platform according to a preset time period to maintain the validity of the registration status.

[0015] According to another aspect of this application, an IoT terminal registration process optimization device is also provided, comprising: an establishment module for establishing a radio resource control connection with a base station; a first sending module for sending mobility management information to the core network through the radio resource control connection during the non-access stratum signaling interaction phase, wherein the mobility management information includes: a location area update request and extended fields, the extended fields including: IoT platform registration information, security authentication information, and device permission information; the IoT platform registration information is used to instruct the IoT platform to start a verification process, the verification process including: verifying the IoT terminal according to the security authentication information and device permission information, and obtaining a pre-verification result; and a first receiving module for receiving the location information sent by the core network after authentication and security mode negotiation with the core network. The location area update result includes: a temporary mobile subscriber identification number (TMI) and uplink / downlink frequency resources dedicated to IoT services; a release module, used to release the radio resource control connection based on the location area update result; a second sending module, used to send a registration request message to the IoT platform within the frequency band corresponding to the uplink / downlink frequency resources after releasing the radio resource control connection, wherein the registration request message includes: a TMI and a registration identifier, the TMI and the registration identifier together indicating that the registration request message is a registration request based on the pre-verification result; and a second receiving module, used to receive a registration acceptance message sent by the IoT platform in response to the registration request message, wherein the registration acceptance message is sent after the registration operation is completed based on the pre-verification result.

[0016] According to another aspect of this application, a non-volatile storage medium is also provided, the storage medium including a stored program, wherein the program, when running, controls the device where the storage medium is located to execute the above-mentioned IoT terminal registration process optimization method.

[0017] According to another aspect of this application, an electronic device is also provided, including: a memory and a processor, the processor being used to run a program stored in the memory, wherein the program executes the above-described IoT terminal registration process optimization method during runtime.

[0018] According to another aspect of this application, a computer program is also provided, wherein when the computer program is executed by a processor, it implements the above-described IoT terminal registration process optimization method.

[0019] According to another aspect of this application, a computer program product is also provided, which includes a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the above-mentioned IoT terminal registration process optimization method.

[0020] In this application, a radio resource control (RFC) connection is established with the base station. During the non-access stratum signaling interaction phase, mobility management information is sent to the core network via the RRC connection. This mobility management information includes a location area update request and extended fields, such as IoT platform registration information, security authentication information, and device permission information. The IoT platform registration information instructs the IoT platform to initiate a verification process, which includes: verifying the IoT terminal based on the security authentication information and device permission information, and obtaining a pre-verification result; after completing authentication and security mode negotiation with the core network, receiving the location area update result sent by the core network, which includes a temporary mobile subscriber identification code and dedicated uplink and downlink frequency resources for IoT services; releasing the RRC connection based on the location area update result; and after releasing the RRC connection, sending a registration request to the IoT platform within the frequency band corresponding to the uplink and downlink frequency resources. The system requests a registration request message, which includes a Temporary Mobile Subscriber Identity (TMS) identifier and a registration identifier. These two identifiers together indicate that the registration request message is based on a pre-verification result. It also receives a registration acceptance message from the IoT platform in response to the registration request message. This registration acceptance message is sent after the registration operation is completed based on the pre-verification result. This achieves the goal of completing the pre-verification of IoT platform registration information during the core network circuit-switched domain registration phase, and sending only a simplified registration request based on the pre-verification result during the subsequent IoT platform registration phase. This avoids redundant transmission of non-access stratum signaling, thereby reducing air interface signaling transmission volume, shortening the overall terminal registration time, and improving satellite channel bandwidth utilization. Ultimately, it solves the technical problems of increased air interface signaling load, prolonged registration time, and low satellite channel bandwidth utilization caused by redundant transmission of non-access stratum signaling due to separate registration by the core network and the IoT platform. Attached Figure Description

[0021] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0022] Figure 1 This is a sequence diagram of the air interface signaling interaction during the registration process in related technologies;

[0023] Figure 2 This is a flowchart of an IoT terminal registration process optimization method according to an embodiment of this application;

[0024] Figure 3 This is a flowchart of a method for releasing a wireless resource control connection according to an embodiment of this application;

[0025] Figure 4 This is a signaling interaction diagram of an IoT terminal registration process optimization method according to an embodiment of this application;

[0026] Figure 5 This is a structural diagram of an IoT terminal registration process optimization device according to an embodiment of this application;

[0027] Figure 6 This is a hardware structure block diagram of a computer terminal for an IoT terminal registration process optimization method according to an embodiment of this application. Detailed Implementation

[0028] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. 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 apparatus that comprises 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 such processes, methods, products, or apparatus.

[0030] To better understand the embodiments of this application, the technical terms involved in the embodiments of this application are explained below:

[0031] Tiantong Terminal: A mobile terminal device that supports the Tiantong satellite communication system, has satellite link access capability, and can realize voice, SMS and data communication in areas without coverage of terrestrial cellular networks.

[0032] Satellite communication: Using artificial Earth satellites as relay stations to forward radio waves, it enables communication between earth stations and is suitable for areas with insufficient terrestrial network coverage.

[0033] Core Network CS Domain: A core component of the Tiantong IoT communication system, responsible for handling circuit-switched service-related functions. During this stage, terminals complete hardware activation, cell search, signaling interaction, and other operations to obtain basic communication configurations and resources.

[0034] Internet of Things (IoT) Platform: A crucial carrier for TianTong IoT terminals to achieve data interaction, device management, and other functions. Terminals must register in the core network CS domain before accessing the platform.

[0035] AT commands: A set of commands used to control communication devices. During the registration and communication process of TianTong IoT terminals, AT+CFUN=5 and AT+CFUN=1 are used for hardware activation and function configuration; AT+IOTFUN=1 is used to trigger IoT platform registration; and AT+ULDATA is used for data transmission.

[0036] NAS layer signaling: Non-access stratum signaling is responsible for handling signaling processes related to user services, such as mobility management, session management, and authentication. It does not involve specific operations of radio resources, but it is crucial for the interaction between the terminal and the network.

[0037] In related technologies, the Tiantong IoT communication system, based on a satellite network architecture, divides terminal communication preparation into three major stages: core network CS domain registration, IoT platform registration, and data transmission. Figure 1 As shown, the specific steps include the following.

[0038] Step 1: RACH:RRC Connection Request.

[0039] The terminal initiates the Radio Resource Control (RRC) connection establishment process by sending an RRC connection request to the base station through the Random Access Channel (RACH).

[0040] Step 2: AGCH:RRC Connection Setup.

[0041] The base station replies to the terminal with an RRC connection establishment message via the Access Grant Channel (AGCH) to allocate radio resources to the terminal.

[0042] Step 3: DACCH: RRC Connection Setup Complete.

[0043] The terminal sends an RRC connection establishment complete message to the base station through the Dedicated Access Control Channel (DACCH) to confirm that the connection has been established.

[0044] Step 4: DACCH: Initial DT (LA Update Request) (Dedicated Access Control Channel: Initial Direct Transmission (Location Area Update Request)).

[0045] The terminal sends an initial direct transmission message via DACCH, carrying a location area update request, and the base station forwards the message to the core network.

[0046] Step 5: RANAP: Initial UE Message (Radio Access Node Application Part: Initial UE Message).

[0047] The base station forwards the terminal's initial message to the core network through the Radio Access Node Application Part (RANAP) protocol, and the core network begins to process the terminal's access request.

[0048] Step 6: RANAP:DT (Authentication Request) (Wireless Access Node Application Part: Direct Transmission (Authentication Request)).

[0049] The core network sends a direct transmission authentication request message to the base station, requesting that the terminal authenticate its identity.

[0050] Step 7: DACCH:DT (Authentication Request) (Dedicated Access Control Channel: Direct Transmission (Authentication Request)).

[0051] The base station forwards the authentication request issued by the core network to the terminal via DACCH.

[0052] Step 8: DACCH:DT (Authentication Response) (Dedicated Access Control Channel: Direct Transmission (Authentication Response)).

[0053] After completing the authentication calculation, the terminal returns an authentication response message to the base station via DACCH.

[0054] Step 9: RANAP:DT (Authentication Response) (Wireless Access Node Application Part: Direct Transmission (Authentication Response)).

[0055] The base station forwards the terminal's authentication response to the core network via RANAP, and the core network verifies the authentication result.

[0056] Step 10: RANAP: Security Mode Command (Radio Access Node Application Part: Security Mode Command).

[0057] The core network sends a security mode command to the base station, requesting the activation of encryption and integrity protection mechanisms.

[0058] Step 11: DACCH: Security Mode Command.

[0059] The base station forwards the security mode command to the terminal via DACCH, and the terminal begins to configure security parameters.

[0060] Step 12: DACCH: Security Mode Complete.

[0061] After the terminal completes the security mode configuration, it returns a security mode completion message to the base station via DACCH.

[0062] Step 13: RANAP: Security Mode Complete (Radio Access Node Application Section: Security Mode Complete).

[0063] The base station forwards the security mode completion message to the core network via RANAP, and the security activation process ends.

[0064] Step 14: RANAP:DT (LA Update Accept) (Radio Access Node Application Part: Direct Transmission (Location Area Update Accept)).

[0065] The core network sends a location area update acceptance message to the base station, indicating that the terminal's location registration was successful.

[0066] Step 15: DACCH:DT (LA Update Accept) (Dedicated Access Control Channel: Direct Transmission (Location Area Update Accept)).

[0067] The base station forwards the location area update receive message to the terminal via DACCH, notifying the terminal that the location update is complete.

[0068] Step 16: RANAP:DT (LA Update Reject) (Radio Access Node Application Part: Direct Transmission (Location Area Update Reject)).

[0069] If the core network rejects the terminal's location area update request, it sends a location area update rejection message to the base station.

[0070] Step 17: DACCH:DT (LA Update Reject) (Dedicated Access Control Channel: Direct Transmission (Location Area Update Reject)).

[0071] The base station forwards the location area update rejection message to the terminal, and the terminal needs to perform subsequent processing based on the reason for the rejection.

[0072] Step 18: RANAP: Iu Release Command (Radio Access Node Application Part: Iu Release Command).

[0073] The core network sends an Iu interface release command to the base station, instructing the base station to release the connection resources with the terminal.

[0074] Step 19: RANAP: Iu Release Complete (Radio Access Node Application Section: Iu Release Complete).

[0075] After the base station completes the release of Iu interface resources, it returns an Iu release completion message to the core network.

[0076] Step 20: DACCH: RRC Connection Release.

[0077] The base station sends an RRC connection release message to the terminal via DACCH, notifying the terminal to disconnect the wireless connection.

[0078] Step 21: DACCH: RRC Connection Release Complete.

[0079] After receiving the release message, the terminal returns an RRC connection release complete message to the base station via DACCH, indicating that the radio resource reclamation is complete.

[0080] Step 22: DBCCH: IOT DBCCH REQ (Dedicated Broadcast Control Channel: IoT DBCCH Request).

[0081] The terminal sends an IoT broadcast channel request to the base station through the Dedicated Broadcast Control Channel (DBCCH) to request IoT-related system information.

[0082] Step 23: DBCCH: IOT DBCCH IND (Dedicated Broadcast Control Channel: IoT DBCCH Indicator).

[0083] The base station replies to the terminal via DBCCH with an IoT broadcast channel indication, carrying the information required for IoT network access.

[0084] Step 24: DRACH: IOT REGISTER REQ (Dedicated Random Access Channel: IoT Registration Request).

[0085] The terminal sends an IoT registration request to the IoT platform through the Dedicated Random Access Channel (DRACH) to initiate the IoT service registration process.

[0086] Step 25: DAGCH:IOT AUTH REQ (Dedicated Access Permitted Channel: IoT Authentication Request).

[0087] The IoT platform sends an IoT authentication request to the terminal through the Dedicated Access Grant Channel (DAGCH), requiring the terminal to perform platform-level identity authentication.

[0088] Step 26: DRACH:IOT AUTH RSP (Dedicated Random Access Channel: IoT Authentication Response).

[0089] The terminal returns an IoT authentication response to the IoT platform via DRACH, carrying the credential information required for platform authentication.

[0090] Step 27: DAGCH:IOT REGISTER ACCEPT (Dedicated Access Grant Channel: IoT Registration Acceptance).

[0091] After the IoT platform verifies the terminal's identity, it sends an IoT registration acceptance message to the terminal via DAGCH, and the terminal successfully connects to the IoT platform.

[0092] The aforementioned signaling interaction plays a crucial role in each stage, but it also has obvious problems.

[0093] 1. Core network CS domain registration phase.

[0094] Hardware activation: After the module is powered on, it executes the AT+CFUN=5 and AT+CFUN=1 commands to complete card activation, physical layer initialization, and function configuration. Although this process does not involve a large amount of signaling interaction, the accurate execution of commands is the foundation for subsequent signaling interactions.

[0095] Cell search and connection establishment: The terminal scans frequencies to obtain a cell list, parses Broadcast Control Channel (CCCH) system messages, and establishes a Radio Resource Control (RRC) connection. During this process, the terminal initiates a random access request via the Random Access Channel (RACH), and the base station returns a response via the Access Grant Channel (AGCH). This series of operations involves initial signaling interaction, establishing a channel for subsequent signaling transmission.

[0096] Signaling interaction process: Mobility management, two-way authentication, identity recognition, and security mode configuration are completed through NAS layer signaling. The terminal first sends a Mobility Management Registration Request (MM REGISTRATION REQUEST) (LA Update Request) to report its location and mobility status; the network side returns an Authentication Request to initiate authentication, and the terminal responds with an Authentication Response to complete identity verification; subsequently, the network issues a Security Mode Command for encryption configuration, and the terminal replies with a Security Mode Complete confirmation; finally, the terminal obtains a Temporary Mobile Subscriber Identity (TMSI) and IoT-specific frequency resources (including downlink carriers, downlink access license channels / downlink broadcast control channels configured in a 1+6+1 cycle), and releases the IU interface and air interface radio resources after registration. This NAS layer signaling interaction is crucial for ensuring the terminal's legitimate access to the core network CS domain, but the process is complex, involving multiple signaling types and interaction procedures.

[0097] 2. IoT platform registration phase.

[0098] After core network CS domain registration is completed, the terminal activates its dedicated channel via the AT+IOTFUN=1 command, reads system messages using the downlink broadcast control channel, and initiates an IoT registration request (IOTREGISTER REQ) containing the terminal ID and authentication information on the allocated uplink frequency in a contention-based manner. After completing authentication interaction with the IoT platform (IOT AUTH REQ / RSP), it obtains a registration acceptance message (IOT REGISTER ACCEPT), thus completing platform access. This stage requires another complete authentication interaction and other signaling procedures, resulting in significant overlap with the signaling interaction during the core network CS domain registration phase.

[0099] 3. Issues with signaling interaction mode.

[0100] The current separate registration mechanism for the core network CS domain and the IoT platform leads to redundant signaling transmission at the NAS layer. For example, in the authentication and identification process, the terminal needs to perform one registration in the core network CS domain and another in the IoT platform registration, increasing the air interface signaling load by more than 30% compared to the optimized solution. Excessive signaling transmission not only prolongs registration time but also reduces satellite channel bandwidth utilization. In scenarios with multiple terminals registering concurrently, a large amount of redundant signaling can easily cause signaling congestion, leading to registration failures for some terminals or a significant degradation in communication quality.

[0101] To address the aforementioned issues, this application provides relevant solutions, which are detailed below.

[0102] According to an embodiment of this application, a method embodiment for optimizing the registration process of an Internet of Things (IoT) terminal is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0103] Figure 2 This is a flowchart of an IoT terminal registration process optimization method according to an embodiment of this application, such as... Figure 2 As shown, the method includes the following steps:

[0104] Step S201: Establish a radio resource control connection with the base station.

[0105] In step S201, after the IoT terminal powers on, it completes hardware activation and physical layer initialization by executing the AT+CFUN=5 and AT+CFUN=1 commands. Then, it scans frequency points to obtain the cell list, parses system messages in the Broadcast Control Channel (BCCH), and initiates a random access request on the Random Access Channel (RACH). After the base station returns a response through the Access Grant Channel (AGCH), an RRC connection is successfully established. The main purpose of this stage is to establish a stable wireless transmission channel for subsequent Non-Access Stratum (NAS) signaling interactions, ensuring that the terminal and the network side have basic connectivity capabilities.

[0106] In step S202, during the non-access stratum signaling interaction phase, mobility management information is sent to the core network through the radio resource control connection. The mobility management information includes a location area update request and extended fields. The extended fields include IoT platform registration information, security authentication information, and device permission information. The IoT platform registration information is used to instruct the IoT platform to start the verification process. The verification process includes verifying the IoT terminal based on the security authentication information and device permission information, and obtaining a pre-verification result.

[0107] In step S202, after establishing the RRC connection, the terminal enters the non-access stratum signaling interaction phase and sends mobility management information containing extended fields to the core network through the established RRC connection. This mobility management information mainly includes a Location Area Update Request (LA Update Request) and innovatively added extended fields.

[0108] The extended fields include IoT platform registration information, security authentication information, and device permission information. The IoT platform registration information instructs the network side to trigger the IoT platform's pre-verification process; the security authentication information contains a pre-assigned authentication key for subsequent identity verification with the IoT platform; and the device permission information defines policies such as the data range and upload frequency that the terminal can access.

[0109] Upon receiving the extended signaling, the network-side signaling processing module performs two main actions: firstly, it processes the mobility management information required for core network CS domain registration according to traditional procedures; secondly, it extracts the IoT platform registration information from the extended fields and sends it to the IoT platform via an encrypted dedicated signaling transmission channel (e.g., using SSL encryption and CRC check mechanisms). Based on the received security authentication information and device permission information, the IoT platform performs preliminary identity verification and permission review of the terminal, generating and temporarily storing a pre-verification result. This achieves parallel processing of core network registration and IoT platform pre-verification, significantly reducing the number of signaling rounds required for subsequent interactions.

[0110] Optionally, in step S202, sending mobility management information to the core network via the radio resource control connection specifically includes:

[0111] When the terminal encapsulates a location area update request message that is not part of the access layer, it inserts an extended signaling unit into the message body. The extended signaling unit includes an IoT platform identifier, a pre-allocated authentication key, and a service permission policy.

[0112] After receiving the location area update request message, the core network performs the following collaborative processing operations:

[0113] Parse location area update request messages to complete the mobility management, two-way authentication, and security mode configuration process in the core network CS domain;

[0114] Meanwhile, the IoT platform identifier, pre-allocated authentication key, and business permission policy are extracted from the extended signaling unit, and the extracted information is packaged into a pre-verification request message and sent to the IoT platform through the dedicated signaling interface established between the core network and the IoT platform.

[0115] After receiving the pre-verification request message, the IoT platform verifies the legitimacy of the terminal's identity based on the pre-allocated authentication key, reviews the terminal's access permissions according to the business permission policy, generates a pre-verification result containing a verification status code, and caches it. The verification status code is used to indicate whether the registration request has passed the pre-verification.

[0116] Step S203: After completing authentication and security mode negotiation with the core network, receive the location area update result sent by the core network. The location area update result includes: temporary mobile subscriber identification code and uplink / downlink frequency resources dedicated to IoT services.

[0117] In step S203, after mobility management, two-way authentication, and security mode negotiation are completed on the core network side, the terminal receives the location area update result sent by the core network. The location area update result includes a unique temporary mobile subscriber identity (TMSI) allocated by the network side, and dedicated uplink and downlink frequency resources for IoT services (e.g., DAGCH / DBCCH channel resources configured in a 1+6+1 cycle). During this process, the terminal replies with a security mode completion message to confirm that the encryption and integrity protection algorithm configuration has taken effect. It can be understood that obtaining the TMSI and dedicated frequency resources signifies that the terminal has legally accessed the core network CS domain and possesses the basic conditions for data transmission of services in the satellite network. At this time, the terminal uses the acquired TMSI as its identity identifier for subsequent communication, ensuring its uniqueness and security during the IoT platform registration process. Simultaneously, the allocation of dedicated frequency resources reserves channel resources for subsequent low-latency, high-reliability IoT data transmission.

[0118] Step S204: Release the radio resource control connection based on the location area update result.

[0119] In step S204, after successfully obtaining the location area update result, the terminal executes the step of releasing the radio resource control (RRC) connection. Since the core network CS domain registration process has ended, and subsequent interactions with the IoT platform will be based on a dedicated IoT service channel, the terminal actively releases the current RRC connection to save terminal power and free up air interface resources. After releasing the RRC connection, the terminal utilizes the previously allocated dedicated uplink and downlink frequency resources for IoT services to switch to the corresponding channel mode. This resource release operation not only optimizes the utilization of radio resources but also avoids the additional signaling overhead incurred during the subsequent IoT platform registration process due to maintaining the RRC connection.

[0120] Step S205: After releasing the radio resource control connection, a registration request message is sent to the IoT platform within the frequency band corresponding to the uplink and downlink frequency resources. The registration request message includes a temporary mobile subscriber identification code and a registration identifier. The temporary mobile subscriber identification code and the registration identifier together indicate that the registration request message is a registration request based on the pre-verification result.

[0121] In step S205, after releasing the RRC connection, the terminal sends a registration request message to the IoT platform within the frequency bands corresponding to the uplink and downlink frequency resources. It is worth noting that the registration request message in this embodiment is simplified, containing only a Temporary Mobile Subscriber Identity (TMSI) and a specific registration identifier. The TMSI proves that the terminal has passed the core network's authentication, and the registration identifier indicates that the request is a rapid registration initiated based on the results previously transmitted from the network side and pre-verified by the IoT platform. This streamlined signaling structure avoids the repeated transmission of sensitive information such as authentication vectors and keys, reduces air interface signaling load, and shortens signaling transmission time, making it particularly suitable for application scenarios where satellite channel bandwidth is limited and latency is sensitive.

[0122] Step S206: Receive a registration acceptance message sent by the IoT platform in response to the registration request message, wherein the registration acceptance message is sent after the registration operation is completed based on the pre-verification result.

[0123] In step S206, after receiving the registration request message, the IoT platform quickly completes the registration operation for the terminal based on the previously cached pre-verification results. If the pre-verification is successful, the IoT platform returns a registration acceptance message (IOTREGISTER ACCEPT) to the terminal. This message return eliminates the need for complex authentication interactions or permission re-verification processes, thus enabling the terminal to connect to the IoT platform in seconds or even milliseconds.

[0124] Through steps S201 to S206, the signaling interaction that was originally scattered in the two stages of registration in the core network CS domain and registration on the IoT platform was successfully integrated and optimized, eliminating redundant NAS layer signaling transmission, significantly reducing registration time and air interface signaling load, and improving the registration success rate and overall communication performance of the IoT communication system in multi-terminal concurrent scenarios.

[0125] The following are Figure 2 The steps shown are illustrated and explained by way of example.

[0126] According to some optional embodiments of this application, receiving the location area update result sent by the core network can be achieved through the following steps: receiving a radio resource control direct transmission message sent by the core network, wherein the radio resource control direct transmission message includes at least: a location area update acceptance message; a temporary mobile subscriber identification code; and an information cell field in the location area update acceptance message containing uplink and downlink frequency resources.

[0127] In this embodiment, the step of the terminal receiving the location area update result sent by the core network can be implemented through the Radio Resource Control (RRC) direct transmission mechanism. Specifically, after the core network CS domain completes the authentication, identity recognition, and security mode negotiation of the terminal, it generates a location area update acceptance message. Since non-access stratum signaling needs to rely on the radio access stratum for transmission, the core network encapsulates the location area update acceptance message in an RRC direct transmission message and sends it to the base station, which then forwards it to the terminal through the downlink radio channel.

[0128] After receiving the RRC direct transmission message, the terminal parses out the included Location Area Update Acceptance Message. This message carries a Temporary Mobile Subscriber Identity (TMSI) assigned to the terminal by the core network, along with IoT service-specific uplink and downlink frequency resource information, through specific information cell fields. The TMSI serves as the terminal's temporary identity identifier in the core network, used for authentication in subsequent communications; the uplink and downlink frequency resources indicate which specific physical frequencies and time slots the terminal should switch to after releasing the RRC connection to send subsequent IoT platform registration requests.

[0129] The process described above, which synchronously distributes identity identifiers and service resources in the same signaling flow, ensures that the terminal can obtain the physical resources required for service communication while acquiring network access qualifications.

[0130] Figure 3 This is a flowchart of a method for releasing a radio resource control connection according to an embodiment of this application, such as... Figure 3 As shown, the method includes the following steps:

[0131] Step S301: Verify whether the temporary mobile subscriber identification code and uplink / downlink frequency resources in the location area update result meet the preset requirements.

[0132] In step S301, the terminal verifies the validity of the received location area update result, specifically verifying whether the Temporary Mobile Subscriber Identity (TMSI) identifier and the uplink / downlink frequency resources dedicated to IoT services meet preset requirements. These preset requirements may include a valid TMSI length and frequency resource parameters conforming to the TianTong IoT protocol specifications. If the verification passes, confirming that the terminal has legally obtained its identity and possesses the physical resources required for subsequent communication, the terminal performs a subsequent release operation. If the verification fails, the terminal can maintain the RRC connection or initiate a reconnection request to avoid registration failure due to invalid resources.

[0133] Step S302: If the verification is successful, the radio resource control release message sent by the base station is received via the dedicated access control channel; wherein, the radio resource control release message is triggered by the base station after the interface connection between the base station and the core network is released.

[0134] In step S303, if the verification is successful, the terminal receives a Radio Resource Control (RRC) release message from the base station via a dedicated access control channel. This RRC release message is triggered by the base station after it completes the release of the interface connection with the core network (such as the IU interface or the Tiantong core network interface). At this point, the base station no longer needs to maintain the RRC connection with the terminal for core network signaling interaction, and therefore issues a release command. The terminal parses the release message, obtains the necessary idle state configuration or reselection information, and prepares to disconnect the current RRC connection.

[0135] Step S303: After receiving the radio resource control release message, return a radio resource control release completion message to the base station to complete the release of the radio resource control connection.

[0136] In step S303, after receiving the radio resource control release message, the terminal returns a radio resource control release completion message to the base station. This completion message confirms that the terminal has performed the local resource release operation and notifies the base station that the radio resources allocated to the terminal can be completely reclaimed.

[0137] Through the aforementioned closed-loop signaling interaction, the terminal officially exits the RRC connection state of the registration process in the core network CS domain, releases air interface resources, and enters the idle state or prepares to switch to the uplink and downlink frequency resources dedicated to IoT services, thus preparing the environment and resources for sending a fast registration request to the IoT platform.

[0138] According to some alternative embodiments of this application, sending a registration request message to the IoT platform within the frequency band corresponding to the uplink and downlink frequency resources can be achieved through the following steps: synchronizing and locking the radio frequency link according to the uplink and downlink frequency resources so that the IoT terminal and the IoT access point of the IoT platform are in frequency alignment; establishing a dedicated IoT channel matching the IoT platform according to the channel bandwidth requirements corresponding to the uplink and downlink frequency resources; and sending a registration request message to the IoT platform through the dedicated IoT channel.

[0139] In this embodiment, the terminal first performs a synchronization locking operation on the radio frequency link based on the uplink and downlink frequency resource parameters obtained from the core network. Specifically, the terminal adjusts its local oscillator frequency to align its receive and transmit carrier frequencies with the IoT access point on the IoT platform side, ensuring that both are in a precise frequency synchronization state. This synchronization process is particularly important for satellite communication because satellite links have a significant Doppler frequency shift, and the terminal needs to compensate for the frequency offset by locking a specific frequency point to ensure the reliability of subsequent signal transmission.

[0140] Secondly, based on the channel bandwidth requirements and time slot structure corresponding to the uplink and downlink frequency resources, the terminal establishes a dedicated IoT channel that matches the IoT platform. This dedicated IoT channel differs from the general service channels in traditional cellular networks; it is a physical channel specifically configured for TianTong IoT services (e.g., a dedicated data channel configured based on a 1+6+1 cycle). By configuring the baseband processing module, the terminal maps this dedicated channel to a locked radio frequency, thereby forming an independent data transmission path for the IoT platform.

[0141] Finally, the terminal sends a registration request message to the IoT platform via the established dedicated IoT channel. Since pre-authentication has already been completed through the core network CS domain, the registration request message sent by the terminal in this step only contains a temporary mobile subscriber identification code and a quick registration identifier. This message is transmitted directly to the IoT platform via the dedicated IoT channel, without needing to be relayed through the core network CS domain or undergo complex signaling interactions again. Upon receiving this message, the IoT platform, combined with the previously cached pre-authentication results, quickly completes the registration process and returns a registration acceptance message, thereby achieving efficient and low-latency access for IoT terminals in a satellite network environment.

[0142] The above process, through radio frequency synchronization locking based on dedicated frequency points and the establishment of dedicated channels, can achieve precise frequency alignment between the terminal and the IoT platform and rapid construction of independent data transmission channels, thereby avoiding the redundancy of traditional general signaling interaction, significantly reducing registration latency and improving the resource utilization of satellite channels.

[0143] In some optional embodiments of this application, before establishing a radio resource control connection with a base station, the following steps may be performed: configuring the hardware module of the IoT terminal to an active state by executing a function configuration instruction; in the active state, performing a cell search to obtain the synchronization information of the base station.

[0144] Furthermore, establishing a radio resource control connection with a base station can be achieved through the following steps: sending a radio resource control connection request to the base station on a random access channel; receiving a radio resource control connection establishment message sent by the base station on an access license channel; and sending a radio resource control connection establishment completion message to the base station through a dedicated access control channel to establish a radio resource control connection with the base station.

[0145] In this embodiment, before establishing a Radio Resource Control (RRC) connection with the base station, the IoT terminal first performs hardware initialization and network synchronization operations. Specifically, the terminal executes preset function configuration commands (such as AT+CFUN=5 and AT+CFUN=1 commands) to activate the IoT terminal's hardware modules, completing card activation, physical layer initialization, and radio frequency function configuration. After the hardware modules are activated, the terminal performs a cell search process, scanning available frequency points and obtaining the base station's synchronization information (including time synchronization and frequency synchronization parameters), thereby ensuring that the terminal can maintain accurate synchronization with the network side, laying the foundation for subsequent signaling interaction.

[0146] After synchronization is achieved, the terminal executes the RRC connection establishment procedure to establish a radio resource control (RRC) connection with the base station. First, the terminal sends a RRC connection request message to the base station on the random access channel (RACH). This message carries a establishment reason identifier to indicate the purpose of establishing the connection. Upon receiving the request, the base station sends a RRC connection establishment message to the terminal via the access grant channel (AGCH) or a dedicated control channel. This message contains the terminal's temporary identifier in the connected state and uplink resource grant information. After receiving this establishment message, the terminal returns a RRC connection establishment completion message to the base station via a dedicated access control channel (such as a dedicated service channel or dedicated control channel). At this point, the RRC connection between the terminal and the base station is formally established, and the terminal enters the RRC connected state, gaining the ability to transmit non-access stratum signaling, thus enabling it to execute subsequent core network CS domain registration and IoT platform pre-verification procedures.

[0147] As some optional embodiments of this application, the security authentication information includes: a pre-allocated authentication key; the device permission information includes at least one of the following: the frequency information of the IoT terminal uploading data to the IoT platform and the data range information that the IoT terminal is allowed to access.

[0148] In this embodiment, the security authentication information includes a pre-allocated authentication key. This authentication key is a fixed credential pre-allocated by the IoT platform and stored in the terminal's security module during the IoT terminal's production or network access configuration phase.

[0149] Device permission information includes at least one of the following: First, the frequency information of data uploaded by the IoT terminal to the IoT platform. This information is used to define the time interval or maximum frequency at which the terminal is allowed to report data, which helps the platform to perform resource scheduling and rate limiting management. Second, the information on the range of data that the IoT terminal is allowed to access. This information limits the permissions of specific business data items, device nodes or functional modules that the terminal can read, write or control, such as access permissions for specific sensor data or execution permissions for control commands.

[0150] By integrating the aforementioned security authentication information and device permission information into the extended fields during the registration phase of the core network CS domain, the IoT platform can simultaneously confirm the legitimacy of the terminal's identity and conduct a preliminary review of business permissions when receiving a pre-verification request forwarded by the core network. This enables rapid registration based on the pre-verification results, avoiding repeated signaling interactions for identity authentication and permission policy issuance during the subsequent registration phase, and significantly improving the access efficiency and security of IoT terminals.

[0151] In some optional embodiments of this application, after receiving the registration acceptance message sent by the IoT platform in response to the registration request message, the following steps may also be performed: sending a service activation confirmation message to the IoT platform, wherein the service activation confirmation message includes: the operating status parameters of the IoT terminal; starting a heartbeat timer, and performing keep-alive signaling interaction with the IoT platform according to a preset time period to maintain the validity of the registration status.

[0152] In this embodiment, after receiving the registration acceptance message, the terminal sends a service activation confirmation message to the IoT platform. This service activation confirmation message includes at least the IoT terminal's operating status parameters, which may include the terminal's current battery level, signal reception quality, operating mode (such as normal mode or power-saving mode), and device health status. By receiving this message, the IoT platform can monitor the terminal's operational status in real time, thereby providing a basis for decision-making in subsequent data distribution, command issuance, and device management.

[0153] In addition, to maintain the validity of the registration status and adapt to the dynamic changes in the satellite communication environment, the terminal starts a heartbeat timer. This timer triggers keep-alive signaling interactions according to a preset time period (e.g., a fixed interval determined based on terminal service requirements or network configuration). The terminal sends a brief status report to the IoT platform via keep-alive signaling to prove that the terminal is online and communicable; upon receiving the keep-alive signaling, the IoT platform updates the terminal's online status identifier. If the IoT platform does not receive the terminal's keep-alive signaling within a preset timeout period, it determines that the terminal is offline and clears the relevant registration context and resource reservations.

[0154] Through the above mechanism, IoT terminals can maintain the validity of their logical connection with the IoT platform even in areas with no satellite network coverage or weak signal, ensuring the continuity and reliability of IoT services.

[0155] Figure 4 This is a signaling interaction diagram of an IoT terminal registration process optimization method according to an embodiment of this application, such as... Figure 4 As shown, the specific steps are as follows:

[0156] Step 1: RACH:RRC Connection Request.

[0157] When the terminal is idle, it sends an RRC connection request message to the base station via the Random Access Channel (RACH). This message carries an Establishment Cause, indicating the purpose for which the terminal wishes to establish a connection (such as mobility management or IoT registration).

[0158] Step 2: AGCH:RRC Connection Setup.

[0159] Upon receiving the request, the base station sends an RRC connection establishment message to the terminal via the Access Grant Channel (AGCH) or a dedicated control channel. This message contains a temporary identifier (such as a Temporary Radio Identifier (TID) / C-RNTI) to be used by the terminal in subsequent communications, as well as uplink resource authorization information, indicating that the terminal can establish an RRC connection and is ready to receive subsequent instructions.

[0160] Step 3: DACCH: RRC Connection Setup Complete.

[0161] After confirming that the RRC layer parameters have been configured, the terminal sends an RRC connection establishment completion message to the base station via the Dedicated Access Control Channel (DACCH). At this point, the RRC connection between the terminal and the base station is officially established, and both parties enter the RRC connected state, enabling transparent transmission of higher-layer signaling (NAS signaling).

[0162] Step 4: DACCH: Initial DT (Dedicated Access Control Channel: Initial Direct Transmission, including IOT extension field).

[0163] The terminal sends an Initial Direct Transfer (InitialDT) message over the established RRC connection. This message encapsulates a Location Area Update (NA) request or similar signaling from the NAS layer, and its key innovation lies in extending the NAS signaling with IoT extended fields. These fields contain the IoT platform's access identifier, a pre-assigned authentication key, and device permission information (such as data upload frequency and access range). This allows the core network to obtain the information required by the IoT platform during the registration process.

[0164] Step 5: RANAP: Initial UE Message (RAN Application Part: Initial UE Message, including IoT extended fields).

[0165] The base station encapsulates the Initial DT message sent by the terminal into an Initial UE Message using the RANAP protocol and sends it to the core network CS domain (such as MSC or SGSN). This message contains the terminal's identity identifier (such as IMSI or old TMSI) and also includes IoT extension fields carried by the terminal, ensuring that IoT platform-related data can directly reach the core network processing module.

[0166] Step 6: Parse the IoT registration message.

[0167] After receiving the Initial UE Message, the signaling processing module in the core network CS domain parses the NAS signaling to complete the regular CS domain registration process, and extracts the IoT platform registration information (key, permissions, etc.) from the IoT extended fields.

[0168] Step 7: Transmit pre-verification information via a dedicated channel (SSL encrypted).

[0169] The core network CS domain sends the extracted IoT extended fields (pre-authentication information) to the IoT platform through a pre-established dedicated signaling transmission channel encrypted with SSL (Secure Sockets Layer). Encrypted transmission ensures the security of sensitive authentication keys and authorization information when transmitted between the core network and the IoT platform, preventing eavesdropping or tampering.

[0170] Step 8: Verification result confirmation.

[0171] After receiving the pre-verification information, the IoT platform performs preliminary identity verification and permission audit on the terminal based on its built-in key store and permission policies. Upon successful verification, the IoT platform temporarily stores the verification result (success flag and validity period) and may return confirmation information to the core network (or the core network may directly record this status). At this point, the soft registration on the IoT platform side is complete, eliminating the need for the terminal to initiate complex authentication interactions again.

[0172] Step 9: RANAP:DT (Authentication Request) (RANAP: Authentication Request).

[0173] The core network CS domain initiates two-way authentication with the terminal according to standard procedures. The core network generates an authentication challenge value and sends the authentication request via a Direct Transfer (DT) message using the RANAP protocol. This is a crucial step in ensuring the legitimacy of the terminal.

[0174] Step 10: DACCH:DT (Authentication Request).

[0175] The base station transparently transmits the authentication request issued by the core network to the terminal through the Dedicated Access Control Channel (DACCH).

[0176] Step 11: DACCH:DT (Authentication Response).

[0177] The terminal uses the stored key to calculate the challenge value, generates an authentication response, and sends it back to the base station via DACCH.

[0178] Step 12: RANAP:DT (Authentication Response).

[0179] The base station forwards the terminal's authentication response to the core network CS domain via the RANAP protocol. The core network verifies the response value; if they match, the terminal's identity is confirmed as legitimate.

[0180] Step 13: RANAP: Security Mode Command.

[0181] After successful authentication, the core network issues a security mode command, requiring the terminal to enable encryption and integrity protection.

[0182] Step 14: DACCH: Security Mode Command.

[0183] The base station transmits the security mode command to the terminal via DACCH.

[0184] Step 15: DACCH: Security Mode Complete.

[0185] The terminal confirms and enables the specified security mode, and sends a security mode completion message via DACCH, indicating that the terminal is ready for encrypted communication.

[0186] Step 16: RANAP: Security Mode Complete.

[0187] The base station forwards the terminal's security mode completion message to the core network, and the core network confirms that the security link has been established.

[0188] Step 17: RANAP:DT (LA Update Accept) (RANAP: Location Area Update Accept).

[0189] The core network sends a Location Area Update (MIB) receive message. This message contains the Temporary Mobile Subscriber Identity (TMSI) assigned to the terminal by the core network, as well as uplink and downlink frequency resource information specific to IoT services. The TMSI is a temporary identity identifier used by the terminal in subsequent communications, replacing the IMSI.

[0190] Step 18: DACCH:DT (LA Update Accept) (Radio Resource Control: Direct Transmission, including Location Area Update Accept Message).

[0191] The base station transparently transmits the Location Area Update Accept (LA Update Accept) message from the core network to the terminal via the Dedicated Access Control Channel (DACCH) using the Radio Resource Control Protocol. Upon receiving this message, the terminal completes CS domain registration and obtains the TMSI and frequency resources.

[0192] Step 19: RANAP:DT (LA Update Reject) (RANAP: Location Area Update Reject).

[0193] This is a branching step. If core network verification fails or resources are insufficient, a rejection message is sent. If this path is entered, the process will jump to step 20, causing registration failure. The terminal may need to retry or enter other processing procedures.

[0194] Step 20: DACCH:DT (LA Update Reject).

[0195] If a rejection occurs, the base station will transmit this message to the terminal, and the terminal will stop the subsequent registration process upon receiving it.

[0196] Step 21: RANAP: Iu Release Command (RANAP: Iu port release command).

[0197] After successful CS domain registration (steps 17 / 18), the core network considers the NAS signaling interaction of the CS domain to be completed, initiates the Iu interface release command, and prepares to release the Iu connection resources with the base station.

[0198] Step 22: RANAP: Iu Release Complete (RANAP: Iu port release complete).

[0199] The base station responded that Iu release was complete, confirming that the logical connection of the Iu interface had been disconnected.

[0200] Step 23: DACCH: RRC Connection Release.

[0201] The base station sends an RRC connection release message to the terminal. The RRC connection release message instructs the terminal to disconnect the current RRC connection and enter Idle Mode. At this time, the terminal holds TMSI and frequency resources, but the air interface radio resources are released.

[0202] Step 24: DACCH: RRC Connection Release Complete.

[0203] The terminal confirms that the RRC connection has been released and replies with a completion message. At this point, the core network signaling interaction phase between the terminal and the base station ends, and the terminal prepares to switch to the IoT service channel.

[0204] Step 25: DBCCH: IOT DBCCH REQ (Dedicated Broadcast Control Channel: IoT DBCCH Request).

[0205] Based on the frequency resources obtained in step 17, the terminal switches to the dedicated Internet of Things Broadcast Control Channel (DBCCH) and sends a request message indicating that the terminal wishes to access the Internet of Things platform and requests the allocation of dedicated data channel resources.

[0206] Step 26: DBCCH: IOT DBCCH IND (Dedicated Broadcast Control Channel: IoT DBCCH Indicator).

[0207] When an IoT access point (or base station) responds to a request, it sends an instruction message via DBCCH, allowing the terminal to use a specific uplink frequency or time slot for subsequent data transmission.

[0208] Step 27: DRACH: IOT REGISTER REQ (Dedicated Data Random Access Channel: IoT Registration Request, TMSI+ Fast Registration Identifier Only).

[0209] The terminal sends an IoT registration request on the assigned uplink frequency (DRACH). Unlike traditional methods, this message only contains the TMSI obtained in step 17 and a fast registration identifier (indicating that this is a fast registration based on pre-verification). Since the IoT platform has already completed pre-verification in step 8, there is no need to send complex authentication vectors or challenge responses here, greatly simplifying the signaling volume.

[0210] Step 28: DAGCH:IOT REGISTER ACCEPT (Dedicated Access Control Channel: IoT registration accepted, registration completed directly).

[0211] Upon receiving the simplified registration request, the IoT platform queries the cached pre-verification results. If everything is correct, it directly returns an IoT REGISTER ACCEPT message via the downlink channel (DAGCH). Once the terminal receives this message, it is considered to have successfully registered on the IoT platform and can begin normal IoT business data interaction.

[0212] The following section uses the TianTong IoT terminal for remote monitoring of smart grids as an example to explain in detail the specific implementation method of the IoT terminal registration process optimization method.

[0213] Core Network CS Domain Registration Extended Signaling Interaction: After the terminal powers on, it executes the AT+CFUN=5 and AT+CFUN=1 commands to complete hardware activation and function configuration, followed by cell search and establishment of an RRC connection. During the NAS layer signaling interaction phase, an extended field is added to the mobility management information (MM information) sent by the terminal. This field contains the unique access identifier of the IoT platform, the pre-allocated authentication key (an encryption key used for IoT platform authentication), and device permission information (such as data upload frequency, accessible monitoring data range, etc.). After receiving this signaling, the network side's signaling processing module first processes the core network CS domain registration information, completing mobility management, two-way authentication, and identity recognition operations to confirm the terminal's legitimate access to the core network CS domain. Simultaneously, it extracts the IoT platform registration information from the extended field and sends it to the power company's IoT platform through a dedicated signaling transmission channel. The dedicated signaling transmission channel uses SSL encryption protocol and CRC check mechanism to ensure the security and accuracy of information transmission.

[0214] IoT Platform Pre-verification: After receiving the terminal registration information from the network side, the IoT platform initiates the pre-verification process. Based on the received authentication key and device permission information, it performs preliminary identity verification and permission review of the terminal. Upon successful pre-verification, the IoT platform temporarily stores the verification result and awaits the terminal's formal registration request.

[0215] Terminal Fast Registration: After completing core network CS domain registration and obtaining the TMSI identifier and dedicated uplink and downlink frequency resources for IoT services, the terminal sends a registration request to the IoT platform. At this point, the registration request signaling contains only the terminal identifier and a fast registration identifier, indicating that the request is based on previously pre-verified fast registration. Upon receiving the request, the IoT platform quickly completes the registration operation based on the previous pre-verification results and returns an IOT_REGISTER_ACCEPT message to the terminal. Compared to traditional methods, this registration process reduces a significant amount of repetitive authentication and identification signaling interactions, substantially lowering the air interface signaling load.

[0216] The above process innovatively integrates the NAS layer signaling of core network CS domain registration and IoT platform registration. By expanding the signaling content of core network CS domain registration, it achieves a new signaling interaction mode of "one-time authentication, two-layer registration," reducing the number of signaling interaction rounds and redundant transmissions. A dedicated signaling processing module and transmission channel are established on the network side to achieve collaborative signaling processing and pre-verification between the core network CS domain and the IoT platform, ensuring efficient and secure signaling transmission between the two platforms. A rapid registration process for terminals based on pre-verification results is designed, simplifying the registration request signaling content and enabling rapid terminal access to the IoT platform.

[0217] Figure 5 This is a structural diagram of an IoT terminal registration process optimization device according to an embodiment of this application, such as... Figure 5 As shown, the device includes:

[0218] Module 51 is established to establish a wireless resource control connection with the base station.

[0219] The first sending module 52 is used to send mobility management information to the core network through the radio resource control connection during the non-access stratum signaling interaction phase. The mobility management information includes a location area update request and extended fields. The extended fields include IoT platform registration information, security authentication information, and device permission information. The IoT platform registration information is used to instruct the IoT platform to start the verification process. The verification process includes verifying the IoT terminal based on the security authentication information and device permission information, and obtaining a pre-verification result.

[0220] The first receiving module 53 is used to receive the location area update result sent by the core network after authentication and security mode negotiation with the core network. The location area update result includes: temporary mobile subscriber identification code and uplink and downlink frequency resources dedicated to IoT services.

[0221] Release module 54 is used to release the radio resource control connection based on the location area update result.

[0222] The second sending module 55 is used to send a registration request message to the Internet of Things platform in the frequency band corresponding to the uplink and downlink frequency resources after releasing the radio resource control connection. The registration request message includes a temporary mobile subscriber identification code and a registration identifier. The temporary mobile subscriber identification code and the registration identifier together indicate that the registration request message is a registration request based on the pre-verification result.

[0223] The second receiving module 56 is used to receive a registration acceptance message sent by the IoT platform in response to the registration request message, wherein the registration acceptance message is sent when the registration operation is completed based on the pre-verification result.

[0224] It should be noted that the above Figure 5 The modules in the above can be program modules (e.g., a set of program instructions that implement a specific function) or hardware modules. For the latter, they can be represented in the following forms, but are not limited to these: each of the above modules is represented by a processor, or the functions of each of the above modules are implemented by a processor.

[0225] It should be noted that, Figure 5 Preferred embodiments of the shown examples can be found in [reference needed]. Figure 1 The relevant descriptions of the embodiments shown will not be repeated here.

[0226] Figure 6 A hardware block diagram of a computer terminal for implementing an optimization method for the registration process of Internet of Things (IoT) terminals is shown. Figure 6 As shown, the computer terminal 60 may include one or more processors 602 (shown as 602a, 602b, ..., 602n in the figure) 602 (processor 602 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 604 for storing data, and a transmission module 606 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 6 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, the computer terminal 60 may also include... Figure 6 The more or fewer components shown, or having the same Figure 6 The different configurations shown.

[0227] It should be noted that the aforementioned one or more processors 602 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 60. As described in the embodiments of this application, the data processing circuits serve as processor control (e.g., selection of a variable resistor termination path connected to an interface).

[0228] The memory 604 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the IoT terminal registration process optimization method in this embodiment. The processor 602 executes various functional applications and data processing by running the software programs and modules stored in the memory 604, thereby realizing the aforementioned IoT terminal registration process optimization method. The memory 604 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 604 may further include memory remotely located relative to the processor 602, and these remote memories can be connected to the computer terminal 60 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0229] The transmission module 606 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 60. In one example, the transmission module 606 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission module 606 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0230] The display may be, for example, a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the computer terminal 60.

[0231] It should be noted here that, in some optional embodiments, the above... Figure 6 The computer terminal shown may include hardware elements (including circuitry), software elements (including computer code stored on a computer-readable medium), or a combination of both hardware and software elements. It should be noted that... Figure 6 This is only one instance of a specific particular instance, and is intended to illustrate the types of components that may exist in the aforementioned computer terminal.

[0232] It should be noted that, Figure 6 The computer terminal shown is used to execute Figure 1 The IoT terminal registration process optimization method shown above also applies to this electronic device, and will not be repeated here.

[0233] This application embodiment also provides a non-volatile storage medium, which includes a stored program, wherein the program, when running, controls the device where the storage medium is located to execute the above-mentioned IoT terminal registration process optimization method.

[0234] The non-volatile storage medium performs the following functions: establishing a radio resource control (RRC) connection with the base station; during the non-access stratum signaling interaction phase, sending mobility management information to the core network via the RRC connection, wherein the mobility management information includes: a location area update request and extended fields, the extended fields including: IoT platform registration information, security authentication information, and device permission information; the IoT platform registration information is used to instruct the IoT platform to initiate the verification process, the verification process including: verifying the IoT terminal based on the security authentication information and device permission information, and obtaining a pre-verification result; after completing authentication and security mode negotiation with the core network, receiving the location area update result sent by the core network, wherein... The location area update result includes: a temporary mobile subscriber identification code and uplink / downlink frequency resources dedicated to IoT services; based on the location area update result, the radio resource control connection is released; after releasing the radio resource control connection, a registration request message is sent to the IoT platform within the frequency band corresponding to the uplink / downlink frequency resources, wherein the registration request message includes: a temporary mobile subscriber identification code and a registration identifier, the temporary mobile subscriber identification code and the registration identifier together indicate that the registration request message is a registration request based on the pre-verification result; and the registration acceptance message sent by the IoT platform in response to the registration request message is received, wherein the registration acceptance message is sent after the registration operation is completed based on the pre-verification result.

[0235] This application also provides an electronic device, including: a memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the program executes the above-described IoT terminal registration process optimization method during runtime.

[0236] The processor runs programs that perform the following functions: establishing a radio resource control (RRC) connection with the base station; during the non-access stratum signaling interaction phase, sending mobility management information to the core network via the RRC connection, wherein the mobility management information includes: a location area update request and extended fields, the extended fields including: IoT platform registration information, security authentication information, and device permission information; the IoT platform registration information is used to instruct the IoT platform to initiate a verification process, the verification process including: verifying the IoT terminal based on the security authentication information and device permission information, and obtaining a pre-verification result; and, after completing authentication and security mode negotiation with the core network, receiving the location area update result sent by the core network, wherein... The location area update result includes: a temporary mobile subscriber identification code and uplink / downlink frequency resources dedicated to IoT services; based on the location area update result, the radio resource control connection is released; after releasing the radio resource control connection, a registration request message is sent to the IoT platform within the frequency band corresponding to the uplink / downlink frequency resources, wherein the registration request message includes: a temporary mobile subscriber identification code and a registration identifier, the temporary mobile subscriber identification code and the registration identifier together indicate that the registration request message is a registration request based on the pre-verification result; and the registration acceptance message sent by the IoT platform in response to the registration request message is received, wherein the registration acceptance message is sent after the registration operation is completed based on the pre-verification result.

[0237] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

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

[0239] In the above embodiments of this application, the information collected is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data all comply with relevant laws, regulations and standards, take necessary protective measures, do not violate public order and good morals, and provide corresponding operation entry points for users to choose to authorize or refuse.

[0240] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0241] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0242] 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. The integrated unit can be implemented in hardware or as a software functional unit.

[0243] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to related technologies, 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, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0244] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for optimizing the registration process of Internet of Things (IoT) terminals, characterized in that, include: Establish a wireless resource control connection with the base station; During the non-access stratum signaling interaction phase, mobility management information is sent to the core network through the radio resource control connection. The mobility management information includes a location area update request and extended fields. The extended fields include IoT platform registration information, security authentication information, and device permission information. The IoT platform registration information is used to instruct the IoT platform to initiate a verification process. The verification process includes verifying the IoT terminal based on the security authentication information and the device permission information, and obtaining a pre-verification result. After completing authentication and security mode negotiation with the core network, the location area update result sent by the core network is received, wherein the location area update result includes: temporary mobile subscriber identification code and uplink and downlink frequency resources dedicated to IoT services; Based on the location area update result, release the radio resource control connection; After releasing the wireless resource control connection, a registration request message is sent to the IoT platform within the frequency band corresponding to the uplink and downlink frequency resources. The registration request message includes: the temporary mobile subscriber identification code and the registration identifier. The temporary mobile subscriber identification code and the registration identifier together indicate that the registration request message is a registration request based on the pre-verification result. The system receives a registration acceptance message sent by the IoT platform in response to the registration request message, wherein the registration acceptance message is sent after the registration operation is completed based on the pre-verification result.

2. The method according to claim 1, characterized in that, Receiving the location area update result sent by the core network includes: The system receives a Radio Resource Control (RRC) direct transmission message sent by the core network, wherein the RRC direct transmission message includes at least: a Location Area Update (LAC) Accept message; the Temporary Mobile Subscriber Identity (TMS) identifier; and the uplink / downlink frequency resources located in the cell field of the LAC Accept message.

3. The method according to claim 1, characterized in that, Based on the location area update result, releasing the radio resource control connection includes: Verify whether the temporary mobile subscriber identification code and the uplink / downlink frequency resources in the location area update result meet the preset requirements; If the verification is successful, the radio resource control release message issued by the base station is received via a dedicated access control channel; wherein, the radio resource control release message is triggered by the base station after completing the release of the interface connection with the core network; After receiving the radio resource control release message, a radio resource control release completion message is returned to the base station to complete the release of the radio resource control connection.

4. The method according to claim 1, characterized in that, Within the frequency bands corresponding to the uplink and downlink frequency resources, a registration request message is sent to the IoT platform, including: Synchronization locking of the radio frequency link is performed based on the uplink and downlink frequency resources to ensure that the IoT terminal and the IoT access point of the IoT platform are in frequency alignment. Based on the channel bandwidth requirements corresponding to the uplink and downlink frequency resources, a dedicated IoT channel matching the IoT platform is established. The registration request message is sent to the IoT platform through the dedicated IoT channel.

5. The method according to claim 1, characterized in that, Before establishing a radio resource control connection with the base station, the method further includes: By executing the function configuration command, the hardware module of the IoT terminal is configured to be in an active state; In the activated state, a cell search is performed to obtain the synchronization information of the base station; Establishing a radio resource control connection with the base station includes: Send a radio resource control connection request to the base station on the random access channel; Receive the radio resource control connection establishment message sent by the base station on the access permission channel; The system sends a Radio Resource Control (RRC) connection establishment completion message to the base station via a dedicated access control channel to establish the RRC connection with the base station.

6. The method according to claim 1, characterized in that, The security authentication information includes: a pre-assigned authentication key; the device permission information includes at least one of the following: the frequency information of the IoT terminal uploading data to the IoT platform and the data range information that the IoT terminal is allowed to access.

7. The method according to claim 1, characterized in that, After receiving the registration acceptance message sent by the IoT platform in response to the registration request message, the method further includes: Send a service activation confirmation message to the IoT platform, wherein the service activation confirmation message includes: the operating status parameters of the IoT terminal; A heartbeat timer is started, and keep-alive signaling is exchanged with the IoT platform according to a preset time period to maintain the validity of the registration status.

8. An IoT terminal registration process optimization device, characterized in that, include: Establishment module, used to establish a radio resource control connection with the base station; The first sending module is used to send mobility management information to the core network through the radio resource control connection during the non-access stratum signaling interaction phase. The mobility management information includes a location area update request and extended fields. The extended fields include IoT platform registration information, security authentication information, and device permission information. The IoT platform registration information is used to instruct the IoT platform to initiate a verification process. The verification process includes verifying the IoT terminal based on the security authentication information and the device permission information, and obtaining a pre-verification result. The first receiving module is used to receive the location area update result sent by the core network after authentication and security mode negotiation are completed with the core network. The location area update result includes: temporary mobile subscriber identification code and uplink and downlink frequency resources dedicated to IoT services. A release module is used to release the radio resource control connection based on the location area update result; The second sending module is used to send a registration request message to the Internet of Things platform in the frequency band corresponding to the uplink and downlink frequency point resources after releasing the radio resource control connection. The registration request message includes: the temporary mobile subscriber identification code and the registration identifier. The temporary mobile subscriber identification code and the registration identifier together indicate that the registration request message is a registration request based on the pre-verification result. The second receiving module is used to receive a registration acceptance message sent by the IoT platform in response to the registration request message, wherein the registration acceptance message is sent when the registration operation is completed based on the pre-verification result.

9. A non-volatile storage medium, characterized in that, The non-volatile storage medium includes a stored program, wherein, when the program is executed, it controls the device where the non-volatile storage medium is located to execute the IoT terminal registration process optimization method according to any one of claims 1 to 7.

10. An electronic device, characterized in that, include: A memory and a processor, the processor being configured to run a program stored in the memory, wherein the program, when running, executes the IoT terminal registration process optimization method according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the IoT terminal registration process optimization method according to any one of claims 1 to 7.

Images