Relay communication method and apparatus, and communication device, communication system and storage medium

Abstract

Disclosed in the embodiments of the present disclosure are a relay communication method and apparatus. The method comprises: receiving a first message transmitted by a second terminal, wherein the first message comprises an identifier of the second terminal; and transmitting the first message to a first network element by means of an access network device, wherein the identifier of the second terminal is used for retrieving, from subscription data stored in a second network element, subscription data corresponding to the second terminal, and the subscription data corresponding to the second terminal is used for indicating that the second terminal supports store-and-forward communication with a first terminal, such that when there is no end-to-end connection between an ambient power-enabled Internet of Things device and a network, the ambient power-enabled Internet of Things device can communicate with the network by means of a relay terminal, and regardless of whether the connection between the relay terminal and the network is available or unavailable, the ambient power-enabled Internet of Things device can communicate with the network successfully, thereby effectively improving the communication efficiency of a system.

Description

Relay communication method and device, communication equipment, communication system, and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a relay communication method and apparatus, communication equipment, a communication system, and a storage medium. Background Art

[0002] Ambient power-enabled Internet of Things (A-IoT) is an IoT service that uses harvested energy to power IoT devices, which can be battery-free or have limited power storage capacity. Typically, Ambient power-enabled IoT devices lack traditional batteries. Instead, the IoT devices themselves use energy harvested from radio waves or any other form of energy available in the given situation.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure propose a relay communication method and apparatus, which can solve the problem of how to communicate when there is no end-to-end connection between the ambient power supply Internet of Things device and the network.

[0005] According to a first aspect of an embodiment of the present disclosure, a relay communication method is provided, where the method is performed by a first terminal and includes:

[0006] receiving a first message sent by a second terminal, where the first message includes an identifier of the second terminal;

[0007] The first message is sent to the first network element through the access network device, and the identifier of the second terminal is used to retrieve the subscription data corresponding to the second terminal from the subscription data stored in the second network element, and the subscription data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

[0008] According to a second aspect of an embodiment of the present disclosure, a relay communication method is provided, where the method is performed by a second terminal and includes:

[0009] Sending a first message to a first terminal;

[0010] The first message is used to be sent by the first terminal to the first network element through the access network device. The first message includes the identifier of the second terminal. The identifier of the second terminal is used to retrieve the contract data corresponding to the second terminal from the contract data stored in the second network element. The contract data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

[0011] According to a third aspect of an embodiment of the present disclosure, a relay communication method is provided. The method is performed by a first network element, and the method includes:

[0012] receiving a first message sent by a first terminal through an access network device, where the first message includes an identifier of a second terminal;

[0013] A sixth message is sent to the second network element, where the sixth message includes an identifier of the second terminal. The identifier of the second terminal is used to retrieve the contract data corresponding to the second terminal from the contract data stored in the second network element, and the contract data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

[0014] According to a fourth aspect of an embodiment of the present disclosure, a relay communication method is provided. The method is performed by a second network element, and the method includes:

[0015] receiving a sixth message sent by the first network element, where the sixth message includes an identifier of the second terminal;

[0016] Retrieving, based on the identifier of the second terminal, subscription data corresponding to the second terminal from the stored subscription data, where the subscription data corresponding to the second terminal is used to indicate that the second terminal supports store and forward communication with the first terminal;

[0017] The identifier of the second terminal is included in a first message sent by the first terminal to the first network element through the access network device.

[0018] The solution proposed in the embodiment of the present disclosure receives a first message sent by a second terminal, where the first message includes an identifier of the second terminal, and sends the first message to a first network element through an access network device. The identifier of the second terminal is used to retrieve the contract data corresponding to the second terminal from the contract data stored in the second network element, and the contract data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal, so that in the absence of an end-to-end connection between the environment-powered Internet of Things device and the network, communication with the network can be carried out through a relay terminal, and the environment-powered Internet of Things device and the network can successfully communicate whether the connection between the relay terminal and the network is available or unavailable, thereby effectively improving the communication efficiency of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0020] FIG1 is a schematic diagram of the architecture of some communication systems provided by embodiments of the present disclosure;

[0021] FIG2 is an interactive diagram of a relay communication method provided by an embodiment of the present disclosure;

[0022] FIG3A is a schematic diagram showing a flow chart of a relay communication method according to an embodiment of the present disclosure;

[0023] FIG3B is a schematic diagram showing a flow chart of a relay communication method according to an embodiment of the present disclosure;

[0024] FIG3C is a schematic diagram showing a flow chart of a relay communication method according to an embodiment of the present disclosure;

[0025] FIG4A is a schematic diagram showing a flow chart of a relay communication method according to an embodiment of the present disclosure;

[0026] FIG4B is a schematic diagram showing a flow chart of a relay communication method according to an embodiment of the present disclosure;

[0027] FIG4C is a schematic diagram showing a flow chart of a relay communication method according to an embodiment of the present disclosure;

[0028] FIG5A is a schematic diagram showing a flow chart of a relay communication method according to an embodiment of the present disclosure;

[0029] FIG5B is a schematic diagram showing a flow chart of a relay communication method according to an embodiment of the present disclosure;

[0030] FIG6A is a schematic diagram showing a flow chart of a relay communication method according to an embodiment of the present disclosure;

[0031] FIG6B is a schematic diagram showing a flow chart of a relay communication method according to an embodiment of the present disclosure;

[0032] FIG7A is an interactive schematic diagram illustrating a relay communication method according to an embodiment of the present disclosure;

[0033] FIG7B is an interactive schematic diagram illustrating a relay communication method according to an embodiment of the present disclosure;

[0034] FIG8 is a schematic diagram of system interaction of a relay communication method according to an embodiment of the present disclosure;

[0035] FIG9A is a schematic structural diagram of a first terminal proposed in an embodiment of the present disclosure;

[0036] FIG9B is a schematic structural diagram of a second terminal proposed in an embodiment of the present disclosure;

[0037] FIG9C is a schematic structural diagram of a first network element proposed in an embodiment of the present disclosure;

[0038] FIG9D is a schematic structural diagram of a second network element proposed in an embodiment of the present disclosure;

[0039] FIG9E is a schematic structural diagram of a core network device proposed in an embodiment of the present disclosure;

[0040] FIG10A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0041] FIG10B is a schematic structural diagram of a chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0042] The embodiments of the present disclosure provide a relay communication method and apparatus, a communication device, a communication system, and a storage medium.

[0043] In a first aspect, an embodiment of the present disclosure provides a relay communication method, which is performed by a first terminal and includes:

[0044] receiving a first message sent by a second terminal, where the first message includes an identifier of the second terminal;

[0045] The first message is sent to the first network element through the access network device, and the identifier of the second terminal is used to retrieve the subscription data corresponding to the second terminal from the subscription data stored in the second network element, and the subscription data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

[0046] In the above embodiment, when there is no end-to-end connection between the first terminal and the network, communication with the network can be carried out through a relay second terminal, and the relay second terminal supports storage and forwarding communication with the first terminal, so that the first terminal and the network can successfully communicate whether the connection between the relay second terminal and the network is available or unavailable, effectively improving the communication efficiency of the system and the coverage of the network.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0048] receiving a second message sent by the first network element through an access network device, where the second message is used to indicate authorization of store and forward communication between the second terminal and the first terminal;

[0049] Send the second message to the second terminal.

[0050] In the above embodiment, the second terminal can be informed that the network has authorized the store-and-forward communication between the second terminal and the first terminal, thereby improving communication efficiency.

[0051] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0052] Sending a third message to the first network element through the access network device, the third message including an identifier of the first terminal, where the identifier of the first terminal is used to retrieve subscription data corresponding to the first terminal from subscription data stored in the second network element, where the subscription data corresponding to the first terminal is used to indicate that the first terminal supports store and forward communication with the second terminal;

[0053] A fourth message is received, which is sent by the first network element through an access network device, where the fourth message is used to indicate authorization of store and forward communication between the first terminal and the second terminal.

[0054] In the above embodiment, the first terminal can be informed that the network has authorized the store-and-forward communication between the first terminal and the second terminal, thereby improving communication efficiency.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0056] A fifth message is sent to the second terminal, where the fifth message is used to instruct the second terminal to perform store-and-forward communication with the first terminal.

[0057] In the above embodiment, the first terminal can learn that the second terminal can perform store-and-forward communication between the first terminal and the second terminal, and then perform store-and-forward communication with the second terminal, thereby improving communication efficiency.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0059] The connection between the first terminal and the access network device is unavailable, and information sent by the second terminal is received and stored.

[0060] In the above embodiment, when the connection between the second terminal of the relay and the network is unavailable, the first terminal and the network can still communicate successfully, which effectively improves the communication efficiency of the system and improves the coverage of the network.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0062] The connection between the first terminal and the access network device is available, and the information sent by the second terminal and stored by the first terminal is sent to the access network device; and / or,

[0063] Receive information sent by the second terminal, and forward the information sent by the second terminal to the access network device.

[0064] In the above embodiment, whether the connection between the second terminal of the relay and the network is available or unavailable, the first terminal and the network can successfully communicate, which effectively improves the communication efficiency of the system and improves the coverage of the network.

[0065] In a second aspect, an embodiment of the present disclosure provides a relay communication method, which is performed by a second terminal and includes:

[0066] Sending a first message to a first terminal;

[0067] The first message is used to be sent by the first terminal to the first network element through the access network device. The first message includes the identifier of the second terminal. The identifier of the second terminal is used to retrieve the contract data corresponding to the second terminal from the contract data stored in the second network element. The contract data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

[0068] In the above embodiment, when there is no end-to-end connection between the first terminal and the network, communication with the network can be carried out through a relay second terminal, and the relay second terminal supports storage and forwarding communication with the first terminal, so that the first terminal and the network can successfully communicate whether the connection between the relay second terminal and the network is available or unavailable, effectively improving the communication efficiency of the system and the coverage of the network.

[0069] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0070] A second message sent by the first terminal is received, where the second message is sent by the first network element to the first terminal through an access network device, and the second message is used to indicate authorization of storage and forwarding communication between the second terminal and the first terminal.

[0071] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0072] A fifth message sent by the first terminal is received, where the fifth message is used to instruct the second terminal to perform store-and-forward communication with the first terminal.

