Communication method and device

Abstract

The embodiment of the invention provides a communication method and device, and the method comprises the steps that first access network equipment receives response information of first request information from a network element of a core network, the response information of the first request information is used for indicating a network to accept registration of first terminal equipment, and the first access network equipment carries out the registration of the first terminal equipment according to the response information of the first request information; sending the first paging message; the first paging message comprises first identification information of a first terminal device; the first access network equipment receives a first paging response message from the first terminal equipment, wherein the first paging response message is used for responding to the first paging message; and 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. In the registration process of the first terminal device, through the 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 is effectively registered in the network.

Description

Technical Field

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

[0002] Non-terrestrial network (NTN) communication refers to communication achieved with the help of non-terrestrial network equipment. NTN systems can include satellite systems, etc. NTN usually includes two scenarios: transparent load and regenerative load. Transparent load can regard the satellite as a relay node on the network side. The satellite changes the frequency carrier of the uplink RF signal, filters and amplifies it before downlink transmission, but the waveform of the loaded signal does not change. Regenerative load is a payload that converts and amplifies the uplink RF signal before transmission on the downlink, which is equivalent to having all or part of the base station functions on the satellite.

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

[0004] 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. Summary of the invention

[0005] The present 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.

[0006] In the first aspect, the present application implements 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, and there is no specific limitation on this. Taking the first access network device as an example, the method can specifically include: the first access network device receives a response message of a first request message from a core network network element, and the response message of 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 according to the response message of 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 of the first request message to the first terminal device according to the first paging response message.

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

[0008] In a possible implementation, the first access network device receives a response message to the first request message from the core network network element, and 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 sends a first paging message including the above-mentioned first identification information according to the response message to the first request message. This implementation can be applied to but is not limited to non-continuous power feeding scenarios. 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.

[0009] The "network" involved 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. The core network element belongs to the network.

[0010] In a possible implementation manner, the first paging message includes indication information for indicating that the first paging message is a core network CN paging message.

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

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

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

[0014] Based on the above-mentioned second embodiment, in a possible embodiment, the first identification information is allocated to the first terminal device by the core network in the authentication process of the first terminal device. Then the method also includes: in the authentication process, the first access network device sends a second paging message, and the second paging message includes the second identification information of the first terminal device.

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

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

[0017] For the above-mentioned implementation mode 1, and sub-mode 1 under implementation mode 2, in a possible implementation mode, 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 to register the first terminal device 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), the 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 the 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.

[0018] For the above-mentioned implementation method 2 that is not combined with the sub-method, and sub-method 2 in implementation method 2, in a possible implementation method, the method may also include: 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 second message is sent to the first terminal device, the second message is used to trigger the first terminal device to release the radio resource control RRC context. In the embodiment of the present application, the first access network device can carry the second message in the RRC connection release message and send it to the first terminal device.

[0019] In a possible implementation, the method further includes: the first access network device determines that the first access network device has no feeder connection according to local configuration; or the first access network device determines that the first access network device has no feeder connection according to interface connection information between the first access network device and the core network device; or determines that the first access network device has no feeder connection according to feeder connection state information of the first access network device. Through this implementation, the first access network device can effectively determine whether it has a feeder connection.

[0020] In the embodiment of the present application, the first access network device has no feeder connection, which can also be referred to as: the type of the first access network device is S&F. The first access network device has no feeder connection, which 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 the core network element, or there is no N2 or N3 connection between the first access network device and the core network element).

[0021] In a possible implementation, the method further includes: the first access network device sends 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 the response information of the first request information. This implementation can be applied but not limited to the scenario of non-continuous feeding. Through this implementation, it is possible to avoid the first terminal device from continuously sending the first request information when there is no feeding connection, thereby wasting resources.

[0022] 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 a 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.

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

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

[0025] 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 after receiving the response information of the first paging message or the first request information. Through this implementation, the first terminal device can delete the first identification information used in the current process to respond to the paging in a timely manner to prevent affecting the next response to other paging messages.

[0026] In the second aspect, the present application implements 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 first access network device, and the first request message is used to request that the first terminal device be registered to the network; then the first terminal device receives 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 first terminal device is a non-continuous feeding type, and determines not to send a service request message to the first access network device.

[0027] In the present application scheme, the first terminal device sends a first request message to the first access network device to request to register with the network; then the first terminal device receives a first paging message from the first terminal device, the first paging message includes the first identification information of the first terminal device; if the first terminal device is of a non-continuous feeding type, the service request message is not sent to the first access network device. Thus, the resource overhead generated by sending the service request message can be effectively reduced.

[0028] In a possible implementation manner, the first paging message includes indication information for indicating that the first paging message is a core network CN paging message.

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

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

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

[0032] In a 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 indicate that the network accepts the registration of the first terminal device.

[0033] This implementation can be applied in a scenario 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.

[0034] In a possible implementation, based on the above 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 according to the first information. This implementation facilitates the subsequent first access network device to page the first terminal 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.

[0035] In a possible implementation, based on the above-mentioned implementation mode 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 mode can be applied to scenarios 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 mode. 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.

[0036] In a 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.

[0037] 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 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 the identification information of the access layer; if the RRC context is released, the second identification information is the identification information of the non-access layer.

[0038] In a possible implementation, 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.

[0039] Through this implementation, the first terminal device can delete the first identification information used in the current process to respond to the paging in time to prevent affecting the next response to other paging messages.

[0040] 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, and is not specifically limited to this. 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, and the first request message is used to request that the first terminal device be registered to 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 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 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.

[0041] 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 the local configuration, thereby avoiding multiple requests to occupy resources and generate additional overhead.

[0042] In the fourth aspect, the present application implements 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 receives a first request message from a first access network device, and the first request message is used to request that the first terminal device be registered to the network; when the first terminal device is a non-continuous feeding type, the core network element sends a paging message to the first access network device according to the first request message, and the paging message is used to trigger the first access network device to page the first terminal device.

[0043] In the present application scheme, after the core network network element receives the first request information from the first access network device, if the first terminal device is of a non-continuous feeding type, 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.

[0044] In a possible implementation, the method further includes: the core network element sends a response message to the first request message to the first access network device, 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.

[0045] In a possible implementation, the method further includes: the core network element sending 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 the response information of the first request information. Through this implementation, additional overhead caused by sending the response information of the first request information can be avoided.

[0046] In a possible implementation manner, the method further includes: the core network element determines that the first terminal device is of a non-continuous feeding type. Through this implementation manner, it can be effectively determined that the first terminal device is of a non-continuous feeding type.

[0047] In the embodiment of the present application, the core network element determines that the first terminal device is of a non-continuous feeding type, which may be done by, but not limited to, the following methods:

[0048] Method 1: The core network element determines that the first terminal device is a non-continuous feeding type according to 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.

[0049] Method 2: The core network element determines that the first terminal device is of a non-continuous 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 non-continuous feeding. For example, the first access network device RAN can indicate to the core network element (mobility management entity MME / mobility management function AMF) that it supports non-continuous feeding or is of a non-continuous feeding type in an NG setup message or a radio access network configuration update (RAN configuration update) message, and the core network element MME / AMF can know that the first terminal device served by the first access network device is also of a non-continuous feeding type.

[0050] Mode 3: The core network element determines that the first terminal device is of a non-continuous feeding type 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. 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, and the indication information indicates that the tracking area TA list supported by the first access network device does not include the tracking area TA where the first terminal device is located.

[0051] In a 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, and the core network element subsequently 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.

[0052] In a possible implementation, the method further includes: a 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.

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

[0054] In a possible implementation manner, 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.

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

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

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

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

[0059] In the 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, and there is no specific limitation on this. Taking the first access network device as an example, the method can specifically include: the first access network device receives a response message of a first request message from a core network network element, and the response message of 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 according to the response message of 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 of the first request message to the first terminal device according to the first paging response message.

[0060] In a possible implementation, the first access network device receives a response message to the first request message from the core network network element, and 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 sends a first paging message including the above-mentioned first identification information according to the response message to the first request message. This implementation can be applied to but not limited to non-continuous power feeding scenarios. 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.

[0061] In a possible implementation manner, the first paging message includes indication information for indicating that the first paging message is a core network CN paging message.

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

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

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

[0065] Based on the above-mentioned second embodiment, in a possible embodiment, the first identification information is allocated to the first terminal device by the core network in the authentication process of the first terminal device. Then the method also includes: in the authentication process, the first access network device sends a second paging message, and the second paging message includes the second identification information of the first terminal device.

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

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

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

