Communication method, access and mobility management function entity and terminal equipment

Abstract

The invention discloses a communication method, an access and mobility management function entity and terminal equipment. The method comprises the steps that a registration request message sent by terminal equipment is received, and the registration request message at least comprises a load container type cell and a load container cell; after determining that the registration request message carries the short message according to the load container type cell, extracting the content of the short message from the load container cell; under the condition that the access and mobility management functional entity supports a short message service based on a non-access layer, forwarding the content of the short message to a short message service functional entity, and sending a registration acceptance message to the terminal equipment; and the terminal equipment is used for releasing the connection and entering an idle state after receiving the registration acceptance message. The technical problem that in the prior art, the short message is transmitted through an independent NAS message after the terminal equipment is successfully registered, and consequently the resource overhead is large is solved.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a communication method, an access and mobility management functional entity, and a terminal device. Background Art

[0002] Short Message Service over Non-AccessStratum (SMS over NAS) is a mechanism for providing short message services in 5G networks. SMS over NAS allows sending and receiving short messages through the NAS layer of the 5G core network. This function was introduced in the R15 version of 3GPP. SMS overNAS supports SMS over non-3GPP access, which means that it not only supports short message services within the 5G network, but also supports short message services through non-3GPP access points (such as Wi-Fi). In the 5G network, the Short Message Service Function (SMSF) is the core network element responsible for processing SMS over NAS. SMSF can provide short message services for 5G terminals and can provide services for both human network terminals and Internet of Things terminals. In addition, SMSF also supports interaction with existing short message centers and network structures to support 2G, 3G, 4G, and 5G short message services, with minimal modification to the existing network. Therefore, SMS over NAS is an important function in 5G networks. It enhances the communication capabilities of 5G networks and allows users to continue using traditional short message services in the 5G environment.

[0003] Figure 1 The process of sending a single SMS over NAS message by a user in the idle state is shown. Figure 1 It can be seen that in the existing 3GPP standard protocol, the mobile originated (MO) short message service / mobile terminated (MT) short message service in the SMS over NAS function is transmitted through a separate uplink or downlink NAS message after the user equipment (UE) is successfully registered.

[0004] However, in non-terrestrial network (NTN) scenarios, especially in Internet of Things non-terrestrial network (IoT-NTN) narrowband satellite scenarios, separate air interface messages will bring additional resource overhead and delay.

[0005] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0006] The present application provides a communication method, an access and mobility management functional entity, and a terminal device, to at least solve the technical problem in the prior art that short messages are transmitted through a separate NAS message after the terminal device is successfully registered, resulting in large resource overhead.

[0007] According to one aspect of the present application, a communication method is provided, comprising: receiving a registration request message sent by a terminal device, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element being used to indicate whether the registration request message carries a short message, and the payload container information element including the content of the short message carried in the registration request message; after determining that the registration request message carries a short message based on the payload container type information element, extracting the content of the short message from the payload container information element; in a case where an access and mobility management function entity supports a short message service based on a non-access layer, forwarding the content of the short message to a short message service function entity, and sending a registration acceptance message to the terminal device; the terminal device being configured to release the connection and enter an idle state after receiving the registration acceptance message.

[0008] Optionally, the registration acceptance message includes: a registration result optional information element, wherein the short message service allowed field in the registration result optional information element includes: allowing the short message service based on the non-access layer.

[0009] Optionally, the method also includes: when the access and mobility management function entity does not support the short message service based on the non-access layer, sending a registration acceptance message to the terminal device, wherein the registration acceptance message includes: a registration result optional information element, and the allowed short message service field in the registration result optional information element includes: not allowing the short message service based on the non-access layer; the terminal device is used to release the connection and enter the idle state after receiving the registration acceptance message.

[0010] Optionally, the registration request message further includes: a registration type mandatory information element, wherein the FOR field of the registration type mandatory information element includes: no subsequent request to be processed.

[0011] Optionally, the registration request message further includes: an update type optional information element, wherein the short message service request field of the update type optional information element includes: supporting a short message service based on a non-access layer.

[0012] Optionally, the method further includes: caching the content of the short message in a target storage area after extracting the content of the short message from the payload container cell; and clearing the content of the short message in the target storage area when the access and mobility management function entity does not support a short message service based on the non-access layer.

[0013] Optionally, the payload container type cell and the payload container cell are both optional cells; the format of the payload container type cell is type and value; the format of the payload container cell is: type, length and value, and the format of the payload container cell supports extension.

[0014] According to another aspect of the present application, a communication method is also provided, including: sending a registration request message to an access and mobility management function entity, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message; receiving a registration acceptance message sent by the mobility management function entity, releasing the connection and entering an idle state, wherein the registration acceptance message is sent when the access and mobility management function entity supports a short message service based on a non-access layer, and the access and mobility management function entity is used to extract the content of the short message in the payload container information element after determining that the registration request message carries a short message according to the payload container type information element, and forward the content of the short message to the short message service function entity.

[0015] According to another aspect of the present application, a communication method is also provided, including: receiving a registration request message sent by a terminal device, wherein the registration request message is sent by the terminal device after receiving a paging message, and the registration request message includes at least: a registration type mandatory element; in response to the registration request message, sending a registration acceptance message to the terminal device, wherein the registration acceptance message includes at least: a payload container type element and a payload container element, the payload container type element is used to indicate whether the registration request message carries a short message, and the payload container element includes the content of the short message carried in the registration request message; the terminal device is used to release the connection and enter an idle state after receiving the registration acceptance message.

[0016] Optionally, the payload container type cell and the payload container cell are both optional cells; the format of the payload container type cell is type and value; the format of the payload container cell is: type, length and value, and the format of the payload container cell supports extension.

[0017] Optionally, before receiving the registration request message sent by the terminal device, the method further includes: establishing a communication connection with a short message service function entity.

[0018] According to another aspect of the present application, a communication method is also provided, including: after receiving a paging message, sending a registration request message to an access and mobility management function entity, wherein the registration request message is sent by the terminal device after receiving the paging message, and the registration request message includes at least: a registration type mandatory information element; receiving a registration acceptance message sent by the access and mobility management function entity in response to the registration request message, wherein the registration acceptance message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message; after receiving the registration acceptance message, releasing the connection and entering the idle state.

[0019] According to another aspect of the present application, an access and mobility management functional entity is also provided, including: a first receiving submodule, used to receive a registration request message sent by a terminal device, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message; a first extraction submodule, used to extract the content of the short message in the payload container information element after determining that the registration request message carries a short message according to the payload container type information element; a first sending submodule, used to forward the content of the short message to the short message service functional entity and send the registration acceptance message to the terminal device when the access and mobility management functional entity supports a short message service based on a non-access layer; the terminal device is used to release the connection and enter an idle state after receiving the registration acceptance message.