[0073] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0074] The connection between the first terminal and the access network device is unavailable, and information is sent to the first terminal, where the information is stored in the first terminal.

[0075] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0076] The connection between the first terminal and the access network device is available, and the information stored in the first terminal is forwarded by the first terminal to the access network device; and / or,

[0077] The connection between the first terminal and the access network device is available, information is sent to the first terminal, and the information is forwarded by the first terminal to the access network device.

[0078] In a third aspect, an embodiment of the present disclosure provides a relay communication method, which is performed by a first network element and includes:

[0079] receiving a first message sent by a first terminal through an access network device, where the first message includes an identifier of a second terminal;

[0080] A sixth message is sent to the second network element, where the sixth message includes an identifier of the second terminal. The identifier of the second terminal is used to retrieve the contract data corresponding to the second terminal from the contract data stored in the second network element, and the contract data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

[0081] In the above embodiment, the network can authorize storage and forwarding communication between the first terminal and the second terminal, so that when there is no end-to-end connection between the first terminal and the network, communication with the network can be carried out through a relay second terminal, and the relay second terminal supports storage and forwarding communication with the first terminal, so that whether the connection between the relay second terminal and the network is available or unavailable, the first terminal and the network can successfully communicate, effectively improving the communication efficiency of the system and improving the coverage of the network.

[0082] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0083] A second message is sent to the first terminal through an access network device, where the second message is sent from the first terminal to the second terminal, and the second message is used to indicate authorization for store and forward communication between the second terminal and the first terminal.

[0084] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0085] receiving a third message sent by the first terminal through an access network device, where the third message includes an identifier of the first terminal;

[0086] sending a seventh message to the second network element, the seventh message including an identifier of the first terminal, the identifier of the first terminal being used to retrieve subscription data corresponding to the first terminal from subscription data stored in the second network element, the subscription data corresponding to the first terminal being used to indicate that the first terminal supports store and forward communication with the second terminal;

[0087] A fourth message is sent to the first terminal through the access network device, where the fourth message is used to indicate authorization of store and forward communication between the first terminal and the second terminal.

[0088] In a fourth aspect, an embodiment of the present disclosure provides a relay communication method, which is performed by a second network element and includes:

[0089] receiving a sixth message sent by the first network element, where the sixth message includes an identifier of the second terminal;

[0090] Retrieving, based on the identifier of the second terminal, subscription data corresponding to the second terminal from the stored subscription data, where the subscription data corresponding to the second terminal is used to indicate that the second terminal supports store and forward communication with the first terminal;

[0091] The identifier of the second terminal is included in a first message sent by the first terminal to the first network element through the access network device.

[0092] In the above embodiment, the network can authorize storage and forwarding communication between the first terminal and the second terminal, so that when there is no end-to-end connection between the first terminal and the network, communication with the network can be carried out through a relay second terminal, and the relay second terminal supports storage and forwarding communication with the first terminal, so that whether the connection between the relay second terminal and the network is available or unavailable, the first terminal and the network can successfully communicate, effectively improving the communication efficiency of the system and improving the coverage of the network.

[0093] In conjunction with some embodiments of the fourth aspect, in some embodiments, the method further includes:

[0094] receiving a seventh message sent by the first network element, where the seventh message includes an identifier of the first terminal;

[0095] Retrieving, based on the identifier of the first terminal, subscription data corresponding to the first terminal from the stored subscription data, where the subscription data corresponding to the first terminal is used to indicate that the first terminal supports store and forward communication with the second terminal;

[0096] The identifier of the first terminal is included in a third message sent by the first terminal to the first network element through the access network device.

[0097] In a fifth aspect, an embodiment of the present disclosure provides a relay communication method, which is performed by a core network device and includes:

[0098] Receive a first message sent by a first terminal through an access network device, where the first message includes an identifier of a second terminal. The identifier of the second terminal is used to retrieve the subscription data corresponding to the second terminal from the subscription data stored in the core network device, and the subscription data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

[0099] In the above embodiment, the network can authorize storage and forwarding communication between the first terminal and the second terminal, so that when there is no end-to-end connection between the first terminal and the network, communication with the network can be carried out through a relay second terminal, and the relay second terminal supports storage and forwarding communication with the first terminal, so that whether the connection between the relay second terminal and the network is available or unavailable, the first terminal and the network can successfully communicate, effectively improving the communication efficiency of the system and improving the coverage of the network.

[0100] In conjunction with some embodiments of the fifth aspect, in some embodiments, the method further includes:

[0101] A second message is sent to the first terminal through an access network device, where the second message is sent from the first terminal to the second terminal, and the second message is used to indicate authorization for store and forward communication between the second terminal and the first terminal.

[0102] In conjunction with some embodiments of the fifth aspect, in some embodiments, the method further includes:

[0103] receiving a third message sent by a first terminal through an access network device, the third message including an identifier of the first terminal, the identifier of the first terminal being used to retrieve subscription data corresponding to the first terminal from subscription data stored in the core network device, the subscription data corresponding to the first terminal being used to indicate that the first terminal supports store and forward communication with a second terminal;

[0104] A fourth message is sent to the first terminal through an access network device. The fourth message is sent by the first terminal to the second terminal. The fourth message is used to indicate authorization of store and forward communication between the first terminal and the second terminal.

[0105] In a sixth aspect, an embodiment of the present disclosure provides a relay communication method, the method comprising:

[0106] The first network element sends a sixth message to the second network element, where the sixth message includes an identifier of the second terminal;

[0107] The second network element retrieves, based on the identifier of the second terminal, subscription data corresponding to the second terminal from the stored subscription data, where the subscription data corresponding to the second terminal is used to indicate that the second terminal supports store and forward communication with the first terminal;

[0108] The identifier of the second terminal is included in a first message sent by the first terminal to the first network element through the access network device.

[0109] In the above embodiment, the network can authorize storage and forwarding communication between the first terminal and the second terminal, so that when there is no end-to-end connection between the first terminal and the network, communication with the network can be carried out through a relay second terminal, and the relay second terminal supports storage and forwarding communication with the first terminal, so that whether the connection between the relay second terminal and the network is available or unavailable, the first terminal and the network can successfully communicate, effectively improving the communication efficiency of the system and improving the coverage of the network.

[0110] In conjunction with some embodiments of the sixth aspect, in some embodiments, the method further includes:

[0111] a seventh message sent by the first network element to the second network element, the seventh message including an identifier of the first terminal;

[0112] The second network element retrieves, based on the identifier of the first terminal, subscription data corresponding to the first terminal from the stored subscription data, where the subscription data corresponding to the first terminal is used to indicate that the first terminal supports store and forward communication with the second terminal;

[0113] The identifier of the first terminal is included in a third message sent by the first terminal to the first network element through the access network device.

[0114] In a seventh aspect, an embodiment of the present disclosure provides a relay communication method, the method comprising:

[0115] The second terminal sends a first message to the first terminal, where the first message includes an identifier of the second terminal;

[0116] The first terminal sends the first message to the first network element through the access network device;

[0117] The first network element sends a sixth message to the second network element, where the sixth message includes an identifier of the second terminal;

[0118] The second network element retrieves the subscription data corresponding to the second terminal from the stored subscription data based on the identifier of the second terminal, where the subscription data corresponding to the second terminal is used to indicate that the second terminal supports store and forward communication with the first terminal.

[0119] In the above embodiment, when there is no end-to-end connection between the first terminal and the network, communication with the network can be carried out through a relay second terminal, and the relay second terminal supports storage and forwarding communication with the first terminal, so that the first terminal and the network can successfully communicate whether the connection between the relay second terminal and the network is available or unavailable, effectively improving the communication efficiency of the system and the coverage of the network.

[0120] In conjunction with some embodiments of the seventh aspect, in some embodiments, the method further includes:

[0121] The first network element sends a second message to the first terminal through an access network device, where the second message is used to indicate authorization for store and forward communication between the second terminal and the first terminal;

[0122] The first terminal sends the second message to the second terminal.

[0123] In conjunction with some embodiments of the seventh aspect, in some embodiments, the method further includes:

[0124] The first terminal sends a third message to the first network element through the access network device, where the third message includes an identifier of the first terminal;

[0125] Sending a seventh message to the second network element, where the seventh message includes an identifier of the first terminal;

[0126] The second network element retrieves, based on the identifier of the first terminal, subscription data corresponding to the first terminal from the stored subscription data, where the subscription data corresponding to the first terminal is used to indicate that the first terminal supports store and forward communication with the second terminal;

[0127] The first network element sends a fourth message to the first terminal through the access network device, where the fourth message is used to indicate authorization of store and forward communication between the first terminal and the second terminal.

[0128] In conjunction with some embodiments of the seventh aspect, in some embodiments, the method further includes:

[0129] The first terminal sends a fifth message to the second terminal, where the fifth message is used to instruct the second terminal to perform store and forward communication with the first terminal.

[0130] In conjunction with some embodiments of the seventh aspect, in some embodiments, the method further includes:

[0131] The connection between the first terminal and the access network device is unavailable, the second terminal sends information to the first terminal, and the first terminal stores the information sent by the second terminal.

[0132] In conjunction with some embodiments of the seventh aspect, in some embodiments, the method further includes:

[0133] The connection between the first terminal and the access network device is available, and the first terminal sends to the access network device the information sent by the second terminal and stored by the first terminal; and / or,

[0134] The second terminal sends information to the first terminal, and the first terminal forwards the information sent by the second terminal to the access network device.

[0135] In an eighth aspect, an embodiment of the present disclosure proposes a first terminal, which includes at least one of a transceiver module and a processing module; wherein the first terminal is used to execute the first aspect and the optional implementation method of the first aspect.

[0136] In a ninth aspect, an embodiment of the present disclosure proposes a second terminal, which includes at least one of a transceiver module and a processing module; wherein the second terminal is used to execute the second aspect and the optional implementation method of the second aspect.

[0137] In the tenth aspect, an embodiment of the present disclosure proposes a first network element, which includes at least one of a transceiver module and a processing module; wherein the first network element is used to execute the third aspect and the optional implementation method of the third aspect.

[0138] In the eleventh aspect, an embodiment of the present disclosure proposes a second network element, which includes at least one of a transceiver module and a processing module; wherein the second network element is used to execute the fourth aspect and the optional implementation method of the fourth aspect.