[0069] In a 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 context of RRC, wherein the RRC context includes identification information of the access layer corresponding to the first terminal device.

[0070] In a possible implementation manner, the first access network device receives the connection context of the second access network device, which may include but is not limited to the following methods:

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

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

[0073] Based on the above-mentioned method 2, in a 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 context request information to the second access network device, and the context request information is used to request the connection context of the second access network device.

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

[0075] The present application does not specifically limit the way and manner of sending the connection context of the second access network device to the first access network device.

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

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

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

[0079] 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 after receiving the response information of the first paging message or the first request information. Through this implementation, the first terminal device can delete the first identification information used in the current process to respond to the paging in a timely manner to prevent affecting the next response to other paging messages.

[0080] In the sixth aspect, the present application implements 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 a non-continuous feeding type, and the method can specifically include: the second access network device receives a first request message from a first terminal device, and the first request message is used to request that the first terminal device be registered to the network; sends the first request message to a core network network element, and sends the connection context of the second access network device.

[0081] In the present application scheme, after the second access network device receives the first request information from the first terminal device, when the second access network device sends the first request information to the core network network element, the connection context of the second access network device also occurs, 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.

[0082] In a 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, the first information is used to trigger the first terminal device to release or retain the 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.

[0083] 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 paging the first terminal device using the identification information of the access layer; if the first terminal device is paging using the identification information of the non-access layer, the first terminal device is instructed to release the RRC context, which can save the resources and overhead occupied by the RRC context.

[0084] In a possible implementation manner, the second access network device sends the connection context of the second access network device, which may include but is not limited to the following methods:

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

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

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

[0088] 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 of the second access network device; and then sends the connection context to the first access network device based on the context request information.

[0089] Based on the above-mentioned method 2, in another possible implementation manner, the second access network device first receives the 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.

[0090] In a 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 a 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.

[0091] In a possible implementation manner, the second access network device having no feeder connection may 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).

[0092] In a possible implementation, the method further includes: 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 not to send the first request message within a preset time or before receiving a response message to the first request message. This implementation can be applied but not limited to a scenario where power feeding is not continuous. Through this implementation, it is possible to avoid the first terminal device from continuously sending the first request message when there is no power feeding connection, thereby wasting resources.

[0093] In the seventh aspect, the present application implements 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, and the first request message is used to request that the first terminal device be registered to the network; the first terminal device receives 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; 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, it is determined not to send a service request message to the first access network device.

[0094] In the present application scheme, the first terminal device sends a first request message to the second access network device to request to register with the network; the first terminal device receives a first paging message from the first terminal device, and the first paging message includes the first identification information of the first terminal device; if the first terminal device is of a non-continuous feeding type, the service request message is not sent to the first access network device. Thus, the resource overhead generated by sending the service request message can be effectively reduced.

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

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

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

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

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

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

[0101] In another possible implementation, based on the above implementation 2, the method further includes: the first terminal device receives second information, 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 can be applied to 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.

[0102] In a 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. After the RRC connection is restored, the first terminal device receives response information to the first request information 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 the registration of the first terminal device.

[0103] 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 wireless 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.

[0104] The above implementation can be applied in a scenario 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 an RRC connection, and then effectively receive response information to the first request information from the first access network device through the RRC connection.

[0105] In a 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.

[0106] 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 determines 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.

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

[0108] In a possible implementation, the method further includes: the first terminal device receives third indication information from the first access network device, the third indication information is used to trigger the first terminal device to delete the first identification information after receiving the response information of the first paging message or the first request information; and then the first terminal device deletes the first identification information according to the third indication information. Through this implementation, the first terminal device promptly deletes the first identification information used in the current process to respond to the paging, so as to prevent affecting the next response to other paging messages.

[0109] 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, and is not specifically limited to this. 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, and the first request message is used to request that the first terminal device be registered to 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 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 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.

[0110] 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 the local configuration, thereby avoiding multiple requests to occupy resources and generate additional overhead.

[0111] In the ninth aspect, the present application implements 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 receives a first request message from a second access network device, and the first request message is used to request that the first terminal device be registered to the network; when the first terminal device is a non-continuous feeding type, the core network element sends a paging message to the first access network device according to the first request message, and the paging message is used to trigger the first access network device to page the first terminal device.

[0112] In the present application scheme, after the core network network element receives the first request information from the first access network device, if the first terminal device is of a non-continuous feeding type, 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.

[0113] In a possible implementation, the method further includes: the core network element sending a response message to the first request message to the first access network device, the response message to the first request message being 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.

[0114] In a possible implementation, the method further includes: the core network element sending 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 the response information of the first request information. Through this implementation, additional overhead caused by sending the response information of the first request information can be avoided.

[0115] In a possible implementation manner, the method further includes: the core network element determines that the first terminal device is of a non-continuous feeding type. Through this implementation manner, it can be effectively determined that the first terminal device is of a non-continuous feeding type.

[0116] In the embodiment of the present application, the core network element determines that the first terminal device is of a non-continuous feeding type, which may be done in the following ways but not limited to:

[0117] Method 1: The core network element determines that the first terminal device is a non-continuous feeding type according to 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.

[0118] Method 2: The core network element determines that the first terminal device is of a non-continuous 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 non-continuous 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 (RAN configuration update) message that it supports non-continuous feeding or is of a non-continuous feeding type, and then the core network element MME / AMF can know that the first terminal device served by the second access network device is also of a non-continuous feeding type.

[0119] Method 3: Determine that the first terminal device is of a non-continuous feeding type according to 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, and the indication information indicates that the tracking area TA list supported by the second access network device does not include the tracking area TA where the first terminal device is located.

[0120] In a possible implementation, the method further includes: the core network element receives 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 through the second access network device, and the core network element subsequently 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.

[0121] In a possible implementation, the method further includes: the core network element assigning first identification information of the first terminal device; the core network element sending the first identification information to the first access network device, and the first identification information is used by the first access network device to page the first terminal device. 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 to effectively page the first terminal device later.

[0122] In a possible implementation, the first identification information is allocated to the first terminal device by the core network in the authentication process of the first terminal device. Through this implementation, the first terminal device can effectively obtain the first identification information so that it can respond normally to the first paging message of the first access network device later.

[0123] In a possible implementation, the method further includes: a core network element sending 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 an authentication process of the first terminal device.

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

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

[0126] 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 hardware circuit combined with 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 implementation of the first aspect, or the processing unit may be used to perform the method described in the fifth aspect or any possible implementation of the fifth aspect.

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

[0128] In a 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 hardware circuit combined with software. In a 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 implementation of the second aspect, or the processing unit may be used to perform the method described in the third aspect or any possible implementation of the third aspect, or the processing unit may be used to perform the method described in the seventh aspect or any possible implementation of the seventh aspect, or the processing unit may be used to perform the method described in the eighth aspect or any possible implementation of the eighth aspect.

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

[0130] 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 hardware circuit combined with 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 implementation of the fourth aspect, or the processing unit may be used to perform the method described in the ninth aspect or any possible implementation of the ninth aspect.

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

[0132] In one possible implementation, the device may include a module or unit corresponding to the method / operation / step / action 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.

[0133] In the fourteenth aspect, an apparatus is provided in an embodiment of the present application, comprising: at least one processor and a communication interface; wherein the communication interface is used to communicate with other apparatuses; the processor is used to run a set of programs so that the apparatus implements the method provided in the first aspect or any possible implementation manner thereof, or implements the method provided in the second aspect or any possible implementation manner thereof, or implements the method provided in the third aspect or any possible implementation manner thereof, or implements the method provided in the fourth aspect or any possible implementation manner thereof, or implements the method provided in the fifth aspect or any possible implementation manner thereof, or implements the method provided in the sixth aspect or any possible implementation manner thereof, or implements the method provided in the seventh aspect or any possible implementation manner thereof, or implements the method provided in the eighth aspect or any possible implementation manner thereof, or implements the method provided in the ninth aspect or any possible implementation manner thereof.

[0134] In a fifteenth aspect, an embodiment of the present application further provides a computer storage medium storing a software program, which, when read and executed by one or more processors, 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.

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

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

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

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

[0139] In a possible design, the chip system further includes a memory, which is used to store necessary program instructions and data executed by the loading device. The chip system can be composed of chips or include chips and other discrete devices.

[0140] 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 referred 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

[0141] Figure 1A It is a schematic diagram of the structure of a transparent payload NTN;

[0142] Figure 1B is a structural schematic diagram of a regenerative load;

[0143] Figure 1C A schematic diagram of data storage and forwarding in a discontinuous feeding scenario of a regenerative load;

