Communication method and apparatus

Abstract

Provided in the embodiments of the present application are a communication method and apparatus. The method comprises: a first access network device receiving response information for first request information from a core network element, wherein the response information for the first request information is used for indicating that a network accepts the registration of a first terminal device; the first access network device sending a first paging message on the basis of the response information for the first request information, wherein the first paging message comprises first identification information of the first terminal device; the first access network device receiving a first paging response message from the first terminal device, wherein the first paging response message is used for responding to the first paging message; and then, the first access network device sending the response information for the first request information to the first terminal device on the basis of the first paging response message. In a registration process of the first terminal device, by means of the method, the first access network device can send registration response information from a core network to the first terminal device in a normal manner, so that the first terminal device is effectively registered with a network.

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on November 3, 2023, with application number 202311461399.9 and application name “A Communication Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of wireless communication technology, and in particular to a communication method and device. Background Art

[0004] Non-terrestrial network (NTN) communications refer to communications achieved with the aid of non-terrestrial network equipment. NTN systems can include satellite systems, among others. Generally, NTNs include two major scenarios: transparent payloads and regenerative payloads. Transparent payloads consider satellites to be relay nodes on the network side. The satellites alter the frequency carrier of uplink RF signals, filtering and amplifying them before downlink transmission, but the waveform of the carried signals remains unchanged. Regenerative payloads, on the other hand, convert and amplify uplink RF signals before downlink transmission, effectively providing full or partial base station functionality on the satellite.

[0005] In a discontinuous regenerative payload feeding scenario, also known as store and forward (S&F), during the operation of a regenerative payload satellite, both the access connection and the feed connection are not always available. This means that the access connection and the feed connection may be disconnected for a period of time. When a terminal initiates the initial access process, if the feed connection is not always available, the access network device may not be able to find the terminal to receive the message when forwarding it from the core network device. This may prevent the terminal from completing the initial access process normally.

[0006] In view of this, in the S&F scenario, how to normally complete the initial access process of the terminal is an urgent problem to be solved.

[0007] Summary of the Invention

[0008] This application proposes a communication method and device, which can be applied in the S&F scenario and can normally complete the initial access process of the terminal.

[0009] In the first aspect, the present application provides a communication method, which can be executed by a first access network device, or by a chip or chip system corresponding to the first access network device, without specific limitation. Taking the first access network device as an example, the method can specifically include: the first access network device receives a response message to a first request message from a core network network element, and the response message to the first request message is used to indicate that the network accepts the registration of the first terminal device; then the first access network device sends a first paging message based on the response message to the first request message; the first paging message includes the first identification information of the first terminal device; then the first access network device receives a first paging response message from the first terminal device, and the first paging response message is used to respond to the first paging message; finally, the first access network device sends a response message to the first request message to the first terminal device based on the first paging response message.

[0010] In the present application scheme, after the first access network device receives the response information of the first request information from the core network network element, it can send a first paging message based on the response information of the first request information, and the first paging message includes the first identification information of the first terminal device; then, after receiving the first paging response message from the first terminal device, it can send the response information of the first request information to the first terminal device normally based on the first paging response message, so that the registration process of the first terminal device is completed normally.

[0011] In one possible implementation, the first access network device receives a response message to the first request message from the core network network element. At this time, the service area of ​​the first access network device does not cover the location of the first terminal device when the first request message is received. When the service area of ​​the first access network device covers the location of the first terminal device when the first request message is received, the first access network device then sends a first paging message including the above-mentioned first identification information based on the response message to the first request message. This implementation can be applied to, but is not limited to, a non-continuous power feeding scenario. Through this implementation, after the first access network device receives the response message to the first request message from the core network network element, and the service area of ​​the first access network device covers the location of the first terminal device when the first request message is received, it can ensure that the first terminal device can be effectively paged.

[0012] The "network" referred to in the embodiments of the present application may be a 4G evolved packet system (EPS), a 5G system (5GS), or other communication systems or future communication systems. EPS and 5GS include an access network and a core network. Core network elements belong to the network.

[0013] In a possible implementation manner, the first paging message includes indication information, so as to indicate that the first paging message is a core network CN paging message.

[0014] In the embodiments of the present application, the first identification information includes but is not limited to the following implementations:

[0015] Implementation method 1: the first identification information is identification information of the access layer; the identification information of the access layer is allocated by the first access network device; or the identification information of the access layer is allocated by the first terminal device.

[0016] Implementation method 2: the first identification information is the identification information of the non-access layer; the identification information of the non-access layer is allocated by the core network element; or the identification information of the non-access layer is pre-configured on the first terminal device and the core network element.

[0017] Based on the second embodiment described above, in one possible implementation, the first identification information is assigned to the first terminal device by the core network during an authentication and authorization process for the first terminal device. The method further includes: during the authentication and authorization process, the first access network device sending a second paging message, where the second paging message includes the second identification information of the first terminal device.

[0018] The second identification information may include the following:

[0019] Sub-method 1: the second identification information is identification information of the access layer; Sub-method 2: the second identification information is identification information of the non-access layer.

[0020] For the above-mentioned embodiment 1, and sub-method 1 under embodiment 2, in a possible embodiment, the method further includes: the first access network device receives a first request message from the first terminal device, the first request message is used to request that the first terminal device be registered to the network; if the first access network device has no feeder connection (the type of the first access network device may also be referred to as the S&F type), a first message is sent to the first terminal device, the first message is used to trigger the first terminal device to retain the radio resource control RRC context, and the RRC context includes identification information of the access layer corresponding to the first terminal device. In an embodiment of the present application, the first access network device may carry the first message in an RRC connection release message and send it to the first terminal device.

[0021] For the above-mentioned embodiment 2 not combined with the sub-method, and sub-method 2 in embodiment 2, in one possible implementation, the method may further include: a first access network device receives a first request message from a first terminal device, the first request message being used to request that the first terminal device be registered with the network; if the first access network device has no feeder connection, sending a second message to the first terminal device, the second message being used to trigger the first terminal device to release the radio resource control RRC context. In this embodiment of the present application, the first access network device may carry the second message in an RRC connection release message and send it to the first terminal device.

[0022] In one possible implementation, the method further includes: the first access network device determining, based on a local configuration, that the first access network device has no feeder connection; or, the first access network device determining, based on interface connection information between the first access network device and a core network device, that the first access network device has no feeder connection; or, determining, based on feeder connection status information of the first access network device, that the first access network device has no feeder connection. With this implementation, the first access network device can effectively determine whether it has a feeder connection.

[0023] In the embodiment of the present application, the first access network device having no feeder connection may also be referred to as: the type of the first access network device is S&F. The first access network device having no feeder connection may include, but is not limited to, the following situations: the satellite where the first access network device is located has no connection with the gateway; or the first access network device has no connection with the gateway; or the first access network device has no connection with the core network device (for example, there is no transport layer connection between the first access network device and a core network element, or there is no N2 or N3 connection between the first access network device and a core network element).

[0024] In one possible implementation, the method further includes: the first access network device sending first indication information to the first terminal device; the first indication information is used to trigger the first terminal device to not send the first request information within a preset time or before receiving a response to the first request information. This implementation is applicable, but not limited to, scenarios where power feeding is discontinuous. This implementation avoids the waste of resources caused by the first terminal device continuously sending the first request information when there is no power feeding connection.

[0025] In a possible implementation, before the first access network device sends the first paging message, it also includes: the first access network device receives second indication information from the core network network element; the second indication information is used to trigger the first access network device to page the first terminal device before receiving the response information of the first request information; then the first access network device sends the first paging message according to the response information of the first request information, which may include: sending the first paging message according to the second indication information and the response information of the first request information.

[0026] In an embodiment of the present application, the first access network device receiving a response to the first request may trigger the first access network device to send a first paging message; or the response to the first request may carry identification information, and the first access network device may generate or determine the first identification information based on the identification information. This application does not specifically limit how the first access network device sends the first paging message based on the response to the first request.

[0027] Through this implementation, the first access network device can send response information to the first request information after paging the first terminal device, thereby effectively reducing the overhead caused by sending the response information to the first request information.

[0028] In one possible embodiment, the method further includes: the first access network device sending a third indication message to the first terminal device, where the third indication message is used to trigger the first terminal device to delete the first identification information after receiving the first paging message or the response message of the first request message. Through this embodiment, the first terminal device promptly deletes the first identification information used in the current paging response process to prevent it from affecting the next response to other paging messages.

[0029] In a second aspect, the present application provides a communication method, which can be executed by a first terminal device or by a chip or chip system corresponding to the first terminal device, without specific limitation. Taking the first terminal device as an example, the method can specifically include: the first terminal device sends a first request message to a first access network device, where the first request message is used to request that the first terminal device be registered with the network; the first terminal device then receives a first paging message from the first access network device, where the first paging message includes first identification information of the first terminal device; the first terminal device is of a discontinuous feeding type, and determines not to send a service request message to the first access network device.

[0030] In this application solution, a first terminal device sends a first request message to a first access network device to request network registration. The first terminal device then receives a first paging message from the first terminal device, which includes first identification information of the first terminal device. If the first terminal device is of a discontinuous power feeding type, the service request message is not sent to the first access network device. This effectively reduces the resource overhead associated with sending service request messages.

[0031] In a possible implementation manner, the first paging message includes indication information, so as to indicate that the first paging message is a core network CN paging message.

[0032] In the embodiments of the present application, the first identification information includes but is not limited to the following implementations:

[0033] Implementation method 1: the first identification information is identification information of the access layer; the identification information of the access layer is allocated by the first access network device; or the identification information of the access layer is allocated by the first terminal device.

[0034] Implementation method 2: the first identification information is the identification information of the non-access layer; the identification information of the non-access layer is allocated by the core network element; or the identification information of the non-access layer is pre-configured on the first terminal device and the core network element.

[0035] In one possible implementation, based on the above implementation one, the first terminal device sends a first paging response message to the first access network device, and the first paging response message is used to respond to the first paging message and request to restore the radio resource control RRC connection. Or based on the above implementation two, the first terminal device sends a first paging response message to the first access network device, and the first paging response message is used to respond to the first paging message and request to establish a radio resource control RRC connection; after the RRC connection is restored or the RRC connection is established, the first terminal device receives response information of the first request information from the first access network device through the RRC connection; the response information of the first request information is used to instruct the network to accept the registration of the first terminal device.

[0036] This embodiment can be applied in scenarios where power feeding is discontinuous. After the first terminal device responds to the first paging message of the first access network device, it can request to establish or restore an RRC connection, and then effectively receive response information to the first request information from the first access network device through the RRC connection.

[0037] In one possible implementation, based on the above-mentioned implementation one, the method further includes: the first terminal device receives first information, and the first information is used to trigger the first terminal device to retain the radio resource control RRC context; then the first terminal device retains the RRC context based on the first information. This implementation facilitates the subsequent paging of the first terminal device by the first access network device using the identification information of the access layer. In an embodiment of the present application, the second access network device can carry the first information in an RRC connection release message and send it to the first terminal device.

[0038] In a possible implementation, based on the above-mentioned implementation method 2, the method further includes: the first terminal device receives second information, and the second information is used to trigger the first terminal device to release the radio resource control RRC context; then the first terminal device releases the RRC context according to the second information. This implementation method can be applied in a scenario where the feeding is discontinuous. When the first access network device has no feeding connection, the resources and overhead occupied by the connection between the first terminal device and the first access network device can be reduced through this implementation method. In an embodiment of the present application, the second access network device can carry the first information in an RRC connection release message and send it to the first terminal device.

[0039] In one possible implementation, the first identification information is allocated to the first terminal device by the core network during the authentication and authorization process of the first terminal device; then the method also includes: during the authentication and authorization process, the first terminal device receives a second paging message from the first access network device, and the second paging message includes the second identification information of the first terminal device.

[0040] In an embodiment of the present application, the second identification information may be identification information of the access stratum or identification information of the non-access stratum. The core network allocates identification information of the access stratum or the non-access stratum to the first terminal device, and determines whether the first access network device instructs the first terminal device to release the RRC context. If the RRC context is not released, the second identification information is identification information of the access stratum; if the RRC context is released, the second identification information is identification information of the non-access stratum.

[0041] In a possible embodiment, the method also includes: the first terminal device receives third indication information from the first access network device, and the third indication information is used to trigger the first terminal device to delete the first identification information after receiving the first paging message or the response information of the first request information; the first terminal device deletes the first identification information according to the third indication information.

[0042] Through this implementation, the first terminal device can promptly delete the first identification information used in the current process of responding to the paging message, so as to prevent it from affecting the next response to other paging messages.

[0043] In a third aspect, the present application provides a communication method, which can be executed by a first terminal device or by a chip or chip system corresponding to the first terminal device, without specific limitation. Taking the first terminal device as an example, the method may specifically include: the first terminal device sends a first request message to the first access network device, the first request message being used to request that the first terminal device be registered with the network; the first terminal device receives a first paging message from the first access network device, and the first terminal device sends a first paging response message; the first paging response message is used to respond to the first paging message; then the first terminal device receives a first indication message from the first access network device, the first indication message being used to trigger the first terminal device not to send the first request message within a preset time or before receiving a response message to the first request message; the first terminal device stops sending the first request message according to the first indication message within the preset time or before receiving a response message to the first request message; or the first terminal device stops sending the first request message according to local configuration within a preset time or before receiving a response message to the first request message.

[0044] In the present application scheme, the first terminal device can send a first paging response message to the first access network device after responding to the first paging message of the first access network device; it can also not send the first request information within a preset time period or before receiving the response information of the first request information based on the instruction information from the first access network device or local configuration, thereby avoiding multiple requests to occupy resources and generate additional overhead.

[0045] In a fourth aspect, the present application provides a communication method, which can be executed by a core network element, or by a chip or chip system corresponding to the core network element, without specific limitation. Taking the core network element as an example, the method can specifically include: the core network element receiving a first request message from a first access network device, the first request message being used to request that the first terminal device be registered with the network; when the first terminal device is of a discontinuous power feeding type, the core network element sending a paging message to the first access network device based on the first request message, the paging message being used to trigger the first access network device to page the first terminal device.

[0046] In the present application scheme, after the core network network element receives the first request information from the first access network device, the first terminal device is of a non-continuous feeding type. Then, the core network network element can send a paging message to the first access network device based on the first request information to trigger the first access network device to page the first terminal device, so that the subsequent first access network device can normally send the response information of the first request information from the core network network element to the first terminal device.

[0047] In one possible implementation, the method further includes: the core network element sending a response message to the first access network device, wherein the response message to the first request message is used to indicate that the network accepts the registration of the first terminal device. Through this implementation, the registration of the first terminal device can be completed.

[0048] In one possible implementation, the method further includes: the core network element sending second instruction information to the first access network device; the second instruction information is used to instruct the first access network device to page the first terminal device before receiving the response information to the first request information. This implementation avoids additional overhead caused by sending the response information to the first request information.

[0049] In a possible implementation, the method further includes: the core network element determining that the first terminal device is of a discontinuous power feeding type. Through this implementation, it can be effectively determined that the first terminal device is of a discontinuous power feeding type.

[0050] In the embodiment of the present application, the core network element may determine that the first terminal device is of a discontinuous feeding type by, but not limited to, the following methods:

[0051] Method 1: The core network element determines that the first terminal device is a non-continuous feeding type based on the contract information of the terminal device; the contract information may include but is not limited to one or more of a specific group, a specific DNN, and S-NSSAI.

[0052] Method 2: The core network element determines that the first terminal device is of the discontinuous power feeding type based on the capability information of the first access network device; the capability information of the first access network device indicates that the first access network device supports discontinuous power feeding. For example, the first access network device RAN can indicate to the core network element (mobility management entity MME / mobility management function AMF) in an NG setup message or a radio access network configuration update message that it supports discontinuous power feeding or is of the discontinuous power feeding type. The core network element MME / AMF can then know that the first terminal device served by the first access network device is also of the discontinuous power feeding type.

[0053] Method 3: The core network element determines that the first terminal device is of a non-continuous power feeding type based on the tracking area TA information supported by the first access network device and the tracking area TA where the first terminal device is located. For example, when the core network element receives the first request information, it also receives tracking area TA indication information from the first access network device, which indicates that the tracking area TA where the first terminal device is located is not included in the tracking area TA list supported by the first access network device.

[0054] In one possible implementation, the method further includes: the core network element receives first identification information of the first terminal device from the first access network device, and the first identification information is allocated by the first terminal device. Optionally, the first terminal device can carry the first identification information in the first request information and send it to the core network element through the first access network device. Subsequently, the core network element carries the first identification information in a paging message and sends it to the first access network device. Through this implementation, the core network element effectively obtains the first identification information allocated by the first terminal device, so that the core network element subsequently forwards it to the first access network device for paging the first terminal device.

[0055] In a possible implementation, the method further includes: the core network element allocating first identification information of the first terminal device; and then sending the first identification information to the first access network device, where the first identification information is used by the first access network device to page the first terminal device.

[0056] Through this implementation method, the first access network device can obtain the first identification information of the first terminal device, so as to be used for subsequent effective paging of the first terminal device.

[0057] In a possible implementation, the first identification information is allocated to the first terminal device by the core network during an authentication and authorization process of the first terminal device.

[0058] Through this implementation, the first terminal device can effectively obtain the first identification information so that it can subsequently respond normally to the first paging message of the first access network device.

[0059] In a possible implementation, the method further includes: the core network element sends second identification information of the first terminal device, and the second identification information is used by the first access network device to page the first terminal device in the first terminal device authentication process.

[0060] Through this implementation, the first terminal device can normally respond to the paging of the first access network device during the authentication process, so as to effectively complete the authentication process.

[0061] The embodiment of the present application also provides another communication method, which can be seen in detail in the following fifth to ninth aspects.

[0062] In a fifth aspect, the present application provides a communication method, which can be executed by a first access network device, or by a chip or chip system corresponding to the first access network device, without specific limitation. Taking the first access network device as an example, the method may specifically include: the first access network device receives a response message to a first request message from a core network network element, and the response message to the first request message is used to indicate that the network accepts the registration of the first terminal device; the first access network device sends a first paging message based on the response message to the first request message; the first paging message includes the first identification information of the first terminal device; then the first access network device receives a first paging response message from the first terminal device, and the first paging response message is used to respond to the first paging message; the first access network device sends a response message to the first request message to the first terminal device based on the first paging response message.

[0063] In one possible implementation, the first access network device receives a response message to the first request message from the core network network element. At this time, the service area of ​​the first access network device does not cover the location of the first terminal device when the first request message is received. When the service area of ​​the first access network device covers the location of the first terminal device when the first request message is received, the first access network device then sends a first paging message including the above-mentioned first identification information based on the response message to the first request message. This implementation can be applied to, but is not limited to, a non-continuous power feeding scenario. Through this implementation, after the first access network device receives the response message to the first request message from the core network network element, and the service area of ​​the first access network device covers the location of the first terminal device when the first request message is received, it can ensure that the first terminal device can be effectively paged.

[0064] In a possible implementation manner, the first paging message includes indication information, so as to indicate that the first paging message is a core network CN paging message.

[0065] In the embodiments of the present application, the first identification information includes but is not limited to the following implementations:

[0066] Implementation method 1: the first identification information is identification information of the access layer; the identification information of the access layer is allocated by the first access network device; or the identification information of the access layer is allocated by the first terminal device.

[0067] Implementation method 2: the first identification information is the identification information of the non-access layer; the identification information of the non-access layer is allocated by the core network element; or the identification information of the non-access layer is pre-configured on the first terminal device and the core network element.

[0068] Based on the second embodiment described above, in one possible implementation, the first identification information is assigned to the first terminal device by the core network during an authentication and authorization process for the first terminal device. The method further includes: during the authentication and authorization process, the first access network device sending a second paging message, where the second paging message includes the second identification information of the first terminal device.

[0069] The second identification information may include the following:

[0070] Sub-method 1: the second identification information is identification information of the access layer; Sub-method 2: the second identification information is identification information of the non-access layer.

[0071] The technical effects of the fifth aspect can refer to the technical effects of the first aspect mentioned above, and will not be repeated here.

[0072] In one possible implementation, a context connection is established between the first terminal device and the second access network device, but no context connection is established with the first access network device; the method also includes: the first access network device receives the connection context of the second access network device; the connection context of the second access network device includes the RRC context, wherein the RRC context includes identification information of the access layer corresponding to the first terminal device.

[0073] In a possible implementation, the first access network device receives the connection context of the second access network device in the following ways, but not limited to:

[0074] Method 1: The first access network device receives the connection context of the second access network device from the core network element.

[0075] Method 2: The first access network device receives the connection context of the second access network device from the second access network device.

[0076] Based on the above-mentioned method 2, in one possible implementation manner, the first access network device first receives the identification information of the second access network device; then, based on the identification information of the second access network device, the first access network device sends a context request message to the second access network device, where the context request message is used to request the connection context of the second access network device.

[0077] Based on the above-mentioned method 2, in another possible implementation manner, the core network network element first sends the identification information / indication information of the first access network device to the second access network device; then the second access network device sends its own connection context to the first access network device based on the identification information / indication information of the first access network device.

[0078] This application does not specifically limit the way and method of sending the connection context of the second access network device to the first access network device.

[0079] In a possible implementation, before the first access network device sends the first paging message, it also includes: the first access network device receives second indication information from the core network network element; the second indication information is used to trigger the first access network device to page the first terminal device before receiving the response information of the first request information; then the first access network device sends the first paging message according to the response information of the first request information, which may include: the first access network device sends the first paging message according to the second indication information and the response information of the first request information.