[0139] In the twelfth aspect, an embodiment of the present disclosure proposes a core network device, which includes at least one of a transceiver module and a processing module; wherein the core network device is used to execute the fifth aspect and the optional implementation method of the fifth aspect.

[0140] In a thirteenth aspect, an embodiment of the present disclosure proposes a first terminal, which includes: one or more processors; wherein the first terminal is used to execute the first aspect and the optional implementation method of the first aspect.

[0141] In the fourteenth aspect, an embodiment of the present disclosure proposes a second terminal, which includes: one or more processors; wherein the second terminal is used to execute the second aspect and the optional implementation method of the second aspect.

[0142] In the fifteenth aspect, an embodiment of the present disclosure proposes a first network element, which includes: one or more processors; wherein the first network element is used to execute the third aspect and the optional implementation method of the third aspect.

[0143] In the sixteenth aspect, an embodiment of the present disclosure proposes a second network element, which includes: one or more processors; wherein the second network element is used to execute the fourth aspect and the optional implementation method of the fourth aspect.

[0144] In the seventeenth aspect, an embodiment of the present disclosure proposes a core network device, which includes: one or more processors; wherein the core network device is used to execute the fifth aspect and the optional implementation method of the fifth aspect.

[0145] In aspect 18, an embodiment of the present disclosure proposes a communication system, which includes: a first terminal, a second terminal, and a core network device; wherein, the first terminal is configured to execute the method described in the first aspect and the optional implementation of the first aspect, the second terminal is configured to execute the method described in the second aspect and the optional implementation of the second aspect, and the core network device is configured to execute the method described in the third aspect, the fourth aspect and the fifth aspect, and the third aspect, the fourth aspect and the optional implementation of the fifth aspect.

[0146] In the nineteenth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first to fifth aspects and the optional implementation methods of the first to fifth aspects.

[0147] In the twentieth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first to fifth aspects and the optional implementation methods of the first to fifth aspects.

[0148] In the twenty-first aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the methods described in the first to fifth aspects and the optional implementations of the first to fifth aspects.

[0149] In a twenty-second aspect, an embodiment of the present disclosure provides a chip or chip system, which includes a processing circuit configured to execute the method described in accordance with the first to fifth aspects and the optional implementations of the first to fifth aspects.

[0150] It is understandable that the first terminal, second terminal, first network element, second network element, core network device, communication device, communication system, storage medium, program product, and computer program described above are all used to execute the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0151] The present disclosure provides a relay communication method and apparatus, communication device, communication system, and storage medium. In some embodiments, the terms relay communication method, information processing method, and communication method are interchangeable; the terms relay communication apparatus, information processing apparatus, and communication apparatus are interchangeable; and the terms information processing system and communication system are interchangeable.

[0152] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0153] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0154] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0155] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0156] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0157] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0158] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0159] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0160] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0161] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0162] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0163] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0164] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0165] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0166] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0167] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0168] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0169] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0170] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0171] In order to better understand the relay communication method disclosed in the embodiment of the present disclosure, the communication system to which the embodiment of the present disclosure is applicable is first described below.

[0172] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0173] As shown in FIG1 , a communication system 100 includes a first terminal 101 , a second terminal 102 , and a core network device 103 .

[0174] In some embodiments, the first terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0175] In some embodiments, the second terminal 102 is, for example, an ambient power-enabled Internet of Things (A-IoT) device or an A-IoT tag, powered by ambient energy, such as energy from solar energy, light, motion / vibration, heat, pressure, or any other power source. The second terminal may be battery-free or have limited power storage capacity, and may use energy harvested from radio waves or any other form of energy available under specific circumstances.

[0176] In some embodiments, the communication system 100 also includes an access network device, which is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0177] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0178] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0179] In some embodiments, the core network device 103 may be a single device including a first network element 1031, a second network element 1032, etc., or may be a plurality of devices or a device group including all or part of the first network element 1031, the second network element 1032, etc. The network element may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0180] In some embodiments, the first network element 1031 is, for example, an access and mobility management function (AMF).

[0181] In some embodiments, the first network element 1031 is used to manage the mobility of the terminal and can authorize and authenticate the access of the terminal, etc., and the name is not limited thereto.

[0182] In some embodiments, the second network element 1032 is, for example, a unified data management (UDM) or a user data register (UDR).

[0183] In some embodiments, the second network element 1032 is used to calculate and store user data, and the name is not limited thereto.

[0184] In some embodiments, the core network device 103 may further include a third network element, such as a user plane function (UPF).

[0185] In some embodiments, the third network element is used for packet routing and forwarding, policy implementation, traffic reporting, QoS processing, etc., and the name is not limited thereto.

[0186] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0187] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0188] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0189] In the disclosed embodiments, the A-IoT device may be battery-free or have limited power storage capabilities (e.g., using capacitors). Optionally, the A-IoT device may communicate without a traditional power source and / or avoid the need for human intervention to charge or replace batteries. The device itself may be able to use energy harvested from radio waves or any other form of energy available under specific circumstances. Because the A-IoT device does not require traditional batteries, it is environmentally friendly.

[0190] For example, in some embodiments, A-IoT devices can harvest energy from radio waves, which may originate from 5G NR network entities or user equipment. In some embodiments, A-IoT devices can also harvest energy from solar energy, light, motion / vibration, heat, pressure, or any other form of energy.

[0191] In some embodiments, some potential challenges of A-IoT include:

[0192] A-IoT devices are expected to harvest energy and use the harvested energy to support communications;

[0193] Despite the limitations of complexity, size, power consumption, etc. of A-IoT devices, it needs to be able to provide sufficient communication services to meet the corresponding requirements.

[0194] In some embodiments, a user can use a handheld device to trigger the ambient-powered IoT device on the box to send the device's ID to the network. Alternatively, if within network coverage, the ambient-powered IoT device can communicate directly with the network. If not, the handheld device can relay the communication.

[0195] In some embodiments, if the handheld device is also not connected to the network, communication between the ambient-powered IoT device and the network will fail. In this case, if the ambient-powered IoT device can still send messages to the handheld device, the handheld device can forward these messages to the network when it connects to the network, which will greatly improve the communication efficiency of the system.

[0196] Therefore, when there is no end-to-end connection between the ambient-powered IoT device and the network, how to support store-and-forward communication from the ambient-powered IoT device to the network through another terminal is an urgent problem to be solved.

[0197] In the embodiment of the present disclosure, it is assumed that the operator authorizes the first terminal and the second terminal (environmentally powered IoT device) to communicate with each other.

[0198] FIG2 is an interactive diagram of a relay communication method according to an embodiment of the present disclosure. As shown in FIG2 , the method according to the embodiment of the present disclosure is used in a communication system 100, and the method includes:

[0199] Step S2101: The second terminal sends a first message to the first terminal.

[0200] In some embodiments, the first terminal receives a first message sent by the second terminal.

[0201] In some embodiments, the first message includes an identifier of the second terminal.

[0202] In some embodiments, the identifier of the second terminal may be at least one of a Subscription Concealed Identifier (SUCI), a 5G Globally Unique Temporary Identity (5G-GUTI), and a Permanent Equipment Identifier (PEI).

[0203] In some embodiments, the identifier of the second terminal is used to retrieve subscription data corresponding to the second terminal from subscription data stored in the second network element.

[0204] In some embodiments, the first message may also include other parameters for registration, such as at least one of a registration type and a security parameter.

[0205] In some embodiments, the first message is used to request that the second terminal device be connected to the network.

[0206] In some embodiments, the first message is used to request registration of the second terminal in the network.

[0207] In some embodiments, the name of the first message is not limited, and may be, for example, "access request", "registration request", "connection request", etc.

[0208] In some embodiments, the second terminal may collect energy before sending the first message to obtain sufficient energy to support the second terminal in sending the first message. For example, the second terminal may obtain energy from radio waves sent by the first terminal to the second terminal.

[0209] In some embodiments, before the second terminal sends the first message to the first terminal, the first terminal may send radio energy to the second terminal.

[0210] In some embodiments, before the second terminal sends the first message to the first terminal, the first terminal may send signaling to the second terminal, where the signaling is used to instruct to activate the second terminal.

[0211] Step S2102: The first terminal sends a first message to the first network element through the access network device.

[0212] In some embodiments, the first network element receives a first message sent by the first terminal through the access network device.

[0213] In each embodiment of the present disclosure, the access network device is used to transparently transmit messages exchanged between the first terminal and the core network device.

[0214] In some embodiments, the first message includes an identifier of the second terminal.

[0215] In some embodiments, the identifier of the second terminal may be at least one of a Subscription Concealed Identifier (SUCI), a 5G Globally Unique Temporary Identity (5G-GUTI), and a Permanent Equipment Identifier (PEI).

[0216] In some embodiments, the identifier of the second terminal is used to retrieve subscription data corresponding to the second terminal from subscription data stored in the second network element.

[0217] In some embodiments, the first message may also include other parameters for registration.

[0218] In some embodiments, the first message is used to request that the second terminal device be connected to the network.

[0219] In some embodiments, the first message is used to request registration of the second terminal in the network.

[0220] In some embodiments, the name of the first message is not limited, and may be, for example, "Access Request", "Registration Request", "Connection Request", etc.

[0221] In some embodiments, the first message may be included in an uplink (UL) non-access stratum (NAS) transport message sent by the first terminal to the first network element through the access network device.

[0222] In some embodiments, the first message may be included in a NAS container.

[0223] Step S2103: The first network element sends a sixth message to the second network element.

[0224] In some embodiments, the second network element receives the sixth message sent by the first network element.

[0225] In some embodiments, the sixth message includes an identifier of the second terminal received by the first network element.

[0226] In some embodiments, the sixth message is used to request to retrieve subscription data (subscription) corresponding to the second terminal from subscription data stored in the second network element.

[0227] In some embodiments, the sixth message is used to request downloading of subscription data corresponding to the second terminal.

[0228] In some embodiments, the subscription data corresponding to the second terminal is used to indicate that the second terminal supports store and forward communication with the first terminal.

[0229] In some embodiments, the subscription data corresponding to the second terminal includes "A-IoT store-and-forward communication allowed".

[0230] In some embodiments, the name of the sixth message is not limited, and it can be, for example, "retrieval request", "user data acquisition request", "contract data retrieval request", etc.

