Satellite terminal access management method and system based on GMR

Abstract

The invention discloses a satellite terminal access management method and system based on GMR. The method comprises the following steps: a satellite communication access network establishes an RRC connection with a terminal; receiving a location update request message carrying terminal location information sent by the terminal, the terminal location information being acquired by the terminal before establishing an RRC connection with the satellite communication access network; sending an initial terminal information message carrying the terminal position information to a core network; responding to access permission information fed back by the core network under the condition that the core network determines that the terminal is located in a preset emergency guarantee communication area based on the terminal position information, and accessing the terminal to the core network; and in response to access refusing information fed back by the core network under the condition that the terminal is determined not to be in the preset emergency guarantee communication area based on the terminal position information, refusing the terminal to access the core network. The technical problem that an existing terminal position reporting scheme cannot be suitable for an emergency guarantee communication scene is solved.

Description

Technical Field

[0001] This application relates to the field of satellite communication technology, and more specifically, to a satellite terminal access management method and system based on GMR. Background Technology

[0002] In today's society, satellite terminal access management systems based on GMR (Geostationary Earth Orbit-Mobile Radio) have become an important means of ensuring communication in special environments such as remote areas, maritime navigation, and emergency rescue. Especially for emergency support needs, such as communication recovery after natural disasters and large-scale accidents, operators have proposed the concept of backup communication, aiming to ensure basic communication services using satellite networks even when terrestrial networks fail, facilitating rescue command and information transmission. However, traditional GMR-based satellite terminal access management systems have shortcomings in terminal access control, which directly affects the efficiency and resource allocation of emergency backup communication.

[0003] Currently, in the GMR satellite communication protocol, terminal location updates mainly occur during the random access procedure or are triggered by the network itself. During random access, the terminal reports its relative location information to the access network via an RRC (Radio Resource Control) connection request message, but this information does not directly reach the core network. The process of the network actively querying location information is more cumbersome, requiring the access network to query the terminal, the terminal to locate itself, and then report its location back to the access network via a location reporting message. Finally, the access network forwards this information to the core network. While this process is reliable, the late triggering of the access network's location query, typically after the terminal has initiated a location update request, not only increases latency but also requires additional air interface signaling exchanges, unnecessarily consuming already limited satellite communication resources. Furthermore, according to the GMR protocol, the access network does not directly transmit the terminal identifier to the core network, resulting in a blind spot in the core network's terminal access control, preventing real-time resource allocation and scheduling based on location information.

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

[0005] This application provides a satellite terminal access management method and system based on GMR, which at least solves the technical problem that existing terminal location reporting schemes cannot be applied to emergency backup communication scenarios.

[0006] According to one aspect of the embodiments of this application, a satellite terminal access management method based on GMR is provided, comprising: establishing an RRC connection between a satellite communication access network and a terminal; receiving a location update request message carrying terminal location information sent by the terminal, wherein the terminal location information is obtained by the terminal before establishing an RRC connection with the satellite communication access network; sending an initial terminal information message carrying terminal location information to a core network; in response to an access permission message fed back by the core network when it determines that the terminal is located within a preset emergency backup communication area based on the terminal location information, allowing the terminal to access the core network; and in response to an access denial message fed back by the core network when it determines that the terminal is not within the preset emergency backup communication area based on the terminal location information, denying the terminal access to the core network.

[0007] Optionally, the location update request message includes: a relative location optional information cell, wherein the information cell identifier of the relative location optional information cell is a 1-byte preset identifier; when the information cell format of the relative location optional information cell is a tag-value format, the information cell length of the relative location optional information cell is 5 bytes, wherein the first byte is the information cell identifier, the second and third bytes are the relative latitude of the terminal relative to the preset reference latitude, and the fourth and fifth bytes are the relative longitude of the terminal relative to the preset reference longitude; when the information cell format of the relative location optional information cell is a tag-length-value format, the information cell length of the relative location optional information cell is 6 bytes, wherein the first byte is the information cell identifier, the second byte is the information cell length, the third and fourth bytes are the relative latitude, and the fifth and sixth bytes are the relative longitude.

[0008] Optionally, the location update request message includes: a GPS location optional cell; wherein, the cell identifier of the GPS location optional cell is a 1-byte preset identifier, the cell format is a tag-value format, and the cell length is 6 bytes; the eighth bit of the first byte of the GPS location optional cell is 0, the seventh bit to the first bit of the first byte is the cell identifier, the eighth bit of the second byte is the current positioning indication, the seventh bit to the first bit of the second byte, the eighth bit to the fifth bit of the third byte, and the fourth bit to the first bit of the fourth byte are the GPS latitude of the terminal, and the fourth bit to the first bit of the fourth byte, the fifth byte, and the sixth byte are the GPS longitude of the terminal.

[0009] Optionally, establishing an RRC connection with the terminal includes: receiving an RRC connection request message sent by the terminal; sending an RRC connection establishment message to the terminal; and receiving an RRC connection establishment completion message sent by the terminal.

[0010] Optionally, in response to the access permission information fed back by the core network when it determines that the terminal is located within a preset emergency backup communication area based on the terminal location information, the terminal is connected to the core network, including: receiving an authentication request message sent by the core network and sending the authentication request message to the terminal; receiving an authentication response message sent by the terminal and sending the authentication response message to the core network; receiving a security mode command message sent by the core network and sending the security mode command message to the terminal; receiving a security mode completion message sent by the terminal and sending the security mode completion message to the core network; and receiving a location update acceptance message from the core network and sending the location update acceptance message to the terminal.