[0144] Figure 2A A schematic diagram of a 5G initial access process;

[0145] Figure 2B A schematic diagram of a 4G attach process;

[0146] Figure 2C A schematic diagram of a 5G initial registration process;

[0147] Figure 3A A communication system to which the method of an embodiment of the present application can be adapted;

[0148] Figure 3B Another communication system to which the method of the embodiment of the present application can be adapted;

[0149] Figure 3C A schematic diagram of a network structure to which the method of an embodiment of the present application can be adapted;

[0150] Figure 4A A flow chart of a communication method provided in an embodiment of the present application;

[0151] Figure 4B A flowchart of another communication method provided in an embodiment of the present application;

[0152] Figure 5A A flow chart of another communication method is provided for an embodiment of the present application;

[0153] Figure 5B A flowchart of another communication method provided in an embodiment of the present application;

[0154] Figure 6 A flowchart of the first implementation method provided in the embodiment of the present application;

[0155] Figure 7 A flowchart of a second implementation method provided in an embodiment of the present application;

[0156] Figure 8 A flowchart of a third implementation method provided in the embodiment of the present application;

[0157] Fig. 9 A flowchart of a fourth implementation method provided in an embodiment of the present application;

[0158] Fig.10 A flowchart of a fifth implementation method provided in the embodiment of the present application;

[0159] Fig.11 A flowchart of a sixth implementation method provided in an embodiment of the present application;

[0160] Fig.12 A schematic diagram of a communication device provided in an embodiment of the present application;

[0161] Fig.13 A schematic diagram of another communication device provided in an embodiment of the present application;

[0162] Fig.14 A schematic diagram of another chip device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0163] 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 used as limitations on the present application. As used in the specification and the appended claims of the present application, the singular expressions "one", "a kind", "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 the associated objects, indicating that three relationships may exist; for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0164] References to "one embodiment" or "some embodiments" 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. Thus, the statements "in one embodiment", "in some embodiments", "in other embodiments", etc. that appear in different places in this specification are not necessarily all referenced to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "include", "comprise", "have" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways. Words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations, 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 design. The use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way for easy understanding. In addition, in the accompanying drawings of the embodiments of the present application, the steps in the dotted or dotted boxes are optional steps.

[0165] 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 to indicate" 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 that a certain indication information is 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.

[0166] The present application provides a communication method. In order to better understand the embodiments of the present application, the names and related technical features involved in the embodiments of the present application are explained below. It should be noted that these explanations are intended to make the embodiments of the present application easier to understand and should not be regarded as limiting the scope of protection claimed by the present application.

[0167] 1. Satellite architecture:

[0168] 3GPP is committed to combining 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).

[0169] NTN includes two scenarios: transparent forwarding and regenerative forwarding. Figure 1AAs shown in the figure, the transparent payload NTN can regard the satellite as a relay node on the network side. The satellite changes the frequency carrier of the uplink RF signal, filters and amplifies it before downlink transmission, but the waveform of the loaded signal does not change. Figure 1B As shown, the regenerative payload is a payload that converts and amplifies the uplink RF signal before transmission on the downlink, including demodulation / decoding, encoding / modulation, etc., which is equivalent to having all or part of the base station functions on the satellite.

[0170] Figure 1A and Figure 1B In the context of the LTE, service link refers to the wireless connection between the NTN load and the terminal UE, or the connection between the satellite and the terminal UE. For example, in the regenerative load scenario, if there is no service link, there will be no connection between the access network RAN ​​and the terminal UE. Feeder connection refers to the wireless connection between the NTN gateway and the NTN load, 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 through a third-party connection (such as intersatellite links between other satellites, connections between other satellites and gateways). For example, in the regenerative load scenario, if there is no feeder connection, there will be no connection between the RAN and the core network.

[0171] In this application, the essence of whether there is a service connection or not refers to whether there is a connection between the UE and the RAN, and the essence of whether there is a feeder connection or not refers to whether there is 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", etc., and "feeder connection" can be replaced by "ground link", etc.

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

[0173] 2. Scenarios where power feeding is discontinuous:

[0174] 3GPP R19 discusses the scenario of discontinuous feeding based on regenerative load, also known as the store and forward (S&F) scenario. Figure 1C As shown, 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 (available), that is, the access connection and the feed connection will be disconnected within 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 uplink data of the UE 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 the sake of 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 can be applied to other non-continuous feeding scenarios.

[0175] 3. Initial access process:

[0176] Take the 5G initial UE access process as an example, see Figure 2A As shown, it may 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.

[0177] When a UE accesses the network, it must first perform S201A (cell search and selection) and S202A (random access). The purpose of these two steps is to allow the UE to negotiate physical layer uplink and downlink synchronization information with the access network equipment RAN (such as gNodeB) and determine a UE identifier used between the UE and RAN. After these two steps are completed, the UE and RAN can send signaling to each other without being confused with signaling sent by other UEs.

[0178] After completing the random access in S202A, the UE establishes an RRC connection with the RAN, that is, a communication signaling radio bearer (SRB) is established between the RAN and the UE. The SRB is used for signaling transmission and can be divided into the following types according to the different bearer signaling:

[0179] 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 exists after the first two steps are completed)

[0180] 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 a copy of the 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)

[0181] 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 subscription concealed identifier (SUCI), the globally unique temporary identity (GUTI), etc.

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

[0183] Exemplarily, the initial access process takes the 4G attach process as an example, and the UE sends an initial access request ( Figure 2BS201B), including the globally unique temporary identifier GUTI, 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 the process of obtaining the UE's subscription and policy, authenticating the UE and other processes according to the UE's request, and then replies to the UE through the access network device. Initial access acceptance message ( 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 the message and performs actions such as bearer configuration, the initial access process is completed.

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

[0185] S201B: The UE sends an attach request message to the RAN, where the message includes IMSI or GUTI, Attach Type, and ESM message container.

[0186] S202B: RAN forwards the attach request message to the mobility management entity (MME), which includes Selected Network, TAI+ECGI

[0187] S203B: The MME sends an Identity Request to the UE; if the MME does not recognize the globally unique temporary identifier GUTI provided by the UE, it will instruct the UE to provide an international mobile subscriber identity (IMSI).

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

[0189] S205B: The UE executes the authentication process.

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

[0191] S207B: The MME sends a downlink non-access layer transport attach accept message (Donwnlink NAS transport with attach accept) to the RAN, which includes: GUTI, target tracking area identity (tracking area identity, TAI) List, and session management request Session Management Request.

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

[0193] Figure 2B Only some general steps in the 4G attach process are illustrated. The detailed steps of the process can refer to the existing 4G attach process, which will not be listed here one by one.

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

[0195] 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 mobilesubscriber identity, S-TMSI), selected public land mobile network identity (selected-public landmobile network-identity, Selected PLMN ID), network slice selection assistance information (network slice selection assistance information, NSSAI), and a registration request container.

[0196] S202C: RAN sends a registration request Registration Request message to AMF, which may also be referred to as an N2 message.

[0197] The message includes the selected PLMN ID, UE location information and cell identity, and a registration request container.

[0198] S203C: If the AMF does not recognize the GUTI provided by the UE, the AMF sends an identity request message to the UE to instruct the UE to provide a hidden user identifier SUCI. S203C is an optional step.

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

[0200] S205C: The UE executes the authentication process.

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

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

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

[0204] Figure 2C Only some general steps / processes in the 5G registration process are illustrated. The detailed steps of the process can refer to the existing 5G registration process and will not be listed here one by one.

[0205] 4. UE connection status:

[0206] The establishment of a connection between the UE and the access network equipment is mainly divided into three steps: cell search, physical access, and signaling process establishment. Among them, the first step of the signaling process establishment includes the establishment of the 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. When the initial access process is completed, the connection between the UE and the core network is established.

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

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

[0209] When the UE is in idle state: a. Uu interface between the UE and gNB: There is no RRC connection. At the same time, there is no RRC context information of the UE on the gNB, and there is no RRC context on the UE. However, the UE will retain the context between the core network (such as GUTI). c. The UE in idle state will listen to the paging message to find out whether there is any called service. Once it receives its own paging message, it will restore the RRC connection of the Uu interface and re-access the network (initiate the service request process). The paging message includes the identifier used between the UE and the core network to identify the UE (such as GUTI, IMSI).

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