[0080] In an embodiment of the present application, the first access network device receiving a response to the first request may trigger the first access network device to send a first paging message; or the response to the first request may carry identification information, and the first access network device may generate or determine the first identification information based on the identification information. This application does not specifically limit how the first access network device sends the first paging message based on the response to the first request.

[0081] Through this implementation, the first access network device can send response information to the first request information after paging the first terminal device, thereby effectively reducing the overhead caused by sending the response information to the first request information.

[0082] In one possible implementation, the method further includes: the first access network device sending a third indication message to the first terminal device, where the third indication message is used to trigger the first terminal device to delete the first identification information after receiving the first paging message or the response message to the first request message. Through this implementation, the first terminal device promptly deletes the first identification information used in the current paging response process to prevent it from affecting the next response to other paging messages.

[0083] In a sixth aspect, the present application provides a communication method, which can be executed by a second access network device or by a chip or chip system corresponding to the second access network device, without specific limitation. Taking the second access network device as an example, the second access network device is of a discontinuous feeding type. The method may specifically include: the second access network device receiving a first request message from a first terminal device, the first request message being used to request that the first terminal device be registered with the network; sending the first request message to a core network network element, and sending a connection context of the second access network device.

[0084] In the present application scheme, after the second access network device receives the first request information from the first terminal device, the second access network device sends the first request information to the core network network element, and the connection context of the second access network device is also generated, so that the response information of the first request information from the core network network element can be forwarded to the first terminal device through other more suitable access network devices (i.e., the first access network device), thereby more efficiently completing the registration process of the first terminal device.

[0085] In one possible implementation, the method further includes: when the second access network device determines that the second access network device has no feeder connection, sending first information to the first terminal device, where the first information is used to trigger the first terminal device to release or retain a connection context; the connection context includes an RRC context. The RRC context includes identification information of the access layer corresponding to the first terminal device. In an embodiment of the present application, the second access network device can carry the first information in an RRC connection release message and send it to the first terminal device.

[0086] Through this implementation, when the second access network device has no feeder connection, if the first terminal device is instructed to retain the RRC context, it is convenient to subsequently use the access layer identification information to paging the first terminal device; if the first terminal device is paged using the non-access layer identification information, the first terminal device is instructed to release the RRC context, which can save the resources and overhead occupied by the RRC context.

[0087] In a possible implementation manner, the second access network device may send the connection context of the second access network device in the following manners, but not limited to:

[0088] Method 1: The second access network device sends the connection context of the second access network device to the core network element.

[0089] Then, the core network element sends the connection context of the second access network device to the first access network device.

[0090] Method 2: Send the connection context of the second access network device to the first access network device.

[0091] Based on the above-mentioned method 2, in a possible implementation manner, the second access network device first receives context request information from the first access network device, where the context request information is used to request a connection context for the second access network device; and then sends the connection context to the first access network device based on the context request information.

[0092] Based on the above-mentioned second approach, in another possible implementation, the second access network device first receives identification information of the first access network device; and then sends the connection context to the first access network device according to the identification information of the first access network device.

[0093] In one possible implementation, the second access network device determines that the second access network device has no feeder connection, which may include but is not limited to: determining that the second access network device has no feeder connection based on local configuration; or, determining that the second access network device has no feeder connection based on interface connection information between the second access network device and the core network device; or, determining that the second access network device has no feeder connection based on feeder connection status information of the second access network device.

[0094] In one possible implementation, the second access network device having no feeder connection may be referred to as: the second access network device type is S&F. The second access network device having no feeder connection may include, but is not limited to, the following situations: the satellite where the second access network device is located has no connection with the gateway; or the second access network device has no connection with the gateway; or the second access network device has no connection with the core network device (for example, there is no transport layer connection between the second access network device and a core network element, or there is no N2 or N3 connection between the second access network device and a core network element).

[0095] In one possible implementation, the method further includes: the second access network device sending first indication information to the first terminal device; the first indication information is used to trigger the first terminal device to not send the first request information within a preset time or before receiving a response to the first request information. This implementation is applicable, but not limited to, scenarios where power feeding is discontinuous. This implementation avoids the waste of resources caused by the first terminal device continuously sending the first request information when there is no power feeding connection.

[0096] In the seventh aspect, the present application provides a communication method, which can be executed by a first terminal device or by a chip or chip system corresponding to the first terminal device, without specific limitation. Taking the first terminal device as an example, the method can specifically include: the first terminal device sends a first request message to the second access network device, where the first request message is used to request that the first terminal device be registered with the network; the first terminal device receives a first paging message from the first access network device, where the first paging message includes the first identification information of the first terminal device; when the first terminal device is of a non-continuous feeding type and the first terminal device does not receive a response message to the first request message, it is determined not to send a service request message to the first access network device.

[0097] In this application solution, a first terminal device sends a first request message to a second access network device to request network registration. The first terminal device receives a first paging message from the first terminal device, which includes the first identification information of the first terminal device. If the first terminal device is of a discontinuous power feeding type, the service request message is not sent to the first access network device. This effectively reduces the resource overhead generated by sending the service request message.

[0098] In a possible implementation manner, the first paging message includes message indication information, so as to indicate that the first paging message is a core network CN paging message.

[0099] In the embodiments of the present application, the first identification information includes but is not limited to the following implementations:

[0100] Implementation method 1: the first identification information is identification information of the access layer; the identification information of the access layer is allocated by the first access network device; or the identification information of the access layer is allocated by the first terminal device.

[0101] Implementation method 2: the first identification information is the identification information of the non-access layer; the identification information of the non-access layer is allocated by the core network element; or the identification information of the non-access layer is pre-configured on the first terminal device and the core network element.

[0102] In a possible implementation, based on the above-mentioned implementation one, the method also includes: the first terminal device receives first information, and the first information is used to trigger the first terminal device to retain the radio resource control RRC context; then the first terminal device retains the RRC context according to the first information.

[0103] According to the implementation method, after receiving the response information of the first request information, the first access network device can use the identification information of the access layer to page the first terminal device.

[0104] In another possible implementation, based on the second implementation, the method further includes: the first terminal device receiving second information, the second information being used to trigger the first terminal device to release a radio resource control (RRC) context; and the first terminal device releasing the RRC context based on the second information. This implementation can be applied in scenarios where power feeding is discontinuous. When the first access network device has no power feeding connection, this implementation can reduce the resources and overhead occupied by the connection between the first terminal device and the first access network device.

[0105] In one possible implementation, based on the above-described first implementation, the first terminal device sends a first paging response message to the first access network device, where the first paging response message is used to respond to the first paging message and request restoration of the radio resource control (RRC) connection. After the RRC connection is restored, the first terminal device receives response information to the first request information from the first access network device via the RRC connection; the response information to the first request information is used to instruct the network to accept the registration of the first terminal device.

[0106] In another possible implementation, based on the above-mentioned implementation mode 2, the first terminal device sends a first paging response message to the first access network device, and the first paging response message is used to respond to the first paging message and request to establish a radio resource control RRC connection; after the RRC connection is established, the first terminal device receives response information of the first request information from the first access network device through the RRC connection; the response information of the first request information is used to indicate that the network accepts the registration of the first terminal device.

[0107] The above implementation can be applied to scenarios where power feeding is discontinuous. When the first terminal device responds to the first paging message of the first access network device, it can also request to establish or restore the RRC connection, and then effectively receive the response information of the first request information from the first access network device through the RRC connection.

[0108] In one possible implementation, the first identification information is allocated to the first terminal device by the core network during the authentication and authorization process of the first terminal device; then the method also includes: during the authentication and authorization process, the first terminal device receives a second paging message from the first access network device, and the second paging message includes the second identification information of the first terminal device.

[0109] In an embodiment of the present application, the second identification information may be identification information of the access layer or identification information of the non-access layer. The core network allocates identification information of the access layer or the non-access layer to the first terminal device, and will determine whether the second access network device instructs the first terminal device to release the RRC context. If the second identification information is identification information of the access layer, correspondingly, the first terminal device receives first information from the second access network device, and the first information is used to instruct the first terminal device to retain the RRC context; if the second identification information is identification information of the non-access layer, correspondingly, the first terminal device receives first information from the second access network device, and the first information is used to instruct the first terminal device to release the RRC context.

[0110] In an embodiment of the present application, the second access network device can carry the first information in an RRC connection release message and send it to the first terminal device.

[0111] In one possible implementation, the method further includes: the first terminal device receiving third indication information from the first access network device, the third indication information being used to trigger the first terminal device to delete the first identification information after receiving the first paging message or the response information to the first request information; and the first terminal device deleting the first identification information based on the third indication information. This implementation allows the first terminal device to promptly delete the first identification information used in the current paging response to prevent it from affecting the next response to another paging message.

[0112] In an eighth aspect, the present application provides a communication method, which can be executed by a first terminal device or by a chip or chip system corresponding to the first terminal device, without specific limitation. Taking the first terminal device as an example, the method may specifically include: the first terminal device sends a first request message to the second access network device, the first request message being used to request that the first terminal device be registered with the network; the first terminal device receives a first paging message from the first access network device; the first terminal device sends the first paging response message; the first paging response message is used to respond to the first paging message; the first terminal device receives a first indication message from the first access network device, the first indication message being used to trigger the first terminal device to not send the first request message within a preset time or before receiving a response message to the first request message; the first terminal device stops sending the first request message according to the first indication message within the preset time or before receiving a response message to the first request message; or the first terminal device stops sending the first request message according to local configuration within a preset time or before receiving a response message to the first request message.

[0113] In the present application scheme, the first terminal device can send a first paging response message to the first access network device after responding to the first paging message of the first access network device; it can also not send the first request information within a preset time period or before receiving the response information of the first request information based on the instruction information from the first access network device or local configuration, thereby avoiding multiple requests to occupy resources and generate additional overhead.

[0114] Ninthly, the present application provides a communication method, which can be executed by a core network element, or by a chip or chip system corresponding to the core network element, without specific limitation. Taking the core network element as an example, the method may specifically include: the core network element receiving a first request message from a second access network device, the first request message being used to request registration of a first terminal device to the network; when the first terminal device is of a discontinuous power feeding type, the core network element sending a paging message to the first access network device based on the first request message, the paging message being used to trigger the first access network device to page the first terminal device.

[0115] In the present application scheme, after the core network network element receives the first request information from the first access network device, the first terminal device is of a non-continuous feeding type. Then, the core network network element can send a paging message to the first access network device based on the first request information to trigger the first access network device to page the first terminal device, so that the subsequent first access network device can normally send the response information of the first request information from the core network network element to the first terminal device.

[0116] In one possible implementation, the method further includes: the core network element sending a response message to the first access network device regarding the first request message, wherein the response message to the first request message is used to indicate that the network accepts the registration of the first terminal device. With this implementation, the registration of the first terminal device can be completed.

[0117] In one possible implementation, the method further includes: the core network element sending second instruction information to the first access network device; the second instruction information is used to instruct the first access network device to page the first terminal device before receiving the response information to the first request information. This implementation avoids additional overhead caused by sending the response information to the first request information.

[0118] In a possible implementation, the method further includes: the core network element determining that the first terminal device is of a discontinuous power feeding type. Through this implementation, it can be effectively determined that the first terminal device is of a discontinuous power feeding type.

[0119] In the embodiment of the present application, the core network element may determine that the first terminal device is of a discontinuous feeding type by, but not limited to, the following methods:

[0120] Method 1: The core network element determines that the first terminal device is a non-continuous feeding type based on the contract information of the terminal device; the contract information may include but is not limited to one or more of a specific group, a specific DNN, and S-NSSAI.

[0121] Method 2: The core network element determines that the first terminal device is of the discontinuous power feeding type based on the capability information of the second access network device; the capability information of the second access network device indicates that the second access network device supports discontinuous power feeding. For example, the second access network device RAN can indicate to the core network element (mobility management entity MME / mobility management function AMF) in an NG setup message or a radio access network configuration update message that it supports discontinuous power feeding or is of the discontinuous power feeding type. The core network element MME / AMF then knows that the first terminal device served by the second access network device is also of the discontinuous power feeding type.

[0122] Method 3: Determine that the first terminal device is of a non-continuous feeding type based on the tracking area TA information supported by the second access network device and the TA where the first terminal device is located. For example, when the core network element receives the first request information, it also receives tracking area TA indication information from the second access network device, which indicates that the tracking area TA where the first terminal device is located is not included in the tracking area TA list supported by the second access network device.

[0123] In one possible implementation, the method further includes: the core network element receiving the first identification information of the first terminal device from the second access network device. Optionally, the first terminal device can carry the first identification information in the first request information and send it to the core network element via the second access network device. The core network element then carries the first identification information in a paging message and sends it to the first access network device. Through this implementation, the core network element effectively obtains the first identification information allocated by the first terminal device, and the core network element subsequently forwards it to the first access network device for paging the first terminal device.

[0124] In one possible implementation, the method further includes: a core network element allocating first identification information of the first terminal device; and the core network element sending the first identification information to the first access network device, where the first access network device uses the first identification information to page the first terminal device. This implementation method enables the first access network device to obtain the first identification information of the first terminal device, thereby subsequently using it to effectively page the first terminal device.

[0125] In one possible implementation, the first identification information is assigned to the first terminal device by the core network during the authentication process of the first terminal device. This implementation effectively enables the first terminal device to obtain the first identification information so that it can subsequently respond normally to the first paging message from the first access network device.

[0126] In a possible implementation, the method further includes: the core network element sends second identification information of the first terminal device to the first access network device, and the second identification information is used by the first access network device to page the first terminal device in the authentication process of the first terminal device.

[0127] Through this implementation, the first terminal device can normally respond to the paging of the first access network device during the authentication process, so as to effectively complete the authentication process.

[0128] In the tenth aspect, an embodiment of the present application also provides a communication device, which can be used to execute the method of the first aspect or the fifth aspect. The device can be a first access network device, or the device can be a component in the first access network device (for example, a chip, or a chip system, or a circuit), or it can be a device that can be used in combination with the first access network device.

[0129] In one possible implementation, the device may include a module or unit corresponding to the method / operation / step / action described in the first aspect or the fifth aspect, and the module or unit may be a hardware circuit, or software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the method described in the first aspect or any possible embodiment of the first aspect, or the processing unit may be used to perform the method described in the fifth aspect or any possible embodiment of the fifth aspect.

[0130] In the eleventh aspect, an embodiment of the present application also provides a communication device, which can be used to execute the method of the second aspect or the third aspect or the seventh aspect or the eighth aspect. The device can be a first terminal device, or the device can be a component in the first terminal device (for example, a chip, or a chip system, or a circuit), or it can be a device that can be used in combination with the first terminal device.

[0131] In one possible implementation, the device may include a module or unit corresponding to the method / operation / step / action described in the second aspect or the third aspect or the seventh aspect or the eighth aspect, and the module or unit may be a hardware circuit, or software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, the processing unit may be used to perform the method described in the second aspect or any possible embodiment of the second aspect, or the processing unit may be used to perform the method described in the third aspect or any possible embodiment of the third aspect, or the processing unit may be used to perform the method described in the seventh aspect or any possible embodiment of the seventh aspect, or the processing unit may be used to perform the method described in the eighth aspect or any possible embodiment of the eighth aspect.

[0132] In the twelfth aspect, an embodiment of the present application also provides a communication device, which can be used to execute the method of the fourth aspect or the ninth aspect. The device can be a core network element, or the device can be a component in the core network element (for example, a chip, or a chip system, or a circuit), or it can be a device that can be used in combination with the core network element.

[0133] In one possible implementation, the device may include a module or unit corresponding to the method / operation / step / action described in the fourth aspect or the ninth aspect, and the module or unit may be a hardware circuit, or software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the method described in the fourth aspect or any possible embodiment of the fourth aspect, or the processing unit may be used to perform the method described in the ninth aspect or any possible embodiment of the ninth aspect.

[0134] In the thirteenth aspect, an embodiment of the present application also provides a communication device, which can be used to execute the method of the sixth aspect. The device can be a second access network device, or the device can be a component in the second access network device (for example, a chip, or a chip system, or a circuit), or it can be a device that can be used in combination with the second access network device.

[0135] In one possible implementation, the device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the sixth aspect, and the module or unit may be a hardware circuit, or software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the method described in any possible implementation of the eighth aspect or the sixth aspect.

[0136] In the fourteenth aspect, an embodiment of the present application provides a device, which includes: at least one processor and a communication interface; wherein the communication interface is used to communicate with other devices; the processor is used to run a set of programs so that the device can implement the method provided by the above-mentioned first aspect or any possible implementation method thereof, or so that the device can implement the method provided by the above-mentioned second aspect or any possible implementation method thereof, or so that the device can implement the method provided by the above-mentioned third aspect or any possible implementation method thereof, or so that the device can implement the method provided by the above-mentioned fourth aspect or any possible implementation method thereof, or so that the device can implement the method provided by the above-mentioned fifth aspect or any possible implementation method thereof, or so that the device can implement the method provided by the above-mentioned sixth aspect or any possible implementation method thereof, or so that the device can implement the method provided by the above-mentioned seventh aspect or any possible implementation method thereof, or so that the device can implement the method provided by the above-mentioned eighth aspect or any possible implementation method thereof, or so that the device can implement the method provided by the above-mentioned ninth aspect or any possible implementation method thereof.

[0137] In the fifteenth aspect, an embodiment of the present application also provides a computer storage medium, which stores a software program. When the software program is read and executed by one or more processors, it can implement the method provided by the first aspect or any possible implementation method thereof, or implement the method provided by the second aspect or any possible implementation method thereof, or implement the method provided by the third aspect or any possible implementation method thereof, or implement the method provided by the fourth aspect or any possible implementation method thereof, or implement the method provided by the fifth aspect or any possible implementation method thereof, implement the method provided by the sixth aspect or any possible implementation method thereof, or implement the method provided by the seventh aspect or any possible implementation method thereof, or implement the method provided by the eighth aspect or any possible implementation method thereof, or implement the method provided by the ninth aspect or any possible implementation method thereof.

[0138] In the sixteenth aspect, an embodiment of the present application also provides a computer program product comprising instructions, which, when run on a computer, enables the method provided in the first aspect or any possible implementation thereof to be executed, or enables the method provided in the second aspect or any possible implementation thereof to be executed, or enables the method provided in the third aspect or any possible implementation thereof to be executed, or enables the method provided in the fourth aspect or any possible implementation thereof to be executed, or enables the method provided in the fifth aspect or any possible implementation thereof to be executed, or enables the method provided in the sixth aspect or any possible implementation thereof to be executed, or enables the method provided in the seventh aspect or any possible implementation thereof to be executed, or enables the method provided in the eighth aspect or any possible implementation thereof to be executed, or enables the method provided in the ninth aspect or any possible implementation thereof to be executed.

[0139] In the seventeenth aspect, an embodiment of the present application provides a communication system, comprising a first access network device capable of implementing the method provided in the first or fifth aspect above, a first terminal device capable of implementing the method provided in the second or third aspect above or the seventh or eighth aspect above, and a core network network element capable of implementing the method provided in the fourth or ninth aspect above.

[0140] In a possible implementation, the communication system also includes a second access network device capable of implementing the method provided in the sixth aspect above.

[0141] In the eighteenth aspect, an embodiment of the present application also provides a chip system, which includes a processor for supporting a first access network device to implement the functions involved in the first or fifth aspect above; or for supporting a first terminal device to implement the functions involved in the second or third aspect or the seventh or eighth aspect above; or for supporting a core network network element to implement the functions involved in the fourth or ninth aspect above, or for supporting a second access network device to implement the functions involved in the sixth aspect above.

[0142] In one possible design, the chip system further includes a memory for storing necessary program instructions and data for execution by the loading device. The chip system can be composed of a chip or include a chip and other discrete devices.

[0143] It should be noted that the technical effects that can be achieved by any possible implementation method of the above-mentioned tenth to eighteenth aspects or the tenth to eighteenth aspects can be correspondingly described with reference to the technical effects that can be achieved by any possible implementation method of the above-mentioned first to ninth aspects or the first to ninth aspects; they will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0144] FIG1A is a schematic diagram of the structure of a transparent payload NTN;

[0145] FIG1B is a schematic structural diagram of a regenerative load;

[0146] FIG1C is a schematic diagram of data storage and forwarding in a discontinuous power feeding scenario of a regenerative load;

[0147] FIG2A is a schematic diagram of a 5G initial access process;

[0148] FIG2B is a schematic diagram of a 4G attach process;

[0149] FIG2C is a schematic diagram of a 5G initial registration process;

[0150] FIG3A is a communication system to which the method according to an embodiment of the present application can be adapted;

[0151] FIG3B is another communication system to which the method according to an embodiment of the present application can be adapted;

[0152] FIG3C is a schematic diagram of a network structure to which the method according to an embodiment of the present application can be adapted;

[0153] FIG4A is a flow chart of a communication method according to an embodiment of the present application;

[0154] FIG4B is a flow chart of another communication method provided in an embodiment of the present application;

[0155] FIG5A is a flow chart of another communication method provided in an embodiment of the present application;

[0156] FIG5B is a flow chart of another communication method provided in an embodiment of the present application;

[0157] FIG6 is a flow chart of a first implementation method provided in an embodiment of the present application;

[0158] FIG7 is a flow chart of a second implementation method provided in an embodiment of the present application;

[0159] FIG8 is a flow chart of a third implementation method provided in an embodiment of the present application;

[0160] FIG9 is a flow chart of a fourth implementation method provided in an embodiment of the present application;

[0161] FIG10 is a flow chart of a fifth implementation method provided in an embodiment of the present application;