[0020] According to another aspect of the present application, a terminal device is also provided, including: a second sending submodule, used to send a registration request message to an access and mobility management function entity, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message; a second receiving submodule, used to receive a registration acceptance message sent by the mobility management function entity, release the connection and enter an idle state, wherein the registration acceptance message is sent when the access and mobility management function entity supports a short message service based on a non-access layer, and the access and mobility management function entity is used to extract the content of the short message in the payload container information element after determining that the registration request message carries a short message according to the payload container type information element, and forward the content of the short message to the short message service function entity.

[0021] According to another aspect of the present application, an access and mobility management functional entity is also provided, including: a third receiving submodule, used to receive a registration request message sent by a terminal device, wherein the registration request message is sent by the terminal device after receiving a paging message, and the registration request message includes at least: a registration type mandatory element; a third sending submodule, used to respond to the registration request message and send a registration acceptance message to the terminal device, wherein the registration acceptance message includes at least: a payload container type element and a payload container element, the payload container type element is used to indicate whether the registration request message carries a short message, and the payload container element includes the content of the short message carried in the registration request message; the terminal device is used to release the connection and enter an idle state after receiving the registration acceptance message.

[0022] According to another aspect of the present application, a terminal device is also provided, including: a fourth sending submodule, used to send a registration request message to an access and mobility management function entity after receiving a paging message, wherein the registration request message is sent by the terminal device after receiving the paging message, and the registration request message at least includes: a registration type mandatory element; a fourth receiving submodule, receiving a registration acceptance message sent by the access and mobility management function entity in response to the registration request message, wherein the registration acceptance message at least includes: a payload container type element and a payload container element, the payload container type element is used to indicate whether the registration request message carries a short message, and the payload container element includes the content of the short message carried in the registration request message; a releasing submodule, used to release the connection and enter an idle state after receiving the registration acceptance message.

[0023] According to another aspect of the present application, a communication system is also provided, including: a terminal device, an access and mobility management functional entity and a short message service functional entity, wherein the terminal device is used to send a registration request message to the access and mobility management functional entity, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message; the access and mobility management functional entity is used to extract the content of the short message in the payload container information element after determining that the registration request message carries a short message according to the payload container type information element; the access and mobility management functional entity is also used to forward the content of the short message to the short message service functional entity and send a registration acceptance message to the terminal device when supporting a short message service based on a non-access layer; the terminal device is also used to release the connection and enter an idle state after receiving the registration acceptance message.

[0024] According to another aspect of the present application, a communication system is also provided, including: a terminal device and an access and mobility management functional entity, wherein the terminal device is used to send a registration request message to the access and mobility management functional entity after receiving a paging message, wherein the registration request message is sent by the terminal device after receiving the paging message, and the registration request message includes at least: a registration type mandatory element; the access and mobility management functional entity is used to respond to the registration request message and send a registration acceptance message to the terminal device, wherein the registration acceptance message includes at least: a payload container type element and a payload container element, the payload container type element is used to indicate whether the registration request message carries a short message, and the payload container element includes the content of the short message carried in the registration request message; the terminal device is also used to release the connection and enter an idle state after receiving the registration acceptance message.

[0025] In the present application, a registration request message sent by a receiving terminal device is adopted, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message; after determining that the registration request message carries a short message according to the payload container type information element, the content of the short message is extracted from the payload container information element; when the access and mobility management function entity supports a short message service based on a non-access layer, the content of the short message is forwarded to the short message service function entity, and a registration acceptance message is sent to the terminal device; the terminal device is used to release the connection and enter an idle state after receiving the registration acceptance message, thereby achieving the purpose of transmitting the short message content during the terminal device registration process, thereby realizing the technical effect of saving air interface resources and optimizing the sending and receiving delays of short messages, and thus solving the technical problem in the prior art that the short message is transmitted through a separate NAS message after the terminal device successfully registers, resulting in a large resource overhead. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0027] Figure 1 A schematic diagram of signaling interaction is shown;

[0028] Figure 2 is a flow chart of a communication method according to an embodiment of the present application;

[0029] Figure 3 is a flow chart of another communication method according to an embodiment of the present application;

[0030] Figure 4 is a flow chart of another communication method according to an embodiment of the present application;

[0031] Figure 5 is a flow chart of another communication method according to an embodiment of the present application;

[0032] Figure 6 is a structural diagram of an access and mobility management function entity according to an embodiment of the present application;

[0033] Figure 7 is a structural diagram of a terminal device according to an embodiment of the present application;

[0034] Figure 8 is a structural diagram of another access and mobility management function entity according to an embodiment of the present application;

[0035] Figure 9 is a structural diagram of another terminal device according to an embodiment of the present application;

[0036] Figure 10 is a structural diagram of a communication system according to an embodiment of the present application;

[0037] Figure 11 This is a schematic diagram of signaling interaction according to an embodiment of the present application;

[0038] Figure 12 is a structural diagram of another communication system according to an embodiment of the present application;

[0039] Figure 13 is another signaling interaction diagram according to an embodiment of the present application;

[0040] Figure 14 A hardware structure block diagram of a computer terminal according to a communication method of an embodiment of the present application. DETAILED DESCRIPTION

[0041] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0042] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0043] According to an embodiment of the present application, a method embodiment of a communication method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0044] Figure 2 is a flow chart of a communication method according to an embodiment of the present application, such as Figure 2 As shown, the method includes the following steps:

[0045] Step S202: Receive a registration request message sent by the terminal device, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message.

[0046] The Access and Mobility Management Function (AMF) receives uplink NAS signaling from the UE, namely the Registration Request message. This is the initial message sent by the UE when attempting to access the network. This message includes the Payload Container Type information element and the Payload Container information element. The Payload Container Type information element is optional and is filled with SMS, indicating that it carries an SMS short message. The Payload Container information element is optional and is filled with SMS payload, indicating the content of the short message.

[0047] Step S204: After determining that the registration request message carries a short message according to the payload container type information element, extract the content of the short message from the payload container information element.

[0048] After the AMF identifies the registration request message as carrying an SMS message, it extracts the SMS payload and caches the SMS payload.