[0211] a. Uu interface between UE and gNB: There is no RRC connection, but the UE context information is stored on the gNB, and the UE also stores the RRC context information (such as RNTI). c. Compared with idle UE, when inactive UE re-enters the connected state, it only needs to restore the RRC connection of the Uu interface, and the recovery delay is short. Inactive UE will monitor RAN paging. This paging message includes the identifier used between UE and RAN (such as RNTI). After receiving RAN paging, the inactive UE will re-enter the connected state.

[0212] In 4G, the UE connection states are only idle and connected, but there is also a special state in the idle state, namely CM-IDLE with suspend. This state is similar to the RRC inactive part, and the UE can also be paged using the identity used between the UE and the RAN.

[0213] 4. Paging:

[0214] Core network (CN) paging: triggered by the mobility management function AMF (5G) / MME (4G), sends a paging message to the RAN. Based on the paging message sent by the AMF / MME, the RAN sends a paging message to the UE (the paging messages sent by the RAN and AMF / MME are not exactly the same). The paging message sent by the RAN to the UE also includes the UE identifier used between the core network and the UE. After receiving the paging message sent by the RAN, the UE first establishes an RRC connection with the RAN, and then initiates a service request process to restore the connection with the core network.

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

[0216] In the S&F scenario of regenerative payload feeding discontinuity, during the operation of a regenerative payload satellite, the access connection and the feeding connection are not always available, that is, the access connection and the feeding connection will be disconnected for a period of time. When the terminal device initiates the initial access process, if the feeding 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 be unable to complete the initial access process normally. 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.

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

[0218] The communication method provided in the embodiment of the present application can be applied to the NTN communication system, which can include the use of non-ground network devices such as drones, high altitude platform stations (HAPS), satellites, etc. to form a network and provide data transmission, voice communication and other services for terminal devices. In addition, the NTN system can also include other non-ground network devices, which are not limited in the present application.

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

[0220] In NTN communication, the working modes of NTN equipment may include: transparent mode and regenerative mode. According to the working mode of NTN equipment, the architecture of NTN communication can be divided into the following two categories: one is the transparent forwarding architecture, in which the NTN equipment can be a relay or amplifier, and can perform radio frequency filtering, amplification, etc., to regenerate the physical layer signal. The NTN equipment can be responsible for layer 1 (layer1, L1) relay, which is used for physical layer forwarding, and the upper layer is invisible. The second is the regenerative architecture, in which the NTN equipment has the processing function of the access network equipment. Exemplarily, in the regenerative working mode, the satellite can be divided into a regenerative satellite without an inter-satellite link, that is, there is no inter-satellite link (ISL) between satellites; or a regenerative satellite with an inter-satellite link, that is, there is an interface between satellites to directly exchange data, where the inter-satellite link is an Xn port; or a regenerative satellite with a distributed unit (DU) processing function of an access network device, in which the satellite acts as a DU.

[0221] For example, Figure 3A A schematic diagram of an NTN communication architecture applicable to the embodiment of the present application is shown, and the NTN scenario can be a transparent forwarding communication architecture. Figure 3A In the communication architecture shown, the 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 the terminal device and the access network device or as remote radio units (RRUs) of the access network device.

[0222] For example, Figure 3B Another NTN communication architecture schematic diagram applicable to the embodiment of the present application is shown, and the NTN communication architecture can be a regenerative communication architecture. Figure 3B In the communication architecture shown, the satellite can be used as an access network device to form an access network with the NTN gateway and communicate with the core network through the NTN gateway. In addition, the satellite can also provide wireless access services for terminal devices. Figure 3B A regenerative satellite architecture without intersatellite links is illustrated.

[0223] It should be noted that Figure 3A and Figure 3BOnly one satellite and one NTN gateway are shown. In actual use, a plurality of satellites and / or a plurality of NTN gateways may be used as required. 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, which is not specifically limited in the embodiments of the present application.

[0224] It should be noted that Figure 3A and Figure 3B This is only an example of the NTN communication architecture, and the NTN communication architecture may also include other specific devices, which are not limited in this application. Based on the NTN communication architecture, the embodiment of this application may be applicable but not limited to the scenario of non-continuous feeding (also known as store and forward (S&F)).

[0225] The devices involved in the embodiments of the present application include terminal devices, access network devices and core network devices. Among them:

[0226] Terminal equipment, also known as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., refers to equipment that provides voice and / or data connectivity to users. For example, the terminal equipment may be a handheld device, a vehicle-mounted device, etc. with a wireless connection function. At present, some examples of terminal equipment may be: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.

[0227] The access network device may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network, such as a base station. Some examples of RAN nodes may include: a gNB, a transmission reception point (TRP), an evolved NodeB (eNB), a radio network controller (RNC), a NodeB (NB), a base station controller (BSC), a base transceiver station (BTS), a home evolved NodeB (e.g., home NodeB, or home NodeB, HNB), a base band unit (BBU), or a wireless fidelity (Wifi) access point (AP).

[0228] In addition, in a network structure, the access network device may include a centralized unit (CU) node, a distributed unit (DU) node, or a CU node and a DU node. The RAN device including the CU node and the DU node splits the protocol layer of the gNB in ​​the NR system, places the functions of some protocol layers in the CU for centralized control, and distributes the functions of the remaining part or all of the protocol layers in the DU, which is centrally controlled by the CU, such as Figure 3CAs shown. Furthermore, CU can also be divided into control plane (CU-CP) and user plane (CU-UP). CU-CP is responsible for control plane functions, mainly including radio resource control (RRC) and packet data convergence protocol (PDCP) (i.e. PDCP-C) corresponding to the control plane. PDCP-C is mainly responsible for encryption and decryption, integrity protection, data transmission, etc. of control plane data. CU-UP is responsible for user plane functions, mainly including service data adaptation protocol (SDAP) and PDCP corresponding to the user plane (i.e. PDCP-U). SDAP is mainly responsible for processing the data of the core network and mapping the flow to the bearer. PDCP-U is mainly responsible for encryption and decryption, integrity protection, header compression, sequence number maintenance, data transmission, etc. of the data plane. CU-CP and CU-UP are connected through the E1 interface. CU-CP represents that gNB is connected to the core network through the NG interface, and is connected to DU through the F1 interface control plane (i.e. F1-C). CU-UP is connected to DU via F1 interface user plane (i.e. F1-U). Of course, another possible implementation is that PDCP-C is also in CU-UP.

[0229] It can be understood 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 takes CU, CU-CP, CU-UP and DU as examples for description.

[0230] 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, an AMF entity can also be referred to as an AMF network element or an AMF functional entity. For another example, an 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.

[0231] 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 including the network device function. The control subsystem including the network device function 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 including the terminal device function.

[0232] 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. A person of ordinary skill in the art can appreciate that with the evolution of the 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.

[0233] In this application, the names of the messages in the following processes are only used as examples. With the evolution of communication technology, the names of the information / messages in the following processes may change. However, no matter how the names change, as long as their meanings are the same as the functions or meanings of the messages in this application, they all fall within the protection scope of this application. For example, the first request information in this application can also be replaced by messages such as an attachment request message or a registration request message.

[0234] The technical solution of the present application is introduced below in conjunction with specific embodiments.

[0235] The present invention provides a communication method which is applicable to but not limited to Figure 3A-3B The communication system shown is applicable but not limited to scenarios with discontinuous power feeding (also known as store-and-forward S&F scenarios). 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 specifically limit 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 for explanation. The order of steps in the following processes is only an example. In actual applications, the execution order of the steps in each process can be adjusted.

[0236] See also Figure 4A As shown, the specific process of this method is as follows:

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

[0238] The first request information may be used to request that the first terminal device be registered to the network.

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

[0240] In the embodiment 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 scenarios in which the embodiment scheme is applied, the name corresponding to the initial access request message may be different, which is not limited. Exemplarily, the initial access request message may be an attach request or a registration request.

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

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

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

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

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

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

[0247] In an optional implementation, when the first terminal device is of a non-continuous 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.

[0248] 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 a 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 (stored and forwarded) by an access network device; or a terminal device that can support use in a discontinuous feeding scenario (i.e., a scenario in which the service connection and the feeding connection are not available at the same time at any time).

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

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

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

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

[0253] Mode b: The core network element determines that the first terminal device is of a discontinuous power feeding type according to 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.

[0254] 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, and then the MME / AMF can know that the first terminal device served by the first access network device is also of the discontinuous feeding type.

[0255] Method c: The core network element determines that the first terminal device is a non-continuous feeding type according to the tracking area TA information supported by the first access network device and the TA where the first terminal device is located.

[0256] For example, the core network element receives the 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; wherein 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 a non-continuous feeding type.

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

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

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

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