[0162] FIG11 is a flow chart of a sixth implementation method provided in an embodiment of the present application;

[0163] FIG12 is a schematic diagram of a communication device provided in an embodiment of the present application;

[0164] FIG13 is a schematic diagram of another communication device provided in an embodiment of the present application;

[0165] FIG14 is a schematic diagram of another chip device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0166] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. The terms used in the following embodiments are only for the purpose of describing specific embodiments and are not intended to be limiting of the present application. As used in the specification and appended claims of the present application, the singular expressions "one", "a kind of", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the embodiments of the present application, "one or more" refers to one, two or more; "and / or" describes the association relationship of associated objects, indicating that three relationships may exist; for example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship.

[0167] References to "one embodiment" or "some embodiments" etc. described in this specification mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the sentences "in one embodiment", "in some embodiments", "in other embodiments" etc. that appear in different places in this specification do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in another way. The terms "include", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in another way. Words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions, and any embodiment or design described as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other embodiments or designs. The use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete way for easy understanding. In addition, in the drawings of the embodiments of the present application, the steps in the dotted lines or dotted boxes are optional steps.

[0168] The multiple involved in the embodiments of the present application refers to greater than or equal to two. It should be noted that in the description of the embodiments of the present application, words such as "first" and "second", or specific numbers "1", "2", "3", etc., are only used to distinguish the purpose of description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order. In addition, the term "used for indication" mentioned in the description of the embodiments of the present application can include being used for direct indication and being used for indirect indication. When describing a certain indication information used to indicate A, it can include that the indication information directly indicates A or indirectly indicates A, and it does not mean that the indication information must carry A.

[0169] This application provides a communication method. To better understand the embodiments of this application, the following first explains the names and related technical features involved in the embodiments of this application. It should be noted that these explanations are intended to make the embodiments of this application easier to understand and should not be regarded as limiting the scope of protection claimed by this application.

[0170] 1. Satellite architecture:

[0171] 3GPP is committed to integrating 5G networks with satellites. Starting from the R15 version, 3GPP has carried out the standardization work of non-terrestrial networks (NTN) and satellite overall architecture (SAT_ARCH).

[0172] NTN includes two major scenarios: transparent forwarding and regenerative forwarding. As shown in Figure 1A, transparent payload NTN treats the satellite as a network-side relay node. The satellite changes the frequency carrier of the uplink RF signal, filtering and amplifying it before downlink transmission, but the waveform of the carried signal remains unchanged. As shown in Figure 1B, regenerative payload converts and amplifies the uplink RF signal before downlink transmission, including demodulation / decoding, encoding / modulation, and other functions. This is equivalent to having all or part of the base station functions on the satellite.

[0173] In Figures 1A and 1B, a service link refers to the wireless connection between the NTN payload and the terminal UE, or the connection between the satellite and the terminal UE. For example, in a regenerative payload scenario, if there is no service link, there will be no connection between the access network RAN ​​and the terminal UE. A feeder link refers to the wireless connection between the NTN gateway and the NTN payload, or the connection between the satellite and the gateway. This connection can be a direct connection between the satellite and the gateway, or an indirect connection between the satellite and the gateway via a third-party connection (such as an intersatellite link between other satellites or a connection between other satellites and the gateway). For example, in a regenerative payload scenario, if there is no feeder link, there will be no connection between the RAN and the core network.

[0174] In this application, the presence or absence of a service connection essentially refers to the presence or absence of a connection between the UE and the RAN, and the presence or absence of a feeder connection essentially refers to the presence or absence of a connection between the RAN and the core network. "Service connection" and "feeder connection" can also be replaced by other terms. For example, "service connection" can be replaced by "access connection," and "feeder connection" can be replaced by "ground link."

[0175] 5GC is the 5G core network, which can also be replaced by EPC, the 4G evolved packet core (EPC). The MME is part of the EPC, and the AMF is part of the 5GC. The radar shown in the figure is a gateway. In the figure, the satellite and gateway are maintained by the satellite operator. The mobile phone (UE), SAT-BS (i.e., NG-RAN, which is on the satellite in the regenerative satellite scenario), 5GC, and EPC are maintained by the public land mobile network (PLMN). Satellite operators maintain the physical connection between the satellite and the terrestrial UE and gateway. Mobile network operators send data and signaling within the mobile network based on the physical connection maintained by the satellite operator.

[0176] 2. Scenario of discontinuous power feeding:

[0177] The 3GPP R19 version discusses a scenario of discontinuous feeding based on regenerative load, also known as a store and forward (S&F) scenario. As shown in Figure 1C, in this scenario, during the operation of a satellite, the service connection (access connection) and the feed connection of a base station on a satellite are not always available, that is, the access connection and the feed connection will be disconnected for a certain period of time. In this scenario, the service connection (access connection) and the feed connection cannot be available at the same time. Therefore, the base station deployed on the satellite can receive and store the UE's uplink data when the service connection (access connection) is available; when the feed connection is available, forward the stored UE uplink data to the core network, and receive and store the downlink data sent to the UE from the core network. When the service connection (access connection) is available again, forward the stored downlink data to the UE. For ease of explanation, the embodiments of the present application are described based on the scenario that the service connection (also called access connection) and the feed connection are not available at the same time at any time, but it is applicable to other discontinuous feeding scenarios.

[0178] 3. Initial access process:

[0179] Taking the process of initial UE access to the 5G network as an example, as shown in Figure 2A, it can include: S201A: UE performs cell search and selection based on the broadcast of the base station gNodeB; S202A: UE and the base station gNodeB perform a random access process; S203A: UE and the base station gNodeB perform an RRC connection establishment process; S204A: UE and the core network 5GC perform an initial context establishment process; S205A: UE and the core network 5GC perform a PDU session establishment process.

[0180] When a UE joins the network, it first performs S201A (cell search and selection) and S202A (random access). These two steps allow the UE to negotiate physical layer uplink and downlink synchronization with the access network equipment (RAN) (e.g., gNodeB) and determine a UE identifier used between the UE and RAN. After these two steps are completed, signaling between the UE and RAN can be exchanged without being confused with signaling from other UEs.

[0181] After completing random access in S202A, the UE establishes an RRC connection with the RAN. This establishes a signaling radio bearer (SRB) between the RAN and the UE. The SRB is used for signaling transmission and can be categorized into the following types based on the signaling carried:

[0182] SRB0: SRB0 does not need to be established and always exists. SRB0 is used to carry RRC signaling before the RRC connection is successfully established and is transmitted through the CCCH logical channel. (That is, SRB0 will be available after the first two steps are completed)

[0183] SRB1: SRB1 is used to carry the RRC signaling after the successful establishment of the radio resource control (RRC) connection and the NAS signaling before the establishment of SRB2, and is transmitted through the DCCH logical channel. Therefore, the purpose of establishing an RRC connection is to establish SRB1, and then transmit the RRC signaling after the successful establishment of the RRC connection through SRB1. After the RRC connection is successfully established, the UE and RAN will each save an RRC context, including the UE's identifier (such as the cell radio network temporary identifier (C-RNTI)), SRB resource information, etc. (The RRC layer mentioned below may refer to RRC signaling and RRC context)

[0184] SRB2: SRB2 is used to carry non-access stratum (NAS) signaling and is transmitted through the DCCH logical channel. SRB2 has a lower priority than SRB1 and can only be established after the security mode is activated. SRB2 is established through RRC reconfiguration. NAS signaling is the signaling for transmitting information between the UE and the core network elements. The RAN is only responsible for forwarding. This signaling is above the RRC layer, that is, NAS signaling can only occur after the RRC connection is established. The NAS layer mentioned later refers to the NAS signaling and the context stored by the UE and the core network for the connection between the UE and the core network, such as the content sent in the initial access process, including the NAS layer identifier of the UE, such as the user concealed identifier (SUCI), the globally unique temporary identity (GUTI), etc.

[0185] In the embodiments of the present application, the "initial access" involved refers to the initial context establishment, that is, the process of establishing a connection between the UE and the core network. For example, the initial access process of 4G is the 4G attach process. The initial access process of 5G is the 5G initial registration process.

[0186] Exemplarily, the initial access process takes the 4G attach process as an example. The UE sends an initial access request to the access network device (S201B in Figure 2B), including a globally unique temporary identifier GUTI, a tracking area identity (last visit TAI) and other information. The access network device forwards the UE's initial access request to the core network. The core network executes processes such as obtaining the UE's subscription and policy and authenticating the UE based on the UE's request, and then replies with an initial access acceptance message to the UE through the access network device (step S207B in Figure 2B). After receiving the initial access acceptance message, the UE replies with an initial access completion message to the core network through the access network device. After the core network receives this message and performs actions such as configuring the bearer, the initial access process is completed.

[0187] 1. As shown in Figure 2B, the 4G attach process may include the following:

[0188] S201B: The UE sends an Attach Request message to the RAN. The message includes the IMSI or GUTI, Attach Type, and ESM message container.

[0189] S202B: The RAN forwards an attach request message to the mobility management entity (MME), where the message includes the selected network (TAI+ECGI).

[0190] S203B: The MME sends an Identity Request to the UE. If the MME does not recognize the GUTI provided by the UE, it instructs the UE to provide an International Mobile Subscriber Identity (IMSI).

[0191] S204B: The MME receives the IMSI provided by the UE.

[0192] S205B: The UE performs the authentication process.

[0193] S206B: The MME interacts with other core network elements to complete the session establishment and other processes.

[0194] S207B: The MME sends a downlink NAS transport with attach accept message to the RAN. The message includes: GUTI, target tracking area identity (TAI) List, and session management request.

[0195] S208B: After RRC connection reconfiguration, the RAN forwards an attach accept message to the UE.

[0196] FIG2B only illustrates some general steps in the 4G attach process. The detailed steps of the process can refer to the existing 4G attach process and are not listed here one by one.

[0197] 2. As shown in Figure 2C, the 5G registration process may include the following:

[0198] S201C: The UE sends a registration request message to the RAN. The registration request message may also be called an AN message. The message includes: 5G-S temporary mobile subscriber identity (sae-temporary mobile subscriber identity, S-TMSI), selected public land mobile network identity (selected-public land mobile network-identity, Selected PLMN ID), network slice selection assistance information (NSSAI), and registration request container.

[0199] S202C: The RAN sends a Registration Request message to the AMF. The Registration Request message may also be referred to as an N2 message.

[0200] The message includes the selected public land mobile network identifier (selected PLMN ID), terminal location information and cell identifier (UE Location Information and Cell Identity), and a registration request container.

[0201] S203C: If the AMF does not recognize the GUTI provided by the UE, the AMF sends an Identity Request message to the UE, instructing the UE to provide the Sured User Identifier (SUCI). S203C is optional.

[0202] S204C: The AMF receives the SUCI provided by the UE.

[0203] S205C: The UE performs the authentication process.

[0204] S206C: AMF interacts with other core network elements to complete the process of obtaining UE subscription and policy information.

[0205] S207C: AMF sends a registration accept message to RAN. The registration accept message includes: 5G-GUTI, registration area, and allowed network slice selection auxiliary information Allowed NSSAI.

[0206] S208C: RAN forwards the registration accept message to the UE.

[0207] FIG2C only illustrates some general steps / processes in the 5G registration process. The detailed steps of the process can refer to the existing 5G registration process and are not listed here one by one.

[0208] 4. UE connection status:

[0209] The process of establishing a connection between a UE and an access network device is mainly divided into three steps: cell search, physical access, and signaling process establishment. Among them, the first step of establishing the signaling process includes establishing an RRC connection. After the RRC connection between the UE and the RAN is established, both the UE and the RAN side will save an RRC context, which includes a radio network temporary identifier (RNTI). This identifier is the identifier assigned by the RAN to the UE in this RRC connection. It is the identifier used between the UE and the RAN to identify the UE. After the RRC connection is established, the UE can establish a connection with the core network, that is, initiate the initial access process. Once the initial access process is completed, the connection between the UE and the core network is established.

[0210] After the initial access process between the UE and the core network is completed, the UE can have multiple connection states:

[0211] Taking 5G as an example, the UE connection states include: connected state (CM-CONNECTED), idle state (CM-IDLE), and RRC deactivated state (RRC-INACTIVE).

[0212] When a UE is in idle state: a. There is no RRC connection on the Uu interface between the UE and the gNB. Similarly, there is no RRC context information for the UE on the gNB, nor on the UE itself. However, the UE retains context with the core network (e.g., GUTI). c. A UE in idle state monitors paging messages to learn if there are any incoming calls. Upon receiving a paging message, it restores the RRC connection on the Uu interface and reconnects to the network (initiating a service request procedure). The paging message includes identifiers used between the UE and the core network to identify the UE (e.g., GUTI, IMSI).

[0213] When the UE is in the inactive state:

[0214] a. Uu interface between the UE and gNB: No RRC connection exists, but the gNB stores the UE's context information, and the UE also stores RRC context information (e.g., RNTI). c. Compared to an idle UE, an inactive UE can re-enter the connected state by simply restoring the RRC connection over the Uu interface, resulting in shorter recovery latency. The inactive UE monitors RAN paging messages, which include identifiers used between the UE and the RAN (e.g., RNTI). Upon receiving the RAN paging message, the inactive UE re-enters the connected state.

[0215] In 4G, the UE connection states are only idle and connected. However, there is also a special state in the idle state - CM-IDLE with suspend. This state is similar to the RRC inactive part and can also use the identity used between the UE and the RAN to page the UE.

[0216] 5. Paging:

[0217] Core Network (CN) paging: Triggered by the AMF (5G) / MME (4G) Mobility Management Function (AMF), a paging message is sent to the RAN. Based on this paging message, the RAN sends a paging message to the UE (the paging messages sent by the RAN and AMF / MME are not identical). This paging message also includes the UE identifier used between the CN and UE. Upon receiving this paging message from the RAN, the UE establishes an RRC connection with the RAN and then initiates a service request to restore its connection to the CN.

[0218] RAN paging: Triggered by the RAN, a paging message is sent to the UE. The RAN-triggered paging message includes the UE identifier (e.g., RNTI) used between the RAN and the UE. After receiving the RAN paging message, the UE initiates the RRC resume procedure to restore the RRC connection with the RAN.

[0219] In a regenerative payload feed discontinuous (S&F) scenario, during the operation of a regenerative payload satellite, the access connection and the feed connection are not always available, that is, the access connection and the feed connection will be disconnected for a period of time. When the terminal device initiates the initial access process, if the feed connection is not always available, the access network device may not be able to find the UE to receive the message when forwarding the message from the core network device to the UE, which will cause the terminal to fail to complete the initial access process normally. In view of this, how to normally complete the initial access process of the terminal in the S&F scenario is an urgent problem to be solved.

[0220] Therefore, the present application proposes a communication method, which can be applied in the S&F scenario and can normally complete the initial access process of the terminal.

[0221] The communication method provided in the embodiments of this application can be applied to an NTN communication system. The NTN communication system can include non-terrestrial network devices such as drones, high altitude platform stations (HAPS), and satellites to form a network and provide services such as data transmission and voice communication to terminal devices. In addition, the NTN system can also include other non-terrestrial network devices, which are not limited by this application.

[0222] The NTN communication system can also support various mobile communication systems, such as a new radio (NR) system, a long term evolution (LTE) system, or other communication systems such as future communication systems, and the specific ones are not limited here.

[0223] In NTN communications, NTN equipment can operate in two modes: transparent and regenerative. Based on the operating mode of the NTN equipment, NTN communication architectures can be categorized into two types: First, a transparent forwarding architecture, in which NTN equipment can act as relays or amplifiers, performing RF filtering, amplification, and regenerating physical layer signals. NTN equipment can be responsible for Layer 1 (L1) relaying, performing physical layer forwarding, and is invisible to higher layers. Second, a regenerative architecture, in which NTN equipment performs the processing functions of access network equipment. For example, satellites operating in regenerative mode can be categorized as regenerative satellites without inter-satellite links (ISLs) between satellites; regenerative satellites with ISLs, in which satellites have interfaces for direct data exchange, where the ISLs are Xn ports; or regenerative satellites with the processing functions of distributed units (DUs) of access network equipment, in which case the satellites act as DUs.

[0224] For example, Figure 3A shows a schematic diagram of an NTN communication architecture applicable to embodiments of the present application. This NTN scenario can be a transparent forwarding communication architecture. In the communication architecture shown in Figure 3A, a terminal device can communicate with the 5G core network (CN) through the access network, and then connect to the data network (DN) through the 5G CN. Satellites and NTN gateways can serve as relay devices between terminal devices and access network devices or as remote radio units (RRUs) of access network devices.

[0225] For example, Figure 3B illustrates another NTN communication architecture applicable to embodiments of the present application. This NTN communication architecture can be a regenerative communication architecture. In the communication architecture shown in Figure 3B , satellites can serve as access network devices, forming an access network with NTN gateways and communicating with the core network through the NTN gateways. Furthermore, satellites can provide wireless access services to terminal devices. Figure 3B exemplifies a regenerative satellite architecture without intersatellite links.

[0226] It should be noted that Figures 3A and 3B only illustrate one satellite and one NTN gateway. In actual use, an architecture with multiple satellites and / or multiple NTN gateways may be adopted as needed. Each satellite may provide services to one or more terminal devices, each NTN gateway may correspond to one or more satellites, and each satellite may correspond to one or more NTN gateways, although this embodiment of the present application does not specifically limit this.

[0227] It should be noted that Figures 3A and 3B are only examples of the NTN communication architecture. The NTN communication architecture may also include other specific devices, and this application does not limit this. Based on the NTN communication architecture, the embodiments of this application can be applied to, but not limited to, discontinuous feeding (also known as store and forward (S&F) scenarios).

[0228] The devices involved in the embodiments of the present application include terminal devices, access network devices, and core network devices.

[0229] A terminal device, also known as user equipment (UE), mobile station (MS), or mobile terminal (MT), refers to a device that provides voice and / or data connectivity to users. For example, a terminal device can be a handheld device or vehicle-mounted device with wireless connectivity. Currently, some examples of terminal devices include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving cars, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes.

[0230] Access network equipment may refer to a radio access network (RAN) node (or device), such as a base station, that connects a terminal device to a wireless network. Examples of RAN nodes include: evolved Node B (gNB), transmission reception point (TRP), evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved Node B (HNB), base band unit (BBU), or wireless fidelity (Wi-Fi) access point (AP).

[0231] In one network architecture, access network equipment may include centralized unit (CU) nodes, distributed unit (DU) nodes, or both CU and DU nodes. RAN equipment including CU and DU nodes splits the protocol layers of the gNB in ​​the NR system, centrally controlling some protocol layer functions within the CU and distributing some or all of the remaining protocol layer functions within the DU, which is then centrally controlled by the CU, as shown in Figure 3C. Furthermore, the CU can be divided into a control plane (CU-CP) and a user plane (CU-UP). The CU-CP is responsible for control plane functions, primarily including radio resource control (RRC) and the control plane's corresponding packet data convergence protocol (PDCP) (i.e., PDCP-C). PDCP-C is primarily responsible for encryption, decryption, integrity protection, and data transmission of control plane data. The CU-UP is responsible for user plane functions, primarily including the service data adaptation protocol (SDAP) and the user plane's corresponding PDCP (i.e., PDCP-U). SDAP is primarily responsible for processing core network data and mapping flows to bearers. The PDCP-U is primarily responsible for data plane encryption and decryption, integrity protection, header compression, sequence number maintenance, and data transmission. The CU-CP and CU-UP are connected via the E1 interface. The CU-CP represents the gNB's connection to the core network via the NG interface and to the DU via the F1 interface control plane (i.e., F1-C). The CU-UP connects to the DU via the F1 interface user plane (i.e., F1-U). Alternatively, the PDCP-C may also reside in the CU-UP.

[0232] It is understandable that in different systems, CU (including CU-CP or CU-UP) or DU may have different names, but those skilled in the art can understand their meanings. For example, in an open radio access network (O-RAN) system, CU may also be referred to as O-CU (open CU), DU may also be referred to as O-DU, CU-CP may also be referred to as O-CU-CP, and CU-UP may also be referred to as O-CU-UP. For the convenience of description, this application uses CU, CU-CP, CU-UP and DU as examples for description.

[0233] Core network equipment refers to equipment in the core network that provides service support for terminal equipment. At present, some examples of core network equipment are: access and mobility management function (AMF) entity, session management function (SMF) entity, user plane function (UPF) entity, etc., which are not listed here one by one. Among them, the AMF entity can be responsible for access and mobility management in the mobile network, such as user registration management, connection management, and reachability management. The specific functions are non-access layer signaling termination, registration area management, access authentication, etc. The SMF entity can be responsible for session management, such as user session establishment, etc.; the UPF entity can be a functional entity of the user plane, mainly responsible for connecting to the external network. In this application, "entity" can also be referred to as a network element or a functional entity. For example, the AMF entity can also be referred to as an AMF network element or an AMF functional entity. For another example, the SMF entity can also be referred to as an SMF network element or an SMF functional entity, etc. Similarly, the embodiments of the present application can also be applied to 4G LTE systems. The functions of the mobility management entity MME included in the 4G core network are similar to those of the AMF. The MME is a key control node of the LTE access network. The MME is mainly responsible for mobility management and control, including user authentication, paging, location update and switching, etc.

[0234] In the embodiments of the present application, the functions of the network device may also be performed by a module (such as a chip) in the network device, or by a control subsystem that includes the network device functions. The control subsystem that includes the network device functions here may be a control center in the above-mentioned application scenarios such as smart grid, industrial control, smart transportation, and smart city. The functions of the terminal device may also be performed by a module (such as a chip or a modem) in the terminal device, or by a device that includes the terminal device functions.