[0049] Specifically, the AMF first parses the PayloadContainerType information element in the received Registration Request message to determine whether the message contains short message content. For example, if the PayloadContainerType value is '0010', it indicates that the message carries an SMS message. Next, the AMF parses the PayloadContainer information element, which contains the actual content of the short message, i.e., the SMS payload. For example, the SMS payload can be of type CP-DATA, CP-ACK, or CP-ERROR, representing different short message service information. After extracting the SMS payload, the AMF caches it in local storage for subsequent processing. This caching ensures that the short message content is not lost even if the AMF requires time for signaling processing or awaits responses from other network functions. The AMF determines whether to allow the short message to be sent via the NAS layer based on network policy and current network status. If allowed, the AMF forwards the cached SMS payload to the appropriate SMSF for processing. If not allowed, the cached SMS payload is discarded or other measures are taken based on network policy.

[0050] Step S206: If the access and mobility management function entity supports the short message service based on the non-access layer, the content of the short message is forwarded to the short message service function entity, and the registration acceptance message is sent to the terminal device; the terminal device is used to release the connection and enter the idle state after receiving the registration acceptance message.

[0051] If AMF allows SMS over NAS, the AMF shall carry the 5GS registration result optional information element when sending the Registration Accept message, where the SMS allowed field is filled with "SMS over NAS allowed", indicating that the AMF allows the SMS over NAS function of this registration.

[0052] After receiving the registration acceptance message, the UE releases the connection and enters the idle state. It is worth noting that after the UE enters the idle state, the SMS over NAS message has been successfully sent, and the UE no longer needs to send an uplink NAS message carrying the SMS message.

[0053] Specifically, after receiving the Registration Accept message, the UE triggers a connection release process, terminating its current connected state connection with the network and returning to the Idle state. This is because the short message has already been successfully sent via the Registration Request message, eliminating the need to maintain the Connected state for additional uplink NAS message transmission. Since the short message content has already been extracted and forwarded to the SMSF by the AMF during the Registration Request process, the UE can assume that its short message transmission has been successfully completed. This means that the UE no longer needs to perform subsequent UL NAS Transport message transmissions for the same short message. After releasing the connection, the UE enters the Idle state, which is the default state when the UE does not need to transmit data or communicate frequently with the network. In the Idle state, the UE conserves power, extends battery life, and reduces radio resource usage. In the Idle state, the UE continues to monitor the Paging channel to receive Paging messages from the network. If the UE receives a Paging message, indicating that the network has data to transmit to the UE, the UE re-enters the Connected state from the Idle state to establish a connection with the network and receive data.

[0054] It should be noted that Figure 2 Steps S202 to S206 shown can be applied to NTN scenarios, especially IoT-NTN scenarios.

[0055] The above steps S202 to S206 propose for the first time that the NAS signaling short message function sends the short message to the core network AMF in advance through the registration request message, which is applicable to the single short message scenario; the NAS signaling short message function proposes for the first time that the AMF decodes and extracts the short message from the registration request message, and caches and forwards it to the SMSF in advance; the NAS signaling short message function proposes for the first time that the short message is sent to the terminal UE in advance through the registration accept message, which is applicable to the single short message scenario.

[0056] The above steps S202 to S206 have the following technical effects: reducing the signaling transmitted over the air interface and optimizing the utilization of satellite air interface resources; the UE sends a short message to the AMF in advance, the AMF forwards it to the SMSF in advance, and the AMF sends the short message to the UE in advance, thereby reducing the delay in sending and receiving short messages.

[0057] By embedding the short message content directly into the Registration Request message and, with the AMF's permission, extracting and processing the short message from this message, the subsequent UL NAS Transport message is avoided, streamlining the signaling process for the short message service (SMS) in 5G networks. This reduces radio resource consumption in NTN scenarios, a crucial optimization measure for improving system efficiency and user experience, particularly in resource-constrained environments such as IoT-NTNs. Furthermore, the above process ensures the reliability and timeliness of the SMS, making it a key step in optimizing the SMS at the NAS layer.

[0058] The following Figure 2 The steps shown are exemplified and explained.

[0059] Preferably, the registration acceptance message includes: a registration result optional information element, wherein the short message service allowed field in the registration result optional information element includes: allowing the short message service based on the non-access layer.

[0060] Among them, the above-mentioned registration result optional information element is the 5GS registration result optional information element, and the SMS allowed field in the information element is filled in with "SMS over NAS not allowed", indicating that the AMF does not allow the SMS over NAS function of this registration.

[0061] Preferably, Figure 2 The communication method shown also includes the following steps: when the access and mobility management function entity does not support the short message service based on the non-access layer, sending a registration acceptance message to the terminal device, wherein the registration acceptance message includes: a registration result optional information element, and the short message service allowed field in the registration result optional information element includes: not allowing the short message service based on the non-access layer; the terminal device is used to release the connection and enter the idle state after receiving the registration acceptance message.

[0062] Furthermore, after extracting the content of the short message from the payload container cell, the content of the short message is cached in the target storage area; if the access and mobility management function entity does not support the short message service based on the non-access layer, the content of the short message is cleared from the target storage area.

[0063] In the above embodiment, if the AMF does not allow SMS over NAS, the AMF discards the cached SMS payload and does not send it to the SMSF. Compared to the prior art, the AMF has already received the SMS message and needs to clear the cached SMS message. This is because the AMF caches the message content for subsequent processing and forwarding. However, if the SMS over NAS service is determined to be disallowed, this cached data becomes useless. To effectively manage storage resources and avoid the long-term occupation of useless data, the AMF must promptly clear the cached SMS payload to free up storage space and ensure efficient utilization of network resources. Furthermore, short message content may contain sensitive user information, such as personal communications and verification codes. If the SMS service is not permitted, retaining this content in the AMF cache increases the risk of data leakage. Clearing cached short message data is a necessary security measure that helps protect user privacy and information security. Furthermore, in the core network, the caching and forwarding of SMS payloads are associated with specific UEs. If the AMF does not allow SMS over NAS but still retains the message content, it may cause confusion with other UEs or subsequent SMS service requests, leading to incorrect short message delivery or other signaling processing issues.

[0064] Furthermore, if the AMF does not allow SMS over NAS, the AMF sends a Registration Accept message with the optional 5GSregistration result information element, in which the SMS allowed field is filled with "SMS over NAS not allowed", indicating that the AMF does not allow the SMS over NAS function of this registration. After receiving the Registration Accept message, the terminal device releases the link, enters the idle state, and does not send SMS messages. At this point, the SMS over NAS message sending attempt fails.

[0065] Preferably, the registration request message further includes: a registration type mandatory information element, wherein the FOR field of the registration type mandatory information element includes: no subsequent request to be processed.