[0011] Optionally, in response to the access denial information fed back by the core network when it determines that the terminal is not in the preset emergency backup communication area based on the terminal location information, the terminal is denied access to the core network, including: receiving the location update denial message sent by the core network and sending the location update denial message to the terminal.

[0012] Optionally, during the process of connecting a terminal to the core network or denying a terminal access to the core network, all transmitted messages are transmitted based on direct transmission signaling, which is used to transmit non-access stratum data.

[0013] According to another aspect of the embodiments of this application, another satellite terminal access management method based on GMR is provided, including: the terminal acquiring terminal location information; establishing an RRC connection with the satellite communication access network; sending a location update request message carrying terminal location information to the satellite communication access network; receiving access permission information relayed by the satellite communication access network from the core network when the terminal is determined to be located within a preset emergency backup communication area based on the terminal location information; or receiving access denial information relayed by the satellite communication access network from the core network when the terminal is determined to be located outside the preset emergency backup communication area based on the terminal location information.

[0014] According to another aspect of the embodiments of this application, another satellite terminal access management method based on GMR is provided, including: a core network receiving an initial terminal information message carrying terminal location information sent by a satellite communication access network, wherein the initial terminal information message is generated by the satellite communication access network based on terminal location information obtained by the terminal before establishing an RRC connection with the satellite communication access network, carried in a location update request message from the terminal; determining whether the terminal is located within a preset emergency backup communication area based on the terminal location information; if the terminal is located within the emergency backup communication area, feeding back access permission information to the satellite communication access network to instruct the satellite communication access network to access the terminal to the core network; if the terminal is not located within the emergency backup communication area, feeding back access denial information to the satellite communication access network to instruct the satellite communication access network to deny the terminal access to the core network.

[0015] According to another aspect of the embodiments of this application, a satellite terminal access management system based on GMR is also provided, including: a terminal, a satellite communication access network, and a core network, wherein the terminal is used to obtain its own terminal location information; establish an RRC connection with the satellite communication access network; and send a location update request message carrying the terminal location information to the satellite communication access network; the satellite communication access network is used to send an initial terminal information message carrying the terminal location information to the core network; the core network is used to determine whether the terminal is located within a preset emergency backup communication area based on the terminal location information, and if the terminal is located within the emergency backup communication area, to send access permission information to the satellite communication access network, and if the terminal is not located within the emergency backup communication area, to send access denial information to the satellite communication access network; the satellite communication access network is also used to respond to the access permission information and allow the terminal to access the core network; and respond to the access denial information and refuse the terminal from accessing the core network.

[0016] According to another aspect of the embodiments of this application, a computer program product is also provided, the computer program product comprising: a computer program, wherein the computer program, when executed by a processor, implements the above-described GMR-based satellite terminal access management method.

[0017] According to another aspect of the embodiments of this application, an electronic device is also provided, the electronic device including: a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the above-described GMR-based satellite terminal access management method through the computer program.

[0018] In this embodiment, the terminal triggers a positioning process in advance to obtain its own latitude and longitude information before initiating random access, saving time spent waiting for positioning. By adding optional information elements to the communication protocol, the terminal can directly carry its own latitude and longitude information in the location update request message and report this information to the core network via the access network. This process optimizes latency by reporting latitude and longitude information in advance and eliminates the need for additional queries and reporting of air interface messages, thus optimizing resource utilization. The core network can determine whether the terminal is within the emergency backup communication area based on the terminal's latitude and longitude information, and allow or deny the terminal's access based on the determination result, thus fulfilling the emergency backup communication requirement. This application effectively solves the technical problem that existing terminal location reporting schemes are not applicable to emergency backup communication scenarios. Attached Figure Description

[0019] 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:

[0020] Figure 1This is a schematic diagram of an optional GMR-based satellite terminal access management system according to an embodiment of this application;

[0021] Figure 2 This is a schematic diagram of signaling interaction in an optional GMR-based satellite terminal access management system according to an embodiment of this application;

[0022] Figure 3 This is a flowchart illustrating an optional GMR-based satellite terminal access management method according to an embodiment of this application.

[0023] Figure 4 This is a flowchart illustrating another optional GMR-based satellite terminal access management method according to an embodiment of this application;

[0024] Figure 5 This is a flowchart illustrating another optional GMR-based satellite terminal access management method according to an embodiment of this application;

[0025] Figure 6 This is a schematic diagram of the structure of an optional electronic device according to an embodiment of this application. Detailed Implementation

[0026] 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.

[0027] It should be noted that the terms "first," "second," etc., used in the specification, claims, and 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.

[0028] Example 1

[0029] To meet the communication requirements of operators for emergency backup communication scenarios, this application provides a satellite terminal access management system based on GMR, such as... Figure 1 As shown, the system includes at least: a terminal 11, a satellite communication access network 12, and a core network 13. The terminal 11 can be a Mobile Earth Station (MES). The functions of each module in this system are as follows:

[0030] Terminal 11 is used to obtain its own terminal location information; establish an RRC connection with the satellite communication access network 12; and send a location update request message carrying the terminal location information to the satellite communication access network 12.