[0235] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0236] In this application, the names of the messages in the following processes are merely examples. As communication technologies evolve, the names of the messages in the following processes may change. However, regardless of how the names change, as long as their meanings are the same as the functions or meanings of the messages in this application, they fall within the scope of protection of this application. For example, the first request message in this application can also be replaced by an attach request message or a registration request message.

[0237] The technical solution of this application is introduced below in conjunction with specific embodiments.

[0238] The embodiment of the present application provides a communication method, which is applicable to but not limited to the communication system shown in Figures 3A-3B, and is applicable to but not limited to the scenario of discontinuous feeding (also known as the store-and-forward S&F scenario). The method can be executed by a first terminal device, a first access network device, and a core network element; or the method can be executed by components (modules, chips, etc.) corresponding to the terminal device, the first access network device, and the core network element; or the method can be executed by a device corresponding to the first terminal device, the first access network device, and the core network element; it can be understood that the present application does not make specific restrictions on the specific structure of the execution subject of the method provided in the embodiment of the present application and the number of each execution subject. As long as it is possible to communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, the interaction between the first terminal device, the first access network device, and the core network element will be used as an example. The order of the steps in the following processes is only an example. In actual applications, the execution order of the steps in each process can be adjusted.

[0239] Please refer to FIG4A , the specific process of the method is as follows:

[0240] S401A: The first terminal device sends a first request message to the first access network device.

[0241] The first request information may be used to request registration of the first terminal device to the network.

[0242] Correspondingly, the first access network device receives the first request information.

[0243] In the embodiments of the present application, the first request information may be a message or information carried in a message. For example, the first request information may be an initial access request message. Due to different application scenarios of the embodiments, the name corresponding to the initial access request message may vary and is not limited to this. Exemplarily, the initial access request message may be an attach request or a registration request.

[0244] S402A: The first access network device sends the first request information to the core network network element.

[0245] Correspondingly, the core network element receives the first request information.

[0246] In an embodiment of the present application, the core network network element belongs to the network requested to be registered by the first terminal device, for example, the core network network element is an MME or AMF network element, or it can be other network elements with access and mobility management functions without restriction.

[0247] In one implementation, in a discontinuous power feeding (S&F) scenario, when the first access network device determines that there is a power feeding connection, it sends the first request information to the core network element.

[0248] S403A: The core network element sends a paging message to the first access network device according to the first request information.

[0249] The paging message may be used to trigger the first access network device to page the first terminal device.

[0250] In an optional embodiment, when the first terminal device is of a discontinuous feeding type, the core network element sends a paging message to the first access network device according to the first request information, and the paging message is used to trigger the first access network device to page the first terminal device.

[0251] In an embodiment of the present application, a terminal device of a discontinuous feeding type (or S&F type) may refer to: a terminal device that supports access to the core network through an access network device of a discontinuous feeding type; or a terminal device that communicates through an access network device of a discontinuous feeding type; or a terminal device that has no connection with a core network element when connected to an access network device; or a terminal device whose data needs to be cached and forwarded (store and forward) by an access network device; or a terminal device that can support use in a discontinuous feeding scenario (i.e., a scenario where the service connection and the feeding connection are not available at the same time at any time).

[0252] In an optional implementation, the method further includes: the core network element determining that the first terminal device is a discontinuous feeding type.

[0253] In the embodiment of the present application, the core network element determines that the first terminal device is of a discontinuous feeding type, which can be achieved by, but not limited to, the following methods:

[0254] Method a: The core network element determines that the first terminal device is a non-continuous feeding type based on the contract information of the first terminal device; the contract information may include but is not limited to one or more of a specific group, a specific DNN, and S-NSSAI.

[0255] For example, in the UE's subscription information, the specific group (Internal Group ID) subscribed by the UE is an S&F type group; or the S-NSSAI subscribed by the UE is an S&F type; or the data network name DNN subscribed by the UE is an S&F type; or an indication information in the UE's subscription information is used to indicate that the UE1 is an S&F type. The core network element can determine that the UE is an S&F type based on at least one item in the UE1's subscription information.

[0256] Mode b: The core network element determines that the first terminal device is of a discontinuous power feeding type based on the capability information of the first access network device; the capability information of the first access network device indicates that the first access network device supports discontinuous power feeding.

[0257] For example, the first access network device RAN can indicate to the core network element MME / AMF in the NG setup message or the RAN configuration update message that it supports discontinuous feeding or is of the discontinuous feeding type, so that the MME / AMF can know that the first terminal device served by the first access network device is also of the discontinuous feeding type.

[0258] Method c: The core network element determines that the first terminal device is of a discontinuous feeding type based on the tracking area TA information supported by the first access network device and the TA where the first terminal device is located.

[0259] For example, the core network element receives tracking area TA information (taking the TA list as an example) supported by the first access network device and the TA where the first terminal device is located from the first access network device; the TA where the first terminal device is located refers to the TA where the first terminal device is located or the TA supported by the first access network device when the first access network device receives the first request information from the first terminal device; the tracking area TA supported by the first access network device refers to the TA supported by the first access network device when the core network element receives the first request information forwarded from the first access network device. If the TA where the first terminal device is located is not included in the TA list supported by the first access network device, it is determined that the first terminal device is of the discontinuous feeding type.

[0260] S404A: The core network element sends response information to the first access network device for the first request information.

[0261] The response information of the first request information may be used to indicate that the network accepts the registration of the first terminal device.

[0262] Correspondingly, the first access network device receives response information to the first request information from the core network device.

[0263] In an optional implementation, in a feed-discontinuous (S&F) scenario, S404A is performed when the first access network device has a feeder connection.

[0264] In S404A, the service area of ​​the first access network device at this time does not cover the location of the first terminal device when the first request information is received, which can also be understood as the first terminal device is not in the service area of ​​the first access network device.

[0265] When executing the above S403A, the present application does not impose any specific limitation on the order in which the above S403A and S404A are executed.

[0266] S405A: The first access network device sends a first paging message according to the response information of the first request information. Correspondingly, the first terminal device receives the first paging message.

[0267] The first paging message may include first identification information of the first terminal device, wherein the first identification information may be identification information of the access layer or identification information of the non-access layer.

[0268] Optionally, in S405A, if the service area of ​​the first access network device covers the location of the first terminal device when the first access network device receives the first request information, the first paging message is sent according to the response information of the first request information. For example, if the TAs (TA1-3) supported by the first access network device include the TA (TA1) where the first terminal device is located when the first access network device receives the first request information, the first paging message is sent according to the response information of the first request information.

[0269] It should be pointed out that the first paging message is sent according to the response information of the first request information in S405A. It can be understood that the response information of the first request information is used to trigger the sending of the first paging message. For example, the response information carries the identifier of the first terminal device, and the first paging message can be sent based on the identifier; it can also be understood as a judgment basis for sending the first paging message. For example, the first access network device has received the response information of the first request information without restriction.

[0270] In a possible implementation, when the first access network device receives a response message to the first request message, and the current service range of the first access network device does not cover the location of the first terminal device when the first request message is received (or in other words, there is no service connection between the first access network device and the first terminal device), the first access network device determines to send a first paging message before sending the response message to the first request message to the first terminal. Exemplarily, when the service range of the first access network device covers the location of the first terminal device when the first request message is received, the first paging message includes the first identification information of the first terminal device, and after the first access network device receives the paging response message of the first terminal device, it sends the response message of the first request message to the first terminal device.

[0271] In a possible implementation, before the first access network device sends the first paging message, it may also include: the core network network element sends a second indication message to the first access network device, and the second indication message is used to trigger the first access network device to send the first paging message before sending the response message of the first request message to the first terminal device; accordingly, after the first access network device receives the second indication message, the first access network device sends the first paging message before sending the response message of the first request message to the first terminal device based on the second indication message and the response message of the first request message. Exemplarily, the first access network device sends the first paging message when the service range covers the location of the first terminal device when the first request message is received. The first paging message includes the first identification information of the first terminal device. After the first access network device receives the paging response message of the first terminal device, it sends the response message of the first request message to the first terminal device.

[0272] The first identification information may specifically include but is not limited to the following implementations:

[0273] Implementation method 1: the first identification information is identification information of the access layer.

[0274] In this embodiment, the identification information of the access layer may be allocated by the first access network device, or may be allocated by the first terminal device.

[0275] In the embodiments of the present application, the access stratum identification information may be, but is not limited to, the UE ID used in RRC messages or RRC procedures. For example, message 2 (Random Access Response), message 3 (Scheduled Transmission), or the UE ID in an RRC establishment / reestablishment / recovery / release message. The access stratum identification information may also be part of the RRC context information, which is not limited to this.

[0276] For example, the first identification information may be a cell radio network temporary identifier (C-RNTI), an inactive radio network temporary identifier (I-RNTI), or a combination of any one of the above and a RAN ID. The RAN ID may be a combination of any one or more of a gNB ID, an eNB ID, a cell ID, an E-UTRAN cell global ID, and an NR cell global ID. It may also be a new identifier that can be used to identify the UE in the UE initial access process in the S&F scenario.

[0277] If the identification information of the access layer is allocated by the first access network device, the first access network device can send the identification information of the access layer to the first terminal device through an existing process (such as an RRC connection establishment process). If the identification information of the access layer is allocated by the first terminal device, in the above S401A, the first terminal device can carry the identification information of the access layer in the first request message, or carry it in another message, and send it to the first access network device. In an embodiment of the present application, the identification information of the access layer can also be exchanged between the first terminal device and the first access network device and the core network element through other methods / other transmission paths, which is not limited.

[0278] Implementation method 2: the first identification information is identification information of the non-access layer.

[0279] In this embodiment, the identification information of the non-access layer may be allocated by a core network element, or may be pre-configured on the first terminal device and the core network element.

[0280] In the embodiments of the present application, the non-access stratum identifier may be, but is not limited to, the ID of the terminal device UE used in NAS messages or in the process of interaction between the UE and core network elements. For example, the ID of the terminal device UE used in a NAS message, a registration process, a session establishment process, a handover process, or a service request process. The non-access stratum identifier information may also be part of the NAS context information, which is not limited to this.

[0281] For example, the first identification information can be any one of the following: International Mobile Subscriber Identity (IMSI), Temporary Mobile Subscriber Identity (TMSI), 5G-S-TMSI, P-TMSI, all or part of the Globally Unique Temporary Identifier (GUTI), or SUCI. It can also be a new identifier used to identify the UE during the UE initial access process in the S&F scenario.

[0282] If the first identification information is identification information of the non-access layer, the manner in which the first access network device obtains the first identification information may include: the first access network device obtains the first identification information from the first terminal device, the first identification information may be part of the first request information, or may be information different from the first request information; when the first identification information and the first request information are different information, the first identification information and the first request information may be carried in the same message or in a different message. The first identification information may also be sent by the core network element to the first access network device, the first identification information may be part of the response information to the first request information, or may be information different from the response information to the first request information; when the first identification information and the response information to the first request information are different information, the first identification information and the response information to the first request information may be carried in the same message or in a different message, for example, the first identification information is carried in a paging message.

[0283] In one possible implementation, the first identification information is allocated to the first terminal device by a core network element during the authentication and authorization process for the first terminal device. The method may further include: the core network element sending second identification information of the first terminal device to the first access network device, where the second identification information is used by the first access network device to page the first terminal device during the authentication and authorization process for the first terminal device; accordingly, after the first access network device receives the second identification information, during the authentication and authorization process, the first access network device sends a second paging message, where the second paging message includes the second identification information of the first terminal device. Accordingly, the first terminal device receives the second paging message.

[0284] Exemplarily, in the authentication and authorization process of the first terminal device, the first access network device receives a first message sent to the first terminal device from the core network network element, and the first message includes second identification information; the first access network device sends a second paging message to the first terminal device, and after receiving the second paging response message from the first terminal device, sends the first message to the first terminal device.

[0285] During the authentication process, the second identification information used by the first access network device for paging may include the following implementations:

[0286] Sub-method 1: The second identification information is identification information of the access layer, for example, an ID of the RRC layer, or partial information of the RRC context.

[0287] In sub-mode 2, the second identification information is identification information of the non-access layer, for example, a pre-configured NAS layer ID, or partial information of a NAS context.

[0288] For the above-mentioned embodiment 1, and sub-method 1 under embodiment 2: Since the first access network device needs to use the identification information of the access layer to page the first terminal device; therefore, after the first access network device receives the first request information (i.e., S401A) of the first terminal device, if the first access network device has no feeder connection, it may also include: the first access network device sends a first message to the first terminal device, and the first message is used to trigger the first terminal device to retain the radio resource control RRC context, and the RRC context includes the identification information of the access layer corresponding to the first terminal device. Accordingly, after the first terminal device receives the first message, it retains the RRC context according to the first message. In an embodiment of the present application, the first access network device can carry the first message in an RRC connection release message and send it to the first terminal device.

[0289] For the above-mentioned implementation method 2 that is not combined with the sub-method, and sub-method 2 under implementation method 2: Since the first access network device uses the identification information of the non-access layer to page the first terminal device, rather than the identification information of the access layer (RRC layer); therefore, after the first access network device receives the first request information (i.e., S401A), if the first access network device has no feeder connection, it may also include: the first access network device sends a second information to the first terminal device, and the second information is used to trigger the first terminal device to release the radio resource control RRC context. Accordingly, after receiving the second information, the first terminal device releases the RRC context according to the second information. In an embodiment of the present application, the first access network device can carry the second information in the RRC connection release message and send it to the first terminal device.

[0290] In a possible embodiment, when the first access network device has no feeder connection, the method may further include: the first access network device sends a first indication message to the first terminal device; the first indication message is used to trigger the first terminal device not to send the first request message within a preset time or before receiving the response message of the first request message. Accordingly, after receiving the first indication message, the first terminal device stops sending the first request message according to the first indication message within the preset time or before receiving the response message of the first request message; or; the first terminal device stops sending the first request message according to the local configuration within the preset time or before receiving the response message of the first request message. In an embodiment of the present application, the first indication message may include a preset time period, or may be only one indication message.

[0291] In the embodiment of the present application, the first access network device may determine that there is no feeder connection by, but not limited to, the following methods:

[0292] Method 1: Determine, based on local configuration, that the first access network device has no feeder connection;

[0293] For example, the type of the first access network device is a non-feeder connection type, that is, there may be no feeder connection when there is a service connection.

[0294] Method 2: Determine, based on the interface connection information between the first access network device and the core network device, that the first access network device has no feeder connection;

[0295] For example, the S1 / NG interface connection between the first access network device and the MME / AMF is not established or does not exist or has no context.

[0296] Method three: determining, based on the feeder connection status information of the first access network device, that the first access network device has no feeder connection.

[0297] In the embodiment of the present application, the first access network device having no feeder connection can also be referred to as the type of the first access network device S&F. The first access network device having no feeder connection may include but is not limited to the following situations: the satellite where the first access network device is located has no connection with the gateway station; or the first access network device has no connection with the gateway station; or the first access network device has no connection with the core network device (for example: there is no transport layer connection between the first access network device and the core network element, or there is no N2 or N3 connection between the first access network device and the core network element). In addition, in the embodiment of the present application, an access network device of the discontinuous feed type (or S&F type) may refer to: an access network device whose feeder connection is not always available; or an access network device whose connection with the core network element is not always available; or an access network device whose ground link is not always available.

[0298] Exemplarily, the first identification information may be an international mobile subscriber identity code IMSI, a subscription permanent identifier (SUPI), a subscription concealed identifier (SUCI), a cell radio network temporary identifier (C-RNTI), an inactive radio network temporary identifier (I-RNTI), a RAN ID, or I-RNTI+RAN ID, or C-RANTI+RAN ID, etc.

[0299] In one possible implementation, after the first terminal device receives the first paging message, the method further includes: if the first terminal device is of a discontinuous power feeding type, the first terminal device determining not to send a service request message to the first access network device. Alternatively, if the first terminal device is of a discontinuous power feeding type and the first paging message includes non-access stratum (NAS) identification information of the first terminal device, the first terminal device determining not to send a service request message to the first access network device.

[0300] S406A: The first terminal device sends a first paging response message to the first access network device, where the first paging response message is used to respond to the first paging message. Correspondingly, the first access network device receives the first paging response message.

[0301] In a possible implementation, the method further includes: the first terminal device requests the first access network device to establish or restore a radio resource control RRC connection.

[0302] In an embodiment of the present application, the first paging response message may also be, but is not limited to: a radio resource control RRC connection establishment request message, an RRC connection re-establishment request message, or an RRC connection recovery request message. When the first paging response message is a different request message, the first terminal device currently executes a different process. For example, if the first paging response message is an RRC connection establishment request message, then the process currently initiated by the first terminal device is an RRC connection establishment process, and the first terminal device responds to the first paging message of the first access network device by sending an RRC connection establishment request message to the first access network device.

[0303] S407A: The first access network device sends response information of the first request information to the first terminal device according to the first paging response message.

[0304] The response information of the first request information may be used to indicate that the network accepts the registration of the first terminal device.

[0305] Correspondingly, the first terminal device receives response information to the first request information.

[0306] In one possible implementation, after the above-mentioned RRC connection establishment is completed or the RRC connection is restored, in S407A, the first access network device sends response information to the first request information to the first terminal device through the RRC connection. Correspondingly, the first terminal device also receives response information to the first request information from the first access network device through the RRC connection.

[0307] In this embodiment of the present application, the response information to the first request information is received and stored by the first access network device from the core network element. The first access network device can determine that the response information to the first request information received from the core network element corresponds to the first terminal device based on the stored first identification information and a corresponding terminal identification used between the RAN and the core network element (MME / AMF), such as a RAN UE next generation access point (NGAP) ID.

[0308] In a possible embodiment, the method also includes: the first access network device sends a third indication information to the first terminal device, and the third indication information is used to trigger the first terminal device to delete the first identification information of the first terminal device after receiving the response information of the first paging message or the first request information.

[0309] The embodiment of the present application also provides another communication method, which is also applicable to but not limited to the communication system shown in Figures 3A-3B, and is applicable to but not limited to the scenario of discontinuous feeding (S&F scenario). The method can be executed by the first terminal device, the first access network device, and the core network network element; or the method can be executed by the components (modules, chips, etc.) corresponding to the terminal device, the first access network device, and the core network network element; or the method can be executed by a device corresponding to the first terminal device, the first access network device, and the core network network element; the present application does not make specific restrictions on the specific structure of the aforementioned execution entities and the number of each execution entity. Please refer to Figure 4B. The first terminal device in this method is of the discontinuous feeding type, and the specific process includes the following:

[0310] S401B: The first terminal device sends a first request message to the first access network device. Correspondingly, the first access network device receives the first request message.

[0311] The first request information may be used to request registration of the first terminal device to the network.

[0312] In a possible implementation, the method further includes: the first terminal device receives second information from the first access network device, where the second information is used to trigger the first terminal device to release the RRC context; and then the first terminal device releases the RRC context based on the second information.

[0313] S402B: The first access network device sends a first request message to the core network element. Correspondingly, the core network element receives the first request message from the first access network device.

[0314] In an embodiment of the present application, the core network network element belongs to the network requested to be registered by the first terminal device, for example, the core network network element is an MME or AMF network element, or it can be other network elements with access and mobility management functions without restriction.

[0315] In one implementation, in a discontinuous power feeding (S&F) scenario, when the first access network device determines that there is a power feeding connection, it sends the first request information to the core network element.

[0316] S403B: The core network element sends a paging message to the first access network device according to the first request information.

[0317] The paging message may be used to trigger the first access network device to page the first terminal device.

[0318] Correspondingly, the first access network device receives the paging message.

[0319] S404B: The core network element sends response information to the first access network device.

[0320] There is no specific limitation on the order of executing S403B and S404B.

[0321] S405B: The first access network device sends a first paging message according to the response information of the first request information.

[0322] The first paging message may include the first identification information of the first terminal device. Accordingly, the first terminal device receives the first paging message.

[0323] In one possible implementation, the first identification information is identification information of the non-access layer; the identification information of the non-access layer is allocated by a core network element; or the identification information of the non-access layer is pre-configured on the first terminal device or the core network element.

[0324] In one possible implementation, the first identification information may be assigned to the first terminal device by the core network during an authentication process for the first terminal device. The method may further include: during the authentication process, the first access network device receiving a second paging message, the second paging message including the second identification information of the first terminal device. The second identification information may be non-access stratum identification information.

[0325] The specific implementations of the above S401B to S405B can refer to the specific implementations of the above S401A to S405A one by one, and will not be described in detail here.

[0326] S406B: The first terminal device determines not to send a service request message to the first access network device.

[0327] In a possible implementation manner, the first terminal device executes S406B before receiving the response information of the first request information.

[0328] In a possible embodiment, the method may also include: the first terminal device sends a first paging response message to the first access network device, and the first paging response message is used to respond to the first paging message and request the first access network device to establish or restore a radio resource control RRC connection. Accordingly, the first access network device receives the first paging response message and accepts to establish or restore the RRC connection. Furthermore, after the RRC connection is established or the RRC connection is restored, the first access network device sends a response message of the first request information to the first terminal device through the RRC connection, and the response information of the first request information can be used to indicate that the network accepts the registration of the first terminal device. After the RRC connection is established or restored, the first terminal device receives the response information of the first request information from the first access network device through the RRC accordingly.

[0329] In a possible embodiment, the method also includes: the first terminal device receives a third indication information from the first access network device, and the third indication information is used to trigger the first terminal device to delete the first identification information after receiving the first paging message or the response information of the first request information; and then the first terminal device deletes the first identification information according to the third indication information.