[0066] Among them, the registration type mandatory information element is the 5GS registration type mandatory information element, and the FOR field is filled in with "No follow-on request pending", indicating that the link is released after successful registration and the UE has no additional signaling to send immediately.

[0067] Preferably, the registration request message further includes: an update type optional information element, wherein the short message service request field of the update type optional information element includes: support for short message service based on non-access layer.

[0068] Among them, the update type optional information element is the 5GS update type optional information element, and the SMS requested field is filled in with "SMS over NAS supported", indicating that the UE supports the SMS over NAS function this time.

[0069] As other optional embodiments of the present application, the payload container type cell and the payload container cell are both optional cells; the format of the payload container type cell is type and value; the format of the payload container cell is: type, length and value, and the format of the payload container cell supports extension.

[0070] It should be noted that the detailed definitions of the payload container type information element and the payload container information element are consistent with the existing protocol. The extended message structure is as follows:

[0071]

[0072] It is understandable that the above steps S202 to S206 enhance the terminal device as follows:

[0073] 1. On the UE side, two optional information element encoding capabilities are added for the registration request message: Payload container type and Payload container. Payload container type can only support SMS type, and Payload container can only support SMS payload.

[0074] 2. In the NAS signaling MO short message scenario, when encoding the registration request message on the UE side, the SMS type must be encoded through the Payloadcontainer type information element, and the SMS payload must be encoded through the Payload container information element.

[0075] 3. In the NAS signaling MO short message scenario, when encoding the registration request message on the UE side, the FOR field in the 5GS registration type information element is filled in with "No follow-on request pending".

[0076] 4. After receiving the Registration Accept message carrying "SMS over NAS allowed", the UE releases the link and enters the idle state, and no longer sends short messages through the UL NAS Transport message.

[0077] The enhancements to AMF in steps S202 to S206 are as follows:

[0078] 1.AMF adds two optional element decoding capabilities for registration request messages: Payload container type and Payload container. Payload container type can only support SMS type, and Payload container can only support SMS payload.

[0079] 2. After receiving the registration request message, the AMF determines and decodes the Payload container type and Payloadcontainer optional information elements. If the SMS type and SMS payload are carried, the SMS payload is cached and the original functions such as SMSF selection are performed.

[0080] 3. If AMF allows SMS over NAS, AMF extracts the cached SMS payload and forwards it to SMSF.

[0081] 4. If AMF does not allow SMS over NAS, AMF discards the cached SMS payload and does not forward it to SMSF.

[0082] Figure 3 is a flow chart of another communication method according to an embodiment of the present application. Figure 3 As shown, the method includes the following steps:

[0083] Step S302: Send a registration request message to the access and mobility management function entity, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message.

[0084] When a UE needs to send a short message, it constructs a Registration Request message containing at least the Payload Container Type information element and the Payload Container information element. The Payload Container Type information element is set to indicate the type of short message, explicitly informing the network layer (AMF) that this Registration Request message contains a request to send a short message. The Payload Container information element contains the specific content of the short message, that is, the text of the short message that the UE wishes to send. The UE sends the constructed Registration Request message to the AMF, initiating the process of attempting to send a short message through the NAS layer.

[0085] Step S304: Receive a registration acceptance message sent by the mobility management function entity, release the connection and enter the idle state, wherein the registration acceptance message is sent when the access and mobility management function entity supports the short message service based on the non-access layer, and the access and mobility management function entity is used to determine that the registration request message carries a short message according to the payload container type information element, extract the content of the short message in the payload container information element, and forward the content of the short message to the short message service function entity.

[0086] When AMF receives the registration request message from UE, AMF will check the payload container type information element to determine whether the message contains short message content. If AMF allows sending short messages through the NAS layer (that is, supports SMS over NAS), it will extract the short message content from the payload container information element. After extracting the short message content, AMF forwards this content to SMSF, and AMF then sends a registration acceptance message to the UE to confirm that the UE's registration request has been accepted and indicates support for sending short messages through the NAS layer. After receiving the registration acceptance message sent by AMF, the UE confirms that the short message has been successfully processed through the NAS layer and there is no need to maintain the connection to send additional short message data. Therefore, the UE will release the connection with the network, return to the idle state, and wait for the next network interaction.

[0087] Steps S302 to S304 embed the short message content directly into the registration request message and, with the permission of the AMF, directly extract and process the short message from the message. This avoids the subsequent UL NAS Transport message, simplifies the signaling process of the short message service in the 5G network, and reduces radio resource consumption in the NTN (Non-Terrestrial Network) scenario. This optimization measure is particularly important for improving system efficiency and user experience in resource-constrained environments such as IoT-NTN (Internet of Things Non-Terrestrial Network). At the same time, this process ensures the reliability and timeliness of the short message service and is one of the key steps in optimizing the short message service at the NAS layer.

[0088] It should be noted that Figure 3 and Figure 2 The communication method shown is logically consistent, where Figure 2 The execution subject of the communication method shown is AMF, Figure 3 The execution subject of the communication method shown is UE. Figure 3 The preferred implementation of the embodiment shown can be found in Figure 2 The relevant description of the illustrated embodiment will not be repeated here.

[0089] Figure 4 is a flow chart of another communication method according to an embodiment of the present application. Figure 4As shown, the method includes the following steps:

[0090] Step S402: Receive a registration request message sent by the terminal device, wherein the registration request message is sent by the terminal device after receiving a paging message, and the registration request message includes at least a registration type mandatory information element.

[0091] Prior to step S402, the AMF and SMSF have established a connection. When a terminal device receives a short message in idle state, the UE receives a network downlink paging message. The AMF broadcasts the paging message through the gNB to cells in the network where the UE may be located. The paging message contains the UE's identity, which can be addressed using a 5G-S-TMSI or similar identifier. The UE monitors the paging channel and, upon detecting its identity in the paging message, responds to the network's paging. To formally access the network, the UE sends a Registration Request message.

[0092] In step S402, the registration request message sent by the UE carries the optional 5GS update type information element, in which the SMS requested field is filled with "SMS over NAS supported", indicating that the UE supports the SMS over NAS function in this registration. It also carries the mandatory 5GS registration type information element, in which the FOR field is filled with "No follow-on request pending", indicating that the link will be released after successful registration and the UE does not need to send or receive additional signaling immediately.

[0093] Step S404: In response to the registration request message, a registration acceptance message is sent to the terminal device, wherein the registration acceptance message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message; the terminal device is used to release the connection and enter the idle state after receiving the registration acceptance message.