[0031] Satellite communication access network 12 is used to send an initial terminal information message carrying terminal location information to core network 13;

[0032] Core network 13 is used to determine whether terminal 11 is located within a preset emergency backup communication area based on terminal location information. If terminal 11 is located within the emergency backup communication area, it sends an access permission message to satellite communication access network 12. If terminal 11 is not located within the emergency backup communication area, it sends an access denial message to satellite communication access network 12.

[0033] The satellite communication access network 12 is also used to respond to access permission information to allow terminal 11 to access the core network 13; and to respond to access denial information to deny terminal 11 access to the core network 13.

[0034] In this system, before initiating random access, the terminal triggers a positioning process in advance to obtain its own latitude and longitude information, which can save the time of waiting for positioning. By adding optional information elements to the communication protocol, the terminal can directly carry its own latitude and longitude information in the location update request message and report this information to the core network through the access network. This process optimizes latency by reporting latitude and longitude information in advance and does not require additional querying and reporting of air interface messages, thus optimizing resource utilization. The core network can determine whether the terminal is within the emergency backup communication area based on the terminal's latitude and longitude information, and allow or deny the terminal access according to the judgment result, so as to realize the emergency backup communication requirements.

[0035] The following section describes the interaction methods of each module in the GMR-based satellite terminal access management system, using a specific implementation process as an example.

[0036] According to GMR protocols, whether the network actively queries the terminal's location or the terminal autonomously reports its location, the terminal only triggers the positioning process after establishing an RRC connection with the satellite communication access network. After completing the positioning, the terminal then reports its location information to the satellite communication access network. Since positioning takes time, and time is crucial in emergency backup communication scenarios, this application proposes a scheme to pre-trigger the positioning process before initiating random access, thus saving waiting time for positioning.

[0037] As an optional implementation, before establishing an RRC connection with the satellite communication access network, the terminal's built-in Modem chip can interact with the GPS (Global Positioning System) module to obtain the terminal's current location information, specifically its current latitude and longitude information.

[0038] Subsequently, an RRC connection between the terminal and the satellite communication access network can be established in the following way: the terminal sends an RRC connection request message to the satellite communication access network, the satellite communication access network sends an RRC connection establishment message to the terminal, and after the terminal completes the RRC connection configuration, it sends an RRC connection establishment completion message back to the satellite communication access network.

[0039] According to GMR-related protocols, the network-initiated location query process is triggered relatively late, typically after receiving a location update request message from the terminal, or even after the terminal has completed the entire location update process. Furthermore, this process requires additional downlink query messages over the air interface. To shorten terminal access time and conserve air interface resources, this application embodiment makes certain adjustments to the information elements in the existing location update request message, enabling the terminal to carry its own location information in the sent location update request message without needing to subsequently respond to a location query message from the access network before reporting its own location.

[0040] As an optional implementation, a GPS location optional information element can be added to the location update request message. The information element identifier of the GPS location optional information element is a 1-byte preset identifier, such as 0xxx, the information element format is tag-value format, and the information element length is 6 bytes. An optional structure definition of the location update request message is shown in Table 1.

[0041] Table 1

[0042]

[0043] Optionally, the eighth bit of the first byte of the GPS location selectable cell is 0, the seventh bit to the first bit of the first byte is the cell identifier, the eighth bit of the second byte is the current positioning indication, the seventh bit to the first bit of the second byte, the eighth bit to the fifth bit of the third byte and the fourth bit are the GPS latitude of the terminal, and the fourth bit to the first bit of the fourth byte, the fifth byte and the sixth byte are the GPS longitude of the terminal. The specific structure is shown in Table 2.

[0044] Table 2

[0045]

[0046] To further improve information transmission efficiency, this application also proposes a scheme to replace the aforementioned GPS location with the terminal's relative location. Specifically, the relative latitude of the terminal's GPS latitude relative to a preset reference latitude can be determined, and the relative longitude of the terminal's GPS longitude relative to a preset reference longitude can be determined. The relative latitude and relative longitude are carried in the newly added information cell to reduce the size of the location update request message.

[0047] As an optional implementation, a relative location optional information element can be added to the location update request message. The information element identifier for the relative location optional information element is a 1-byte preset identifier, such as 0x1A.

[0048] The relative position optional information element can also be formatted as a label-length-value, as shown in Table 3. It should be noted that the structures of other mandatory information elements in the location update request message are the same as in Table 1, and will not be repeated here.

[0049] Table 3

[0050]

[0051] In this case, the cell length of the relative position selectable cell is 6 bytes. The first byte is the cell identifier, the second byte is the cell length, the third and fourth bytes are the relative latitude, and the fifth and sixth bytes are the relative longitude. The specific structure is shown in Table 4.

[0052] Table 4

[0053]

[0054] Optionally, the relative position optional information element can also be in label-value format, as shown in Table 5. The structures of other required information elements in the location update request message are the same as those in Table 1, and will not be repeated here.

[0055] Table 5

[0056]

[0057] In this case, the cell length of the relative position optional cell is shorter, only 5 bytes. The first byte is the cell identifier, the second and third bytes are the relative latitude, and the fourth and fifth bytes are the relative longitude. The specific structure is shown in Table 6.

[0058] Table 6

[0059]