[0261] In S404A, the service area of ​​the first access network device at this time does not cover the position 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.

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

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

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

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

[0266] It should be pointed out that the sending of the first paging message according to the response information of the first request information in S405A can be understood as 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.

[0267] 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 (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 information to the first request information to the first terminal. Exemplarily, the first access network device sends a first paging message when the service range covers the location of the first terminal device when the first request information is received, 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 information of the first request information is sent to the first terminal device.

[0268] In a possible implementation, before the first access network device sends the first paging message, it may also include: the core 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 according to 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, 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.

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

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

[0271] In this implementation, 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.

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

[0273] For example, the first identification information may be a cell radio network temporary identifier (C-RNTI), an inactive RNTI (I-RNTI), or a combination of any one of the above and a RAN ID, and 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 cellglobal 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.

[0274] 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 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 to this.

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

[0276] In this implementation, 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.

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

[0278] For example, the first identification information may be any one of the international mobile user identity IMSI, temporary mobile user identity TMSI, 5G-S-TMSI, P-TMSI, all or part of the global unique temporary identifier GUTI, and SUCI. It may also be a new identifier, which is used to identify the UE in the UE initial access process of the S&F scenario.

[0279] 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, and the first identification information may be a part of the first request information, or may be 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, and the first identification information may be a part of the response information to the first request information, or may be 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.

[0280] In a possible implementation, the first identification information is allocated to the first terminal device by the core network element in the authentication process of the first terminal device. Then the method may also include: the core 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 in the authentication process of the first terminal device; accordingly, after the first access network device receives the second identification information, in the authentication process, the first access network device sends a second paging message, and the second paging message includes the second identification information of the first terminal device. Accordingly, the first terminal device receives the second paging message.

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

[0282] In the process of authentication and verification, the second identification information used by the first access network device for paging may include the following implementation methods:

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

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

[0285] For the above-mentioned implementation mode 1, and sub-method 1 under implementation mode 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) from 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 may carry the first information in an RRC connection release message and send it to the first terminal device.

[0286] 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 may carry the second information in an RRC connection release message and send it to the first terminal device.

[0287] In a possible implementation, 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 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 according to the first indication message; or; 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 according to local configuration. In an embodiment of the present application, the first indication message may include a preset time period, or may be only one indication message.

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

[0289] Method 1: determining, according to local configuration, that the first access network device has no feeder connection;

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

[0291] Method 2: Determine that the first access network device has no feeder connection according to the interface connection information between the first access network device and the core network device;

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

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

[0294] In the embodiment of the present application, the first access network device has no feeder connection, and the type of the first access network device can also be referred to as S&F. The first access network device has no feeder connection, which 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 transmission 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, the access network device of the non-continuous feeding type (or S&F type) may refer to: an access network device where the feeder connection is not always available; or an access network device where the connection with the core network element is not always available; or an access network device where the ground link is not always available.

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

[0296] In a possible implementation, after the first terminal device receives the first paging message, the method further includes: if the first terminal device is of a non-continuous feeding type, the first terminal device determines not to send a service request message to the first access network device. Alternatively, if the first terminal device is of a non-continuous feeding type and the first paging message includes the non-access layer NAS identification information of the first terminal device, the first terminal device determines not to send a service request message to the first access network device.

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

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

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

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

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

[0302] Correspondingly, the first terminal device receives response information of the first request information.

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

[0304] In an embodiment of the present application, the response information of 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 of the first request information received from the core network element corresponds to the first terminal device based on the stored first identification information and the corresponding terminal identification used between the RAN and the core network element (MME / AMF), such as the RAN UE next generation access point (NGAP) ID.

[0305] In a possible implementation, the method further includes: the first access network device sends 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.

[0306] The present application embodiment also provides another communication method, which is also applicable to but not limited to Figure 3A-3B The communication system shown is applicable to but not limited to the scenario of discontinuous power feeding (S&F scenario). The method can be executed by the first terminal device, the first access network device, and the core 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 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; this application does not specifically limit the specific structure of the aforementioned execution entities and the number of each execution entity. Please refer to Figure 4B As shown, the first terminal device in the method is of a non-continuous feeding type, and the specific process includes the following:

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

[0308] The first request information may be used to request that the first terminal device be registered to the network.

[0309] In a possible implementation, the method further includes: the first terminal device receives second information from the first access network device, 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 according to the second information.

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

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

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

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

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

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

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

[0317] There is no specific limitation on the execution order of S403B and S404B.

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

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

[0320] In a possible implementation, the first identification information is identification information of a 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.

[0321] In a possible implementation, the first identification information may be allocated to the first terminal device by the core network in the authentication process of the first terminal device. Then the method may also include: in the authentication process, the first access network device receives a second paging message, and the second paging message includes the second identification information of the first terminal device. The second identification information may be the identification information of the non-access layer.

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

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

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

[0325] In a possible implementation, the method may further include: the first terminal device sends a first paging response message to the first access network device, 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. Further, 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, 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.

[0326] In a possible implementation, 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; and then the first terminal device deletes the first identification information according to the third indication information.

[0327] Compared with the above Figure 4A-4B The method described, the embodiment of the present application also provides a communication method, the application scenario of the method is different, that is, the first terminal device can realize the process of registering the first terminal device to the network in the scenario of 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 specifically limit 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 can 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 network element. The order of steps in the following processes is only an example. In actual applications, the execution order of the steps in each process can be adjusted.

[0328] See also Figure 5A As shown, the specific process of this method is as follows:

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

[0330] The first request information may be used to request that the first terminal device be registered to the network.

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

[0332] In the embodiment 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 scenarios in which the embodiment scheme is applied, the name corresponding to the initial access request message may be different, which is not limited. Exemplarily, the initial access request message may be an attach request or a registration request.

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

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

[0335] In a non-continuous feeding (S&F) scenario, when the second access network device determines that there is a feeding connection, S502A is executed.

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

[0337] In a 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 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 within the preset time or before receiving the response message of the first request message according to the first indication message; or; the first terminal device may stop sending the first request message within the preset time or before receiving the response message of the first request message according to the local configuration.

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

[0339] Method 1: According to local configuration, it is determined that the second access network device has no feeder connection.

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

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

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

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

[0344] In the embodiment of the present application, the second access network device has no feeder connection, which can also be referred to as: the type of the second access network device is S&F. The second access network device has no feeder connection, which 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).

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

[0346] 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 MME / AMF (e.g., RAN UE NGAP ID, AMFUE NGAP ID), and the access layer security context of the first terminal device.

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

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

[0349] This S504A is an optional step.

[0350] Exemplarily, the core network 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 sending the first request information faster than the service range of the second access network device, and the core network network element can 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, when any access network device covers the first terminal device, it can serve the first terminal device without configuring ephemeris information, and the time the first terminal device waits for the response information of the first request information can be shortened.

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

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

[0353] In a possible implementation, when the first terminal device is a non-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.

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

[0355] In the embodiment of the present application, the core network element determines that the first terminal device is of a non-continuous feeding type, which may be done in the following ways but not limited to:

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

[0357] Mode b: The core network element can determine that the first terminal device is of the non-continuous 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 non-continuous feeding. For example, the second access network device RAN can indicate to the core network element MME / AMF in the NG setup message or RAN configuration update message that it supports non-continuous feeding or is of the non-continuous feeding type, and then MME / AMF can know that the first terminal device served by the second access network device is also of the non-continuous feeding type.

[0358] Method c: The core network element determines that the first terminal device is a non-continuous feeding type according to the tracking area TA information supported by the second access network device and the TA where the first terminal device is located.

[0359] For example, the core network element receives the 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; wherein 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 a non-continuous feeding type.

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

[0361] The connection context of the second access network device may include an RRC context and the like.

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

[0363] 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; and then the second access network device sends the connection context of the second access network device to the first access network device according to the identification information / indication information of the first access network device. Or 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; the first access network device sends context request information to the second access network device according to the identification information or indication information of the second access network device to request to obtain the connection context of the second access network device; and then the second access network device sends the connection context of the second access network device to the first access network device according to the context request information. In addition, the second access network device can also send the connection context to the first access network device in other ways, which is not specifically limited in the present application, that is, the above S503A and S506A are optional steps.

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

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

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

[0367] 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 a core network element.

[0368] In S507A, the service area of ​​the first access network device at this time does not cover the position 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.

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

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

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

[0372] 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 position of the first terminal device when the first request information is received, so the first terminal device receives the first paging message.