[0330] Compared with the method described in Figures 4A-4B above, the embodiment of the present application also provides a communication method, which has a different application scenario, that is, the first terminal device can implement the process of registering the first terminal device to the network in a scenario where the first terminal device can perform network communication with the help of one or more access network devices. In this method, the second access network device is used as the access network device for the first terminal device to initially access the network, and the first access network device is used as the access network device for the first terminal device to subsequently access the network. The second access network device (also referred to as the source access network device) can complete the process of registering the first terminal device to the network through the first access network device (also referred to as the target access network device). This application does not make specific restrictions on the specific structure of the execution subject of the method provided in the embodiment of the present application and the number of each execution subject. As long as it is possible to communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, the following is an example of the interaction between the first terminal device, the first access network device, the second access network device, and the core network element. The order of the steps in the following processes is only an example. In actual applications, the execution order of the steps in each process can be adjusted.

[0331] Please refer to FIG5A , the specific process of the method is as follows:

[0332] S501A: The first terminal device sends a first request message to the second access network device.

[0333] The first request information may be used to request registration of the first terminal device to the network.

[0334] Correspondingly, the second access network device receives the first request information.

[0335] In the embodiments of the present application, the first request information may be a message or information carried in a message. For example, the first request information may be an initial access request message. Due to different application scenarios of the embodiments, the name corresponding to the initial access request message may vary and is not limited to this. Exemplarily, the initial access request message may be an attach request or a registration request.

[0336] S502A: The second access network device sends a first request message to a core network element. Correspondingly, the core network element receives the first request message.

[0337] In an embodiment of the present application, the core network element belongs to the network requested to be registered by the first terminal device, for example, the core network element is an MME or AMF network element.

[0338] In a feed discontinuous (S&F) scenario, when the second access network device determines that there is a feed connection, S502A is executed.

[0339] In a possible implementation, if it is determined that the second access network device has no feeder connection, the method further includes: the second access network device sends first information to the first terminal device, and the first information is used to trigger the first terminal device to release or retain the RRC context.

[0340] In one possible implementation, if the second access network device has no feeder connection, the method may further include: the second access network device sends a first indication message to the first terminal device; the first indication message is used to trigger the first terminal device to not send the first request message within a preset time or before receiving a response message to the first request message. Accordingly, after receiving the first indication message, the first terminal device stops sending the first request message within the preset time or before receiving a response message to the first request message based on the first indication message; or the first terminal device may stop sending the first request message within the preset time or before receiving a response message to the first request message based on local configuration.

[0341] In the embodiment of the present application, the second access network device may determine that there is no feeder connection by, but not limited to, the following methods:

[0342] Method 1: According to local configuration, determine that the second access network device has no feeder connection.

[0343] For example, the type of the second access network device is a non-feeder connection type, that is, there may be no feeder connection when there is a service connection.

[0344] Method 2: Determine that the second access network device has no feeder connection based on the interface connection information between the second access network device and the core network device.

[0345] For example, the S1 / NG interface connection between the second access network device and the MME / AMF is not established or does not exist or has no context.

[0346] Method three: determining that the second access network device has no feeder connection according to the feeder connection status information of the second access network device.

[0347] In the embodiment of the present application, the second access network device having no feeder connection may also be referred to as: the type of the second access network device is S&F. The second access network device having no feeder connection may include, but is not limited to, the following situations: the satellite where the second access network device is located has no connection with the gateway; or the second access network device has no connection with the gateway; or the second access network device has no connection with the core network device (for example, there is no transport layer connection between the second access network device and the core network element, or there is no N2 or N3 connection between the second access network device and the core network element).

[0348] S503A: The second access network device sends a connection context of the second access network device to the core network element, where the connection context includes an RRC context. Correspondingly, the core network element receives the connection context of the second access network device.

[0349] In an embodiment of the present application, the connection context may include but is not limited to: the RRC context of the first terminal device, the context about the first terminal device between the second access network device and the MME / AMF (for example, RAN UE NGAP ID, AMF UE NGAP ID), and the access layer security context of the first terminal device.

[0350] If in a discontinuous feeding (S&F) scenario, when the second access network device has no feeding connection, S503A is executed.

[0351] S504A: The core network element determines a first access network device.

[0352] This S504A is an optional step.

[0353] Exemplarily, the core network element can determine, based on the ephemeris information, that the service range of the first access network device covers the location of the first terminal device when the first request information is sent faster than the service range of the second access network device. The core network element can then determine the first access network device as the target access network device for the first terminal device. Through this method, the time the first terminal device waits for the response information of the first request information can be shortened. Or the first access network device is an access network device deployed on all satellites in the constellation of the satellite where the second access network device is located. Through the method, any access network device can serve the first terminal device when it covers the first terminal device, without the need to configure ephemeris information, and can shorten the time the first terminal device waits for the response information of the first request information.

[0354] S505A: The core network element sends a paging message to the first access network device according to the first request information.

[0355] The paging message may be used to trigger the first access network device to page the first terminal device.

[0356] In a possible implementation, when the first terminal device is a non-feed type, the core network element sends a paging message to the first access network device according to the first request information, and the paging message is used to trigger the first access network device to page the first terminal device.

[0357] In a possible implementation, the method further includes: the core network element determining that the first terminal device is a discontinuous feeding type.

[0358] In the embodiment of the present application, the core network element may determine that the first terminal device is of a discontinuous feeding type by, but not limited to, the following methods:

[0359] Method a: The core network element determines that the first terminal device is a non-continuous feeding type based on the contract information of the first terminal device; the contract information may include but is not limited to one or more of a specific group, a specific DNN, and S-NSSAI.

[0360] Method b: The core network element can determine that the first terminal device is of the discontinuous power feeding type based on the capability information of the second access network device; the capability information of the second access network device indicates that the second access network device supports discontinuous power feeding. For example, the second access network device RAN can indicate to the core network element MME / AMF in an NG setup message or RAN configuration update message that it supports discontinuous power feeding or is of the discontinuous power feeding type. The MME / AMF can then determine that the first terminal device served by the second access network device is also of the discontinuous power feeding type.

[0361] Method c: The core network element determines that the first terminal device is of a discontinuous feeding type based on the tracking area TA information supported by the second access network device and the TA where the first terminal device is located.

[0362] For example, the core network element receives tracking area TA information (taking the TA list as an example) supported by the second access network device and the TA where the first terminal device is located; the TA where the first terminal device is located refers to the TA where the first terminal device is located or the TA supported by the second access network device when the second access network device receives the first request information from the first terminal device; the tracking area TA supported by the second access network device refers to the TA supported by the second access network device when the core network element receives the first request information forwarded from the second access network device. If the TA where the first terminal device is located is not included in the TA list supported by the second access network device, it is determined that the first terminal device is of the discontinuous feeding type.

[0363] S506A: The core network element sends the connection context of the second access network device to the first access network device.

[0364] The connection context of the second access network device may include an RRC context, etc.

[0365] Correspondingly, the first access network device receives the connection context.

[0366] In an embodiment of the present application, the second access network device may not send the connection context of the second access network device to the core network element, that is, S503A and S506A are not executed. Instead, after the core network element determines the first access network device, the core network element first sends the identification information / indication information of the first access network device to the second access network device; then, based on the identification information / indication information of the first access network device, the second access network device sends the connection context of the second access network device to the first access network device. Alternatively, after the core network element determines the first access network device, the core network element first sends the identification information or indication information of the second access network device to the first access network device; then, based on the identification information or indication information of the second access network device, the first access network device sends a context request message to the second access network device to request the connection context of the second access network device; then, based on the context request message, the second access network device sends the connection context of the second access network device to the first access network device. Furthermore, the second access network device may also send the connection context of the second access network device to the first access network device through other means, which are not specifically limited in this application. That is, S503A and S506A are optional steps.

[0367] S507A: The core network element sends response information to the first access network device for the first request information.

[0368] The response information of the first request information may be used to indicate that the network accepts the registration of the first terminal device.

[0369] Correspondingly, the first access network device receives response information to the first request information from the core network device.

[0370] In a possible implementation, in a discontinuous power feeding (S&F) scenario, when the first access network device has a power feeding connection, it receives response information to the first request information sent by the core network element.

[0371] In S507A, the service area of ​​the first access network device at this time does not cover the location of the first terminal device when the first request information is received, that is, the first terminal device is not in the service area of ​​the first access network device.

[0372] This application does not specifically limit the order of executing the above S506A and S507A.

[0373] S508A: The first access network device sends a first paging message according to the response information of the first request information.

[0374] The first paging message may include first identification information of the first terminal device.

[0375] When the first access network device sends the first paging message according to the response information of the first request information, the service area of ​​the first access network device has covered the location of the first terminal device when the first request information is received, so the first terminal device receives the first paging message.

[0376] In a possible implementation, when the first access network device receives response information to the first request information, and the current service range of the first access network device does not cover the location of the first terminal device when the first request information is received, the method further includes: the first access network device determines to send a first paging message before sending the response information to the first terminal. Exemplarily, if the service range of the first access network device covers the location of the first terminal device when the first request information is received, a first paging message is sent, the first paging message including the first identification information of the first terminal device, and after the first access network device receives the paging response message of the first terminal device, the response information of the first request information is sent to the first terminal device.

[0377] In a possible implementation, before the first access network device sends the first paging message, it may also include: the core network network element sends a second indication message to the first access network device, and the second indication message is used to trigger the first access network device to send the first paging message before sending the response message of the first request message to the first terminal device; accordingly, after the first access network device receives the second indication message, the first access network device sends the first paging message based on the second indication message and the response message of the first request message before sending the response message of the first request message to the first terminal device. Exemplarily, if the service range of the first access network device covers the location of the first terminal device when it receives the first request message, the first paging message is sent, and the first paging message includes the first identification information of the first terminal device. After the first access network device receives the paging response message of the first terminal device, the response message of the first request message is sent to the first terminal device.

[0378] In an embodiment of the present application, when the first access network device receives a connection context from the second access network device including an RRC context (including identification information of the access layer), the first identification information of the first terminal device included in the first paging message, including but not limited to the following possible implementation methods in the embodiment of the present application, can refer to the several implementation methods in S405A in Figure 4A above (such as implementation method one and implementation method two), which will not be described one by one here. If the first access network device does not receive the connection context of the second access network device, then the first identification information of the first terminal device included in the first paging message is the identification information of the non-access layer, which can be allocated by the core network network element or pre-configured on the first terminal device or the core network network element. In this case, the identification information of the non-access layer used by the first access network device to page the first terminal device in implementation method two in S405A above can also be referred to, which will not be described in detail here.

[0379] In one possible implementation, the first identification information is allocated to the first terminal device by the core network during the authentication and authorization process of the first terminal device. Then the method may also include: the core network network element sends the second identification information of the first terminal device to the first access network device, and the second identification information is used by the first access network device to page the first terminal device during the authentication and authorization process of the first terminal device. Accordingly, after receiving the second identification information, the first access network device sends a second paging message during the authentication and authorization process, and the second paging message includes the second identification information. Accordingly, the first terminal device receives the second paging message.

[0380] Exemplarily, in the authentication and authorization process of the first terminal device, the first access network device receives a first message sent to the first terminal device from the core network network element, and the first message includes second identification information; the first access network device sends a second paging message to the first terminal device, and after receiving the second paging response message from the first terminal device, sends the first message to the first terminal device.

[0381] In S508A, in the authentication process, the second identification information used by the first access network device for paging can refer to the second identification information used by the first access network device for paging in S406A above, which will not be repeated here.

[0382] In this step S508A, if the first access network device uses the identification information of the non-access layer to page the first terminal device, rather than the identification information of the access layer (RRC layer). Therefore, in the above S501A, after the second access network device receives the first request information, if the second access network device has no feeder connection, then the second access network device can send a first message to the first terminal device, and the first message is used to trigger the first terminal device to release the radio resource control RRC context. Accordingly, after receiving the first message, the first terminal device releases the RRC context according to the first message.

[0383] In this step S508A, if the first access network device uses the access layer identification information to page the first terminal device. Therefore, in the above S501A, after the second access network device receives the first request information, if the second access network device has no feeder connection, the second access network device can send a first message to the first terminal device, and the first message is used to trigger the first terminal device to retain the radio resource control RRC context. Accordingly, after receiving the first message, the first terminal device retains the RRC context based on the first message.

[0384] Exemplarily, the first identification information may be an international mobile subscriber identity IMSI, a user permanent identity SUPI, a user hidden identity SUCI, a cell radio network temporary identity C-RNTI, an inactive radio network temporary identity I-RNTI, a RAN ID, or I-RNTI+RAN ID, or C-RANTI+RAN ID, etc.

[0385] In one possible implementation, after the first terminal device receives the first paging message, the method further includes: if the first terminal device is of a discontinuous power feeding type, the first terminal device determining not to send a service request message to the first access network device. Alternatively, if the first terminal device is of a discontinuous power feeding type and the first paging message includes non-access stratum (NAS) identification information of the first terminal device, the first terminal device determining not to send a service request message to the first access network device.

[0386] S509A: The first terminal device sends a first paging response message to the first access network device, where the first paging response message is used to respond to the first paging message

[0387] In a possible implementation, the method further includes: the first terminal device requests the first access network device to establish or restore a radio resource control RRC connection.

[0388] In an embodiment of the present application, the first paging response message may also be, but is not limited to: a radio resource control RRC connection establishment request message, an RRC connection re-establishment request message, or an RRC connection recovery request message. When the first paging response message is a different request message, the first terminal device currently executes a different process. For example, if the first paging response message is an RRC connection establishment request message, then the process currently initiated by the first terminal device is an RRC connection establishment process, and the first terminal device responds to the first paging message of the first access network device by sending an RRC connection establishment request message to the first access network device.

[0389] The specific implementation of S509A may refer to the specific implementation of S406A described above.

[0390] S510A: The first access network device sends a response message of the first request information to the first terminal device according to the first paging response message.

[0391] The response information of the first request information may be used to indicate that the network accepts the registration of the first terminal device.

[0392] Correspondingly, the first terminal device receives response information to the first request information.

[0393] In one possible implementation, after the above-mentioned RRC connection establishment is completed or the RRC connection is restored, in S510A, the first access network device sends response information to the first request information to the first terminal device through the RRC connection. Correspondingly, the first terminal device also receives response information to the first request information from the first access network device through the RRC connection.

[0394] In a possible implementation, the method further includes: the first access network device sends a third indication message to the first terminal device, and the third indication message is used to trigger the first terminal device to delete the first identification information of the first terminal device after receiving the first paging message or the response information of the first request information.

[0395] The specific implementation of S510A may refer to the specific implementation of S407A described above.

[0396] In the solution described in FIG5A , the content on the first access network device side may refer to the content on the first access network device side in the solution described in FIG4A above, and will not be repeated here.

[0397] The embodiment of the present application also provides another communication method, which is also applicable to but not limited to the communication system shown in Figures 3A-3B, and is applicable to but not limited to the scenario of discontinuous feeding (S&F scenario). The method can be executed by the first terminal device, the first access network device, and the core network network element; or the method can be executed by the components (modules, chips, etc.) corresponding to the terminal device, the first access network device, and the core network network element; or the method can be executed by a device corresponding to the first terminal device, the first access network device, and the core network network element; the present application does not make specific restrictions on the specific structure of the aforementioned execution entities and the number of each execution entity. Please refer to Figure 5B. The first terminal device in this method is of the discontinuous feeding type, and the specific process includes the following:

[0398] S501B: The first terminal device sends a first request message to the second access network device.

[0399] The first request information may be used to request that the first terminal device be registered with the network. Accordingly, the second access network device receives the first request information.

[0400] S502B: The second access network device sends a first request message to the core network element. Correspondingly, the core network element receives the first request message.

[0401] In a feed discontinuous (S&F) scenario, if the second access network device determines that there is a feed connection, S502B is executed.

[0402] In a possible implementation, if it is determined that the second access network device has no feeder connection, the method further includes: the second access network device sends first information to the first terminal device, where the first information is used to trigger the first terminal device to release or retain the connection context.

[0403] S503B: The second access network device sends its connection context information to the core network element, where the connection context information includes an RRC context. Correspondingly, the core network element receives the connection context of the second access network device.

[0404] In an embodiment of the present application, the connection context may include but is not limited to: the RRC context of the first terminal device, the context about the first terminal device between the second access network device and the MME / AMF (for example, RAN UE NGAP ID, AMF UE NGAP ID), and the access layer security context of the first terminal device.

[0405] S504B: The core network element determines the first access network device.

[0406] S504B is an optional step.

[0407] S505B: The core network element sends a paging message to the first access network device according to the first request information.

[0408] The paging message may be used to trigger the first access network device to page the first terminal device.

[0409] Correspondingly, the first access network device receives the paging message.

[0410] S506B: The core network element sends the connection context of the second access network device to the first access network device.

[0411] S507B: The core network element sends response information to the first access network device for the first request information.

[0412] This application does not specifically limit the order of executing the above S506B and S507B.

[0413] S508B: The first access network device sends a first paging message according to the response information of the first request information. Correspondingly, the first terminal device receives the first paging message.

[0414] The first paging message includes first identification information, and the first identification information may be identification information of an access layer or identification information of a non-access layer.

[0415] The specific implementations of the above S501B to S508B can refer to the specific implementations of the above S501A to S508A one by one, and will not be described in detail here.

[0416] S509B: If the first terminal device does not receive the response information of the first request information, the first terminal device determines not to send a service request message to the first access network device.

[0417] In a possible embodiment, the method may further include: the first terminal device sends a first paging response message to the first access network device, and the first paging response message is used to respond to the first paging message and request to establish or restore a radio resource control RRC connection. Accordingly, the first access network device receives the first paging response message and accepts to establish or restore the RRC connection. After the RRC connection is established or the RRC connection is restored, the first access network device sends response information of the first request information to the first terminal device through the RRC connection according to the first paging response message; accordingly, the first terminal device can receive the response information of the first request information from the first access network device through the RRC connection; wherein, the response information of the first request information can be used to indicate that the network accepts the registration of the first terminal device.

[0418] In a possible embodiment, the method may also include: the first terminal device receives third indication information from the first access network device, and the third indication information is used to trigger the first terminal device to delete the first identification information after receiving the first paging message or the response information of the first request information; and then the first terminal device deletes the first identification information according to the third indication information.

[0419] The specific implementation involved in S509B can refer to the specific implementation involved in S509A-S510A above, and will not be described in detail here.

[0420] In summary, an embodiment of the present application provides a communication method, which includes: a first access network device receives response information of a first request information from a core network network element, the response information of the first request information is used to indicate that the network accepts the registration of the first terminal device, and then the first access network device sends a first paging message according to the response information of the first request information; the first paging message includes the first identification information of the first terminal device; then the first access network device receives a first paging response message from the first terminal device, the first paging response message is used to respond to the first paging message; and then the first access network device sends the response information of the first request information to the first terminal device according to the first paging response message. In the registration process of the first terminal device, through this method, the first access network device can normally send the registration response information from the core network to the first terminal device, so that the first terminal device can effectively register with the network to achieve communication.

[0421] Based on the communication method shown in FIG. 4A-FIG . 4B and FIG. 5A-FIG . 5B , several specific implementations are further described below.

[0422] Implementation method 1:

[0423] Based on the method described in Figures 4A and 4B above, in this implementation method 1, in the S&F scenario, the radio access network device RAN uses the RRC layer identification ID (equivalent to the first identification information of the first terminal device in the solution described in Figures 4A or 4B above) to page UE1 during the initial access process of the terminal device UE (taking UE1 as an example). Referring to Figure 6, the specific process is as follows:

[0424] S600a: The RAN local configuration allows instructing UE1 to enter a suspend state.

[0425] The RAN instructing UE1 to enter the suspended state may be to instruct UE1 to save the RRC context, or to instruct UE1 to release the RRC connection and save the RRC context, or to instruct UE1 to enter the CM-IDLE with suspend / RRC-inactive state, or the RAN sends an indication message to UE1 to instruct UE1 to enter the CM-IDLE with suspend / RRC-inactive state.

[0426] For example, if the RAN determines that it is of the S&F type, it may instruct the UE1 to enter the suspended state (in the prior art, the RAN needs to receive an instruction from the MME / AMF before instructing the UE to enter the suspended state).

[0427] S600b: The MME / AMF triggers the RAN to directly instruct UE1 to enter a suspend state.

[0428] Exemplarily, the MME / AMF may send an indication message to the RAN, indicating that the RAN may instruct the UE1 to enter the suspend state.

[0429] The above-mentioned instructing the UE to enter the suspended state may be replaced by instructing the UE to detect a paging message, or instructing the UE to save a context (the context may be at the RRC layer or the NAS layer), for example, step S603.

[0430] The above S600a and S600b are parallel optional implementation solutions. The embodiment of the present application can adopt either solution, or combine the two solutions to enable UE1 to enter the suspend state, which is not specifically limited.

[0431] S601: UE1 sends an initial access request message to RAN. Correspondingly, RAN receives the initial access request message.

[0432] Since the scenarios in which the solution of this embodiment is applied are different, the name corresponding to the initial access request message (equivalent to the first request information in the solution described in FIG. 4A or FIG. 4B ) may be different, and this is not limited.

[0433] Exemplarily, the initial access request message may be an attach request or a registration request.

[0434] S602: RAN determines that there is no feeder connection.

[0435] In this embodiment, the manner in which the RAN locally determines whether there is a feeder connection may include but is not limited to the following:

[0436] Method 1: Based on configuration information (this RAN is dedicated to providing S&F services and performs this action for all initial accesses);

[0437] Method 2: Based on the status of the satellite feeder link (based on the satellite's functionality, it is found that there is no connection with the gateway);

[0438] Method 3: Or according to the status of the S1 / NG interface (S1 interface is 4G, the interface between RAN and MME; NG interface is 5G, the interface between RAN and AMF. If it is found that this interface is not connected to any MME / AMF, it is determined that there is no feeder connection).

[0439] S603: RAN sends an RRC connection release request message to UE1.

[0440] Correspondingly, the UE1 receives the RRC connection release request message.

[0441] If the RAN determines that there is no feeder connection, the RRC can instruct UE1 to retain the RRC context, and the RAN also retains the UE's RRC context. The underlying purpose is for both the RAN and UE1 to retain an RRC layer ID, such as the C-RNTI. For example, the RRC connection release request message includes an indication to retain the RRC context.

[0442] At this point, UE1 has not yet completed initial access and is not in the RRC-INACTIVE / CM-IDLE with suspend state. Therefore, the RAN's indication message is intended to instruct UE1 to retain the RRC context. This indication message can reuse existing indication message. Exemplarily, the RAN sends an indication message to UE1 indicating that it has entered the RRC-INACTIVE / CM-IDLE with suspend state, instructing UE1 to retain the RRC context.

[0443] S604: RAN instructs UE1 not to send an initial access request message again within a preset time and / or before receiving an initial access accept message.

[0444] This S604 is an optional step.

[0445] If the RAN determines that there is no feeder connection, the RAN sends an indication message 1 to the UE1, indicating that the UE1 cannot initiate an initial access request message again within a preset time (ie, a period of time) and / or before receiving an initial access accept message.

[0446] The preset time may be a time interval between two times when the RAN covers the location of the UE1, and the preset time may be determined by the RAN according to the ephemeris information.

[0447] In this embodiment, if S604 is executed, the order of executing S603 and S604 is not specifically limited.

[0448] S605: UE1 may stop sending the initial access request message according to local logic or instructions of the RAN.

[0449] In a possible implementation (UE1 local logic): UE1 is an S&F type UE, that is, the RAN accessed by UE1 must have an unfed connection. Once UE1 sends an initial access request message, it cannot initiate an initial access request message again within a period of time and / or before receiving an initial access accept message.

[0450] In another possible implementation, according to the instruction information 1 of the RAN, the UE1 does not initiate an initial access request message within the preset time and / or before receiving the initial access accept message.

[0451] In the embodiment of the present application, the RAN instructs the RAN to retain the RRC context, and the RAN instructs UE1 not to initiate the initial access request message again within a preset time period and / or before receiving the initial access accept message. The RAN may use one message / information to indicate, or may use different messages / information to indicate, and there is no specific limitation on this.

[0452] S606: RAN sends an initial access request message of UE1 to MME / AMF.

[0453] Correspondingly, the MME / AMF receives the initial access request message of UE1.

[0454] When the RAN has a feeder connection, it sends the initial access request message to the core network element MME / AMF.

[0455] S607: MME / AMF sends an initial access accept message to RAN.

[0456] Accordingly, the RAN receives the Initial Access Accept message of UE1 from the MME / AMF.

[0457] For example, if the initial access request message sent by UE1 in step 601 is an attach request, then the initial access accept message (equivalent to the response information of the first request message in the solution described in FIG. 4A or FIG. 4B ) sent by the MME / AMF to the RAN in this step is an attach accept. If the initial access request message sent by UE1 in step S601 is a registration request, then the initial access accept message sent by the MME / AMF to the RAN in this step is a registration request accept.

[0458] S608: RAN determines to restore coverage to UE1.

[0459] For example, the cell coverage of the RAN includes the tracking area TA when the RAN receives the initial access request message, or the cell coverage of the RAN includes the UE1 position when the RAN receives the initial access request message, or the supported tracking list of the RAN includes the TA when the RAN receives the initial access request message, or the RAN determines, based on the ephemeris information, that the interval between the current time and the time when the RAN receives the initial access request message is a period of RAN coverage area change.

[0460] S609: The RAN sends a paging message, which includes the ID of the RRC layer.

[0461] Correspondingly, UE1 receives the paging message.

[0462] The RAN initiates paging to UE1 using the reserved RRC layer ID.

[0463] S610: UE1 sends a paging response message to the RAN.

[0464] Correspondingly, the RAN receives the paging response message from UE1.

[0465] S611: RAN sends an initial access accept message to UE1.

[0466] Correspondingly, UE1 receives the initial access accept message.

[0467] S612: Execute the process after the initial access process is completed.

[0468] The process after UE1 completes the initial access process can be referred to in the prior art and will not be described in detail here.

[0469] In summary, in this first implementation, the RAN uses the RRC layer ID in the RRC context to page the UE. Based on local configuration or triggering / instructions from core network elements (such as the MME / AMF, etc.), the RAN can directly instruct the UE to retain the RRC context or instruct the UE to enter the RRC-INACTIVE / CM-IDLE with suspend state. Secondly, after the RAN receives the UE's initial access request message, if the RAN determines that there is no feeder connection, the RAN can instruct the UE to retain the RRC context, and the RAN also retains the RRC context. When the RAN receives the initial access accept message from the core network element, the RAN can use the RRC layer ID in the RRC context to page the UE, and then forward the initial access accept message to the UE that responded to the page, thereby effectively completing the initial access process.

[0470] Implementation method 2:

[0471] Based on the method described in Figures 4A and 4B above, in this second implementation, in the S&F scenario, the radio access network device RAN uses UE1's NAS layer ID (equivalent to the first identification information of the first terminal device in the solution described in Figures 4A or 4B above) to page UE1 during the initial access process of the terminal device UE (taking UE1 as an example). Referring to Figure 7, the specific process is as follows:

[0472] S700a: The RAN local configuration allows instructing the UE to enter a suspend state.

[0473] S700b: The MME / AMF indicates to the RAN that the RAN can directly instruct the UE1 to enter a suspend state.

[0474] The specific implementations of the above S700a-S700b can refer to the implementations of S600a and S600b in the above implementation mode 1 in a one-to-one correspondence, and will not be described in detail here.

[0475] S701: UE1 sends an initial access request message to the RAN, where the initial access request message includes a NAS layer ID.

[0476] The NAS layer ID may be pre-configured between UE1 and the core network, and will not change during the initial access process. For example: IMSI, SUCI, pre-configured GUTI, pre-configured IMSI.

[0477] Since the scenarios in which the solution of this embodiment is applied are different, the name corresponding to the initial access request message (equivalent to the first request information in the solution described in FIG. 4A or FIG. 4B ) may be different, and this is not limited.

[0478] Exemplarily, the initial access request message may be an attach request or a registration request.

[0479] It should be noted that the UE identifier carried in the attach request and the UE identifier carried in the attach accept subsequently fed back by the core network may be different (i.e., may be modified by the MME / AMF).

[0480] S702: RAN determines that there is no feeder connection.

[0481] The specific implementation of the above S702 can refer to the implementation of the above S602, and will not be described in detail here.

[0482] S703: RAN sends an RRC connection release request message to UE1.

[0483] Correspondingly, the UE1 receives the RRC connection release request message.

[0484] In this second implementation, UE1 can retain an NSA layer ID, such as IMSI, and a pre-configured GUTI. Since UE1 has not yet completed initial access at this time and no NAS layer context exists, the UE1 may be saving a new context, which may be different from the existing technology, or the UE1 may have stored a static ID locally, or this ID is the subscription information stored on the UE (for example, stored in the SIM card), and no RRC context (such as IMSI) is required. Therefore, when the RAN determines that there is no feeder connection, it will send an RRC connection release request to UE1 to request UE1 to release / delete the RRC context; at the same time, the RAN will also release / delete the RRC context of UE1.

[0485] S704: RAN instructs UE1 not to send an initial access request message again within a preset time and / or before receiving an initial access accept message.

[0486] S704 is an optional step.

[0487] S705: UE1 stops sending the initial access request message according to local logic or instructions from the RAN.

[0488] S706: RAN sends an initial access request message to MME / AMF.

[0489] The specific implementations of the above S704-S706 can refer to the specific implementations of S604-S606 in the above implementation method 1 in a one-to-one correspondence, and will not be described in detail here.

[0490] S707: MME / AMF determines that UE1 is of S&F type. Optionally, UE1 has subscribed to the NAS layer ID.

[0491] The ways in which the MME / AMF determines that UE1 is of the S&F type may include but are not limited to the following:

[0492] Method 1: MME / AMF can determine that UE1 is an S&F type UE based on UE1's subscription information or the format of the NAS layer ID.

[0493] For example, the group (Internal Group ID) subscribed by UE1 is an S&F type group; or the single network slice selection assistance information (S-NSSAI) subscribed by UE1 is an S&F type; or the data network name (DNN) subscribed by UE1 is an S&F type; or the subscription information of UE1 includes an indication information indicating that the UE1 is an S&F type. That is, there is at least one item in the subscription information of UE1 that can determine that the UE1 is an S&F type.

[0494] For example, the NAS layer ID is IMSI, and the UE1 subscription information indicates that the UE1 is of S&F type. For another example, the NAS layer ID is a special ID that is different from the ID reported by the UE in the existing initial access process. Then the MME can determine that the UE1 is of S&F type based on the ID.

[0495] Method 2: The MME / AMF determines that the RAN is of the S&F type, and determines that the UE1 is an S&F type UE.

[0496] For example, the RAN indicates to the MME / AMF in the S1 / NG process that the RAN is of the S&F type, or the TA supported by the RAN is a special TA. The MME / AMF can determine that the RAN is of the S&F type based on these TAs, or the capability information of the RAN includes an indication information indicating that the RAN is of the S&F type.

[0497] S708: MME / AMF sends a core network paging CN paging message to RAN.

[0498] The CN paging message may include a NAS layer ID.

[0499] Correspondingly, the RAN receives the CN paging message.

[0500] The NAS layer ID (an ID pre-negotiated or configured between UE1 and the core network) serves as the ID of UE1. For example, the NAS layer ID is IMSI or a special ID.

[0501] S709: MME / AMF sends an initial access accept message to RAN.

[0502] Accordingly, the RAN receives the initial access accept message.

[0503] Exemplarily, the initial access accept message may be an attach accept or a registration accept.

[0504] Optionally, the MME / AMF sends an indication message to the RAN to instruct the RAN to page UE1 before sending the initial access accept message.

[0505] In this embodiment, the execution order of the above S708 and S709 is not specifically limited.

[0506] S710: RAN determines to restore coverage to UE1.

[0507] The specific implementation of the above S710 can refer to the implementation of S608 in the above implementation method 1, and will not be described in detail here.

[0508] S711: RAN sends a paging message.

[0509] The paging message may include the NAS layer ID.

[0510] The specific implementation of S711 can refer to the implementation of S609 in the first embodiment. However, unlike S609, in S711, the RAN uses the NAS layer ID (pre-negotiated or configured between UE1 and the core network) in the CN paging message provided by the MME / AMF to page UE1. That is, the paging message sent by the RAN (a CN-type paging) includes the NAS layer ID.

[0511] S712: UE1 sends a paging response message to the RAN.

[0512] When UE1 receives a paging message (CN-type paging) from the RAN, existing logic requires it to first initiate the RRC connection recovery process and then the service request process, i.e., UE1 sends a service request message to the RAN. However, in this implementation, when UE1 receives the RAN paging message, it cannot initiate the service request process. Instead, after the RRC connection recovery process is complete, UE1 waits for an initial access accept message (e.g., an attach accept message) from the RAN.

[0513] S713: RAN sends an initial access accept message to UE1.

[0514] Correspondingly, UE1 receives the initial access accept message.

[0515] S714: Execute the process after the initial access process is completed.

[0516] The specific implementation of the above S713-S714 can refer to the implementation of S611-S612 in the above implementation method one.

[0517] In summary, in this second implementation, the RAN uses the NAS layer ID to page the UE. Upon receiving the UE's Initial Access Request message, if the RAN determines that there is no feeder connection, it can instruct the UE to release the RRC context, and the RAN also releases the RRC context. Next, the core network MME / AMF determines that the UE is an S&F type UE and sends a CN paging message to the RAN. The RAN then uses the NAS layer ID to page the UE based on the CN paging message from the MME / AMF. The RAN then forwards an Initial Access Accept message to the UE that responds to the page, effectively completing the initial access process.

[0518] Implementation method three:

[0519] Based on the method described in Figures 4A and 4B above, in this implementation method three, in the S&F scenario, during the initial access process, the RAN uses a special ID to page UE1. This special ID can be assigned by the RAN or UE1. Referring to Figure 8, the specific process is as follows:

[0520] S800a: The RAN local configuration allows instructing the UE to enter a suspend state.

[0521] S800b: The MME / AMF may trigger the RAN to directly instruct the RAN to enter a suspend state.

[0522] The implementation of the above S800a-S800b can refer to the implementation of S600a and S600b in the above implementation mode 1 in a one-to-one correspondence, and will not be described in detail here.

[0523] In the case where the RAN assigns a special ID, the following steps S801 to S804 are performed:

[0524] S801: UE1 sends an initial access request message to the RAN.

[0525] S802: RAN determines that there is no feeder connection.

[0526] The specific implementation of the above S801-S802 can refer to the specific implementation of the above S601-S602 one by one, and will not be described in detail here.

[0527] S803: RAN allocates a special ID to UE1.

[0528] This special ID is part of the RRC context.

[0529] For example, the combination of C-RNTI and eNB ID, or the combination of C-RNTI and gNB ID, or a new identifier, etc., the essence is that the identifier can globally and uniquely identify the UE.

[0530] S804: RAN sends an RRC connection release request message to UE1. The RRC connection release request message includes a special ID allocated by the RAN.

[0531] Correspondingly, the UE1 receives the RRC connection release request message. Further, the UE1 can obtain the special ID allocated by the RAN from the request and release / delete the RRC context.

[0532] The RAN may also send a special ID allocated by the RAN to the UE1 through an RRC message before the RRC connection release request message.

[0533] When UE1 is assigned a special ID, the following steps S805 to S809 are performed:

[0534] S805: RAN determines that there is no feeder connection.

[0535] S806: RAN sends a broadcast message.

[0536] Correspondingly, UE1 receives the broadcast message.

[0537] The broadcast message is used to notify the RAN that there is no feeder connection. For example, the broadcast message includes indication information for indicating that the RAN has no feeder connection.

[0538] S807: UE1 allocates a special ID.

[0539] The special ID may be part of the RRC context or part of the NAS context.

[0540] In other embodiments, the allocation of a special ID to UE1 may also be achieved in the following manner:

[0541] After establishing an RRC connection with UE1, if the RAN determines that there is no feeder connection, the RAN may send an RRC message to UE1, indicating to UE1 that the RAN currently has no feeder connection. After receiving the RRC message, UE1 allocates a special ID. The special ID may be part of the RRC context or part of the NAS context.

[0542] S808: UE1 sends an initial access request message to the RAN.

[0543] The initial access request message includes the special ID allocated by UE1.

[0544] Accordingly, the RAN receives the initial access request message.

[0545] S809: RAN sends an RRC connection release request message to UE1.

[0546] Correspondingly, the UE1 receives the RRC connection release request message.

[0547] In the case of a special ID assigned by UE1, if the special ID assigned by UE1 is part of an RRC context, the RAN sends an RRC connection release request to UE1 containing an indication message, instructing UE1 to retain the RRC context. If the special ID assigned by UE1 is part of a NAS context, the RAN sends an RRC connection release request to UE1, instructing UE1 to release / delete the RRC context.

[0548] The above-mentioned solution (S801-S804) corresponding to the RAN allocating a special ID and the solution (S805-S808) corresponding to the UE1 allocating a special ID are parallel solutions, and either one of them can be selected for execution, and this application does not limit this.

[0549] If the special ID is an RRC layer ID, refer to the above implementation method 1; if the special ID is a NAS layer ID, refer to implementation method 2.

[0550] S810: The RAN instructs UE1 not to send an initial access request message again within a preset time and / or before receiving an initial access accept message.

[0551] S810 is an optional step. The specific implementation of S810 can refer to S604 in the above implementation mode 1.

[0552] S811: UE1 stops sending the initial access request message according to local logic or instructions from the RAN.

[0553] The specific implementation of S811 may refer to S605 in the above implementation method 1.

[0554] S812: RAN sends an initial access request message of UE1 to MME / AMF, where the initial access request message includes a special ID.

[0555] Correspondingly, the MME / AMF receives the initial access request message of UE1.

[0556] S813: MME / AMF triggers paging according to the special ID.

[0557] S814: The MME / AMF sends a core network paging CN paging message to the RAN, where the CN paging message includes the special ID.

[0558] Correspondingly, the RAN receives the CN paging message.

[0559] S813 and S814 are optional steps.

[0560] S815: MME / AMF sends an initial access accept message to RAN.

[0561] Optionally, the MME / AMF sends an indication message to the RAN to instruct the RAN to page UE1 before sending the initial access accept message.

[0562] In this embodiment, the execution order of the above S814 and S815 is not specifically limited.

[0563] S816: RAN determines to restore coverage to UE1.

[0564] S817: The RAN sends a paging message, which includes the special ID.

[0565] Correspondingly, UE1 receives the paging message.

[0566] S818: UE1 sends a paging response message to the RAN.

[0567] Accordingly, the RAN receives the paging response message.

[0568] S819: RAN sends an initial access accept message to UE1.

[0569] S820: Execute the process after the initial access process is completed.

[0570] The specific implementation of S816-S820 can be referred to in a one-to-one correspondence with the implementation of S710-S714 in the second implementation (or S608-S612 in the first implementation), and will not be described in detail here. However, unlike the paging message sent by the RAN in S711, which includes the NAS layer ID, the paging message sent by the RAN in step S817 includes a special ID assigned by the RAN / UE1.

[0571] In summary, in this third implementation, the RAN uses a special ID assigned by the RAN or the UE to page the UE. To this end, the RAN first notifies the UE via a broadcast message when it determines that there is no feeder connection, or after the RRC establishes an RRC connection with the UE and determines that there is no feeder connection, the RAN sends an RRC message to the UE to inform the UE. In the case where the UE is assigned a special ID, the UE is assigned a special ID after receiving a RAN broadcast message or RRC message. The special ID is then carried in an Initial Access Request message and sent to the RAN. The RAN then forwards the Initial Access Request message to the core network element. After receiving the Initial Access Request message, the core network element can obtain the special ID assigned by the UE. The core network element then sends a paging message containing the special ID to the RAN, so that the RAN can subsequently page the UE based on the special ID assigned by the UE, and then forward the Initial Access Accept message from the core network to the UE, thereby effectively completing the UE's initial access process.

[0572] Implementation method four:

[0573] Based on the method described in Figures 4A and 4B above, in this fourth implementation, in the S&F scenario, during the initial access process of a terminal device UE (using UE1 as an example), if UE1 initiates an authentication process, the RAN will page UE1 using different temporary IDs before and after the authentication process. Referring to Figure 9, the specific process is as follows:

[0574] S900a: The RAN local configuration allows instructing the UE to enter a suspend state.

[0575] S900b: The MME / AMF may trigger the RAN to directly instruct the RAN to enter a suspend state.

[0576] The specific implementation of the above S900a-S900b can refer to the implementation of S600a and S600b in the above embodiment 1 in a one-to-one correspondence, and will not be described in detail here.

[0577] S901: UE1 sends an initial access request message to the RAN.

[0578] Accordingly, the RAN receives the initial access request message.

[0579] S902: RAN determines that there is no feeder connection.

[0580] S903: RAN sends an RRC connection release request message to UE1.

[0581] Correspondingly, the UE1 receives the RRC connection release request message.

[0582] S904: RAN instructs UE1 not to send an initial access request message again within a preset time and / or before receiving an initial access accept message.

[0583] S904 is an optional step.

[0584] S905: UE1 may stop sending the initial access request message according to local logic or instructions of the RAN.

[0585] S906: RAN sends an initial access request message of UE1 to MME / AMF.

[0586] Correspondingly, the MME / AMF receives the initial access request message of UE1.

[0587] The specific implementations of the above S900a-S900b and S902 to S906 can refer to the specific implementations of S600a and S600b and S602-S606 in the above implementation mode 1, and will not be described in detail here.

[0588] In this implementation method four, before the RAN sends the initial access request message to the MME / AMF, and including the RAN sending the initial access request message to the MME / AMF, the steps performed can also be implemented one-to-one with reference to any one of the above-mentioned implementation methods two to three, without limitation.

[0589] S907: RAN sends a paging message 1, which includes a core network paging identifier (temporary ID A). Correspondingly, UE1 receives the paging message 1.

[0590] Before the initial access acceptance message (i.e., S909), an authentication and authorization process is also included. In this process, UE1 and the core network need to complete two interactive processes. In the authentication and authorization process, i.e., in S907, the RAN can first page UE1 using the identifier mentioned in Implementation Methods 1 to 3 (which can be called: temporary ID A); after UE1 responds to the paging, the core network sends an authentication and authorization message and a new temporary ID (called: temporary ID B) to UE1. Temporary ID B is allocated to UE1 by the MME / AMF, not by the RAN / UE. After the authentication and authorization process, the RAN can use temporary ID B to page UE1 until the initial access process is completed.

[0591] S908: Complete the authentication process.

[0592] UE1 can execute and complete the authentication process based on the identification information in the paging message 1. The authentication process in this embodiment can be specifically implemented with reference to the authentication process in the prior art and will not be described in detail here.

[0593] During the authentication process, the MME / AMF may allocate a temporary ID B for the UE and send it to the UE.

[0594] S909: MME / AMF sends an initial access accept message to RAN.

[0595] Accordingly, the RAN receives the Initial Access Accept message of UE1 from the MME / AMF.

[0596] S910: RAN determines to restore coverage to UE1.

[0597] S911: RAN sends a paging message 2, which includes a temporary ID B. Correspondingly, UE1 receives the paging message 2.

[0598] S912: UE1 sends a paging response message to RAN. Correspondingly, RAN receives the paging response message from UE1.

[0599] In S912 , UE1 responds to the paging of the RAN based on the temporary ID B.

[0600] S913: RAN sends an initial access accept message to UE1. Correspondingly, UE1 receives the initial access accept message.

[0601] Optionally, the paging message 2 sent by the RAN includes indication information 2, where the indication information 2 is used to instruct the UE to delete the temporary ID A and / or the temporary ID B. Alternatively, the initial access accept message includes indication information 2, where the indication information 2 is used to instruct the UE1 to delete the temporary ID A and / or the temporary ID B.

[0602] For example, the initial access accept message may carry the S-TMSI (part of the GUTI) and indication information 2. After UE1 receives the initial access accept message, the initial access process is completed, temporary ID A and temporary ID B are deleted, and UE1 may subsequently use the S-TMSI (part of the GUTI) carried in the initial access accept message to respond to paging. Specific implementations can be made with reference to existing technical solutions and will not be described in detail here.

[0603] S914: Execute the process after the initial access process is completed.

[0604] The process after UE1 completes the initial access process can be referred to in the prior art and will not be described in detail here.

[0605] In this fourth implementation, for the S&F scenario, during the initial access process, if the UE's authentication and authorization process is initiated, the RAN uses different temporary IDs to page the UE before and after the authentication and authorization process. Before the authentication and authorization process, the RAN uses temporary ID A to page the UE. Since the MME / AMF will allocate a new temporary ID B after receiving the UE's initial access request message and send it to the UE during the authentication and authorization process, after the authentication and authorization process, the RAN can use the temporary ID B to page the UE and complete the UE's initial access process. In addition, the network can also instruct the UE to delete the temporary ID B after completing the initial access process through the initial access accept message to ensure network security. Therefore, compared with the identification ID allocated by the RAN or UE in the above-mentioned implementations one and three, the identification ID allocated by the core network in this implementation four is more secure. Compared with the above-mentioned implementation two, the temporary ID allocated by the core network in this implementation four is a more dynamic identification and has higher security.

[0606] Implementation method five:

[0607] Based on the method described in Figures 5A and 5B above, in this fifth implementation, in the S&F scenario, during the initial access process of a terminal device UE (using UE1 as an example), UE1's source RAN forwards the context via the core network, and then pages UE1 during the initial access process via another RAN (the target RAN). Referring to Figure 10 , the specific process is as follows:

[0608] S1000a: The source RAN locally configures the permission to instruct the UE to enter a suspend state.

[0609] S1000b: The MME / AMF triggers the source RAN to directly instruct the UE1 to enter a suspend state.

[0610] S1001: UE1 sends an initial access request message to the source RAN.

[0611] S1002: The source RAN determines that there is no feeder connection.

[0612] S1003: The source RAN sends an RRC connection release request message to UE1. Correspondingly, UE1 receives the RRC connection release request message.

[0613] S1004: RAN instructs UE1 not to send an initial access request message again within a preset time and / or before receiving an initial access accept message.

[0614] S1004 is an optional step.

[0615] S1005: UE1 may stop sending the initial access request message according to local logic or instructions of the RAN.

[0616] The specific implementations of the above S1000a-S1000b and S1002 to S1005 can refer to the specific implementations of S600a and S600b and S602-S605 in the above implementation mode 1, and will not be described in detail here.

[0617] S1006: The source RAN sends the context information of the source RAN to the MME / AMF. Correspondingly, the MME / AMF receives the context information of the source RAN from the source RAN.

[0618] The context information of the source RAN includes RRC context, paging ID and the like.

[0619] S1007: The source RAN sends an initial access request message of UE1 to the MME / AMF. Correspondingly, the MME / AMF receives the initial access request message of UE1.

[0620] This embodiment does not impose any specific limitation on the execution order of S1006 and S1007.

[0621] S1008: The MME / AMF determines the target RAN.

[0622] S1009: The MME / AMF sends the context information to the target RAN. Correspondingly, the target RAN receives the context information.

[0623] That is, the target RAN receives the context information of the source RAN.

[0624] S1010: The MME / AMF sends an initial access accept message to the target RAN. Correspondingly, the target RAN receives the initial access accept message.

[0625] S1011: The target RAN determines to restore coverage to UE1.

[0626] S1012: The target RAN sends a paging message. Correspondingly, UE1 receives the paging message sent by the target RAN.

[0627] The identifier used by the target RAN to paging UE1 can be specifically implemented by referring to the solution of RAN paging UE1 in any one of the above implementation modes 1 to 4, and no specific limitation is made thereto.

[0628] S1013: UE1 sends a paging response message to the target RAN. Correspondingly, the target RAN receives the paging response message from UE1.

[0629] S1014: The target RAN sends an initial access accept message to UE1. Correspondingly, UE1 receives the initial access accept message.

[0630] S1015: Execute the process after the initial access process is completed.

[0631] To summarize, in implementation method five, for the S&F scenario, in the initial access process, the RAN forwards the context information through the core network element MME / AMF. After receiving the context information from the source RAN, the core network element MME / AMF determines the target RAN and then forwards the context information from the source RAN to the target RAN. In this way, the UE can be paged more quickly in the initial access process through the target RAN, thereby effectively completing the initial access process.

[0632] Implementation method six:

[0633] Compared to the above-mentioned implementation method 5, the main difference in this implementation method 6 is that the source RAN sends the context to the target RAN in a different way. That is, the source RAN forwards the context information to the target RAN via the inter-satellite link, and then the target RAN pages UE1 in the initial access process. Referring to Figure 11, the specific process is as follows:

[0634] S1100a: The source RAN local configuration allows the UE to enter a suspend state.

[0635] S1100b: The MME / AMF may trigger the source RAN to directly instruct the UE1 to enter a suspend state.

[0636] S1101: UE1 sends an initial access request message to the source RAN.

[0637] S1102: The source RAN determines that there is no feeder connection.

[0638] S1103: The source RAN sends an RRC connection release request message to UE1. Correspondingly, UE1 receives the RRC connection release request message.

[0639] S1104: The source RAN instructs UE1 not to send an initial access request message again within a preset time and / or before receiving an initial access accept message.

[0640] S1104 is an optional step.

[0641] S1105: UE1 stops sending the initial access request message according to local logic or instructions from the RAN.

[0642] The specific implementations of the above-mentioned S1100a-S1100b and S1102 to S1105 can be referred to one by one in the specific implementations of S1000a-S1000b and S1002 to S1005 in the above-mentioned implementation method five (or refer to the specific implementations of S600a and S600b and S602-S605 in the above-mentioned implementation method one), and will not be described in detail here.

[0643] S1106: The source RAN sends an initial access request message to the MME / AMF.

[0644] S1107: The MME / AMF determines the target RAN.

[0645] S1108: The MME / AMF sends an initial access accept message to the target RAN.

[0646] S1109: The MME / AMF sends the indication information / identification information of the target RAN to the source RAN.

[0647] In a possible implementation manner, the indication information of the target RAN may be used to indicate identification information of the target RAN (eg, ID / address of the target RAN), etc.

[0648] S1110: The MME / AMF sends the indication information / identification information of the source RAN to the target RAN. Correspondingly, the target RAN receives the indication information / identification information of the source RAN.

[0649] In a possible implementation manner, the indication information of the source RAN may be used to indicate identification information of the source RAN (eg, ID / address of the source RAN), etc.

[0650] S1111: The target RAN sends a context request message to the source RAN. Correspondingly, the source RAN receives the context request message.

[0651] The above steps S1109-S1111 are optional steps.

[0652] S1112: The source RAN sends the context information of the source RAN to the target RAN. Correspondingly, the target RAN receives the context information of the source RAN.

[0653] The context information includes RRC context, paging ID, etc.

[0654] S1113: The target RAN determines to restore coverage to UE1.

[0655] S1114: The target RAN sends a paging message. Correspondingly, UE1 receives the paging message sent by the target RAN.

[0656] The identifier used by the target RAN to paging UE1 can be specifically implemented by referring to the solution of RAN paging UE1 in any one of the above implementation modes 1 to 4, and is not specifically limited thereto.

[0657] S1115: UE1 sends a paging response message to the target RAN. Correspondingly, the target RAN receives the paging response message from UE1.

[0658] S1116: The target RAN sends an initial access accept message to UE1. Correspondingly, UE1 receives the initial access accept message.

[0659] S1117: Execute the process after the initial access process is completed.

[0660] In this implementation method 6, for the S&F scenario, during the initial access process, the MME / AMF receives the UE's initial access request message forwarded by the source RAN, determines the target RAN, and forwards the source RAN ID to target RAN 2, or forwards the target RAN 2 ID to source RAN 1. This allows the source RAN to forward the context via the inter-satellite link to the target RAN, enabling faster paging of the UE during the initial access process through the target RAN.

[0661] Regarding the above implementations 1 to 6, it should be noted that:

[0662] (1) The above-mentioned implementation methods 1 to 6 can be implemented separately or in combination, without any specific limitation.

[0663] (2) The above description focuses on the differences between implementation modes 1 to 6. Except for the differences, implementation modes 1 to 6 can refer to each other.

[0664] (3) The step numbers in the flowcharts described in Implementations 1 to 6 are merely examples of the execution process and do not limit the order in which the steps are executed. There are no sequential dependencies between the steps in the various implementations of this application, and there is no strict execution order. Furthermore, not all of the steps shown in the flowcharts are mandatory steps, and steps may be added or deleted based on actual needs.

[0665] In the embodiments provided in the present application above, the methods provided in the embodiments of the present application are introduced from the perspective of interaction between various devices. In order to implement the various functions in the methods provided in the embodiments or implementations of the present application above, the first terminal device or the first access network device or the second access network device or the core network element may include a hardware structure and / or a software module to implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether one of the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

[0666] The division of modules in the embodiments of the present application is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments or implementations of the present application may be integrated into a single processor, or may exist physically separately, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or software functional modules.

[0667] Similar to the above concept, as shown in FIG12 , an embodiment of the present application further provides a communication device 1200 for implementing the functions of the first terminal device, first access network device, second access network device, or core network element in the above method. For example, the communication device 1200 may be a software module or a chip system. In the embodiment of the present application, the chip system may be composed of a chip, or may include a chip and other discrete components. The communication device 1200 may include: a communication unit 1201 and a processing unit 1202.

[0668] In the embodiments of the present application, the communication unit 1201 may also be referred to as a transceiver unit, and may include a sending unit and / or a receiving unit, respectively configured to execute the steps of sending and receiving by the first terminal device, the first access network device, the second access network device, or the core network element in the above method embodiments. The processing unit 1202 may be configured to read instructions and / or data from the storage module to enable the communication device 1200 to implement the above method embodiments.

[0669] Optionally, the communication device 1200 may further include a storage unit 1203 , which is equivalent to a storage module and may be used to store instructions and / or data.

[0670] The communication device provided in the embodiments of the present application is described in detail below in conjunction with Figures 12 and 13. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, the contents not described in detail can be implemented with reference to the above Figures 4A and 4B, 5A-5B, and Figures 6 to 11. For the sake of brevity, they are not described here in detail.

[0671] The communication unit 1201 may also be referred to as a transceiver, transceiver, or transceiver device. The processing unit may also be referred to as a processor, processing board, processing module, or processing device. Alternatively, the device in the communication unit 1201 that implements the receiving function may be considered a receiving unit, and the device in the communication unit 1201 that implements the transmitting function may be considered a transmitting unit. That is, the communication unit 1201 includes both a receiving unit and a transmitting unit. A communication unit may also be referred to as a transceiver, transceiver, or transceiver circuit. A receiving unit may also be referred to as a receiver, receiver, or receiving circuit. A transmitting unit may also be referred to as a transmitter, transmitter, or transmitting circuit.

[0672] When the communication device 1200 executes the first access network device of the process shown in Figure 4A in the above embodiment: the communication unit 1201 and the processing unit 1202 in the communication device 1200 are both located in the first access network device; or the communication unit 1201 is located in the DU of the first access network device, and the processing unit 1202 is located in the CU of the first access network device; or in the O-RAN architecture, the communication unit 1201 is located in the O-DU and / or O-RU of the first access network device, and the processing unit 1202 is located in the O-CU and / or O-DU of the first access network device.

[0673] Among them, the communication unit 1201 is used to receive response information of the first request information from the core network network element, and the response information of the first request information is used to indicate that the network accepts the registration of the first terminal device; the processing unit 1202 is used to send a first paging message according to the response information of the first request information; the first paging message includes the first identification information of the first terminal device; the communication unit 1201 is also used to receive a first paging response message from the first terminal device, and the first paging response message is used to respond to the first paging message; and according to the first paging response message, send the response information of the first request information to the first terminal device.

[0674] When the communication device 1200 executes the first terminal device in the process shown in Figure 4A of the above embodiment: the communication unit 1201 is used to send a first request information to the first access network device, and the first request information is used to request that the first terminal device be registered to the network; the communication unit 1201 is also used to receive a first CN paging message from the first access network device, and the first CN paging message includes the first identification information of the first terminal device; the processing unit 1202 is used to control the communication unit 1201 to perform sending and / or receiving functions, and process data and / or information, etc.

[0675] When the communication apparatus 1200 executes the first terminal device in the process shown in FIG. 4A of the above embodiment: the communication unit 1201 is configured to send a first request message to a first access network device, where the first request message is used to request that the first terminal device be registered with a network; and receive a first paging message from the first access network device. The communication unit 1201 is further configured to send a first paging response message; the first paging response message is used to respond to the first paging message.

[0676] The communication unit 1201 is also used to receive a first indication message received from the first access network device, and the first indication message is used to trigger the first terminal device not to send the first request message within a preset time or before receiving the response message of the first request message; according to the first indication message, stop sending the first request message within the preset time or before receiving the response message of the first request message; or; the processing unit 1202 is used to stop sending the first request message through the communication unit 1201 within the preset time or before receiving the response message of the first request message according to local configuration.

[0677] When the communication device 1200 executes the core network element in the process shown in Figure 4A of the above embodiment: the communication unit 1201 is used to receive a first request information from a first access network device, and the first request information is used to request that the first terminal device be registered to the network; the communication unit 1201 is also used to send a paging message to the first access network device according to the first request information when the first terminal device is a non-continuous feeding type, and the paging message is used to trigger the first access network device to page the first terminal device.

[0678] When the communication device 1200 executes the first access network device in the process shown in Figure 4B of the above embodiment: the communication unit 1201 and the processing unit 1202 in the communication device 1200 are both located in the first access network device; or the communication unit 1201 is located in the DU of the first access network device, and the processing unit 1202 is located in the CU of the first access network device; or in the O-RAN architecture, the communication unit 1201 is located in the O-DU and / or O-RU of the first access network device, and the processing unit 1202 is located in the O-CU and / or O-DU of the first access network device.

[0679] The communication unit 1201 is used to receive response information of the first request information from the core network network element, and the response information of the first request information is used to indicate that the network accepts the registration of the first terminal device; the communication unit 1202 is also used to send a first paging message according to the response information of the first request information; the first paging message includes the first identification information of the first terminal device; in addition, the communication unit 1201 is also used to receive a first paging response message from the first terminal device, and the first paging response message is used to respond to the first paging message; and according to the first paging response message, send the response information of the first request information to the first terminal device.

[0680] When the communication device 1200 executes the second access network device in the process shown in Figure 5A of the above embodiment: the communication unit 1201 and the processing unit 1202 in the communication device 1200 are both located in the second access network device; or the communication unit 1201 is located in the DU of the second access network device, and the processing unit 1202 is located in the CU of the second access network device; or in the O-RAN architecture, the communication unit 1201 is located in the O-DU and / or O-RU of the second access network device, and the processing unit 1202 is located in the O-CU and / or O-DU of the second access network device.

[0681] The communication unit 1201 is used to receive a first request message from a first terminal device, where the first request message is used to request that the first terminal device be registered to the network; the communication unit 1201 is also used to send the first request message and the connection context of the second access network device to the core network element when it is determined through the processing unit 1202 that the second access network device has no feeder connection.

[0682] When the communication device 1200 executes the first terminal device in the process shown in Figure 5A of the above embodiment: the communication unit 1201 is used to send a first request message to the second access network device, and the first request message is used to request that the first terminal device be registered to the network; the communication unit 1201 is also used to receive a first paging message from the first access network device, and the first paging message includes the first identification information of the first terminal device; the processing unit 1202 is also used to determine not to send a service request message to the first access network device when the first terminal device is a non-continuous feeding type and the first terminal device does not receive a response message to the first request message.

[0683] When the communication device 1200 executes the first terminal device in the process shown in Figure 5A of the above embodiment: the communication unit 1201 is used to send a first request message to the second access network device, and the first request message is used to request that the first terminal device be registered to the network; the communication unit 1201 is also used to receive a first paging message from the first access network device; send the first paging response message; the first paging response message is used to respond to the first paging message; and receive a first indication message received from the first access network device, and the first indication message is used to trigger the first terminal device not to send the first request message within a preset time or before receiving the response message of the first request message; the communication unit 1201 is also used to stop sending the first request message within the preset time or before receiving the response message of the first request message according to the first indication message; or; the processing unit 1202 is used to stop sending the first request message through the communication unit 1201 within the preset time or before receiving the response message of the first request message according to local configuration.

[0684] When the communication device 1200 executes the core network element in the process shown in Figure 5A of the above embodiment: the communication unit 1201 is used to receive a first request information from the second access network device, and the first request information is used to request that the first terminal device be registered to the network; the communication unit 1201 is also used to send a paging message to the first access network device according to the first request information when the first terminal device is a non-continuous feeding type, and the paging message is used to trigger the first access network device to page the first terminal device.

[0685] The above are just examples. The processing unit 1202 and the communication unit 1201 can also perform other functions. For more detailed descriptions, please refer to the relevant descriptions in the method embodiments shown in Figures 4A and 4B and 5A-5B, which are not repeated here.

[0686] Figure 13 shows a communication device 1300 provided in an embodiment of the present application. The communication device shown in Figure 13 may be a hardware circuit implementation of the communication device shown in Figure 12 . This communication device 1300 can be used in the flowcharts shown above to perform the functions of a first terminal device, a first access network device, a second access network device, or a core network element in the method embodiments described above. For ease of illustration, Figure 13 only shows the main components of the communication device.

[0687] As shown in Figure 13, communication device 1300 includes a communication interface 1301 and a processor 1302. Communication interface 1301 and processor 1302 are coupled to each other. It is understood that communication interface 1301 can be a transceiver or input / output interface, or an interface circuit such as a transceiver circuit. Optionally, communication device 1300 can also include a memory 1303 for storing instructions executed by processor 1302, input data required by processor 1302 to execute instructions, or data generated by processor 1302 after executing instructions.

[0688] When the communication device 1300 is used to implement the methods shown in Figures 4A and 4B, 5A-5B, and Figures 6 to 11, the communication interface 1301 is used to implement the functions of the above-mentioned communication unit 1201, and the processor 1302 is used to implement the functions of the above-mentioned processing unit 1202.

[0689] The specific connection medium between the communication interface 1301, the processor 1302, and the memory 1303 is not limited in the embodiments of the present application. In Figure 13, the embodiment of the present application shows that the memory 1303, the processor 1302, and the communication interface 1301 are connected via a communication bus 1304. The communication bus 1304 is represented by a bold line in Figure 13. The connection method between other components is only for schematic illustration and is not intended to be limiting. The communication bus 1304 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used in Figure 13, but this does not mean that there is only one bus or one type of bus.

[0690] When the communication device is a chip, FIG14 shows a simplified schematic diagram of the chip structure, wherein the chip 1400 includes an interface circuit 1401 and one or more processors 1402. Optionally, the chip 1400 may further include a bus.

[0691] Processor 1402 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above-mentioned method for determining service node information can be completed by hardware integrated logic circuits or software instructions in processor 1402. The above-mentioned processor 1402 can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the various methods and steps disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0692] The interface circuit 1401 can be used to send or receive data, instructions or information. The processor 1402 can use the data, instructions or other information received by the interface circuit 1401 to process it, and can send the processing completion information through the interface circuit 1401.