[0060] After receiving a location update request message carrying the terminal's location information from a terminal, the satellite communication access network can send an initial terminal information message carrying the terminal's location information to the core network.

[0061] After receiving the initial terminal information message, the core network can determine whether the terminal is located within the preset emergency backup communication area based on the terminal location information carried in the message.

[0062] Optionally, when the terminal is located within the emergency backup communication area, the core network can send access permission information back to the satellite communication access network to instruct the satellite communication access network to connect the terminal to the core network. An optional terminal access process is as follows: the satellite communication access network receives an authentication request message from the core network and sends the authentication request message to the terminal; it receives an authentication response message from the terminal and sends the authentication response message to the core network; it receives a security mode command message from the core network and sends the security mode command message to the terminal; it receives a security mode completion message from the terminal and sends the security mode completion message to the core network; and it receives a location update acceptance message from the core network and sends the location update acceptance message to the terminal.

[0063] Optionally, if the terminal is not within the emergency backup communication area, the core network can send an access denial message to the satellite communication access network to instruct the satellite communication access network to deny the terminal access to the core network. One possible process for denying terminal access is as follows: the satellite communication access network receives the location update denial message sent by the core network and sends the location update denial message to the terminal.

[0064] Optionally, whether connecting a terminal to the core network or denying a terminal access to the core network, all transmitted messages are transmitted based on DT (Direct Transfer) signaling, which is used to transmit NAS (Non-Access Stratum) data.

[0065] Figure 2 A schematic diagram of signaling interaction in a complete GMR-based satellite terminal access management system is shown, including the following steps:

[0066] S1, the terminal obtains its own location information;

[0067] S2, the terminal sends an RRC Connection Request message to the satellite communication access network;

[0068] S3, The satellite communication access network sends an RRC Connection Setup message to the terminal;

[0069] S4, the terminal sends an RRC connection setup complete message (RRC Connection SetupComplete) to the satellite communication access network.

[0070] S5, the terminal sends an Initial DT (Location Update Request) message carrying the terminal's location information to the satellite communication access network.

[0071] S6, the satellite communication access network sends an Initial UE Message carrying terminal location information to the core network;

[0072] S7, the core network determines whether the terminal is located in the preset emergency backup communication area based on the terminal location information. If yes, continue to execute S8; otherwise, jump to execute S18.

[0073] S8, the core network sends an authentication request message (DT) to the satellite communication access network.

[0074] S9, the satellite communication access network sends an authentication request message (DT) to the terminal.

[0075] S10, the terminal sends an authentication response message DT to the satellite communication access network;

[0076] S11, the satellite communication access network sends an authentication response message DT (AuthenticationResponse) to the core network.

[0077] S12, the core network sends a Security Mode Command (DT) message to the satellite communication access network.

[0078] S13, the satellite communication access network sends a security mode command message DT (Security ModeCommand) to the terminal.

[0079] S14, the terminal sends a Security Mode Complete message (DT) to the satellite communication access network.

[0080] S15, the satellite communication access network sends a Security Mode Complete (DT) message to the core network.

[0081] S16, the core network sends a Location Update Accept message (DT) to the satellite communication access network.

[0082] S17, the satellite communication access network sends a Location Update Accept message (DT) to the terminal, and the terminal successfully accesses the network;

[0083] S18, the core network sends a Location Update Reject (DT) message to the satellite communication access network.

[0084] S19, the satellite communication access network sends a Location Update Reject (DT) message to the terminal, and the terminal fails to access the network.

[0085] In the GMR-based satellite terminal access management system of this application embodiment, the terminal triggers a positioning process in advance to obtain its own latitude and longitude information before initiating random access, which can save the time of waiting for positioning. By adding optional information elements to the communication protocol, the terminal can directly carry its own latitude and longitude information in the location update request message and report this information to the core network through the access network. This process optimizes latency by reporting latitude and longitude information in advance and does not require additional querying and reporting of air interface messages, thus optimizing resource utilization. The core network can determine whether the terminal is within the emergency backup communication area based on the terminal's latitude and longitude information, and allow or deny the terminal access according to the judgment result, thus realizing the emergency backup communication requirement. The solution of this application effectively solves the technical problem that the existing terminal location reporting scheme cannot be applied to emergency backup communication scenarios.

[0086] Example 2

[0087] Based on the GMR-based satellite terminal access management system provided in Embodiment 1, this application provides a GMR-based satellite terminal access management method implemented by a satellite communication access network. 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.

[0088] Figure 3 This is a flowchart illustrating a satellite terminal access management method based on GMR provided in an embodiment of this application, as shown below. Figure 3 As shown, the method includes the following steps:

[0089] Step S302: Establish an RRC connection with the terminal;

[0090] Step S304: Receive a location update request message carrying terminal location information sent by the terminal, wherein the terminal location information is obtained by the terminal before establishing an RRC connection with the satellite communication access network;

[0091] Step S306: Send an initial terminal information message carrying terminal location information to the core network;

[0092] Step S308: In response to the access permission information fed back by the core network when it is determined that the terminal is located in the preset emergency backup communication area based on the terminal location information, the terminal is connected to the core network.

[0093] Step S310: In response to the access denial information fed back by the core network when it determines that the terminal is not in the preset emergency backup communication area based on the terminal location information, the terminal is denied access to the core network.