[0373] 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, it also 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 it receives the first request information, a 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 information of the first request information is sent to the first terminal device.

[0374] In a possible implementation, before the first access network device sends the first paging message, it may also include: the core 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 according to the second indication message and the response message of the first request message. 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.

[0375] In an embodiment of the present application, the first access network device receives a connection context of the second access network device including an RRC context (including identification information of the access layer), and the first identification information of the first terminal device included in the first paging message. In the embodiment of the present application, including but not limited to the following possible implementation methods, refer to the above Figure 4A Several implementation modes in S405A (such as implementation mode 1 and implementation mode 2) 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, and the identification information of the non-access layer can be allocated by the core network network element, or it can be 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 paging the first terminal device in implementation mode 2 in the above S405A can also be referred to, which will not be described in detail here.

[0376] In a possible implementation, the first identification information is allocated to the first terminal device by the core network in 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 in the authentication and authorization process of the first terminal device. Accordingly, after the first access network device receives the second identification information, it sends a second paging message in 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.

[0377] 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 a 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.

[0378] In S508A, in the process of authentication and verification, 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.

[0379] 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, instead of 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 the first information to the first terminal device, and the first information is used to trigger the first terminal device to release the radio resource control RRC context. Correspondingly, after receiving the first information, the first terminal device releases the RRC context according to the first information.

[0380] In this step S508A, if the first access network device uses the identification information of the access layer 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 the first information to the first terminal device, and the first information is used to trigger the first terminal device to retain the radio resource control RRC context. Correspondingly, after receiving the first information, the first terminal device retains the RRC context according to the first information.

[0381] 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, RANID, or I-RNTI+RAN ID, or C-RANTI+RAN ID, etc.

[0382] In a possible implementation, after the first terminal device receives the first paging message, the method further includes: if the first terminal device is of a non-continuous feeding type, the first terminal device determines not to send a service request message to the first access network device. Alternatively, if the first terminal device is of a non-continuous feeding type and the first paging message includes the non-access layer NAS identification information of the first terminal device, the first terminal device determines not to send a service request message to the first access network device.

[0383] 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

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

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

[0386] The specific implementation of S509A may refer to the specific implementation of S406A mentioned above.

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

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

[0389] Correspondingly, the first terminal device receives response information of the first request information.

[0390] In a 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 of the first request information to the first terminal device through the RRC connection. Correspondingly, the first terminal device also receives the response information of the first request information from the first access network device through the RRC connection.

[0391] In a possible implementation, the method further 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 first paging message or the response information of the first request information.

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

[0393] exist Figure 5AIn the above solution, the content of the first access network device side can refer to the above Figure 4A The contents of the first access network device side in the solution will not be repeated here.

[0394] The present application embodiment also provides another communication method, which is also applicable to but not limited to Figure 3A-3B The communication system shown is applicable to but not limited to the scenario of discontinuous power feeding (S&F scenario). The method can be executed by the first terminal device, the first access network device, and the core 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 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; this application does not specifically limit the specific structure of the aforementioned execution entities and the number of each execution entity. Please refer to Figure 5B As shown, the first terminal device in the method is of a non-continuous feeding type, and the specific process includes the following:

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

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

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

[0398] In a non-continuous feeding (S&F) scenario, if the second access network device determines that there is a feeding connection, S502B is executed.

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

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

[0401] 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 MME / AMF (e.g., RAN UE NGAP ID, AMFUE NGAP ID), and the access layer security context of the first terminal device.

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

[0403] S504B is an optional step.

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

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

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

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

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

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

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

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

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

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

[0414] In a possible implementation, the method may further include: the first terminal device sends a first paging response message to the first access network device, 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.

[0415] In a possible implementation, 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.

[0416] The specific implementation involved in S507B may refer to the specific implementation involved in S509A-S510A above, and will not be described in detail here.

[0417] 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 a 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.

[0418] Based on the above Figure 4A-4B and Figure 5A-Figure 5B The communication method shown is further described in detail below through several specific implementation methods.

[0419] Implementation method 1:

[0420] Based on the above Figure 4A-4B In the implementation mode 1, in the S&F scenario, the radio access network device RAN uses the RRC layer identification ID (equivalent to the above-mentioned Figure 4A or Figure 4B The first identification information of the first terminal device in the solution) pages UE1. Figure 6 As shown, the specific process is as follows:

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

[0422] The RAN instructs UE1 to enter the suspended state by instructing UE1 to save the RRC context, or instructing UE1 to release the RRC connection and save the RRC context, or instructing UE1 to enter the CM-IDLE with suspend / RRC-inactive state, or the RAN sends indication information to UE1 to instruct UE1 to enter the CM-IDLE with suspend / RRC-inactive state.

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

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

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

[0426] 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 an RRC layer or a NAS layer), for example, step S603.

[0427] The above S600a and S600b are parallel optional implementation schemes. The embodiment of the present application can adopt any one of the schemes, or combine the two schemes, to enable UE1 to enter the suspend state, and no specific limitation is made to this.

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

[0429] Since the scenarios in which the embodiments are applied are different, the initial access request message (equivalent to the above Figure 4A or Figure 4B The name corresponding to the first request information in the scheme may be different, and there is no limitation on this.

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

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

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

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

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

[0435] 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).

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

[0437] Correspondingly, the UE1 receives the RRC connection release request (RRC connection release request) message.

[0438] If RAN determines that there is no feeder connection, the RRC can instruct UE1 to retain the RRC context, and RAN also retains the RRC context of the UE. The essential purpose is that both RAN and UE1 retain an ID of the RRC layer, such as C-RNTI. For example, an indication information is included in the RRCconnection release request message to indicate that the RRC context is retained.

[0439] At this time, UE1 has not completed initial access, and there is no RRC-INACTIVE / CM-IDLE with suspend state. Therefore, the indication information of RAN is to let UE1 retain the RRC context, and the indication information can reuse the existing indication information. Exemplarily, RAN sends indication information of entering RRC-INACTIVE / CM-IDLE with suspend state to UE1 to instruct UE1 to retain the RRC context.

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

[0441] This S604 is an optional step.

[0442] If RAN determines that there is no feeder connection, RAN sends indication information 1 to UE1, indicating that 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 acceptance message.

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

[0444] In this embodiment, if S604 is executed, the execution order of the above S603 and S604 is not specifically limited.

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

[0446] In a possible implementation (UE1 local logic): UE1 is an S&F type UE, that is, the RAN accessed by UE1 must be a non-feeder connection. As long as UE1 sends an initial access request message once, it cannot initiate an initial access request message again within a period of time and / or before receiving an initial access acceptance message.

[0447] In another possible implementation, according to the indication information 1 of the RAN, the UE1 no longer initiates an initial access request message within the preset time and / or before receiving the initial access accept message.

[0448] 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 acceptance 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.

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

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

[0451] When there is a feeder connection, the RAN sends the initial access request message to the core network element MME / AMF.

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

[0453] Accordingly, RAN receives the initial access accept message of UE1 from MME / AMF.