[0094] In step S404, the Registration Accept message sent by the AMF carries the 5GS Registration Result optional information element, in which the SMS Allowed field is filled with "SMS over NAS Allowed", indicating that the AMF allows the SMS over NAS function for this registration. It also carries the Payload Container Type optional information element, filled with SMS, indicating that it carries an SMS short message; and the Payload Container optional information element, filled with SMS payload, indicating the content of the carried short message.

[0095] Compared to the existing technology, step S404 sends the short message to the UE in advance. Because the UE has already received the SMS message, there is no need to transmit the SMS message via the DL NAS Transport message. After receiving the Registration Accept message, the UE releases the connection and enters the idle state. At this point, the SMS over NAS short message reception is successful.

[0096] Through the above steps, the network-side AMF directly delivers the short message content during the UE registration process, further improving the efficiency and real-time performance of the short message service, avoiding the subsequent UL NAS Transport message, simplifying the signaling process of the short message service in the 5G network, and reducing radio resource consumption in NTN scenarios. This optimization measure is particularly important for improving system efficiency and user experience in resource-constrained environments such as IoT-NTN. At the same time, this process ensures the reliability and timeliness of the short message service and is one of the key steps in achieving NAS layer short message service optimization.

[0097] It should be noted that the detailed definitions of the payload container type information element and the payload container information element are consistent with the existing protocol. The extended message structure is as follows:

[0098]

[0099] It is understandable that the above steps S402 to S204 enhance the terminal device as follows:

[0100] 1. In the NAS signaling MT short message scenario, when encoding the Registration Request message on the UE side, the FOR field in the 5GSregistration type information element is filled with "No follow-on request pending".

[0101] 2. On the UE side, for the Registration Accept message, two optional information element decoding capabilities are added: Payload container type and Payload container. Payload container type can only support SMS type, and Payload container can only support SMS payload.

[0102] 3. In the NAS signaling MT short message scenario, after receiving the Registration Accept registration request message, the UE needs to determine and decode the Payload container type and Payload container optional information elements. If it carries the SMS type and SMS payload, the SMS short message is successfully received.

[0103] The enhancements to AMF from steps S402 to S204 are as follows:

[0104] 1. The AMF side adds two optional information element encoding capabilities, Payload container type and Payload container, to the Registration Accept registration request message; Payload container type can only support SMS type, and Payload container can only support SMS payload.

[0105] 2. In the NAS signaling MT short message scenario, after the AMF receives the Registration Request message, if SMS over NAS is supported, it shall encode the SMS type through the Payload container type information element and encode the SMS payload through the Payload container information element.

[0106] 3. In the NAS signaling MT short message scenario, after successful registration, the AMF no longer sends short messages via the DL NAS Transport message.

[0107] Figure 5 is a flow chart of another communication method according to an embodiment of the present application. Figure 5 As shown, the method includes the following steps:

[0108] Step S502: After receiving the paging message, a registration request message is sent to the access and mobility management function entity, wherein the registration request message is sent by the terminal device after receiving the paging message, and the registration request message includes at least: a registration type mandatory information element.

[0109] After receiving the Paging message from the network side, the UE will immediately respond and send a registration request message to the AMF. This message contains at least the mandatory registration type element (5GS registration type), which is used to inform the network of the registration type the UE is performing. It also includes the 5GS update type optional element, in which the SMS requested field is set to "SMS over NAS supported", indicating that the UE wants and can receive short messages through the NAS layer. In addition, the FOR field is set to "No follow-on request pending", which means that after the registration is completed, the UE will not immediately initiate other signaling interactions, but will directly enter the idle state.

[0110] Step S504: Receive a registration acceptance message sent by the access and mobility management function entity in response to the registration request message, wherein the registration acceptance message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message.

[0111] The UE then receives a Registration Accept message from the AMF in response to the registration request. This message contains at least the Payload container type and Payload container information elements. The Payload container type element indicates the type of short message being carried, while the Payload container element directly contains the content of the received short message. This optimization allows the short message to be delivered directly to the UE in the Registration Accept message, avoiding subsequent DL NAS Transport signaling interactions and reducing short message reception delays and network resource consumption.

[0112] Step S506: After receiving the registration acceptance message, the connection is released and the idle state is entered.

[0113] After successfully receiving the Registration Accept message and extracting the short message content from it, the UE releases the connection with the AMF and re-enters the idle state. This means that the UE has completed the short message reception process and no longer needs to maintain a connection with the network, thus saving power and radio resources. This is particularly important for resource-constrained IoT-NTN (Internet of Things Non-Terrestrial Network) devices.

[0114] Through steps S502 to S506, in 5G networks, especially in NTN and IoT-NTN environments, the optimized signaling process enables the UE to receive short messages more efficiently. The key to this optimized process is that the UE can directly indicate its support for the short message service in the registration request message and directly receive the short message content in the registration accept message, thus avoiding additional signaling interactions, reducing latency, and improving resource utilization efficiency.

[0115] It should be noted that Figure 5 and Figure 4 The communication method shown is logically consistent, where Figure 4 The execution subject of the communication method shown is AMF, Figure 5 The execution subject of the communication method shown is UE. Figure 5 The preferred implementation of the embodiment shown can be found in Figure 4 The relevant description of the illustrated embodiment will not be repeated here.

[0116] Figure 6 is a structural diagram of an access and mobility management function entity according to an embodiment of the present application, such as Figure 6 As shown, the access and mobility management functional entity includes:

[0117] The first receiving submodule 62 is used to receive a registration request message sent by a terminal device, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message.

[0118] The first extraction submodule 64 is configured to extract the content of the short message from the payload container cell after determining that the registration request message carries the short message according to the payload container type cell.

[0119] The first sending submodule 66 is used to forward the content of the short message to the short message service function entity and send the registration acceptance message to the terminal device when the access and mobility management function entity supports the short message service based on the non-access layer; the terminal device is used to release the connection and enter the idle state after receiving the registration acceptance message.

[0120] Figure 6 The preferred implementation of the embodiment shown can be found in Figure 2 The relevant description of the illustrated embodiment will not be repeated here.

[0121] Figure 7 is a structural diagram of a terminal device according to an embodiment of the present application, such as Figure 7 As shown, the terminal device includes:

[0122] The second sending submodule 72 is used to send a registration request message to the access and mobility management function entity, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message.

[0123] The second receiving submodule 74 is used to receive a registration acceptance message sent by the mobility management function entity, release the connection and enter the idle state, wherein the registration acceptance message is sent when the access and mobility management function entity supports the short message service based on the non-access layer, and the access and mobility management function entity is used to extract the content of the short message in the payload container element after determining that the registration request message carries the short message according to the payload container type element, and forward the content of the short message to the short message service function entity.