[0231] In some embodiments, the sixth message may be a "Nudm_SDM_Get request" (request).

[0232] Step S2104: The second network element retrieves the subscription data corresponding to the second terminal.

[0233] In some embodiments, the second network element retrieves the subscription data corresponding to the second terminal from the stored subscription data based on the identifier of the second terminal in the received sixth message.

[0234] In some embodiments, the second network element may be a UDM or a UDR.

[0235] In some embodiments, the subscription data corresponding to the second terminal may be first retrieved from the subscription data stored in the UDM.

[0236] In some embodiments, if the contract data corresponding to the second terminal is not retrieved from the contract data stored in the UDM, the contract data corresponding to the second terminal can be retrieved from the contract data stored in the UDR based on the identifier of the second terminal.

[0237] In some embodiments, the subscription data corresponding to the second terminal is used to indicate that the second terminal supports store and forward communication with the first terminal.

[0238] In some embodiments, the subscription data corresponding to the second terminal includes "A-IoT store-and-forward communication allowed".

[0239] In some embodiments, after retrieving the subscription data corresponding to the second terminal, the second network element may send a response message of the sixth message to the first network element, where the response message of the sixth message is used to indicate to the first network element that the second terminal supports storage and forwarding communication with the first terminal.

[0240] In some embodiments, the name of the response message of the sixth message is not limited, and it can be, for example, "retrieval response", "user data acquisition response", "contract data retrieval response", etc.

[0241] In some embodiments, the response message of the sixth message may be "Nudm_SDM_Get response" (response).

[0242] Step S2105: The first network element sends a second message to the first terminal through the access network device.

[0243] In some embodiments, the first terminal receives a second message sent by the first network element through the access network device.

[0244] In some embodiments, the second message is used to indicate authorization of store and forward communication between the second terminal and the first terminal.

[0245] In some embodiments, the name of the second message is not limited, and may be, for example, "Access Response", "Registration Accept", "Connection Response", etc.

[0246] In some embodiments, the second message may be included in a downlink (DL) non-access stratum (NAS) transport message sent by the first network element to the first terminal through the access network device.

[0247] Step S2106: The first terminal sends a second message to the second terminal.

[0248] In some embodiments, the second terminal receives the second message forwarded by the first terminal.

[0249] In some embodiments, the second message is used to indicate authorization of store and forward communication between the second terminal and the first terminal.

[0250] In some embodiments, the name of the second message is not limited, and may be, for example, "Access Response", "Registration Accept", "Connection Response", etc.

[0251] In some embodiments, after receiving the second message, the second terminal may initiate a user plane connection from the second terminal to the network and application. The connection may be a protocol data unit (PDU) session or other type of connection, which is not limited in the present disclosure.

[0252] Step S2107: The first terminal sends a third message to the first network element through the access network device.

[0253] In some embodiments, the first network element receives a third message sent by the first terminal through the access network device.

[0254] In some embodiments, the third message includes an identifier of the first terminal.

[0255] In some embodiments, the identifier of the first terminal may be at least one of a subscriber implicit identifier SUCI, a 5G globally unique temporary identifier 5G-GUTI, and a permanent equipment identifier PEI.

[0256] In some embodiments, the identifier of the first terminal is used to retrieve subscription data corresponding to the first terminal from subscription data stored in the second network element.

[0257] In some embodiments, the third message may also include other parameters used for registration, such as at least one of a registration type and a security parameter.

[0258] In some embodiments, the third message is used to request that the first terminal device be connected to the network.

[0259] In some embodiments, the third message is used to request registration of the first terminal in the network.

[0260] In some embodiments, the name of the first message is not limited, and may be, for example, "access request", "registration request", "connection request", etc.

[0261] In some embodiments, the first message may be included in a UL NAS transmission message sent by the first terminal to the first network element through the access network device.

[0262] In some embodiments, the first message may be included in a NAS container.

[0263] Step S2108: The first network element sends a seventh message to the second network element.

[0264] In some embodiments, the second network element receives the seventh message sent by the first network element.

[0265] In some embodiments, the seventh message includes an identifier of the first terminal received by the first network element.

[0266] In some embodiments, the seventh message is used to request retrieval of subscription data corresponding to the first terminal from subscription data stored in the second network element.

[0267] In some embodiments, the seventh message is used to request downloading of subscription data corresponding to the first terminal.

[0268] In some embodiments, the subscription data corresponding to the first terminal is used to indicate that the first terminal supports store and forward communication with the second terminal.

[0269] In some embodiments, the subscription data corresponding to the first terminal includes "A-IoT store-and-forward communication allowed".

[0270] In some embodiments, the name of the seventh message is not limited, and it can be, for example, "retrieval request", "user data acquisition request", "contract data retrieval request", etc.

[0271] In some embodiments, the seventh message may be a "Nudm_SDM_Get request" (request).

[0272] Step S2109: The second network element retrieves the subscription data corresponding to the first terminal.

[0273] In some embodiments, the second network element retrieves the subscription data corresponding to the first terminal from the stored subscription data based on the identifier of the first terminal in the received seventh message.

[0274] In some embodiments, the second network element may be a UDM or a UDR.

[0275] In some embodiments, the subscription data corresponding to the first terminal may be first retrieved from the subscription data stored in the UDM.

[0276] In some embodiments, if the contract data corresponding to the first terminal is not retrieved from the contract data stored in the UDM, the contract data corresponding to the first terminal can be retrieved from the contract data stored in the UDR based on the identifier of the first terminal.

[0277] In some embodiments, the subscription data corresponding to the first terminal is used to indicate that the first terminal supports store and forward communication with the second terminal.

[0278] In some embodiments, the subscription data corresponding to the first terminal includes "A-IoT store-and-forward communication allowed".

[0279] In some embodiments, after retrieving the subscription data corresponding to the first terminal, the second network element may send a response message of the seventh message to the first network element, where the response message of the seventh message is used to indicate to the first network element that the first terminal supports storage and forwarding communication with the second terminal.

[0280] In some embodiments, the name of the response message of the seventh message is not limited, and it can be, for example, "retrieval response", "user data acquisition response", "contract data retrieval response", etc.

[0281] In some embodiments, the response message of the seventh message may be "Nudm_SDM_Get response" (response).

[0282] Step S2110: The first network element sends a fourth message to the first terminal through the access network device.

[0283] In some embodiments, the first terminal receives a fourth message sent by the first network element through the access network device.

[0284] In some embodiments, the fourth message is used to indicate authorization of store and forward communication between the first terminal and the second terminal.

[0285] In some embodiments, the name of the fourth message is not limited, and it can be, for example, "Access Response", "Registration Accept", "Connection Response", etc.

[0286] In some embodiments, the fourth message may be included in a DLNAS transmission message sent by the first network element to the first terminal through the access network device.

[0287] In some embodiments, the fourth message and the second message may be sent together to the first terminal.

[0288] In some embodiments, the fourth message and the second message may be included together in a DLNAS transmission message sent by the first network element to the first terminal through the access network device.

[0289] In some embodiments, after receiving the fourth message, the first terminal may initiate a protocol data unit (PDU) session establishment process to establish a user plane connection from the first terminal to the UPF.

[0290] In some embodiments, after receiving the fourth message, the first terminal may initiate a user plane connection from the first terminal to the network and application. The connection may be a protocol data unit (PDU) session or other types of connections, which are not limited in the present disclosure.

[0291] Step S2111: The first terminal sends a fifth message to the second terminal.

[0292] In some embodiments, the second terminal receives the fifth message sent by the first terminal.

[0293] In some embodiments, the fifth message is used to instruct the second terminal to perform store and forward communication with the first terminal.

[0294] In some embodiments, the fifth message is used to indicate to the second terminal that the first terminal can perform store and forward communication with the second terminal.

[0295] In some embodiments, the name of the fifth message is not limited, and it can be, for example, "execution instruction", "activation instruction", etc.

[0296] In some embodiments, the fifth message may be sent to the second terminal together with the second message.

[0297] In some embodiments, the fifth message and the second message may be included in an access response message.

[0298] Step S2112: The second terminal sends information to the first terminal.

[0299] In some embodiments, the first terminal receives information sent by the second terminal.

[0300] In some embodiments, the second terminal sends uplink data to the first terminal.

[0301] Step S2113: The first terminal stores the information.

[0302] In some embodiments, the connection between the first terminal and the access network device is unavailable, and the first terminal stores the received information sent by the second terminal.

[0303] Step S2114: The first terminal forwards the information to the access network device.

[0304] In some embodiments, the connection between the first terminal and the access network device is available, and the first terminal sends the information sent by the second terminal that is stored in the first terminal to the access network device.

[0305] In some embodiments, the connection between the first terminal and the access network device is available, the first terminal directly receives information sent by the second terminal, and forwards the information sent by the second terminal to the access network device.

[0306] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0307] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0308] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0309] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0310] The communication method involved in the embodiments of the present disclosure may include at least one of steps 2101 to 2114. For example, steps 2101+2102 may be implemented as an independent embodiment, step 2103 may be implemented as an independent embodiment, step 2104 may be implemented as an independent embodiment, steps 2105+2106 may be implemented as an independent embodiment, step 2107 may be implemented as an independent embodiment, step 2108 may be implemented as an independent embodiment, step 2109 may be implemented as an independent embodiment, step 2110 may be implemented as an independent embodiment, step 2111 may be implemented as an independent embodiment, step 2112 may be implemented as an independent embodiment, steps 2111+2112 may be implemented as an independent embodiment, steps 2112+2113+2114 may be implemented as an independent embodiment, and step 2112+2114 may be implemented as an independent embodiment, etc., but the present invention is not limited thereto.

[0311] In some embodiments, steps 2102 and 2107 may be executed in an exchanged order or simultaneously, and steps 2105 and 2110 may be executed in an exchanged order or simultaneously.

[0312] In some embodiments, steps 2105-2114 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0313] In some embodiments, steps 2107-2114 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0314] In some embodiments, steps 2101-2104 and steps 2110-2114 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0315] In some embodiments, steps 2101-2106 and steps 2111-2114 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0316] In some embodiments, steps 2101-2111 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0317] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0318] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0319] FIG3A is a flow chart of a relay communication method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a relay communication method, which is executed by a first terminal and includes:

[0320] Step S3101: Receive a first message sent by a second terminal.

[0321] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0322] In some embodiments, step S3101 is omitted, and the first terminal 101 autonomously implements the function indicated by the first message, or the above function is default or acquiescent.

[0323] Step S3102: Send a first message to the first network element through the access network device.

[0324] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0325] Optionally, the first message is used by the first network element 1031 to send a sixth message to the second network element 1032. For optional implementations thereof, reference may be made to the optional implementations of step S2103 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be described in detail here.

[0326] Optionally, the identifier of the second terminal in the first message is used by the second network element 1032 to retrieve the subscription data corresponding to the second terminal. For optional implementations, see the optional implementation of step S2104 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0327] Step S3103: Receive a second message sent by the first network element through the access network device.

[0328] The optional implementation of step S3103 can refer to the optional implementation of step S2105 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0329] Step S3104: Send a second message to the second terminal.

[0330] The optional implementation of step S3104 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0331] Step S3105: Send a third message to the first network element through the access network device.

[0332] The optional implementation of step S3105 can refer to the optional implementation of step S2107 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0333] Optionally, the third message is used by the first network element 1031 to send the seventh message to the second network element 1032. For optional implementations, please refer to the optional implementations of step S2108 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be described in detail here.

[0334] Optionally, the identifier of the first terminal in the third message is used by the second network element 1032 to retrieve the subscription data corresponding to the first terminal. For optional implementations, see the optional implementation of step S2109 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0335] Step S3106: Receive a fourth message sent by the first network element through the access network device.

[0336] The optional implementation of step S3106 can refer to the optional implementation of step S2110 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0337] Step S3107: Send a fifth message to the second terminal.

[0338] The optional implementation of step S3107 can refer to the optional implementation of step S2111 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0339] Step S3108: Receive information sent by the second terminal.

[0340] The optional implementation of step S3108 can refer to the optional implementation of step S2112 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0341] Step S3109, store information.

[0342] The optional implementation of step S3109 can refer to the optional implementation of step S2113 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0343] Step S3110: forward information to the access network device.

[0344] The optional implementation of step S3110 can refer to the optional implementation of step S2114 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0345] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3110. For example, steps 3101+3102 can be implemented as an independent embodiment, steps 3101+3102+3103+3104 can be implemented as an independent embodiment, step 3105 can be implemented as an independent embodiment, steps 3105+3106 can be implemented as an independent embodiment, step 3107 can be implemented as an independent embodiment, step 3108 can be implemented as an independent embodiment, step 3106 can be implemented as an independent embodiment, step 3107 can be implemented as an independent embodiment, step 3108 can be implemented as an independent embodiment, steps 3107+3108 can be implemented as an independent embodiment, steps 3108+3109+3110 can be implemented as an independent embodiment, and step 3108+3110 can be implemented as an independent embodiment, etc., but the present invention is not limited thereto.

[0346] In some embodiments, steps 3102 and 3105 may be executed in an exchanged order or simultaneously, and steps 3103 and 3106 may be executed in an exchanged order or simultaneously.

[0347] In some embodiments, step 3107 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0348] In some embodiments, steps 3103-3110 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0349] In some embodiments, steps 3105-3110 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0350] In some embodiments, steps 3101-3102 and steps 3106-3110 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0351] In some embodiments, steps 3101-3104 and steps 3107-3110 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0352] In some embodiments, steps 3101-3107 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0353] FIG3B is a flow chart of a relay communication method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a relay communication method, which is executed by a first terminal and includes:

[0354] Step S3201: Receive a first message sent by a second terminal.

[0355] The optional implementation of step S3201 can refer to step S2101 in Figure 2, the optional implementation of step 3101 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0356] In some embodiments, step S3201 is omitted, and the first terminal 101 autonomously implements the function indicated by the first message, or the above function is default or acquiescent.

[0357] Step S3202: Send a first message to the first network element through the access network device.

[0358] Optional implementations of step S3202 can be found in step S2102 of FIG. 2 , optional implementations of step 3102 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0359] Step S3203: Receive a second message sent by the first network element through the access network device.

[0360] The optional implementation of step S3203 can refer to step S2105 in FIG. 2 , the optional implementation of step 3103 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0361] Step S3204: Send a second message to the second terminal.

[0362] Optional implementations of step S3204 can be found in step S2106 of FIG. 2 , optional implementations of step 3104 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0363] Step S3205: Send a third message to the first network element through the access network device.

[0364] The optional implementation of step S3205 can refer to step S2107 of FIG. 2 , the optional implementation of step 3105 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0365] Step S3206: Receive a fourth message sent by the first network element through the access network device.

[0366] Optional implementations of step S3206 can be found in step S2110 of FIG. 2 , optional implementations of step 3106 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0367] Step S3207: Send a fifth message to the second terminal.

[0368] Optional implementations of step S3207 can be found in step S2111 of FIG. 2 , optional implementations of step 3107 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0369] Step S3208: Receive information sent by the second terminal and forward the information to the access network device.

[0370] The optional implementation of step S3208 can be found in step S2112, step 2113, step 2114 of Figure 2, step 3108, step 3109, and step 3110 of Figure 3A, as well as other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0371] The communication method according to the embodiments of the present disclosure may include at least one of steps S3201 to S3208. For example, steps 3201+3202 may be implemented as an independent embodiment, steps 3201+3202+3203+3204 may be implemented as an independent embodiment, step 3205 may be implemented as an independent embodiment, steps 3205+3206 may be implemented as an independent embodiment, step 3207 may be implemented as an independent embodiment, step 3208 may be implemented as an independent embodiment, steps 3207+3208 may be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.

[0372] In some embodiments, steps 3202 and 3205 may be executed in an exchanged order or simultaneously, and steps 3203 and 3206 may be executed in an exchanged order or simultaneously.

[0373] In some embodiments, step 3207 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0374] In some embodiments, steps 3203-3208 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0375] In some embodiments, steps 3205-3208 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0376] In some embodiments, steps 3201-3202 and steps 3206-3208 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0377] In some embodiments, steps 3201-3204 and steps 3207-3208 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0378] In some embodiments, steps 3201-3207 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0379] FIG3C is a flow chart of a relay communication method according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to a relay communication method, which is executed by a first terminal and includes:

[0380] Step S3301: Receive a first message sent by a second terminal.

[0381] The optional implementation of step S3301 can refer to the optional implementation of step S2101 in Figure 2, step 3101 in Figure 3A, step 3201 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0382] In some embodiments, step S3201 is omitted, and the first terminal 101 autonomously implements the function indicated by the first message, or the above function is default or acquiescent.

[0383] Step S3302: Send a first message to the first network element through the access network device.

[0384] The optional implementation of step S3302 can refer to the optional implementation of step S2102 in Figure 2, step 3102 in Figure 3A, step 3202 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0385] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3301 and S3302. For example, step 3301 may be implemented as an independent embodiment, step 3302 may be implemented as an independent embodiment, steps 3301+3302 may be implemented as independent embodiments, etc., but the present disclosure is not limited thereto.

[0386] FIG4A is a flow chart of a relay communication method according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a relay communication method, which is executed by a second terminal and includes:

[0387] Step S4101: Send a first message to a first terminal.

[0388] The optional implementation of step S4101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0389] Optionally, the first message is sent by the first terminal 101 to the first network element 1031 via the access network device. For optional implementations, please refer to the optional implementations of step S2102 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be described in detail here.

[0390] Optionally, the first message is used by the first network element 1031 to send a sixth message to the second network element 1032. For optional implementations thereof, reference may be made to the optional implementations of step S2103 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be described in detail here.

[0391] Optionally, the identifier of the second terminal in the first message is used by the second network element 1032 to retrieve the subscription data corresponding to the second terminal. For optional implementations, see the optional implementation of step S2104 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0392] Step S4102: Receive a second message forwarded by the first terminal.

[0393] The optional implementation of step S4102 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0394] Optionally, the second message is sent by the first network element 1031 to the first terminal 101 via the access network device. For optional implementations, please refer to the optional implementation of step S2105 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be repeated here.

[0395] Step S4103: Receive the fifth message sent by the first terminal.

[0396] The optional implementation of step S4103 can refer to the optional implementation of step S2111 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0397] Step S4104: Send information to the first terminal.

[0398] The optional implementation of step S4104 can refer to the optional implementation of step S2112 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0399] Optionally, the above information is used by the first terminal 101 to store the information and / or forward the information to the access network device. Its optional implementation method can be found in step S2113 and step 2114 of Figure 2, and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0400] The communication method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4104. For example, step 4101 can be implemented as an independent embodiment, steps 4101+4102 can be implemented as an independent embodiment, step 4103 can be implemented as an independent embodiment, steps 4103+4104 can be implemented as an independent embodiment, step 4104 can be implemented as an independent embodiment, steps 4101+4102+4103+4104 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.

[0401] In some embodiments, step 4103 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0402] FIG4B is a flow chart of a relay communication method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a relay communication method, which is executed by a second terminal and includes:

[0403] Step S4201: Send a first message to a first terminal.

[0404] Optional implementations of step S4201 can be found in step S2101 of FIG. 2 , optional implementations of step 4101 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2 and FIG. 4A , which will not be described in detail here.

[0405] Step S4202: Receive a second message forwarded by the first terminal.

[0406] The optional implementation of step S4202 can refer to step S2106 of FIG. 2 , the optional implementation of step 4102 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2 and FIG. 4A , which will not be described in detail here.

[0407] Step S4203: Send information to the first terminal.

[0408] The optional implementation of step S4203 can refer to step S2112 of FIG. 2 , the optional implementation of step 4104 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2 and FIG. 4A , which will not be described in detail here.

[0409] The communication method according to the embodiments of the present disclosure may include at least one of steps S4201 to S4203. For example, step 4201 may be implemented as an independent embodiment, steps 4201+4202 may be implemented as independent embodiments, step 4203 may be implemented as an independent embodiment, steps 4101+4102+4103 may be implemented as independent embodiments, and so on, but the present invention is not limited thereto.

[0410] In some embodiments, step 4103 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0411] FIG4C is a flow chart of a relay communication method according to an embodiment of the present disclosure. As shown in FIG4C , the embodiment of the present disclosure relates to a relay communication method, which is executed by a second terminal and includes:

[0412] Step S4301: Send a first message to a first terminal.