[0094] The following section describes each step of the GMR-based satellite terminal access management method in conjunction with the specific implementation process.

[0095] As an optional implementation, when establishing an RRC connection with a terminal, the satellite communication access network performs the following signaling interactions: receiving an RRC connection request message from the terminal; sending an RRC connection establishment message to the terminal; and receiving an RRC connection establishment completion message from the terminal.

[0096] Optionally, the location update request message sent by the terminal includes: a relative location optional information element, wherein the information element identifier of the relative location optional information element is a 1-byte preset identifier; when the information element format of the relative location optional information element is a tag-value format, the information element length of the relative location optional information element is 5 bytes, wherein the first byte is the information element identifier, the second and third bytes are the relative latitude of the terminal relative to the preset reference latitude, and the fourth and fifth bytes are the relative longitude of the terminal relative to the preset reference longitude; when the information element format of the relative location optional information element is a tag-length-value format, the information element length of the relative location optional information element is 6 bytes, wherein the first byte is the information element identifier, the second byte is the information element length, the third and fourth bytes are the relative latitude, and the fifth and sixth bytes are the relative longitude.

[0097] Optionally, the location update request message sent by the terminal includes: a GPS location optional information cell; wherein, the information cell identifier of the GPS location optional information cell is a 1-byte preset identifier, the information cell format is a tag-value format, and the information cell length is 6 bytes; the eighth bit of the first byte of the GPS location optional information cell is 0, the seventh bit to the first bit of the first byte is the information cell identifier, the eighth bit of the second byte is the current positioning indication, the seventh bit to the first bit of the second byte, the eighth bit to the fifth bit of the third byte, and the fourth bit to the first bit of the fourth byte are the GPS latitude of the terminal, and the fourth bit to the first bit of the fourth byte, the fifth byte, and the sixth byte are the GPS longitude of the terminal.

[0098] As an optional implementation, when the satellite communication access network connects the terminal to the core network in response to the access permission information fed back by the core network, it specifically performs the following signaling interactions: receiving an authentication request message sent by the core network and sending the authentication request message to the terminal; receiving an authentication response message sent by the terminal and sending the authentication response message to the core network; receiving a security mode command message sent by the core network and sending the security mode command message to the terminal; receiving a security mode completion message sent by the terminal and sending the security mode completion message to the core network; and receiving a location update acceptance message from the core network and sending the location update acceptance message to the terminal.

[0099] Optionally, when the satellite communication access network refuses access to the core network in response to the access denial information fed back by the core network, it specifically performs the following signaling interaction: receiving the location update rejection message sent by the core network and sending the location update rejection message to the terminal.

[0100] It should be noted that each implementation step in the satellite terminal access management method based on GMR in this application embodiment has been described in detail in Embodiment 1. Some details not shown in this embodiment can be referred to Embodiment 1, and will not be repeated here.

[0101] Example 3

[0102] Based on the GMR-based satellite terminal access management system provided in Embodiment 1, this application provides a GMR-based satellite terminal access management method implemented by a terminal. 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. Also, although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than that shown here.

[0103] Figure 4 This is a flowchart illustrating a satellite terminal access management method based on GMR provided in an embodiment of this application, as shown below. Figure 4As shown, the method includes the following steps:

[0104] Step S402: Obtain terminal location information;

[0105] Step S404: Establish an RRC connection with the satellite communication access network;

[0106] Step S406: Send a location update request message carrying terminal location information to the satellite communication access network;

[0107] Step S408: Receive access permission information relayed by the core network from the satellite communication access network, provided that the terminal is located within a preset emergency backup communication area based on the terminal location information; or,

[0108] Step S410: Receive access rejection information relayed by the core network from the satellite communication access network when the terminal is determined to be outside the preset emergency backup communication area based on the terminal location information.

[0109] The following section describes each step of the GMR-based satellite terminal access management method in conjunction with the specific implementation process.

[0110] As an optional implementation, before establishing an RRC connection with the satellite communication access network, the terminal's built-in Modem chip can interact with the GPS (Global Positioning System) module to obtain the terminal's current location information, specifically its current latitude and longitude information.

[0111] Optionally, the terminal can establish an RRC connection with the satellite communication access network in the following ways: sending an RRC connection request message to the satellite communication access network; receiving an RRC connection establishment message from the satellite communication access network; and after completing the RRC connection configuration, sending an RRC connection establishment completion message back to the satellite communication access network.

[0112] Optionally, the location update request message sent by the terminal includes: a relative location optional information element, wherein the information element identifier of the relative location optional information element is a 1-byte preset identifier; when the information element format of the relative location optional information element is a tag-value format, the information element length of the relative location optional information element is 5 bytes, wherein the first byte is the information element identifier, the second and third bytes are the relative latitude of the terminal relative to the preset reference latitude, and the fourth and fifth bytes are the relative longitude of the terminal relative to the preset reference longitude; when the information element format of the relative location optional information element is a tag-length-value format, the information element length of the relative location optional information element is 6 bytes, wherein the first byte is the information element identifier, the second byte is the information element length, the third and fourth bytes are the relative latitude, and the fifth and sixth bytes are the relative longitude.