[0124] Figure 7 The preferred implementation of the embodiment shown can be found in Figure 3 The relevant description of the illustrated embodiment will not be repeated here.

[0125] Figure 8 is a structural diagram of another access and mobility management function entity according to an embodiment of the present application, such as Figure 8 As shown, the access and mobility management functional entity includes:

[0126] The third receiving submodule 82 is configured to receive a registration request message sent by a terminal device, wherein the registration request message is sent by the terminal device after receiving a paging message, and the registration request message includes at least a registration type mandatory information element.

[0127] The third sending submodule 84 is used to respond to the registration request message and send a registration acceptance message to the terminal device, wherein the registration acceptance message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message; the terminal device is used to release the connection and enter the idle state after receiving the registration acceptance message.

[0128] Figure 8 The preferred implementation of the embodiment shown can be found in Figure 4 The relevant description of the illustrated embodiment will not be repeated here.

[0129] Figure 9 is a structural diagram of another terminal device according to an embodiment of the present application, such as Figure 9 As shown, the terminal device includes:

[0130] The fourth sending submodule 92 is used to send a registration request message to the access and mobility management function entity after receiving the paging message, wherein the registration request message is sent by the terminal device after receiving the paging message, and the registration request message at least includes: a registration type mandatory information element.

[0131] The fourth receiving submodule 94 receives a registration acceptance message sent by the access and mobility management function entity in response to the registration request message, wherein the registration acceptance message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message.

[0132] The release submodule 96 is configured to release the connection and enter an idle state after receiving the registration acceptance message.

[0133] Figure 9 The preferred implementation of the embodiment shown can be found in Figure 5 The relevant description of the illustrated embodiment will not be repeated here.

[0134] Figure 10 is a structural diagram of a communication system according to an embodiment of the present application, such as Figure 10 As shown, the system includes: terminal equipment 1002, access and mobility management function entity 1004 and short message service function entity 1006, wherein,

[0135] The terminal device 1002 is configured to send a registration request message to the access and mobility management function entity 1004, where the registration request message includes at least a payload container type information element and a payload container information element, the payload container type information element being used to indicate whether the registration request message carries a short message, and the payload container information element including the content of the short message carried in the registration request message;

[0136] The access and mobility management function entity 1004 is configured to extract the content of the short message from the payload container cell after determining that the registration request message carries the short message according to the payload container type cell;

[0137] The access and mobility management function entity 1004 is further configured to forward the content of the short message to the short message service function entity 1006 and send a registration acceptance message to the terminal device 1002 when the short message service based on the non-access layer is supported;

[0138] The terminal device 1002 is further configured to release the connection and enter an idle state after receiving the registration acceptance message.

[0139] Figure 10 The preferred implementation of the embodiment shown can be found in Figure 2The relevant description of the illustrated embodiment will not be repeated here.

[0140] Figure 11 This is a signaling interaction diagram according to an embodiment of the present application. Figure 11 right Figure 2 、 Figure 3 and Figure 10 Specifically, Figure 11 The signaling interaction process shown is as follows:

[0141] (1) In idle state, the terminal user actively sends a short message.

[0142] (2) The UE sends a Registration Request message carrying the 5GS update type optional information element, where the SMS requested field is filled with "SMS over NAS supported", indicating that the UE supports the SMS over NAS function in this registration.

[0143] It's worth noting that the Registration Request message also carries the mandatory 5GS registration type information element, with the FOR field set to "No follow-on request pending," indicating that the link is released after successful registration and that no additional signaling is required from the UE immediately. The Payload container type, which is optional and is set to SMS, indicates that the message carries an SMS short message. The Registration Request message also carries the optional Payload container information element, set to SMS payload, indicating the message content.

[0144] (3) After the AMF recognizes that the Registration Request message carries an SMS message, it extracts the SMS payload, caches the SMS payload, and selects the SMSF.

[0145] (4) If the AMF allows SMS over NAS, the AMF forwards the SMS payload to the SMSF. Compared with the existing technology, this step is performed in advance.

[0146] (5) If the AMF allows SMS over NAS, the AMF shall carry the 5GS registration result optional information element when sending the Registration Accept message, where the SMS allowed field is filled with "SMS over NAS allowed", indicating that the AMF allows the SMS over NAS function for this registration.

[0147] (6) The connection is released and the UE enters the idle state. Compared with the prior art, there is no need to send an uplink NAS message carrying an SMS message.

[0148] (7) At this point, the SMS over NAS has successfully sent the short message.

[0149] (8) If the AMF does not allow SMS over NAS, the AMF discards the cached SMS payload and does not send it to the SMSF. Compared with the existing technology, the AMF has already received the SMS message in advance and needs to clear the cached SMS message.

[0150] (9) If the AMF does not allow SMS over NAS, the AMF shall send a Registration Accept message carrying the 5GS registration result optional information element, where the SMS allowed field is filled with "SMS over NAS not allowed", indicating that the AMF does not allow the SMS over NAS function of this registration.

[0151] (10) The link is released, the UE enters the idle state, and the UE does not send SMS messages.

[0152] (11) At this point, the SMS over NAS message sending process fails.

[0153] The optimized process significantly simplifies the signaling interaction between the UE and the AMF regarding short messages, reduces the radio resource consumption required for sending short messages, and shortens the latency of the entire short message sending process. This process improvement improves the efficiency of short message services and user experience in resource-constrained NTN environments, especially in IoT-NTN scenarios.

[0154] Figure 12 is a structural diagram of another communication system according to an embodiment of the present application, such as Figure 12 As shown, the system includes: a terminal device 1202 and an access and mobility management function entity 1204, wherein:

[0155] The terminal device 1202 is configured to send a registration request message to the access and mobility management function entity 1204 after receiving the paging message, wherein the registration request message is sent by the terminal device 1202 after receiving the paging message, and the registration request message includes at least: a registration type mandatory information element;

[0156] The access and mobility management function entity 1204 is configured to send a registration accept message to the terminal device 1202 in response to the registration request message, where the registration accept message includes at least a payload container type information element and a payload container information element. The payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message.

[0157] The terminal device 1202 is further configured to release the connection and enter an idle state after receiving the registration acceptance message.

[0158] Figure 12 The preferred implementation of the embodiment shown can be found in Figure 4 The relevant description of the illustrated embodiment will not be repeated here.

[0159] Figure 13 This is a signaling interaction diagram according to an embodiment of the present application. Figure 13 right Figure 4 、 Figure 5 and Figure 12 Specifically, Figure 13 The signaling interaction process shown is as follows:

[0160] (1) The core network AMF establishes a connection with the SMSF.