[0693] Optionally, the chip further includes a memory 1403, which may include a read-only memory and a random access memory, and provides operating instructions and data to the processor. A portion of the memory 1403 may also include a non-volatile random access memory (NVRAM).

[0694] Optionally, the memory stores an executable software module or a data structure, and the processor can perform corresponding operations by calling an operation instruction stored in the memory (the operation instruction may be stored in an operating system).

[0695] Optionally, the chip can be used in the first terminal device, first access network device, second access network device, or core network element involved in the embodiments of this application. Optionally, the interface circuit 1401 can be used to output the execution result of the processor 1402. For the communication methods provided in one or more embodiments of this application, reference can be made to the aforementioned embodiments and will not be repeated here.

[0696] It should be noted that the corresponding functions of the interface circuit 1401 and the processor 1402 can be implemented through hardware design, software design, or a combination of hardware and software, and there is no limitation here.

[0697] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions are stored for implementing the method executed by the first terminal device or the first access network device or the second access network device or the core network element in the above method embodiment.

[0698] For example, when the computer program is executed by a computer, the computer can implement the method performed by the first terminal device or the first access network device or the second access network device or the core network element in the above method embodiment.

[0699] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to implement the method executed by the first terminal device or the first access network device or the second access network device or the core network element in the above method embodiment.