[0113] Optionally, the location update request message sent by the terminal includes: a GPS location optional information cell; wherein, the information cell identifier of the GPS location optional information cell is a 1-byte preset identifier, the information cell format is a tag-value format, and the information cell length is 6 bytes; the eighth bit of the first byte of the GPS location optional information cell is 0, the seventh bit to the first bit of the first byte is the information cell identifier, the eighth bit of the second byte is the current positioning indication, the seventh bit to the first bit of the second byte, the eighth bit to the fifth bit of the third byte, and the fourth bit to the first bit of the fourth byte are the GPS latitude of the terminal, and the fourth bit to the first bit of the fourth byte, the fifth byte, and the sixth byte are the GPS longitude of the terminal.

[0114] After the terminal sends a location update request message carrying the terminal's location information to the satellite communication access network, the satellite communication access network sends an initial terminal information message carrying the terminal's location information to the core network. After receiving the initial terminal information message, the core network can determine whether the terminal is located within the preset emergency backup communication area based on the terminal location information carried in it.

[0115] Optionally, when the terminal is located within the emergency backup communication area, the core network can send access permission information to the satellite communication access network to instruct the satellite communication access network to connect the terminal to the core network. One optional terminal access process is as follows: the core network sends an authentication request message to the satellite communication access network, which then sends the authentication request message to the terminal; the terminal sends an authentication response message to the satellite communication access network, which then sends the authentication response message to the core network; the core network sends a security mode command message to the satellite communication access network, which then sends the security mode command message to the terminal; the terminal sends a security mode completion message to the satellite communication access network, which then sends the security mode completion message to the core network; the core network sends a location update acceptance message to the satellite communication access network, which then sends the location update acceptance message to the terminal.

[0116] Optionally, if the terminal is not within the emergency backup communication area, the core network can send an access denial message to the satellite communication access network to instruct the satellite communication access network to deny the terminal access to the core network. One possible process for denying terminal access is as follows: the core network sends a location update denial message to the satellite communication access network, and the satellite communication access network sends the location update denial message to the terminal.

[0117] It should be noted that each implementation step in the satellite terminal access management method based on GMR in this application embodiment has been described in detail in Embodiment 1. Some details not shown in this embodiment can be referred to Embodiment 1, and will not be repeated here.

[0118] Example 4

[0119] Based on the GMR-based satellite terminal access management system provided in Embodiment 1, this application embodiment provides a GMR-based satellite terminal access management method implemented by the core network. 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.

[0120] Figure 5 This is a flowchart illustrating a satellite terminal access management method based on GMR provided in an embodiment of this application, as shown below. Figure 5 As shown, the method includes the following steps:

[0121] Step S502: Receive an initial terminal information message carrying terminal location information sent by the satellite communication access network. The initial terminal information message is generated by the satellite communication access network based on the terminal location information obtained by the terminal before establishing an RRC connection with the satellite communication access network, which is carried in the location update request message from the terminal.

[0122] Step S504: Determine whether the terminal is located within the preset emergency backup communication area based on the terminal location information;

[0123] Step S506: If the terminal is located in the emergency backup communication area, send access permission information to the satellite communication access network to instruct the satellite communication access network to connect the terminal to the core network;

[0124] Step S508: If the terminal is not in the emergency backup communication area, send an access denial message to the satellite communication access network to instruct the satellite communication access network to refuse the terminal access to the core network.

[0125] The following section describes each step of the GMR-based satellite terminal access management method in conjunction with the specific implementation process.

[0126] Optionally, the location update request message sent by the terminal includes: a relative location optional information element, wherein the information element identifier of the relative location optional information element is a 1-byte preset identifier; when the information element format of the relative location optional information element is a tag-value format, the information element length of the relative location optional information element is 5 bytes, wherein the first byte is the information element identifier, the second and third bytes are the relative latitude of the terminal relative to the preset reference latitude, and the fourth and fifth bytes are the relative longitude of the terminal relative to the preset reference longitude; when the information element format of the relative location optional information element is a tag-length-value format, the information element length of the relative location optional information element is 6 bytes, wherein the first byte is the information element identifier, the second byte is the information element length, the third and fourth bytes are the relative latitude, and the fifth and sixth bytes are the relative longitude.

[0127] Optionally, the location update request message sent by the terminal includes: a GPS location optional information cell; wherein, the information cell identifier of the GPS location optional information cell is a 1-byte preset identifier, the information cell format is a tag-value format, and the information cell length is 6 bytes; the eighth bit of the first byte of the GPS location optional information cell is 0, the seventh bit to the first bit of the first byte is the information cell identifier, the eighth bit of the second byte is the current positioning indication, the seventh bit to the first bit of the second byte, the eighth bit to the fifth bit of the third byte, and the fourth bit to the first bit of the fourth byte are the GPS latitude of the terminal, and the fourth bit to the first bit of the fourth byte, the fifth byte, and the sixth byte are the GPS longitude of the terminal.

[0128] After receiving the initial terminal information message, the core network can determine whether the terminal is located within the preset emergency backup communication area based on the terminal location information carried in the message.

[0129] Optionally, when the terminal is located within the emergency backup communication area, the core network can send access permission information to the satellite communication access network to instruct the satellite communication access network to connect the terminal to the core network. One optional terminal access process is as follows: the core network sends an authentication request message to the satellite communication access network, which then sends the authentication request message to the terminal; the terminal sends an authentication response message to the satellite communication access network, which then sends the authentication response message to the core network; the core network sends a security mode command message to the satellite communication access network, which then sends the security mode command message to the terminal; the terminal sends a security mode completion message to the satellite communication access network, which then sends the security mode completion message to the core network; the core network sends a location update acceptance message to the satellite communication access network, which then sends the location update acceptance message to the terminal.