[0161] (2) In idle state, the terminal user receives a short message and the UE receives a downlink paging message from the network.

[0162] (3) The UE sends a Registration Request message carrying the 5GS update type optional information element, where the SMS requested field is filled with "SMS over NAS supported", indicating that the UE supports the SMS over NAS function in this registration.

[0163] It is worth noting that the registration request message also carries the mandatory 5GS registration type information element, in which the FOR field is filled with "No follow-on request pending", indicating that the link is released after successful registration and the UE does not need to send or receive additional signaling immediately;

[0164] (4) The AMF sends a Registration Accept message carrying the 5GS registration result optional information element, where the SMS allowed field is filled with "SMS over NAS allowed", indicating that the AMF allows the SMS over NAS function for this registration.

[0165] It is worth noting that the registration acceptance message also carries the optional Payload container type information element, which is filled in as SMS, indicating that it carries an SMS short message; the registration acceptance message also carries the optional Payload container information element, which is filled in as SMSpayload, indicating the content of the short message it carries.

[0166] Compared with the prior art, this step can send the short message to the UE in advance.

[0167] 5) The link is released and the UE enters the idle state (after successful registration, the UE has already received the SMS message in advance and no longer needs to transmit the SMS message through the DL NAS Transport message).

[0168] 6) At this point, the SMS over NAS successfully receives the short message.

[0169] The above optimization of the short message reception process, by directly carrying the short message content in the Registration Accept message, allows the network side to immediately deliver the short message when the UE completes registration without going through another round of signaling interaction. This not only simplifies UE operation but also reduces network load, which has a positive impact on reducing operating costs and improving service quality.

[0170] Figure 14 FIG1 shows a hardware structure block diagram of a computer terminal for implementing a communication method. Figure 14 As shown, the computer terminal 140 may include one or more (illustrated as 1402a, 1402b, ..., 1402n in the figure) processors 1402 (the processor 1402 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 1404 for storing data, and a transmission module 1406 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 the BUS bus), a network interface, a power supply and / or a camera. It will be understood by those skilled in the art that Figure 14 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 14 More or fewer components than shown, or with Figure 14 Different configurations shown.

[0171] It should be noted that the one or more processors 1402 and / or other data processing circuits described above may generally be referred to herein as "data processing circuitry." The data processing circuitry may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuitry may be a single, independent processing module, or may be incorporated in whole or in part into any of the other components of the computer terminal 140. As described in the embodiments of the present application, the data processing circuitry serves as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0172] The memory 1404 can be used to store software programs and modules of application software, such as program instructions / data storage devices corresponding to the communication method in the embodiment of the present application. The processor 1402 executes various functional applications and data processing by running the software programs and modules stored in the memory 1404, that is, implementing the above-mentioned communication method. The memory 1404 may include a high-speed random access memory, and may also include a 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 1404 may further include a memory remotely located relative to the processor 1402, and these remote memories may be connected to the computer terminal 140 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0173] The transmission module 1406 is configured to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by the communications provider of the computer terminal 140. In one embodiment, the transmission module 1406 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission module 1406 may be a radio frequency (RF) module, which is configured to communicate with the Internet wirelessly.

[0174] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 140 .

[0175] It should be noted that, in some optional embodiments, the above Figure 14 The computer terminal shown may include hardware elements (including circuits), software elements (including computer code stored on a computer-readable medium), or a combination of hardware elements and software elements. Figure 14 This is merely one example of a particular embodiment and is intended to illustrate the types of components that may be present in the computer terminal described above.

[0176] It should be noted that Figure 14 The computer terminal is used to execute Figures 2 to 5 The communication method shown, therefore, the relevant explanations in the execution method of the above command are also applicable to the electronic device and will not be repeated here.

[0177] An embodiment of the present application further provides a non-volatile storage medium, which includes a stored program, wherein when the program is executed, the device where the storage medium is located is controlled to execute the above communication method.

[0178] A program for a non-volatile storage medium to perform the following functions: receiving a registration request message sent by a terminal device, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element being used to indicate whether the registration request message carries a short message, and the payload container information element including the content of the short message carried in the registration request message; after determining that the registration request message carries a short message based on the payload container type information element, extracting the content of the short message from the payload container information element; forwarding the content of the short message to a short message service function entity and sending a registration acceptance message to the terminal device in the case where an access and mobility management function entity supports a short message service based on a non-access layer, and sending the registration acceptance message to the terminal device; the terminal device being used to release the connection and enter an idle state after receiving the registration acceptance message.

[0179] An embodiment of the present application further provides an electronic device, comprising: a memory and a processor, wherein the processor is configured to run a program stored in the memory, wherein the above communication method is executed when the program is run.

[0180] The processor is used to run a program that performs the following functions: receiving a registration request message sent by a terminal device, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message; after determining that the registration request message carries a short message according to the payload container type information element, extracting the content of the short message from the payload container information element; in the case where the access and mobility management function entity supports a short message service based on a non-access layer, forwarding the content of the short message to a short message service function entity, and sending a registration acceptance message to the terminal device; the terminal device is used to release the connection and enter an idle state after receiving the registration acceptance message.

[0181] The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0182] In the above embodiments of the present application, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0183] In the above-mentioned embodiments of the present application, the collected information 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 comply with relevant laws, regulations and standards, take necessary protection measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0184] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0185] The units described as separate components may or may not be physically separate, and 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 may be selected according to actual needs to achieve the purpose of the present embodiment.

[0186] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0187] If the integrated unit is implemented in the form of 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 the present application is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0188] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A communication method, characterized in that: include: receiving a registration request message sent by a terminal device, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element being used to indicate whether the registration request message carries a short message, and the payload container information element including content of the short message carried in the registration request message; After determining, according to the payload container type information element, that the registration request message carries the short message, extracting the content of the short message from the payload container information element; When the access and mobility management function entity supports the short message service based on the non-access layer, the content of the short message is forwarded to the short message service function entity, and the registration acceptance message is sent to the terminal device; the terminal device is used to release the connection and enter the idle state after receiving the registration acceptance message.

2. The method according to claim 1, characterized in that The registration acceptance message includes: a registration result optional information element, wherein the short message service allowed field in the registration result optional information element includes: allowing the short message service based on the non-access layer.

3. The method according to claim 1 or 2, characterized in that The method further comprises: In a case where the access and mobility management function entity does not support the short message service based on the non-access layer, a registration acceptance message is sent to the terminal device, wherein the registration acceptance message includes: a registration result optional information element, and the short message service allowed field in the registration result optional information element includes: not allowing the short message service based on the non-access layer; the terminal device is used to release the connection and enter the idle state after receiving the registration acceptance message.