[0700] An embodiment of the present application also provides a chip, including a processor, for calling the computer program or computer instructions stored in the memory so that the processor executes the communication method of the implementation method shown in Figures 4A and 4B and 5A-5B, and Figures 6 to 11 above.

[0701] In one possible implementation, the input of the chip corresponds to the receiving operation in the implementation shown in Figures 4A and 4B, 5A-5B, and Figures 6 to 11 above, and the output of the chip corresponds to the sending operation in the implementation shown in Figures 4A and 4B, 5A-5B, and Figures 6 to 11 above.

[0702] Optionally, the processor is coupled to the memory via an interface.

[0703] Optionally, the chip further includes a memory in which computer programs or computer instructions are stored.

[0704] The processor mentioned in any of the above may be a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of a program of a communication method in the implementation manner shown in Figures 4A and 4B, 5A-5B, and Figures 6 to 11. The memory mentioned in any of the above may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM), etc.

[0705] It should be noted that, for the sake of convenience and brevity, the explanation and beneficial effects of the relevant contents in any of the above-mentioned communication devices may refer to the corresponding service node information determination method embodiments provided above, which will not be repeated here.

[0706] In the present application, the communication devices may further include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system layer. The hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also known as main memory). The operating system of the operating system layer may be any one or more computer operating systems that implement business processing through processes, such as the Linux operating system, Unix operating system, Android operating system, iOS operating system, or Windows operating system. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

[0707] The division of modules in the embodiments of the present application is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments of the present application may be integrated into a single processor, or may exist physically separately, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or software functional modules.

[0708] Through the description of the above embodiments, it will be clear to those skilled in the art that the embodiments of the present application can be implemented in hardware, firmware, or a combination thereof. When software is used for implementation, the above functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein the communication media include any medium that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that a computer can access. For example, but not limited to: a computer-readable medium may include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer. In addition, any connection can be appropriately a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used in the embodiments of the present application, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically and discs use lasers to reproduce data optically. Combinations of the above should also be included within the scope of protection of computer-readable media.

[0709] In short, the above description is only an embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made based on the disclosure of the present application should be included in the scope of protection of the present application.

Claims

1. A communication method, characterized in that: The method is applied to a first access network device or a chip of the first access network device, and includes: receiving response information to the first request information from a core network element, where the response information to the first request information is used to indicate that the network accepts registration of the first terminal device; Sending a first paging message according to the response information of the first request information; the first paging message includes the first identification information of the first terminal device; receiving a first paging response message from the first terminal device, where the first paging response message is used to respond to the first paging message; According to the first paging response message, response information of the first request information is sent to the first terminal device.

2. The method according to claim 1, characterized in that The first identification information is identification information of the access layer; The identification information of the access layer is allocated by the first access network device; or the identification information of the access layer is allocated by the first terminal device.

3. The method according to claim 1, characterized in that The first identification information is identification information of the non-access layer; The identification information of the non-access layer is allocated by the core network element; or the identification information of the non-access layer is pre-configured on the first terminal device and the core network element.

4. The method according to claim 3, characterized in that The first identification information is allocated to the first terminal device by the core network during the authentication and authorization process of the first terminal device.

5. The method according to claim 4, characterized in that The method further comprises: In the authentication process, a second paging message is sent, and the second paging message includes second identification information of the first terminal device.

6. The method according to claim 5, characterized in that The second identification information is identification information of the access layer.

7. The method according to claim 5, characterized in that The second identification information is identification information of the non-access layer.

8. The method according to claim 2 or 6, characterized in that: The method further comprises: receiving the first request information from the first terminal device, where the first request information is used to request to register the first terminal device to a network; When the first access network device has no feeder connection, first information is sent to the first terminal device, where the first information is used to trigger the first terminal device to retain the radio resource control RRC context, and the RRC context includes identification information of the access layer corresponding to the first terminal device.

9. The method according to claim 3 or 4, characterized in that: The method further comprises: receiving the first request information from the first terminal device, where the first request information is used to request to register the first terminal device to a network; When the first access network device has no feeder connection, second information is sent to the first terminal device, where the second information is used to trigger the first terminal device to release the radio resource control RRC context.

10. The method according to claim 8 or 9, characterized in that: The method further comprises: Determine, according to local configuration, that the first access network device has no feeder connection; or, Determine, according to interface connection information between the first access network device and the core network device, that the first access network device has no feeder connection; or, It is determined that the first access network device has no feeder connection according to the feeder connection state information of the first access network device.

11. The method according to claim 8 or 9, characterized in that: The method further comprises: Sending first indication information to the first terminal device; the first indication information is used to trigger the first terminal device not to send the first request information within a preset time or before receiving response information to the first request information.

12. The method according to any one of claims 8 to 10, characterized in that The first access network device has no feeder connection, including any one of the following: The satellite where the first access network device is located is not connected to the gateway; The first access network device has no connection with the gateway; The first access network device is not connected to the core network device.

13. The method according to any one of claims 1 to 12, characterized in that Before sending the first paging message, the method further includes: receiving second indication information from the core network element; the second indication information is used to trigger the first access network device to page the first terminal device before receiving the response information of the first request information; The sending a first paging message according to the response information of the first request information includes: The first paging message is sent according to the second indication information and the response information of the first request information.

14. The method according to any one of claims 1 to 13, characterized in that The method further comprises: Send third indication information to the first terminal device, where the third indication information is used to trigger the first terminal device to delete the first identification information after receiving the first paging message or the response information of the first request information.

15. A communication method, characterized in that: The method is applied to a first terminal device or a chip of the first terminal device, wherein the first terminal device is of a non-continuous feeding type, and includes: Sending a first request message to a first access network device, where the first request message is used to request that the first terminal device be registered to a network; Receiving a first paging message from the first access network device, where the first paging message includes first identification information of the first terminal device; Determine not to send a service request message to the first access network device.

16. The method according to claim 15, characterized in that The method further comprises: Sending a first paging response message to the first access network device, where the first paging response message is used to respond to the first paging message and request to establish or restore a radio resource control RRC connection; After the RRC connection is established or the RRC connection is restored, response information to the first request information is received from the first access network device through the RRC connection; the response information to the first request information is used to indicate that the network accepts registration of the first terminal device.

17. The method according to claim 15 or 16, characterized in that The method further comprises: receiving second information, where the second information is used to trigger the first terminal device to release a radio resource control RRC context; The RRC context is released according to the second information.

18. The method according to claim 15, characterized in that The first identification information is identification information of the non-access layer; the identification information of the non-access layer is allocated by the core network element; or the identification information of the non-access layer is pre-configured on the first terminal device or the core network element.

19. The method according to claim 18, characterized in that The first identification information is allocated to the first terminal device by the core network during the authentication and authorization process of the first terminal device.

20. The method according to claim 19, characterized in that The method further comprises: In the authentication process, a second paging message is received from the first access network device, and the second paging message includes second identification information of the first terminal device.

21. The method according to claim 20, characterized in that The second identification information is identification information of the non-access layer.

22. The method according to any one of claims 15 to 21, characterized in that The method further comprises: receiving third indication information from the first access network device, where the third indication information is used to trigger the first terminal device to delete the first identification information after receiving the first paging message or the response information of the first request information; According to the third indication information, the first identification information is deleted.

23. A communication method, characterized in that: The method is applied to a first terminal device or a chip of the first terminal device, Sending a first request message to a first access network device, where the first request message is used to request that the first terminal device be registered to a network; receiving a first paging message from the first access network device, Sending the first paging response message; The first paging response message is used to respond to the first paging message; Receiving first indication information received from the first access network device, where the first indication information is used to trigger the first terminal device not to send the first request information within a preset time or before receiving a response information to the first request information; according to the first indication information, stopping sending the first request information within the preset time or before receiving a response information to the first request information; or; According to local configuration, the sending of the first request information is stopped within a preset time or before receiving a response information to the first request information.

24. A communication method, characterized in that: The method is applied to a core network element or a chip of the core network element, and includes: Receiving first request information from a first access network device, where the first request information is used to request to register the first terminal device to the network; When the first terminal device is of a non-continuous feeding type, a paging message is sent to the first access network device according to the first request information, and the paging message is used to trigger the first access network device to page the first terminal device.

25. The method according to claim 24, characterized in that The method further comprises: Send response information to the first request information to the first access network device, where the response information to the first request information is used to indicate that the network accepts registration of the first terminal device.

26. The method according to claim 24 or 25, characterized in that The method further comprises: Send second indication information to the first access network device; the second indication information is used to instruct the first access network device to page the first terminal device before receiving response information to the first request information.

27. The method according to any one of claims 24 to 26, characterized in that The method further comprises: It is determined that the first terminal device is of a discontinuous feeding type.

28. The method according to claim 27, characterized in that The determining that the first terminal device is of a discontinuous feeding type includes: According to the contract information of the terminal device, determining that the first terminal device is a non-continuous feeding type; the contract information includes any one or more of the following: a specific group, a specific DNN, S-NSSAI; or, According to the capability information of the first access network device, determining that the first terminal device is of a discontinuous power feeding type; the capability information of the first access network device indicates that the first access network device supports discontinuous power feeding; or, According to the tracking area TA information supported by the first access network device and the tracking area TA where the first terminal device is located, it is determined that the first terminal device is a feeding discontinuous type.

29. The method according to any one of claims 24 to 28, characterized in that The method further comprises: First identification information of the first terminal device is received from the first access network device, where the first identification information is allocated by the first terminal device.

30. The method according to any one of claims 24 to 29, characterized in that The method further comprises: Allocating first identification information of the first terminal device; The first identification information is sent to the first access network device, where the first identification information is used by the first access network device to page the first terminal device.

31. The method according to claim 30, characterized in that The first identification information is allocated to the first terminal device by the core network after the authentication of the first terminal device is successful.

32. The method according to claim 31, characterized in that The method further comprises: Send second identification information of the first terminal device, where the second identification information is used by the first access network device to page the first terminal device during authentication of the first terminal device.

33. A communication method, characterized in that: The method is applied to a first access network device or a chip of the first access network device, and includes: receiving response information to the first request information from a core network element, where the response information to the first request information is used to indicate that the network accepts registration of the first terminal device; Sending a first paging message according to the response information of the first request information; the first paging message includes the first identification information of the first terminal device; receiving a first paging response message from the first terminal device, where the first paging response message is used to respond to the first paging message; According to the first paging response message, response information of the first request information is sent to the first terminal device.

34. The method according to claim 33, characterized in that The first identification information is identification information of the access layer; The identification information of the access layer is allocated by the second access network device; or, the identification information of the access layer is allocated by the first terminal device.

35. The method according to claim 33, characterized in that The first identification information is identification information of the non-access layer; The identification information of the non-access layer is allocated by the core network element; or the identification information of the non-access layer is preset and configured on the first terminal device and the core network element.

36. The method according to claim 35, characterized in that The first identification information is allocated to the first terminal device by the core network during the authentication and authorization process of the first terminal device.

37. The method according to claim 36, characterized in that The method further comprises: In the authentication process, a second paging message is sent, and the second paging message includes second identification information of the first terminal device.

38. The method according to claim 37, characterized in that The second identification information is identification information of the access layer.

39. The method according to claim 37, characterized in that The second identification information is identification information of the non-access layer.

40. The method according to any one of claims 33 to 39, characterized in that A context connection is established between the first terminal device and the second access network device, but no context connection is established with the first access network device; and the method further includes: Receive the connection context of the second access network device; the connection context of the second access network device includes the RRC context, wherein the RRC context includes identification information of the access layer corresponding to the first terminal device.

41. The method according to claim 40, characterized in that The receiving the connection context of the second access network device includes: A connection context of the second access network device is received from the core network element.

42. The method according to claim 40, characterized in that The receiving the connection context of the second access network device includes: A connection context of the second access network device is received from the second access network device.

43. The method according to claim 42, characterized in that The method further comprises: Receiving identification information of the second access network device; Send context request information to the second access network device according to the identification information of the second access network device, where the context request information is used to request a connection context for the second access network device.

44. The method according to any one of claims 33 to 43, characterized in that Before sending the first paging message, the method further includes: receiving second indication information from the core network element; the second indication information is used to trigger the first access network device to page the first terminal device before receiving the response information of the first request information; The sending a first paging message according to the response information of the first request information includes: The first paging message is sent according to the second indication information and the response information of the first request information.

45. The method according to any one of claims 33 to 44, characterized in that The method further comprises: Send third indication information to the first terminal device, where the third indication information is used to trigger the first terminal device to delete the first identification information after receiving the first paging message or the response information of the first request information.

46. ​​A communication method, characterized in that: The method is applied to a second access network device or a chip of the second access network device, where the second access network device is of a non-continuous feeding type, and includes: Receiving first request information from a first terminal device, where the first request information is used to request that the first terminal device be registered to a network; Send the first request information to a core network element, and send the connection context of the second access network device.

47. The method according to claim 46, characterized in that The method further comprises: When it is determined that the second access network device has no feeder connection, first information is sent to the first terminal device, where the first information is used to trigger the first terminal device to release or retain a connection context, where the connection context includes an RRC connection context.

48. The method according to claim 46, characterized in that The sending the connection context of the second access network device includes: Sending the connection context of the second access network device to the core network element.

49. The method according to claim 46, characterized in that The sending the connection context of the second access network device includes: Send the connection context of the second access network device to the first access network device.

50. The method according to claim 49, characterized in that The method further comprises: receiving context request information from the first access network device, where the context request information is used to request a connection context for the second access network device; The sending the connection context of the second access network device to the first access network device includes: sending the connection context to the first access network device according to the context request information.

51. The method according to claim 49, characterized in that The method further comprises: Receiving identification information of the first access network device; The sending of the connection context of the second access network device to the first access network device comprises: identification information, and sending the connection context to the first access network device.

52. The method of claim 47, wherein: The determining that the second access network device has no feeder connection includes: Determine, according to local configuration, that the second access network device has no feeder connection; or, Determine, according to the interface connection information between the second access network device and the core network device, that the second access network device has no feeder connection; or, According to the feeder connection state information of the second access network device, it is determined that the second access network device has no feeder connection.

53. The method according to claim 52, characterized in that The second access network device has no feeder connection, including any one of the following: The satellite where the second access network device is located is not connected to the gateway; The second access network device has no connection with the gateway; The second access network device is not connected to the core network device.

54. The method according to any one of claims 46 to 53, characterized in that The method further comprises: Sending first indication information to the first terminal device; the first indication information is used to trigger the first terminal device not to send the first request information within a preset time or before receiving response information to the first request information.

55. A communication method, characterized in that: The method is applied to a first terminal device or a chip of the first terminal device, wherein the first terminal device is of a non-continuous feeding type, and includes: Sending first request information to the second access network device, where the first request information is used to request that the first terminal device be registered to the network; Receiving a first paging message from a first access network device, where the first paging message includes first identification information of the first terminal device; If the first terminal device does not receive response information to the first request information, it determines not to send a service request message to the first access network device.

56. The method according to claim 55, characterized in that The method further includes: sending a first paging response message to the first access network device, wherein the first paging response message is used to respond to the first paging message and request to establish or restore a radio resource control RRC connection; After the RRC connection is established or the RRC connection is restored, response information to the first request information is received from the first access network device through the RRC connection; the response information to the first request information is used to indicate that the network accepts registration of the first terminal device.

57. The method according to claim 55 or 56, characterized in that Before receiving the first paging message from the first access network device, the method further includes: Receiving first information, where the first information is used to trigger the first terminal device to release a radio resource control RRC context; The RRC context is released according to the first information.

58. The method according to claim 55, characterized in that The first identification information is identification information of the non-access layer; the identification information of the non-access layer is allocated by the core network element; or the identification information of the non-access layer is preset and configured on the first terminal device and the core network element.

59. The method according to claim 58, characterized in that The first identification information is allocated to the first terminal device by the core network during the authentication and authorization process of the first terminal device.

60. The method according to claim 59, characterized in that The method further comprises: In the authentication process, a second paging message is received from the first access network device, and the second paging message includes second identification information of the first terminal device.

61. The method according to claim 60, characterized in that The second identification information is identification information of the non-access layer.

62. The method according to any one of claims 55 to 61, characterized in that The method further comprises: receiving third indication information from the first access network device, where the third indication information is used to trigger the first terminal device to delete the first identification information after receiving the first paging message or the response information of the first request information; According to the third indication information, the first identification information is deleted.

63. A communication method, characterized in that: The method is applied to a first terminal device or a chip of the first terminal device, Sending first request information to the second access network device, where the first request information is used to request that the first terminal device be registered to the network; Receiving a first paging message from a first access network device; Sending the first paging response message; The first paging response message is used to respond to the first paging message; Receiving first indication information received from the first access network device, where the first indication information is used to trigger the first terminal device not to send the first request information within a preset time or before receiving a response information to the first request information; according to the first indication information, stopping sending the first request information within the preset time or before receiving a response information to the first request information; or; According to local configuration, the sending of the first request information is stopped within a preset time or before receiving a response information to the first request information.

64. A communication method, characterized in that: The method is applied to a core network element or a chip of the core network element, and includes: Receiving first request information from a second access network device, where the first request information is used to request to register the first terminal device to the network; The first terminal device is of a non-continuous feeding type, and sends a paging message to a first access network device according to the first request information, wherein the paging message is used to trigger the first access network device to page the first terminal device.

65. The method according to claim 64, characterized in that The method further comprises: Send response information to the first request information to the first access network device, where the response information to the first request information is used to indicate that the network accepts registration of the first terminal device.

66. The method according to claim 64 or 65, characterized in that The method further comprises: Send second indication information to the first access network device; the second indication information is used to instruct the first access network device to page the first terminal device before receiving response information to the first request information.

67. The method according to any one of claims 64 to 66, characterized in that The method further comprises: It is determined that the first terminal device is of a discontinuous feeding type.

68. The method according to claim 67, characterized in that The determining that the first terminal device is of a discontinuous feeding type includes: According to the contract information of the first terminal device, it is determined that the first terminal device is a non-continuous feeding type; the contract information includes any one or more of the following: a specific group, a specific DNN, S-NSSAI; or, According to the capability information of the second access network device, determining that the first terminal device is of a discontinuous power feeding type; the capability information of the second access network device indicates that the second access network device supports discontinuous power feeding; or, According to the tracking area TA information supported by the second access network device and the tracking area TA where the first terminal device is located, it is determined that the first terminal device is a non-continuous feeding type.

69. The method according to any one of claims 64 to 68, characterized in that The method further comprises: Receive first identification information of the first terminal device from the second access network device.

70. The method according to any one of claims 64 to 68, characterized in that The method further comprises: Allocating first identification information of the first terminal device; The first identification information is sent to the first access network device, where the first identification information is used by the first access network device to page the first terminal device.

71. The method according to claim 70, characterized in that The first identification information is allocated to the first terminal device by the core network during the authentication and authorization process of the first terminal device.

72. The method according to claim 71, characterized in that The method further comprises: Send second identification information of the first terminal device to the first access network device, where the second identification information is used by the first access network device to page the first terminal device during the authentication and authorization process of the first terminal device.

73. A communication device, characterized in that: Comprising a module for executing the method as described in any one of claims 1 to 14, or comprising a module for executing the method as described in any one of claims 15 to 22, or comprising a module for executing the method as described in claim 23, or comprising a module for executing the method as described in any one of claims 24 to 32, or comprising a module for executing the method as described in any one of claims 33 to 45, or comprising a module for executing the method as described in any one of claims 46 to 54, or comprising a module for executing the method as described in any one of claims 55 to 62, or comprising a module for executing the method as described in claim 63, or comprising a module for executing the method as described in any one of claims 64 to 72.

74. A communication device, characterized in that: Comprises a processor and a memory; wherein the memory is used to store one or more computer programs or instructions, and the processor is used to execute the one or more computer programs or instructions stored in the memory, so that the communication device performs the method as described in any one of claims 1 to 14, or performs the method as described in any one of claims 15 to 22, or performs the method as described in claim 23, or performs the method as described in any one of claims 24 to 32, or performs the method as described in any one of claims 33 to 45, or performs the method as described in any one of claims 46 to 54, or performs the method as described in any one of claims 55 to 62, or performs the method as described in claim 63, or performs the method as described in any one of claims 64 to 72.

75. A communication system, characterized in that: It includes a first access network device, a first terminal device and a core network element; The first access network device is used to perform the method according to any one of claims 1 to 14, or the first access network device is used to perform the method according to any one of claims 33 to 45; The first terminal device is used to perform the method according to any one of claims 15 to 22, or the first terminal device is used to perform the method according to claim 23, or the first terminal device is used to perform the method according to any one of claims 55 to 62, or the first terminal device is used to perform the method according to claim 63; The core network element is used to execute the method as described in any one of claims 24 to 32, or the core network element is used to execute the method as described in any one of claims 64 to 72.

76. The communication system according to claim 75, characterized in that It also includes a second access network device, wherein the second access network device is used to execute the method as described in any one of claims 46 to 54.

77. A computer-readable storage medium, characterized in that A computer program or instructions is stored, the computer program or instructions being used to implement the method as claimed in any one of claims 1 to 72.

78. A computer program product, characterized in that The computer program product comprises a computer program which, when run on a computer, causes the computer to perform the method according to any one of claims 1 to 72.

Images