[0413] The optional implementation of step S4301 can refer to the optional implementation of step S2101 in Figure 2, step 4101 in Figure 4A, step 4201 in Figure 4B, and other related parts in the embodiments involved in Figures 2, 4A, and 4B, which will not be repeated here.

[0414] FIG5A is a flow chart of a relay communication method according to an embodiment of the present disclosure. As shown in FIG5A , the embodiment of the present disclosure relates to a relay communication method, which is executed by a first network element and includes:

[0415] Step S5101: Receive a first message sent by a first terminal through an access network device.

[0416] The optional implementation of step S5101 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0417] Optionally, the first message is sent by the second terminal 102 to the first terminal 101. For optional implementations thereof, reference may be made to the optional implementations of step S2101 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be described in detail here.

[0418] Step S5102: Send a sixth message to the second network element.

[0419] The optional implementation of step S5102 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0420] Optionally, the sixth message is used by the second network element 1032 to retrieve the subscription data corresponding to the second terminal. For optional implementations, see the optional implementations of step S2104 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be described in detail here.

[0421] Step S5103: Send a second message to the first terminal through the access network device.

[0422] The optional implementation of step S5103 can refer to the optional implementation of step S2105 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0423] Optionally, the second message is also sent from the first terminal 101 to the second terminal 102. For optional implementations, please refer to the optional implementations of step S2106 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be described in detail here.

[0424] Step S5104: Receive a third message sent by the first terminal through the access network device.

[0425] The optional implementation of step S5104 can refer to the optional implementation of step S2107 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0426] Step S5105: Send the seventh message to the second network element.

[0427] The optional implementation of step S5105 can refer to the optional implementation of step S2108 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0428] Optionally, the seventh message is used by the second network element 1032 to retrieve the subscription data corresponding to the first terminal. For optional implementations, see the optional implementations of step S2109 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be described in detail here.

[0429] Step S5106: Send a fourth message to the first terminal through the access network device.

[0430] The optional implementation of step S5106 can refer to the optional implementation of step S2110 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0431] In some embodiments, the first network element 1031 is, for example, an AMF.

[0432] The communication method involved in the embodiment of the present disclosure may include at least one of steps S5101 to S5106. For example, steps 5101+5102+5103 may be implemented as an independent embodiment, and steps 5104+5105+5106 may be implemented as an independent embodiment, etc., but the present invention is not limited thereto.

[0433] In some embodiments, steps 5101 and 5104 may be executed in an exchanged order or simultaneously, steps 5102 and 5105 may be executed in an exchanged order or simultaneously, and steps 5103 and 5106 may be executed in an exchanged order or simultaneously.

[0434] In some embodiments, steps 5104-5106 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0435] In some embodiments, steps 5101-5103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0436] FIG5B is a flow chart of a relay communication method according to an embodiment of the present disclosure. As shown in FIG5B , the embodiment of the present disclosure relates to a relay communication method, which is executed by a first network element and includes:

[0437] Step S5201: Receive a first message sent by a first terminal through an access network device.

[0438] The optional implementation of step S5201 can refer to step S2102 in Figure 2, the optional implementation of step 5101 in Figure 5A, and other related parts in the embodiments involved in Figures 2 and 5A, which will not be repeated here.

[0439] Step S5202: Send a sixth message to the second network element.

[0440] The optional implementation of step S5202 can refer to step S2103 in Figure 2, the optional implementation of step 5102 in Figure 5A, and other related parts in the embodiments involved in Figures 2 and 5A, which will not be repeated here.

[0441] In some embodiments, the first network element 1031 is, for example, an AMF.

[0442] The communication method involved in the embodiments of the present disclosure may include at least one of steps S5201 and S5202. For example, step 5201 may be implemented as an independent embodiment, step 5202 may be implemented as an independent embodiment, steps 5201+5202 may be implemented as independent embodiments, etc., but the present disclosure is not limited thereto.

[0443] FIG6A is a flow chart of a relay communication method according to an embodiment of the present disclosure. As shown in FIG6A , the embodiment of the present disclosure relates to a relay communication method, which is executed by a second network element and includes:

[0444] Step S6101: Receive the sixth message sent by the first network element.

[0445] The optional implementation of step S6101 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0446] Optionally, the identifier of the second terminal in the sixth message is included in a first message sent by the first terminal 101 to the first network element 1031 via the access network device. For optional implementations, see the optional implementations of steps S2101 and S2102 in FIG. 2 , and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.

[0447] Step S6102: Retrieve the contract data corresponding to the second terminal.

[0448] The optional implementation of step S6102 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0449] Step S6103: Receive the seventh message sent by the first network element.

[0450] The optional implementation of step S6103 can refer to the optional implementation of step S2108 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0451] Optionally, the identifier of the first terminal in the seventh message is included in a third message sent by the first terminal 101 to the first network element 1031 through the access network device. For optional implementations, see the optional implementations of step S2107 in FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.

[0452] Step S6104: Retrieve the contract data corresponding to the first terminal.

[0453] The optional implementation of step S6104 can refer to the optional implementation of step S2109 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0454] In some embodiments, the second network element 1032 is, for example, a UDM or a UDR.

[0455] The communication method involved in the embodiment of the present disclosure may include at least one of steps S6101 to S6104. For example, steps 6101+6102 may be implemented as independent embodiments, and steps 6103+6104 may be implemented as independent embodiments, etc., but the present invention is not limited thereto.

[0456] In some embodiments, steps 6101 and 6103 may be executed in an exchanged order or simultaneously, and steps 6102 and 6104 may be executed in an exchanged order or simultaneously.

[0457] FIG6B is a flow chart of a relay communication method according to an embodiment of the present disclosure. As shown in FIG6B , the embodiment of the present disclosure relates to a relay communication method, which is executed by a second network element and includes:

[0458] Step S6201: Receive the sixth message sent by the first network element.

[0459] The optional implementation of step S6201 can refer to step S2103 in Figure 2, the optional implementation of step S6101 in Figure 6A, and other related parts in the embodiments involved in Figures 2 and 6A, which will not be repeated here.

[0460] Step S6202: Retrieve the contract data corresponding to the second terminal.

[0461] The optional implementation of step S6202 can refer to step S2104 in Figure 2, the optional implementation of step S6102 in Figure 6A, and other related parts in the embodiments involved in Figures 2 and 6A, which will not be repeated here.

[0462] In some embodiments, the second network element 1032 is, for example, a UDM or a UDR.

[0463] The communication method involved in the embodiments of the present disclosure may include at least one of steps S6201 and S6202. For example, step 6201 may be implemented as an independent embodiment, step 6202 may be implemented as an independent embodiment, steps 6201+6202 may be implemented as independent embodiments, etc., but the present disclosure is not limited thereto.

[0464] FIG7A is an interactive diagram of a relay communication method according to an embodiment of the present disclosure. As shown in FIG7A , the embodiment of the present disclosure relates to a relay communication method, which includes:

[0465] Step S7101: The second terminal sends a first message to the first terminal, where the first message includes an identifier of the second terminal.

[0466] The optional implementation of step S7101 can be found in step 2101 of Figure 2, step 3101 of Figure 3A, the optional implementation of step 4101 of Figure 4A, and other related parts in the embodiments involved in Figures 2, 3, 4, 5, and 6, which will not be repeated here.

[0467] Step S7102: The first terminal sends a first message to the first network element through the access network device.

[0468] The optional implementation of step S7102 can be found in step 2102 of Figure 2, step 3102 of Figure 3A, step 4102 of Figure 4A, the optional implementation of step 5101 of Figure 5A, and other related parts in the embodiments involved in Figures 2, 3, 4, 5, and 6, which will not be repeated here.

[0469] Step S7103: The first network element sends a sixth message to the second network element, where the sixth message includes an identifier of the second terminal.

[0470] The optional implementation of step S7103 can be found in step 2103 of Figure 2, step 5102 of Figure 5A, the optional implementation of step 6101 of Figure 6A, and other related parts in the embodiments involved in Figures 2, 3, 4, 5, and 6, which will not be repeated here.

[0471] In step S7104, the second network element retrieves the subscription data corresponding to the second terminal from the stored subscription data based on the identifier of the second terminal, where the subscription data corresponding to the second terminal is used to indicate that the second terminal supports store and forward communication with the first terminal.

[0472] The optional implementation of step S7104 can be found in step 2104 of Figure 2, the optional implementation of step 6102 of Figure 6A, and other related parts in the embodiments involved in Figures 2, 3, 4, 5, and 6, which will not be repeated here.

[0473] In some embodiments, the above method may include the method described in the above-mentioned embodiments of the communication system side, the first terminal side, the second terminal side, the core network device side, the first network element side, the second network element side, etc., which will not be repeated here.

[0474] FIG7B is an interactive diagram of a relay communication method according to an embodiment of the present disclosure. As shown in FIG7B , the embodiment of the present disclosure relates to a relay communication method, which is executed by a core network device. The core network device 103 includes a first network element 1031 and a second network element 1032. The method includes:

[0475] Step S7201: The first network element sends a sixth message to the second network element, where the sixth message includes an identifier of the second terminal.

[0476] The optional implementation of step S7201 can be found in step 2101 of Figure 2, step 5101 of Figure 5A, the optional implementation of step 6101 of Figure 6A, and other related parts in the embodiments involved in Figures 2, 3, 4, 5, and 6, which will not be repeated here.

[0477] In step S7202, the second network element retrieves the subscription data corresponding to the second terminal from the stored subscription data based on the identifier of the second terminal, where the subscription data corresponding to the second terminal is used to indicate that the second terminal supports store and forward communication with the first terminal.

[0478] The optional implementation of step S7202 can be found in step 2102 of Figure 2, the optional implementation of step 6102 of Figure 6A, and other related parts in the embodiments involved in Figures 2, 3, 4, 5, and 6, which will not be repeated here.

[0479] In some embodiments, the above method may include the method described in the above embodiments on the core network device side, the first network element side, the second network element side, etc., which will not be repeated here.

[0480] FIG8 is a schematic diagram of system interaction of a relay communication method according to an embodiment of the present disclosure. As shown in FIG8 , the embodiment of the present disclosure relates to a relay communication method, which includes at least one of the following steps:

[0481] 1. The UE sends a registration request to the Next Generation Radio Access Network (NG-RAN), including the registration type, UE ID (e.g., SUCI or 5G-GUTI or PEI), and security parameters. The NG-RAN forwards the registration request to the AMF via the N2 link.

[0482] 2. AMF sends a Nudm_SDM_Get request to UDM to retrieve the UE's subscription data, which includes the UE ID received in step 1. If the UE's subscription data is not stored in UDM, UDM can retrieve the UE's subscription data from UDR. UDM sends a Nudm_SDM_Get response to AMF, and the UE's subscription data includes "A-IoT store-and-forward communication allowed".

[0483] 3. After authenticating and authorizing the UE, the AMF sends a Registration Accept to the UE via NG-RAN, which includes the indication “Allow A-IoT store and forward communications”.

[0484] 4. The UE may initiate a PDU session establishment procedure to establish a user plane connection from the UE to the UPF.

[0485] 5. The UE may send radio energy to the A-IoT device and then may send an “active” radio signaling indication to the A-IoT device.

[0486] 6. After the A-IoT device obtains sufficient energy for communication, it sends an access request with a registration request to the AMF through the UE, which may include the ID of the A-IoT device for registration and other parameters.

[0487] 7. The UE sends a UL NAS transport message to the AMF via the RAN, where the registration request from the A-IoT device is included in the NAS container (NAS in NAS).

[0488] 8. AMF sends a Nudm_SDM_Get request to UDM to obtain the contract data of the A-IoT device. The contract data includes the A-IoT device ID received in step 7. If the contract data of the A-IoT device is not stored in UDM, UDM can retrieve the contract data from UDR. UDM sends a Nudm_SDM_Get response to AMF, along with the contract data of the A-IoT device. The contract data includes "Allow A-IoT store and forward communication".

[0489] 9. After authenticating and authorizing the A-IoT device, the AMF sends a DL NAS transport message to the UE, which includes a Registration Accept to the A-IoT device (including "Allow A-IoT Store and Forward Communication") and an "Allow A-IoT Store and Forward Communication" indication to the UE. If the UE receives the "Allow A-IoT Store and Forward Communication" indication in this step and step 2, it means that the UE can perform A-IoT Store and Forward Communication for the A-IoT device.

[0490] 10. The UE forwards the Registration Accept received in step 9 to the A-IoT device in an Access Response, where the Registration Accept includes an indication that "A-IoT Store-and-Forward Communications are Allowed," which indicates that the network authorizes the A-IoT device to perform A-IoT Store-and-Forward communications. The UE may indicate to the A-IoT device that it may perform A-IoT Store-and-Forward communications for the A-IoT device by including this indication in the Access Response message outside the container of the Registration Accept message. The A-IoT device is informed that the network has authorized A-IoT Store-and-Forward communications, and the UE may perform A-IoT Store-and-Forward communications.

[0491] 11. The A-IoT device initiates a user plane connection to the network and application, which can be a PDU session or other type of connection.

[0492] 12. A-IoT devices can send uplink data to UEs. If the UE is able to connect to the network, the uplink data should be forwarded to the network; otherwise, the UE should store the data.

[0493] 13. The UE stores the uplink data and waits for the network connection to be restored.

[0494] 14. When network connectivity is available, the UE shall forward the stored uplink data to the network.

[0495] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0496] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0497] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0498] Figure 9A is a schematic diagram of the structure of a first terminal proposed in an embodiment of the present disclosure. As shown in Figure 9A, the first terminal 9100 may include at least one of: a transceiver module 9101, a processing module 9102, etc. In some embodiments, the transceiver module 9101 is configured to receive a first message sent by a second terminal, the first message including an identifier of the second terminal; and is further configured to send the first message to a first network element via an access network device, the identifier of the second terminal being used to retrieve the subscription data corresponding to the second terminal from the subscription data stored by the second network element, the subscription data corresponding to the second terminal being used to indicate that the second terminal supports store-and-forward communication with the first terminal. Optionally, the transceiver module is configured to execute at least one of the communication steps (e.g., steps 2101, 2102, 2105, 2106, 2107, 2110, 2111, 2112, and 2114, but not limited thereto) performed by the first terminal 101 in any of the above methods, which will not be repeated here. Optionally, the processing module is used to execute at least one of the other steps (such as step 2113, but not limited thereto) performed by the first terminal 101 in any of the above methods, which will not be repeated here.

[0499] Figure 9B is a schematic diagram of the structure of a second terminal proposed in an embodiment of the present disclosure. As shown in Figure 9B, the access network device 9200 may include at least one of: a transceiver module 9201, a processing module 9202, etc. In some embodiments, the transceiver module 9201 is configured to send a first message to the first terminal; the first message is sent by the first terminal to the first network element via the access network device, and the first message includes an identifier of the second terminal. The identifier of the second terminal is used to retrieve the subscription data corresponding to the second terminal from the subscription data stored in the second network element, and the subscription data corresponding to the second terminal is used to indicate that the second terminal supports store and forward communication with the first terminal. Optionally, the transceiver module is configured to execute at least one of the communication steps (such as sending and / or receiving) performed by the second terminal 102 in any of the above methods (for example, steps 2101, 2106, 2111, and 2112, but not limited thereto), which are not further described here. Optionally, the processing module is configured to execute at least one of the other steps performed by the second terminal 102 in any of the above methods, which are not further described here.

[0500] Figure 9C is a schematic diagram of the structure of the first network element proposed in an embodiment of the present disclosure. As shown in Figure 9C, the first network element 9300 may include: at least one of a transceiver module 9301, a processing module 9302, etc. In some embodiments, the transceiver module 9301 is configured to receive a first message sent by a first terminal via an access network device, the first message including an identifier of a second terminal; and is further configured to send a sixth message to a second network element, the sixth message including an identifier of the second terminal, the identifier of the second terminal being used to retrieve subscription data corresponding to the second terminal from subscription data stored in the second network element, the subscription data corresponding to the second terminal being used to indicate that the second terminal supports store-and-forward communication with the first terminal. Optionally, the transceiver module is configured to execute at least one of the communication steps (e.g., steps 2102, 2103, 2105, 2107, 2108, and 2110, but not limited thereto) performed by the first network element 1031 in any of the above methods, which will not be repeated here. Optionally, the above-mentioned processing module is used to execute at least one of the other steps performed by the first network element 1031 in any of the above methods, which will not be repeated here.

[0501] Figure 9D is a schematic diagram of the structure of a second network element proposed in an embodiment of the present disclosure. As shown in Figure 9D, the second network element 9400 may include at least one of a transceiver module 9401 and a processing module 9402. In some embodiments, the transceiver module 9401 is configured to receive a sixth message sent by the first network element, the sixth message including an identifier of the second terminal; the transceiver module 9402 is configured to retrieve the subscription data corresponding to the second terminal from the stored subscription data based on the identifier of the second terminal, the subscription data corresponding to the second terminal indicating that the second terminal supports store-and-forward communication with the first terminal. Optionally, the transceiver module is configured to execute at least one of the communication steps (e.g., steps 2103 and 2108, but not limited thereto) performed by the second network element 1032 in any of the above methods, which are not further described here. Optionally, the processing module is configured to execute at least one of the other steps (e.g., steps 2104 and 2109, but not limited thereto) performed by the second network element 1032 in any of the above methods, which are not further described here.

[0502] Figure 9E is a schematic diagram of the structure of the core network device proposed in an embodiment of the present disclosure. As shown in Figure 9E, the core network device 9500 may include: at least one of a transceiver module 9501, a processing module 9502, etc. In some embodiments, the transceiver module 9501 is used to receive a first message sent by a first terminal through an access network device, the first message including an identifier of a second terminal, the identifier of the second terminal being used to retrieve the subscription data corresponding to the second terminal from the subscription data stored in the core network device, the subscription data corresponding to the second terminal being used to indicate that the second terminal supports storage and forwarding communication with the first terminal. Optionally, the transceiver module is used to execute at least one of the communication steps such as sending and / or receiving executed by the core network device 103 in any of the above methods, which will not be repeated here. Optionally, the processing module is used to execute at least one of the other steps executed by the second terminal 102 in any of the above methods, which will not be repeated here.

[0503] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0504] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0505] Figure 10A is a schematic diagram of the structure of a communication device 10100 proposed in an embodiment of the present disclosure. Communication device 10100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user device, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 10100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0506] As shown in FIG10A , a communication device 10100 includes one or more processors 10101. Processor 10101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control a communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or CU, etc.), execute programs, and process program data. The communication device 10100 is used to perform any of the above methods.

[0507] In some embodiments, the communication device 10100 further includes one or more memories 10102 for storing instructions. Optionally, all or part of the memory 10102 may be located outside the communication device 10100.

[0508] In some embodiments, the communication device 10100 further includes one or more transceivers 10103. When the communication device 10100 includes one or more transceivers 10103, the transceiver 10103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step 2101, step 2102, step 2103, step 2105, step 2106, step 2107, step 2108, step 2110, step 2111, step 2112, and step 2114, but not limited thereto), and the processor 10101 performs at least one of the other steps (for example, step 2104, step 2109, and step 2113, but not limited thereto).

[0509] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0510] In some embodiments, the communication device 10100 may include one or more interface circuits 10104. Optionally, the interface circuit 10104 is connected to the memory 10102. The interface circuit 10104 may be configured to receive signals from the memory 10102 or other devices, or to send signals to the memory 10102 or other devices. For example, the interface circuit 10104 may read instructions stored in the memory 10102 and send the instructions to the processor 10101.

[0511] The communication device 10100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 10100 described in the present disclosure is not limited thereto, and the structure of the communication device 10100 may not be limited to FIG. 10A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0512] 10B is a schematic diagram of the structure of a chip 10200 according to an embodiment of the present disclosure. If the communication device 10100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 10200 shown in FIG10B , but the present disclosure is not limited thereto.

[0513] Chip 10200 includes one or more processors 10201, and chip 10200 is used to execute any of the above methods.

[0514] In some embodiments, chip 10200 further includes one or more interface circuits 10202. Optionally, interface circuit 10202 is connected to memory 10203. Interface circuit 10202 can be used to receive signals from memory 10203 or other devices, or to send signals to memory 10203 or other devices. For example, interface circuit 10202 can read instructions stored in memory 10203 and send the instructions to processor 10201.