[0130] Optionally, if the terminal is not within the emergency backup communication area, the core network can send an access denial message to the satellite communication access network to instruct the satellite communication access network to deny the terminal access to the core network. One possible process for denying terminal access is as follows: the core network sends a location update denial message to the satellite communication access network, and the satellite communication access network sends the location update denial message to the terminal.

[0131] It should be noted that each implementation step in the satellite terminal access management method based on GMR in this application embodiment has been described in detail in Embodiment 1. Some details not shown in this embodiment can be referred to Embodiment 1, and will not be repeated here.

[0132] Example 5

[0133] According to an embodiment of this application, a computer program product is also provided, which includes a computer program, wherein when the computer program is executed by a processor, it implements the GMR-based satellite terminal access management method in embodiment 2, embodiment 3, or embodiment 4.

[0134] According to an embodiment of this application, a non-volatile storage medium is also provided, which includes a stored computer program, wherein the device containing the non-volatile storage medium executes the GMR-based satellite terminal access management method in Embodiment 2, Embodiment 3, or Embodiment 4 by running the computer program.

[0135] According to an embodiment of this application, a processor is also provided for running a computer program, wherein the computer program executes the GMR-based satellite terminal access management method in embodiment 2, embodiment 3, or embodiment 4.

[0136] According to an embodiment of this application, an electronic device is also provided, comprising: a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the GMR-based satellite terminal access management method of embodiment 2, embodiment 3, or embodiment 4 through the computer program.

[0137] Optionally, the computer program may execute the following steps during runtime: establishing an RRC connection with the terminal; receiving a location update request message carrying terminal location information sent by the terminal, wherein the terminal location information is obtained by the terminal before establishing an RRC connection with the satellite communication access network; sending an initial terminal information message carrying terminal location information to the core network; in response to the access permission information fed back by the core network when it determines that the terminal is located in a preset emergency backup communication area based on the terminal location information, allowing the terminal to access the core network; and in response to the access denial information fed back by the core network when it determines that the terminal is not in the preset emergency backup communication area based on the terminal location information, denying the terminal access to the core network.

[0138] Optionally, the computer program may also execute the following steps during runtime: acquiring terminal location information; establishing an RRC connection with the satellite communication access network; sending a location update request message carrying the terminal location information to the satellite communication access network; receiving access permission information relayed by the core network from the satellite communication access network when the terminal is determined to be located within a preset emergency backup communication area based on the terminal location information; or receiving access denial information relayed by the core network from the satellite communication access network when the terminal is determined to be located outside the preset emergency backup communication area based on the terminal location information.

[0139] Optionally, the computer program may also execute the following steps during runtime: receiving an initial terminal information message carrying terminal location information sent by the satellite communication access network, wherein the initial terminal information message is generated by the satellite communication access network based on the terminal location information obtained by the terminal before establishing an RRC connection with the satellite communication access network, carried in a location update request message from the terminal; determining whether the terminal is located within a preset emergency backup communication area based on the terminal location information; if the terminal is located within the emergency backup communication area, sending access permission information to the satellite communication access network to instruct the satellite communication access network to connect the terminal to the core network; if the terminal is not located within the emergency backup communication area, sending access denial information to the satellite communication access network to instruct the satellite communication access network to deny the terminal access to the core network.

[0140] As an alternative implementation, the above-mentioned electronic device may exist in the form of a mobile terminal, a computer terminal, or a similar computing device. Figure 6 A hardware block diagram of an electronic device for implementing a GMR-based satellite terminal access management method is shown. Figure 6 As shown, the electronic device 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 device 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 electronic device described above. For example, electronic device 60 may also include... Figure 6 The more or fewer components shown, or having the same Figure 6 The different configurations shown.

[0141] 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 of the electronic device 60. As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0142] The memory 604 can be used to store software programs and modules of application software, such as the program instruction / data storage device corresponding to the GMR-based satellite terminal access management 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 implementing the aforementioned application vulnerability detection 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 electronic device 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.

[0143] The transmission device 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 electronic device 60. In one example, the transmission device 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 device 606 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0144] The display may be, for example, a touchscreen liquid crystal display (LCD), which allows the user to interact with the user interface of the electronic device 60.

[0145] The sequence numbers of the above embodiments are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0146] 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.

[0147] 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 example, 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 couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0148] 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.

[0149] 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.

[0150] 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 the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

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

Claims

1. A satellite terminal access management method based on GMR, applied to a satellite communication access network, characterized in that, include: Establish a Radio Resource Control (RRC) connection with the terminal; The terminal receives a location update request message carrying terminal location information sent by the terminal, wherein the terminal location information is obtained by the terminal before establishing an RRC connection with the satellite communication access network; Send an initial terminal information message carrying the terminal location information to the core network; In response to the access permission information fed back by the core network when it determines that the terminal is located in a preset emergency backup communication area based on the terminal location information, the terminal is connected to the core network; In response to the access denial information fed back by the core network when it determines, based on the terminal location information, that the terminal is not in the preset emergency backup communication area, the terminal is denied access to the core network.