[0454] For example, if the initial access request message sent by UE1 in the above step 601 is an attach request, then the initial access acceptance message sent by MME / AMF to RAN in this step (equivalent to the above Figure 4A or Figure 4B The response message of the first request message in the scheme is attach accept. If the initial access request message sent by UE1 in S601 is a registration request, then the initial access accept message sent by MME / AMF to RAN in this step is registration request accept.

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

[0456] 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 supported TA 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.

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

[0458] Correspondingly, UE1 receives the paging message.

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

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

[0461] Correspondingly, the RAN receives the paging response message of UE1.

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

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

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

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

[0466] In summary, in the first implementation, the RAN uses the ID of the RRC layer in the RRC context to page the UE. For this, 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 according to the local configuration or the trigger / instruction of the core network element (such as MME / AMF, etc.). Secondly, after the RAN receives the initial access request message from the UE, 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 acceptance message from the core network element, the RAN can use the ID of the RRC layer in the RRC context to page the UE, and then forward the initial access acceptance message to the UE that responds to the paging, so that the initial access process can be effectively completed.

[0467] Implementation method 2:

[0468] Based on the above Figure 4A-4B In the second implementation, in the S&F scenario, the wireless access network device RAN uses the NAS layer ID of UE1 (equivalent to the above-mentioned Figure 4A or Figure 4B The first identification information of the first terminal device in the solution) pages UE1. Figure 7 As shown, the specific process is as follows:

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

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

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

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

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

[0474] Since the scenarios in which the embodiments are applied are different, the initial access request message (equivalent to the above Figure 4A or Figure 4B The name corresponding to the first request information in the scheme may be different, and there is no limitation on this.

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

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

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

[0478] The specific implementation of the above S702 may refer to the implementation of the above S602, which will not be described in detail here.

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

[0480] Correspondingly, the UE1 receives the RRC connection release request (RRC connection release request) message.

[0481] In the second implementation, UE1 can retain an ID of the NSA layer, such as IMSI, and a pre-configured GUTI. Since UE1 has not completed initial access at this time, there is no NAS layer context. The UE1 may save a new one, that is, a context that may be different from the prior art, or UE1 may store 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 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, RAN also releases / deletes the RRC context of UE1.

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

[0483] S704 is an optional step.

[0484] S705: UE1 stops sending the initial access request message according to the local logic or the instruction of the RAN.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0504] The specific implementation of the above S710 may refer to the implementation of S608 in the above implementation mode 1, and will not be described in detail here.

[0505] S711: RAN sends a paging message.

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

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

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

[0509] When UE1 receives a paging message (CN type paging) from RAN, according to the existing logic, it needs to first initiate an RRC connection recovery process, and then initiate a service request process, that is, UE1 sends a service request message to RAN. However, in this implementation, when UE1 receives a paging message from the RAN, it cannot initiate a service request process, but waits to receive an initial access acceptance message (such as an attach accept message) from RAN after the RRC connection recovery process is completed.

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

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

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

[0513] The specific implementation of the above S713-S714 may refer to the implementation of S611-S612 in the above implementation method 1.

[0514] In summary, in the second implementation, the RAN uses the NAS layer ID to page the UE. After the RAN receives the initial access request message from the UE, if it is determined that there is no feeder connection, the RAN can instruct the UE to release the RRC context, and the RAN also releases the RRC context. Secondly, the core network element MME / AMF determines that the UE is an S&F type UE and sends a CN paging message to the RAN. Then the RAN can page the UE using the NAS layer ID according to the CN paging message from the MME / AMF. Then the RAN forwards the initial access acceptance message to the UE that responds to the paging, so that the initial access process can be effectively completed.

[0515] Implementation method three:

[0516] Based on the above Figure 4A-4B In the third implementation of the method, in the S&F scenario, in the initial access process, the RAN uses a special ID to page the UE1, and the special ID can be allocated by the RAN or the UE1. Figure 8 As shown, the specific process is as follows:

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

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

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

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

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

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

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

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

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

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

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

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

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

[0530] In the case where UE1 is assigned a special ID, the following steps S805 to S809 are performed:

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

[0532] S806: RAN sends a broadcast message.

[0533] Correspondingly, UE1 receives the broadcast message.

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

[0535] S807: UE1 allocates a special ID.

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

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

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

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

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

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

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

[0543] Correspondingly, the UE1 receives the RRC connection release request (RRC connection release request) message.

[0544] In the case of a special ID assigned by UE1, if the special ID assigned by UE1 is part of the RRC context, then the RAN sends an RRC connection release request to UE1 carrying an indication information for instructing UE1 to retain the RRC context. If the special ID assigned by UE1 is part of the NAS context, then the RAN sends an RRC connection release request to UE1 to instruct UE1 to release / delete the RRC context.

[0545] 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 any one of them can be selected for execution, and this application is not limited to this.

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

[0547] S810: 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.

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

[0549] S811: UE1 stops sending the initial access request message according to the local logic or the instruction of the RAN.

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

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

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

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

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

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

[0556] S813 and S814 are optional steps.

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

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

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

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

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

[0562] Correspondingly, UE1 receives the paging message.

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

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

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

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

[0567] The specific implementation of the above S816-S820 can refer to the implementation of S710-S714 in the above implementation mode 2 (or S608-S612 in the above implementation mode 1) in a one-to-one correspondence, and will not be described in detail here. However, unlike the paging message sent by the RAN in the above S711, which includes the NAS layer ID, the paging message sent by the RAN in the above step S817 includes a special ID allocated by the RAN / UE1.

[0568] In summary, in the third implementation method, the RAN uses a special ID assigned by the RAN or the UE to page the UE. For this, the RAN first determines that there is no feeder connection and informs the UE through a broadcast message, or the RRC determines that there is no feeder connection after establishing an RRC connection with the UE, then the RAN sends an RRC message to the UE to inform the UE. In the case where the UE assigns a special ID, the UE assigns a special ID after receiving the RAN broadcast message or RRC message, and then carries it in the initial access request message and sends it to the RAN, and 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, and 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 acceptance message from the core network to the UE, thereby effectively completing the initial access process of the UE.

[0569] Implementation method 4:

[0570] Based on the above Figure 4A-4B In the fourth implementation of the method, in the S&F scenario, during the initial access process of the terminal device UE (taking UE1 as an example), if UE1 initiates an authentication process, RAN uses different temporary IDs to page UE1 before and after the authentication process. Fig. 9 As shown, the specific process is as follows:

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

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

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

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

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

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

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

[0578] Correspondingly, the UE1 receives the RRC connection release request (RRC connection release request) message.

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

[0580] S904 is an optional step.

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

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

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

[0584] 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 in a one-to-one correspondence, and will not be described in detail here.

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

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

[0587] Before the initial access acceptance message (i.e. S909), an authentication and authorization process is also included, in which UE1 and the core network need to complete two interactive processes. In the authentication and authorization process, i.e. S907, RAN can first refer to the identification mentioned in implementation methods one to three to page UE1 (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. The temporary ID B is allocated to UE1 by MME / AMF, not RAN / UE. After the authentication and authorization process, RAN can use temporary ID B to page UE1 until the initial access process is completed.

[0588] S908: Complete the authentication process.

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

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

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

[0592] Accordingly, RAN receives the initial access accept message of UE1 from MME / AMF.

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

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

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

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

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

[0598] 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. Or the initial access acceptance 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.

[0599] For example, the initial access acceptance message may carry S-TMSI (a part of GUTI) and indication information 2. After UE1 receives the initial access acceptance message, the initial access process is completed, temporary ID A and temporary ID B are deleted, and UE1 may subsequently use the S-TMSI (a part of GUTI) carried in the initial access acceptance message to respond to paging. The specific implementation may refer to the existing technical solution and will not be described in detail here.

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

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

[0602] In the fourth implementation, for the S&F scenario, in the initial access process, if the authentication and authorization process of the UE 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 initial access request message from the UE and send it to the UE in 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 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 acceptance 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 the fourth implementation is more secure. Compared with the above-mentioned implementation two, the temporary ID allocated by the core network in the fourth implementation is a more dynamic identification and has higher security.

[0603] Implementation method five:

[0604] Based on the above Figure 5A-Figure 5B In the method, in the fifth implementation, in the S&F scenario, in the initial access process of the terminal device UE (taking UE1 as an example), the source RAN of UE1 forwards the context through the core network, and then pages UE1 in the initial access process through another RAN (target RAN). Fig.10 As shown, the specific process is as follows:

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

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

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

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

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

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

[0611] S1004 is an optional step.

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

[0613] 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 in a one-to-one correspondence, and will not be described in detail here.

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

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

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

[0617] This embodiment does not specifically limit the execution order of S1006 and S1007.

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

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

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

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

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

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

[0624] 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 to this.

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

[0626] S1014: The target RAN sends an initial access accept message to UE1, and accordingly, UE1 receives the initial access accept message.

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

[0628] To summarize, in the fifth implementation, for the S&F scenario, in the initial access process, the RAN forwards the context information through the core network element MME / AMF. After the core network element MME / AMF receives the context information of the source RAN, it determines the target RAN and then forwards the context information of the source RAN to the target RAN. In this way, the UE can be paged faster in the initial access process through the target RAN, thereby effectively completing the initial access process.

[0629] Implementation method six:

[0630] Compared with the above implementation mode 5, the main difference in the implementation mode 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 through the intersatellite link, and then pages UE1 in the initial access process through the target RAN. Fig.11 As shown, the specific process is as follows:

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

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

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

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

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

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

[0637] S1104 is an optional step.

[0638] S1105: UE1 stops sending the initial access request message according to the local logic or the instruction of the RAN.

[0639] The specific implementations of the above-mentioned S1100a-S1100b and S1102 to S1105 can refer to 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), which will not be described in detail here.

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

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

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

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

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

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

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

[0647] S1111: The target RAN sends context request information to the source RAN. Correspondingly, the source RAN receives the context request information.

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

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

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

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

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

[0653] The identifier used by the target RAN to paging UE1 may 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.

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

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

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

[0657] In the sixth implementation, for the S&F scenario, in the initial access process, the MME / AMF receives the initial access request message of the UE forwarded by the source RAN, determines the target RAN, and forwards the ID of the source RAN to the target RAN 2, or forwards the ID of the target RAN 2 to the source RAN 1, so that the source RAN can forward the context through the inter-satellite link to reach the target RAN, and then the UE can be paged faster in the initial access process through the target RAN.

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

[0659] (1) The above implementation modes 1 to 6 can be implemented separately or in combination, without any specific limitation.

[0660] (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.

[0661] (3) The step numbers of the flowcharts described in Implementations 1 to 6 are only examples of the execution process and do not constitute a limitation on the order of execution of the steps. There are no steps in the implementations of this application that have a time dependency relationship with each other, and there is no strict execution order between them. In addition, not all the steps shown in the flowcharts are steps that must be executed, and some steps can be added or deleted based on the actual needs of each flowchart.

[0662] In the embodiments provided by the present application above, the methods provided by 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 by 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.

[0663] The division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment or implementation of the present application may be integrated into a processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0664] Same as above idea, Fig.12 As shown, the embodiment of the present application also provides a communication device 1200 for implementing the functions of 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. For example, the communication device 1200 can be a software module or a chip system. In the embodiment of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices. The communication device 1200 may include: a communication unit 1201 and a processing unit 1202.

[0665] In the embodiment 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, which are respectively used to execute the steps of sending and receiving 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. The processing unit 1202 may be used to read instructions and / or data in the storage module so that the communication device 1200 implements the above method embodiment.

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

[0667] The following, combined Figure 12 to Figure 13 The communication device provided in the embodiment of the present application is described in detail. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment, so the contents not described in detail can be referred to above. Figure 4A and Figure 4B and 5A- Figure 5B , Figures 6 to 11 The method shown is implemented, and for the sake of brevity, it will not be repeated here.

[0668] The communication unit 1201 may also be referred to as a transceiver, a transceiver, a transceiver device, etc. The processing unit may also be referred to as a processor, a processing board, a processing module, a processing device, etc. Optionally, the device used to implement the receiving function in the communication unit 1201 may be regarded as a receiving unit, and the device used to implement the sending function in the communication unit 1201 may be regarded as a sending unit, that is, the communication unit 1201 includes a receiving unit and a sending unit. The communication unit may also be sometimes referred to as a transceiver, a transceiver, or a transceiver circuit, etc. The receiving unit may also be sometimes referred to as a receiver, a receiver, or a receiving circuit, etc. The sending unit may also be sometimes referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0669] When the communication device 1200 executes the above embodiment Figure 4A When the process shown is the first access network device: 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.

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