4. The method according to claim 1, wherein The registration request message further includes: a registration type mandatory information element, wherein the FOR field of the registration type mandatory information element includes: no subsequent request to be processed.

5. The method according to claim 1 or 4, characterized in that The registration request message further includes: an update type optional information element, wherein the short message service request field of the update type optional information element includes: Supports short message service based on non-access layer.

6. The method according to claim 1, characterized in that The method further comprises: After extracting the content of the short message from the payload container cell, caching the content of the short message in a target storage area; In a case where the access and mobility management function entity does not support the short message service based on the non-access layer, the content of the short message is cleared from the target storage area.

7. The method according to claim 1, characterized in that include: The payload container type cell and the payload container cell are both optional cells; The format of the payload container type information element is type and value; The format of the payload container cell is: type, length and value, and the format of the payload container cell supports extension.

8. A communication method, characterized in that: include: Sending a registration request message to an access and mobility management function entity, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element being used to indicate whether the registration request message carries a short message, and the payload container information element including the content of the short message carried in the registration request message; Receive a registration acceptance message sent by the mobility management function entity, release the connection and enter an idle state, wherein the registration acceptance message is sent when the access and mobility management function entity supports a short message service based on a non-access layer, and the access and mobility management function entity is used to extract the content of the short message in the payload container information element after determining that the registration request message carries the short message according to the payload container type information element, and forward the content of the short message to the short message service function entity.

9. A communication method, characterized in that: include: Receiving a registration request message sent by a terminal device, wherein the registration request message is sent by the terminal device after receiving a paging message, and the registration request message includes at least: a registration type mandatory information element; In response to the registration request message, a registration acceptance message is sent to the terminal device, wherein the registration acceptance message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message; the terminal device is used to release the connection and enter the idle state after receiving the registration acceptance message.

10. The method according to claim 9, characterized in that include: The payload container type cell and the payload container cell are both optional cells; The format of the payload container type information element is type and value; The format of the payload container cell is: type, length and value, and the format of the payload container cell supports extension.

11. The method according to claim 9, characterized in that Before receiving the registration request message sent by the terminal device, the method further includes: establishing a communication connection with a short message service function entity.

12. A communication method, characterized in that: include: After receiving the paging message, sending a registration request message to the access and mobility management function entity, wherein the registration request message is sent by the terminal device after receiving the paging message, and the registration request message includes at least: a registration type mandatory information element; receiving a registration accept message sent by the access and mobility management function entity in response to the registration request message, wherein the registration accept message includes at least: a payload container type information element and a payload container information element, the payload container type information element being used to indicate whether the registration request message carries a short message, and the payload container information element including content of the short message carried in the registration request message; After receiving the registration acceptance message, the connection is released and the idle state is entered.

13. An access and mobility management functional entity, characterized in that: include: a first receiving submodule, configured to receive a registration request message sent by a terminal device, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element being used to indicate whether the registration request message carries a short message, and the payload container information element including the content of the short message carried in the registration request message; A first extraction submodule is configured to extract the content of the short message from the payload container information element after determining, based on the payload container type information element, that the registration request message carries the short message; The first sending submodule is used to forward the content of the short message to the short message service function entity and send the registration acceptance message to the terminal device when the access and mobility management function entity supports the short message service based on the non-access layer; the terminal device is used to release the connection and enter the idle state after receiving the registration acceptance message.

14. A terminal device, characterized in that: include: a second sending submodule, configured to send a registration request message to an access and mobility management function entity, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element being used to indicate whether the registration request message carries a short message, and the payload container information element including content of the short message carried in the registration request message; The second receiving submodule is used to receive a registration acceptance message sent by the mobility management function entity, release the connection and enter the idle state, wherein the registration acceptance message is sent when the access and mobility management function entity supports a short message service based on the non-access layer, and the access and mobility management function entity is used to extract the content of the short message in the payload container information element after determining that the registration request message carries the short message according to the payload container type information element, and forward the content of the short message to the short message service function entity.

15. An access and mobility management functional entity, characterized in that: include: a third receiving submodule, configured to receive a registration request message sent by a terminal device, wherein the registration request message is sent by the terminal device after receiving a paging message, and the registration request message includes at least: a registration type mandatory information element; The third sending submodule is used to respond to the registration request message and send a registration acceptance message to the terminal device, wherein the registration acceptance message at least includes: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message; the terminal device is used to release the connection and enter the idle state after receiving the registration acceptance message.

16. A terminal device, characterized in that: include: a fourth sending submodule, configured to send a registration request message to the access and mobility management function entity after receiving the paging message, wherein the registration request message is sent by the terminal device after receiving the paging message, and the registration request message includes at least: a registration type mandatory information element; a fourth receiving submodule, receiving a registration accept message sent by the access and mobility management function entity in response to the registration request message, wherein the registration accept message includes at least: a payload container type information element and a payload container information element, the payload container type information element being used to indicate whether the registration request message carries a short message, and the payload container information element including the content of the short message carried in the registration request message; The release submodule is used to release the connection and enter the idle state after receiving the registration acceptance message.

17. A communication system, characterized in that: include: Terminal equipment, access and mobility management functional entity and short message service functional entity, wherein, The terminal device is used to send a registration request message to the access and mobility management function entity, wherein the registration request message includes at least: a payload container type information element and a payload container information element, the payload container type information element is used to indicate whether the registration request message carries a short message, and the payload container information element includes the content of the short message carried in the registration request message; The access and mobility management function entity is configured to extract the content of the short message from the payload container information element after determining, according to the payload container type information element, that the registration request message carries the short message; The access and mobility management function entity is further configured to forward the content of the short message to the short message service function entity and send a registration acceptance message to the terminal device when a short message service based on a non-access layer is supported; The terminal device is further configured to release the connection and enter an idle state after receiving the registration acceptance message.

18. A communication system, characterized in that: include: Terminal equipment and access and mobility management functional entities, where: The terminal device is configured to send a registration request message to the access and mobility management function entity after receiving the paging message, wherein the registration request message is sent by the terminal device after receiving the paging message, and the registration request message includes at least: a registration type mandatory information element; The access and mobility management function entity is configured to send a registration acceptance message to the terminal device in response to the registration request message, wherein the registration acceptance message includes at least: a payload container type information element and a payload container information element, the payload container type information element being used to indicate whether the registration request message carries a short message, and the payload container information element including content of the short message carried in the registration request message; The terminal device is further configured to release the connection and enter an idle state after receiving the registration acceptance message.

Images