2. The method according to claim 1, characterized in that, The location update request message includes: a relative location optional information element, wherein the information element identifier of the relative location optional information element is a 1-byte preset identifier; When the cell format of the relative position selectable cell is a tag-value format, the cell length of the relative position selectable cell is 5 bytes, wherein the first byte is the cell identifier, the second and third bytes are the latitude of the terminal relative to the preset reference latitude, and the fourth and fifth bytes are the longitude of the terminal relative to the preset reference longitude. When the cell format of the relative position selectable cell is a label-length-value format, the cell length of the relative position selectable cell is 6 bytes, wherein the first byte is the cell identifier, the second byte is the cell length, the third and fourth bytes are the relative latitude, and the fifth and sixth bytes are the relative longitude.

3. The method according to claim 1, characterized in that, The location update request message includes: optional information elements for GPS location; The cell identifier of the GPS location selectable cell is a 1-byte preset identifier, the cell format is a tag-value format, and the cell length is 6 bytes. The eighth bit of the first byte of the GPS location selectable cell is 0, the seventh bit to the first bit of the first byte is the cell identifier, the eighth bit of the second byte is the current positioning indication, the seventh bit to the first bit of the second byte, the eighth bit to the fifth bit of the third byte, and the fourth bit to the first bit of the fourth byte are the GPS latitude of the terminal, and the fourth bit to the first bit of the fourth byte, the fifth byte, and the sixth byte are the GPS longitude of the terminal.

4. The method according to claim 1, characterized in that, Establishing an RRC connection with the terminal includes: Receive the RRC connection request message sent by the terminal; Send an RRC connection establishment message to the terminal; Receive the RRC connection establishment complete message sent by the terminal.

5. The method according to claim 1, characterized in that, In response to the access permission information fed back by the core network when it determines, based on the terminal location information, that the terminal is located within a preset emergency backup communication area, the terminal is connected to the core network, including: The system receives an authentication request message sent by the core network and sends the authentication request message to the terminal; it also receives an authentication response message sent by the terminal and sends the authentication response message to the core network. The system receives a security mode command message sent by the core network and sends the security mode command message to the terminal; it also receives a security mode completion message sent by the terminal and sends the security mode completion message to the core network. The system receives the location update acceptance message from the core network and sends the location update acceptance message to the terminal.

6. The method according to claim 1, characterized in that, In response to the access denial information fed back by the core network when it determines, based on the terminal location information, that the terminal is not within a preset emergency backup communication area, the core network denies the terminal access to the core network, including: The system receives a location update rejection message from the core network and sends the location update rejection message to the terminal.

7. The method according to claim 5 or 6, characterized in that, During the process of connecting the terminal to the core network or denying the terminal access to the core network, all transmitted messages are transmitted based on direct transmission signaling, wherein the direct transmission signaling is used to transmit non-access stratum data.

8. A satellite terminal access management method based on GMR, applied to a terminal, characterized in that, include: Obtain terminal location information; Establish an RRC connection with the satellite communication access network; Send a location update request message carrying the terminal's location information to the satellite communication access network; The core network receiving the satellite communication access network forwards the access permission information fed back by the terminal when it determines that the terminal is located in a preset emergency backup communication area based on the terminal location information; or, The core network receiving the satellite communication access network forwards a rejection message when it determines, based on the terminal's location information, that the terminal is not within a preset emergency backup communication area.

9. A satellite terminal access management method based on GMR, applied to the core network, characterized in that, include: The system receives an initial terminal information message carrying terminal location information sent by a satellite communication access network. The initial terminal information message is generated by the satellite communication access network based on the terminal location information obtained by the terminal before establishing an RRC connection with the satellite communication access network, which is carried in a location update request message from the terminal. Based on the terminal location information, determine whether the terminal is located within a preset emergency backup communication area; When the terminal is located within the emergency backup communication area, it sends access permission information back to the satellite communication access network to instruct the satellite communication access network to connect the terminal to the core network; If the terminal is not within the emergency backup communication area, it sends an access denial message to the satellite communication access network to instruct the satellite communication access network to refuse the terminal access to the core network.

10. A satellite terminal access management system based on GMR, characterized in that, include: Terminals, satellite communication access networks, and core networks, among which, The terminal is used to obtain its own terminal location information; establish an RRC connection with the satellite communication access network; and send a location update request message carrying the terminal location information to the satellite communication access network. The satellite communication access network is used to send an initial terminal information message carrying the terminal location information to the core network; The core network is used to determine whether the terminal is located within a preset emergency backup communication area based on the terminal location information. If the terminal is located within the emergency backup communication area, the core network sends an access permission message to the satellite communication access network. If the terminal is not located within the emergency backup communication area, the core network sends an access denial message to the satellite communication access network. The satellite communication access network is also used to respond to the access permission information by allowing the terminal to access the core network, and to respond to the access denial information by denying the terminal access to the core network.

11. A computer program product, characterized in that, include: A computer program, wherein when executed by a processor, the computer program implements the GMR-based satellite terminal access management method according to any one of claims 1 to 9.

12. An electronic device, characterized in that, include: A memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the GMR-based satellite terminal access management method according to any one of claims 1 to 9 through the computer program.

Images