[0515] In some embodiments, the interface circuit 10202 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step 2101, step 2102, step 2103, step 2105, step 2106, step 2107, step 2108, step 2110, step 2111, step 2112, step 2114, but not limited to these), and the processor 10201 executes at least one of the other steps (for example, step 2104, step 2109, step 2113, but not limited to these).

[0516] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0517] In some embodiments, the chip 10200 further includes one or more memories 10203 for storing instructions. Alternatively, all or part of the memories 10203 may be outside the chip 10200.

[0518] The present disclosure also provides a storage medium having instructions stored thereon. When the instructions are executed on the communication device 10100, the communication device 10100 is caused to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0519] The present disclosure also provides a program product, which, when executed by the communication device 10100, enables the communication device 10100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0520] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A relay communication method, characterized in that: The method is performed by a first terminal, and includes: receiving a first message sent by a second terminal, where the first message includes an identifier of the second terminal; The first message is sent to the first network element through the access network device, and the identifier of the second terminal is used to retrieve the subscription data corresponding to the second terminal from the subscription data stored in the second network element, and the subscription data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

2. The method according to claim 1, characterized in that: The method further comprises: receiving a second message sent by the first network element through an access network device, where the second message is used to indicate authorization for store-and-forward communication between the second terminal and the first terminal; Sending the second message to the second terminal.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: Sending a third message to the first network element through the access network device, the third message including the identifier of the first terminal, the identifier of the first terminal being used to retrieve subscription data corresponding to the first terminal from the subscription data stored in the second network element, the subscription data corresponding to the first terminal being used to indicate that the first terminal supports store and forward communication with the second terminal; A fourth message is received, which is sent by the first network element through an access network device, and is used to indicate authorization of storage and forwarding communication between the first terminal and the second terminal.

4. The method according to claim 3, characterized in that The method further comprises: A fifth message is sent to the second terminal, where the fifth message is used to instruct the second terminal to perform store-and-forward communication with the first terminal.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: The connection between the first terminal and the access network device is unavailable, and the information sent by the second terminal is received and stored.

6. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: The connection between the first terminal and the access network device is available, and the information sent by the second terminal and stored by the first terminal is sent to the access network device; and / or, Receive information sent by the second terminal, and forward the information sent by the second terminal to the access network device.

7. A relay communication method, characterized in that: The method is performed by a second terminal, and the method includes: Sending a first message to a first terminal; The first message is used to be sent by the first terminal to the first network element through the access network device. The first message includes an identifier of the second terminal. The identifier of the second terminal is used to retrieve the contract data corresponding to the second terminal from the contract data stored in the second network element. The contract data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

8. The method according to claim 7, characterized in that The method further comprises: A second message sent by the first terminal is received, where the second message is sent by the first network element to the first terminal through an access network device, and the second message is used to indicate authorization of storage and forwarding communication between the second terminal and the first terminal.

9. The method according to claim 8, characterized in that The method further comprises: A fifth message sent by the first terminal is received, where the fifth message is used to instruct the second terminal to perform store-and-forward communication with the first terminal.

10. The method according to any one of claims 7 to 9, characterized in that: The method further comprises: The connection between the first terminal and the access network device is unavailable, information is sent to the first terminal, and the information is stored in the first terminal.

11. The method according to any one of claims 7 to 9, characterized in that: The method further comprises: The connection between the first terminal and the access network device is available, and the information stored in the first terminal is forwarded by the first terminal to the access network device; and / or, The connection between the first terminal and the access network device is available, information is sent to the first terminal, and the information is forwarded by the first terminal to the access network device.

12. A relay communication method, characterized in that: The method is performed by a first network element, and the method includes: Receiving a first message sent by a first terminal through an access network device, where the first message includes an identifier of a second terminal; A sixth message is sent to the second network element, wherein the sixth message includes an identifier of the second terminal, and the identifier of the second terminal is used to retrieve the contract data corresponding to the second terminal from the contract data stored in the second network element, and the contract data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

13. The method according to claim 12, characterized in that The method further comprises: A second message is sent to the first terminal through an access network device, the second message is sent from the first terminal to the second terminal, and the second message is used to indicate authorization for storage and forwarding communication between the second terminal and the first terminal.

14. The method according to claim 1 or 2, characterized in that: The method further comprises: receiving a third message sent by the first terminal through an access network device, where the third message includes an identifier of the first terminal; sending a seventh message to the second network element, the seventh message including an identifier of the first terminal, the identifier of the first terminal being used to retrieve subscription data corresponding to the first terminal from subscription data stored in the second network element, the subscription data corresponding to the first terminal being used to indicate that the first terminal supports store and forward communication with the second terminal; A fourth message is sent to the first terminal through the access network device, where the fourth message is used to indicate authorization for store-and-forward communication between the first terminal and the second terminal.

15. A relay communication method, characterized in that: The method is performed by a second network element, and the method includes: receiving a sixth message sent by the first network element, where the sixth message includes an identifier of the second terminal; Based on the identifier of the second terminal, searching for subscription data corresponding to the second terminal in the stored subscription data, where the subscription data corresponding to the second terminal is used to indicate that the second terminal supports store and forward communication with the first terminal; The identifier of the second terminal is included in a first message sent by the first terminal to the first network element through the access network device.

16. The method according to claim 15, characterized in that The method further comprises: receiving a seventh message sent by the first network element, where the seventh message includes an identifier of the first terminal; Based on the identifier of the first terminal, searching for subscription data corresponding to the first terminal in the stored subscription data, where the subscription data corresponding to the first terminal is used to indicate that the first terminal supports store and forward communication with the second terminal; The identifier of the first terminal is included in a third message sent by the first terminal to the first network element through the access network device.

17. A relay communication method, characterized in that: The method is performed by a core network device, and the method includes: Receive a first message sent by a first terminal through an access network device, where the first message includes an identifier of a second terminal, where the identifier of the second terminal is used to retrieve subscription data corresponding to the second terminal from subscription data stored in a core network device, where the subscription data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

18. The method according to claim 17, characterized in that The method further comprises: A second message is sent to the first terminal through an access network device, the second message is sent from the first terminal to the second terminal, and the second message is used to indicate authorization for storage and forwarding communication between the second terminal and the first terminal.

19. The method according to claim 17 or 18, characterized in that The method further comprises: receiving a third message sent by the first terminal through the access network device, the third message including an identifier of the first terminal, the identifier of the first terminal being used to retrieve subscription data corresponding to the first terminal from subscription data stored in the core network device, the subscription data corresponding to the first terminal being used to indicate that the first terminal supports store and forward communication with the second terminal; A fourth message is sent to the first terminal through the access network device, the fourth message is sent by the first terminal to the second terminal, and the fourth message is used to indicate authorization for storage and forwarding communication between the first terminal and the second terminal.

20. A relay communication method, characterized in that: The method comprises: The first network element sends a sixth message to the second network element, where the sixth message includes an identifier of the second terminal; The second network element retrieves, based on the identifier of the second terminal, subscription data corresponding to the second terminal from the stored subscription data, where the subscription data corresponding to the second terminal is used to indicate that the second terminal supports store and forward communication with the first terminal; The identifier of the second terminal is included in a first message sent by the first terminal to the first network element through the access network device.

21. The method according to claim 20, characterized in that The method further comprises: A seventh message sent by the first network element to the second network element, the seventh message including an identifier of the first terminal; The second network element retrieves the subscription data corresponding to the first terminal from the stored subscription data based on the identifier of the first terminal, The subscription data corresponding to the first terminal is used to indicate that the first terminal supports store-and-forward communication with the second terminal; The identifier of the first terminal is included in a third message sent by the first terminal to the first network element through the access network device.

22. A first terminal, characterized in that: The first terminal includes: a transceiver module, configured to receive a first message sent by a second terminal, wherein the first message includes an identifier of the second terminal; The transceiver module is also used to send the first message to the first network element through the access network device. The identifier of the second terminal is used to retrieve the contract data corresponding to the second terminal from the contract data stored in the second network element. The contract data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

23. A second terminal, characterized in that: The second terminal includes: A transceiver module, configured to send a first message to a first terminal; The first message is used to be sent by the first terminal to the first network element through the access network device. The first message includes an identifier of the second terminal. The identifier of the second terminal is used to retrieve the contract data corresponding to the second terminal from the contract data stored in the second network element. The contract data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

24. A first network element, characterized in that: The first network element includes: A transceiver module, configured to receive a first message sent by a first terminal through an access network device, wherein the first message includes an identifier of a second terminal; The transceiver module is also used to send a sixth message to the second network element, and the sixth message includes an identifier of the second terminal. The identifier of the second terminal is used to retrieve the contract data corresponding to the second terminal in the contract data stored in the second network element, and the contract data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

25. A second network element, characterized in that: The second network element includes: A transceiver module, configured to receive a sixth message sent by the first network element, wherein the sixth message includes an identifier of the second terminal; a processing module, configured to retrieve, based on the identifier of the second terminal, subscription data corresponding to the second terminal from the stored subscription data, where the subscription data corresponding to the second terminal is used to indicate that the second terminal supports store-and-forward communication with the first terminal; The identifier of the second terminal is included in a first message sent by the first terminal to the first network element through the access network device.

26. A core network device, characterized in that: The core network equipment includes: A transceiver module is used to receive a first message sent by a first terminal through an access network device, wherein the first message includes an identifier of a second terminal, and the identifier of the second terminal is used to retrieve contract data corresponding to the second terminal from contract data stored in the core network device, and the contract data corresponding to the second terminal is used to indicate that the second terminal supports storage and forwarding communication with the first terminal.

27. A communication device comprising: one or more processors; The communication device is used to execute the relay communication method as described in any one of claims 1-19.

28. A communication system, characterized in that: include: A first terminal, configured to implement the relay communication method according to any one of claims 1 to 6; A second terminal, configured to implement the relay communication method according to any one of claims 7 to 11; A core network device, configured to implement the relay communication method described in any one of claims 17-19.

29. The system according to claim 28, characterized in that The system further comprises: A first network element, configured to implement the relay communication method according to any one of claims 12 to 14; The second network element is configured to implement the relay communication method according to any one of claims 15-16.

30. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device executes the relay communication method as described in any one of claims 1-6, 7-11, 12-14, 15-16, or 17-19.

Images