[0671] When the communication device 1200 executes the above embodiment Figure 4A When it is the first terminal device in the process shown: 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 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.

[0672] When the communication device 1200 executes the above embodiment Figure 4A In the process shown, when the first terminal device is: the communication unit 1201 is used to send a first request message to the first access network device, the first request message is used to request that the first terminal device be registered to the network; a first paging message is received from the first access network device, and the communication unit 1201 is also used to send the first paging response message; the first paging response message is used to respond to the first paging message;

[0673] 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 a response message to the first request message; according to the first indication message, stop sending the first request message within the preset time or before receiving a response message to the first request message; or; the processing unit 1202 is used to stop sending the first request message through the communication unit 1201 within a preset time or before receiving a response message to the first request message according to local configuration.

[0674] When the communication device 1200 executes the above embodiment Figure 4AIn the core network element of the process shown: 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 to register the first terminal device 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.

[0675] When the communication device 1200 executes the above embodiment Figure 4B When the first access network device is in the process shown: 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.

[0676] The communication unit 1201 is used to receive response information of the first request information from the core 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.

[0677] When the communication device 1200 executes the above embodiment Figure 5A When the second access network device is in the process shown: 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.

[0678] The communication unit 1201 is used to receive a first request message from a first terminal device, wherein the first request message is used to request that the first terminal device be registered to a 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 a core network element when it is determined through the processing unit 1202 that the second access network device has no feeder connection.

[0679] When the communication device 1200 executes the above embodiment Figure 5A When it is the first terminal device in the process shown: 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 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 has not received a response to the first request message.

[0680] When the communication device 1200 executes the above embodiment Figure 5A When it is the first terminal device in the process shown: 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.

[0681] When the communication device 1200 executes the above embodiment Figure 5AIn the core network element of the process shown: the communication unit 1201 is used to receive a first request information from a second access network device, and the first request information is used to request to register the first terminal device 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.

[0682] The above is just an example. The processing unit 1202 and the communication unit 1201 can also perform other functions. For more detailed description, please refer to Figure 4A and Figure 4B and 5A- Figure 5B The relevant description in the method embodiment shown is not repeated here.

[0683] like Fig.13 The communication device 1300 provided in an embodiment of the present application is shown. Fig.13 The communication device shown can be Fig.12 The communication device 1300 can be applied to the flowchart shown above to perform the functions of 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. For the convenience of explanation, Fig.13 Only the main components of the communication device are shown.

[0684] like Fig.13 As shown, the communication device 1300 includes a communication interface 1301 and a processor 1302. The communication interface 1301 and the processor 1302 are coupled to each other. It is understandable that the communication interface 1301 can be a transceiver or an input-output interface, or an interface circuit such as a transceiver circuit. Optionally, the communication device 1300 may also include a memory 1303 for storing instructions executed by the processor 1302 or storing input data required by the processor 1302 to run the instructions or storing data generated after the processor 1302 runs the instructions.

[0685] When the communication device 1300 is used to implement Figure 4A and Figure 4B and 5A- Figure 5B , Figures 6 to 11 In the method shown, 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.

[0686] The specific connection medium between the communication interface 1301, the processor 1302 and the memory 1303 is not limited in the embodiment of the present application. Fig.13The memory 1303, the processor 1302 and the communication interface 1301 are connected via a communication bus 1304. Fig.13 The communication bus 1304 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.13 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0687] When the communication device is a chip, Fig.14 A simplified schematic diagram of a chip device structure is shown, wherein the chip 1400 includes an interface circuit 1401 and one or more processors 1402. Optionally, the chip 1400 may also include a bus.

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

[0689] 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, and can send the processing completion information through the interface circuit 1401.

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

[0691] Optionally, the memory stores executable software modules or data structures, and the processor can perform corresponding operations by calling operation instructions stored in the memory (the operation instructions can be stored in the operating system).

[0692] Optionally, the chip can be used in the first terminal device, the first access network device, the second access network device, or the core network element involved in the embodiment of the present application. Optionally, the interface circuit 1401 can be used to output the execution result of the processor 1402. The communication method provided by one or more embodiments of the present application can refer to the aforementioned embodiments, which will not be repeated here.

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

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

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

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

[0697] The embodiment of the present application also provides a chip, including a processor, which is used to call the computer program or computer instruction stored in the memory so that the processor executes the above Figure 4A and Figure 4B and 5A- Figure 5B , Figures 6 to 11 The communication method of the implementation shown.

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

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

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

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

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

[0703] In the present application, the communication devices may also include a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. Among them, the hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also called 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 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.

[0704] The division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present application may be integrated into a processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0705] Through the description of the above implementation mode, it can be clearly understood by those skilled in the art that the embodiments of the present application can be implemented by 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. Taking this as an example but not limited to: a computer-readable medium can include RAM, ROM, electrically erasable programmable read only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, 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 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, wireless, and microwave are included in the fixation of the medium. As used in the embodiments of the present application, disk and disc include compact disc (CD), laser disc, optical disc, digital video disc (DVD), floppy disk, and Blu-ray disc, where disks usually copy data magnetically and discs use lasers to copy data optically. The above combinations should also be included in the scope of protection of computer-readable media.

[0706] In short, the above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made according to the disclosure of the present application shall be included in the protection scope 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 device, characterized in that: A module for executing the method as claimed in any one of claims 1 to 14, or a module for executing the method as claimed in any one of claims 15 to 22, or a module for executing the method as claimed in claim 23, or a module for executing the method as claimed in any one of claims 24 to 32.

34. 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.

35. A communication system, characterized in that: It includes a first access network device, a first terminal device and a core network network element; the first access network device is used to execute the method as described in any one of claims 1 to 14, the first terminal device is used to execute the method as described in any one of claims 15 to 22, or the first terminal device is used to execute the method as described in claim 23, and the core network network element is used to execute the method as described in any one of claims 24 to 32.

36. 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 according to any one of claims 1 to 32.

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

Images