Device registration method, first device, second device and network device

Abstract

The present disclosure relates to a device registration method, a second device, a first device and a network device. The device registration method is executed by a first device, the first device comprises a relay node or an auxiliary node, and the method comprises: determining a first request, the first request being used for requesting a network device to carry out a registration process of a second device; and sending the first request to the network device. The present disclosure improves the registration convenience, and can effectively solve registration problems under a complex topological structure.

Description

Device registration method, first device, second device and network device Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a device registration method, a first device, a second device, and a network device. Background Art

[0002] The Internet of Things is an extension and expansion of the Internet. It combines various information sensing devices with the Internet to form a huge network, realizing the interconnection of people, machines and things at any time and any place.

[0003] The existing registration process supports the first request initiated by the IoT device, where the IoT device directly sends the first request to the network device.

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure provide a device registration method, a first device, a second device, and a network device.

[0006] According to a first aspect of an embodiment of the present disclosure, a device registration method is provided, which is performed by a first device, where the first device includes a relay node or an auxiliary node. The method includes:

[0007] Determining a first request, the first request being used to request registration of a second device in a network;

[0008] The first request is sent to the network device.

[0009] In the embodiment of the present disclosure, a first request is determined by a first device, and the first request is used to request registration of a second device in the network. When the second device communicates with a network device through the first device, the first device assists the second device in performing the registration process, thereby improving the convenience of registration and effectively dealing with registration problems under complex topology structures.

[0010] According to a second aspect of an embodiment of the present disclosure, a device registration method is provided, which is performed by a second device. The method includes:

[0011] sending a second request to the first device;

[0012] The second request instructs the first device to send a first request to the network device, where the first request is used to request registration of the second device in the network;

[0013] The first device includes a relay node or an assisting node.

[0014] In the embodiment of the present disclosure, the second device sends a second request to the first device, and the second request instructs the first device to send a first request to the network device. The first request is used to request registration of the second device in the network. When the second device communicates with the network device through the first device, the first device assists the second device in the registration process, thereby improving the convenience of registration and effectively dealing with registration problems under complex topology structures.

[0015] According to a third aspect of an embodiment of the present disclosure, a device registration method is provided, which is executed by a network device. The method includes:

[0016] receiving a first request sent by a first device, where the first request is used to request registration of a second device in a network;

[0017] The first device includes a relay node or an auxiliary node.

[0018] In the embodiment of the present disclosure, a network device receives a first request sent by a first device, and the first request is used to request registration of a second device in the network. This implements a new registration process in which the network device directly receives the first request from the second device. The first device assists the second device in performing the registration process, thereby improving the convenience of registration and effectively addressing registration issues under complex topology structures.

[0019] According to a fourth aspect of the embodiments of the present disclosure, a device registration method is proposed, which is applied to a communication system. The method includes:

[0020] The second device sends a second request to the first device;

[0021] The first device sends a first request to the network device according to the second request;

[0022] The network device obtains the first request;

[0023] Wherein, the first device includes a relay node device or an auxiliary node device;

[0024] The first request is used to request registration of the second device in the network,

[0025] The second request is used by the first device to send the first request to the network device

[0026] According to a fifth aspect of an embodiment of the present disclosure, a first device is provided. The first device includes a relay node or an auxiliary node. The first device includes:

[0027] a processing module configured to determine a first request for registering a second device in a network;

[0028] A transceiver module is used to send the first request to the network device.

[0029] According to a sixth aspect of an embodiment of the present disclosure, a second device is provided, including:

[0030] a transceiver module, configured to send a second request to the first device;

[0031] The second request instructs the first device to send a first request to the network device, where the first request is used to request registration of the second device in the network;

[0032] The first device includes a relay node or an assisting node.

[0033] According to a seventh aspect of an embodiment of the present disclosure, a network device is provided, including:

[0034] a transceiver module, configured to receive a first request sent by a first device, wherein the first request is used to request registration of a second device in a network;

[0035] The first device includes a relay node or an auxiliary node.

[0036] According to an eighth aspect of an embodiment of the present disclosure, a communication system is proposed, including a first device, a second device and a network device, wherein the first device is configured to implement the device registration method described in the first aspect, the second device is configured to implement the device registration method described in the second aspect, and the network device is configured to implement the device registration method described in the third aspect.

[0037] According to a ninth aspect of an embodiment of the present disclosure, a storage medium is proposed. When the instruction is executed on a communication device, the communication device executes the device registration method as described in the first, second or third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0039] FIG1A is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0040] FIG1B is a schematic diagram of a topological structure provided according to an embodiment of the present disclosure;

[0041] FIG1C is a schematic diagram of another topological structure provided according to an embodiment of the present disclosure;

[0042] FIG1D is a schematic diagram of a registration management process of a user equipment UE according to the related art;

[0043] FIG2 is an interactive diagram illustrating a device registration method according to an embodiment of the present disclosure;

[0044] FIG3A is a flow chart illustrating a device registration method according to an embodiment of the present disclosure;

[0045] FIG3B is a flow chart of a device registration method according to an embodiment of the present disclosure;

[0046] FIG3C is a flow chart illustrating a device registration method according to an embodiment of the present disclosure;

[0047] FIG3D is a flow chart illustrating a device registration method according to an embodiment of the present disclosure;

[0048] FIG4A is a flow chart illustrating a device registration method according to an embodiment of the present disclosure;

[0049] FIG4B is a flow chart illustrating a device registration method according to an embodiment of the present disclosure;

[0050] FIG4C is a flow chart illustrating a device registration method according to an embodiment of the present disclosure;

[0051] FIG5A is a flow chart illustrating a method for registering a device according to an embodiment of the present disclosure;

[0052] FIG5B is a flow chart of a device registration method according to an embodiment of the present disclosure;

[0053] FIG6 is an interactive diagram illustrating a device registration method according to an embodiment of the present disclosure;

[0054] FIG7A is a schematic structural diagram of a first device proposed in an embodiment of the present disclosure;

[0055] FIG7B is a schematic structural diagram of a second device proposed in an embodiment of the present disclosure;

[0056] FIG7C is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure;

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

[0058] FIG8B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0059] The embodiments of the present disclosure provide a device registration method, a first device, a second device, and a network device.

[0060] In a first aspect, an embodiment of the present disclosure provides a device registration method, which is performed by a first device, where the first device includes a relay node or an auxiliary node. The method includes:

[0061] Determining a first request, wherein the first request is for requesting registration of a second device in a network;

[0062] The first request is sent to the network device.

[0063] In the above embodiment, the first request is determined by the first device, and the first request is used to request registration of the second device in the network. When the second device communicates with the network device through the first device, the first device assists the second device in the registration process, thereby improving the convenience of registration and effectively dealing with registration problems under complex topology structures.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, the first request includes at least one of the following parameters:

[0065] 5GS mobile identity, the fifth generation mobile communication technology system;

[0066] 5GS registration type;

[0067] the capabilities of the second device;

[0068] Preferred network behavior.

[0069] In the above embodiment, the 5GS mobile identity can indicate the unique identity of the second device in the network. The role of the 5GS registration type is to enable the network device to provide a targeted registration process based on the registration type. The capability of the second device included in the first request can help the first device determine the method of assisting the second device in registering. It is also beneficial to determine the transmission method with the second device and improve the transmission stability.

[0070] In conjunction with some embodiments of the first aspect, in some embodiments, the capability of the second device includes at least one of the following:

[0071] Energy storage capability, signal generation capability, data processing capability, type of second device, supported protocol stack, supported topology type, supported signal type, fifth generation mobile communication technology mobility management 5GMM capability, network capability of S1 interface, security capability and unique identification ID of radio capability.

[0072] In the above embodiment, each capability is helpful to determine a feasible topology structure and a suitable transmission mode of the second device, thereby improving transmission stability.

[0073] In conjunction with some embodiments of the first aspect, in some embodiments, before sending the first request to the network device, the method further includes:

[0074] A second request sent by the second device is received, where the second request instructs the first device to send the first request to a network device.

[0075] In the above embodiment, before sending the first request, the first device also receives a second request sent by the second device. The second request at least causes the first device to send the first request to the network device, so that the first device responds to the second request and triggers the process of sending the first request.

[0076] In conjunction with some embodiments of the first aspect, in some embodiments, the second request includes at least one of the following:

[0077] 5GS mobile identity, the fifth generation mobile communication technology system;

[0078] 5GS registration type;

[0079] the capabilities of the second device;

[0080] preferred network behavior;

[0081] Auxiliary method.

[0082] In the above embodiment, the parameters in the second request include the parameters in the first request, so that the first device can generate the first request according to the second request when needed, and can also include an auxiliary method, so that the first device can assist the second device in registering according to the auxiliary method in the second request.

[0083] In conjunction with some embodiments of the first aspect, in some embodiments, determining the first request includes:

[0084] determining the first request according to at least one of the second request and an auxiliary manner;

[0085] The assistance mode is a mode in which the network device assists the second device in registering in the network.

[0086] In the above embodiment, the first request is determined by at least one of the second request and the auxiliary manner, which improves the flexibility of determining the first request.

[0087] In conjunction with some embodiments of the first aspect, in some embodiments, determining the first request according to at least one of the second request and the auxiliary manner includes:

[0088] The second request includes the first request, and the first request is obtained from the second request;

[0089] The second request does not include the first request, and the first request is generated according to the second request;

[0090] The auxiliary mode is the first mode, obtaining the first request from the second request;

[0091] The auxiliary mode is the second mode, generating the first request according to the second request;

[0092] The first manner is as follows: the second request includes the first request, and the first device sends the first request in the second request to the network device;

[0093] The second manner is: the second request does not include the first request, and the first device generates and sends the first request on behalf of the second device.

[0094] In the above embodiments, the first request can be determined by determining whether the second request includes the first request, or by whether the auxiliary mode is the first mode or the second mode, which reflects the multi-selectivity of the present disclosure in determining the first request.

[0095] In conjunction with some embodiments of the first aspect, in some embodiments, the assistance mode is determined by the following method:

[0096] Pre-configured;

[0097] The second request indicates an auxiliary mode, or

[0098] The method is determined according to a capability of at least one of the first device and the second device.

[0099] In the above embodiment, three methods for determining the auxiliary mode are provided, for example, it can be pre-configured, it can be indicated by the second device in the second request, or it can be determined based on the capabilities of the first device and the second device. The embodiment of the present disclosure does not limit whether the auxiliary mode is determined by the first device or the second device, reflecting the multi-selectivity of the present disclosure in determining the auxiliary mode.

[0100] In conjunction with some embodiments of the first aspect, in some embodiments, the assistance mode is determined according to capabilities of the first device and the second device, and determining the first request further includes:

[0101] and determining the capabilities of each other with the second device.

[0102] In the above embodiment, the first device and the second device determine each other's capabilities, so that the first device can determine at least one of the auxiliary mode and the topology type, and the second device can also determine at least one of the auxiliary mode and / or the topology type, laying the foundation for the subsequent determination of the auxiliary mode.

[0103] In conjunction with some embodiments of the first aspect, in some embodiments, sending the first request to the network device further includes:

[0104] A first message sent by the network device is received, where the first message is used to instruct the network to accept registration of the second device.

[0105] In the above embodiment, the first device receives a first message sent by the network device, where the first message instructs the network to accept the registration of the second device, so that the first device knows the registration progress.

[0106] In conjunction with some embodiments of the first aspect, in some embodiments, receiving a first message sent by a network device further includes:

[0107] Sending the first message to the second device; or

[0108] A second message is generated according to the first message, and the second message is sent to the second device, where the second message indicates that the network accepts registration of the second device.

[0109] In some embodiments, the first device can directly send the first message to the second device, or modify the first message to generate a second message, such as adding or deleting some parameters, and send the second message to the second device so that the second device can perform related operations of device registration, reflecting the diversity of registration methods. In conjunction with some embodiments of the first aspect, in some embodiments, the sending of the first request to the network device further includes:

[0110] A third message is sent to the network device, where the third message indicates that the second device has completed registration in the network.

[0111] In the above embodiment, the third message is sent to the network device so that the network device knows that the second device has completed the device registration, thereby ending the registration process.

[0112] In conjunction with some embodiments of the first aspect, in some embodiments, the sending of the third message to the network device also includes:

[0113] generating the third message according to the first message;

[0114] receiving a third message sent by the second device; or

[0115] receiving a fourth message sent by the second device, and generating the third message according to the fourth message;

[0116] The fourth message indicates that the second device has completed registration in the network.

[0117] In the above embodiment, after the first device receives the first message, it can directly generate a third message to return to the network device, without the need for the second device to instruct the second device to complete registration in the network, which can improve registration efficiency. In addition, the first device can also receive the third message sent by the second device and forward the third message directly to the network device, or generate a third message based on the received fourth message, such as adding or deleting parameters in the fourth message. The embodiment of the present application realizes the diversity of instructing the second device to complete registration in the network.

[0118] In a second aspect, an embodiment of the present disclosure provides a device registration method, which is performed by a second device and includes:

[0119] sending a second request to the first device;

[0120] The second request instructs the first device to send a first request to the network device, where the first request is used to register the second device in the network;

[0121] The first device includes at least one of a relay node and an assist node.

[0122] In the above embodiment, the second device sends a second request to the first device, and the second request instructs the first device to send a first request to the network device. The first request is used to request registration of the second device in the network. When the second device communicates with the network device through the first device, the first device assists the second device in the registration process, thereby improving the convenience of registration and effectively dealing with registration problems under complex topology structures.

[0123] In conjunction with some embodiments of the second aspect, in some embodiments, before sending the second request to the first device, the method further includes:

[0124] Determine the assistance method;

[0125] A second request corresponding to the auxiliary mode is generated.

[0126] In the above embodiment, the second device determines the assistance mode and generates the second request corresponding to the assistance mode, thereby laying a foundation for the first device to determine the first request using the same assistance mode.

[0127] In conjunction with some embodiments of the second aspect, in some embodiments, the assistance mode is determined by the following method:

[0128] Pre-configured; or

[0129] The method is determined according to a capability of at least one of the first device and the second device.

[0130] In conjunction with some embodiments of the second aspect, in some embodiments, the capability of the second device includes at least one of the following:

[0131] Energy storage capability, signal generation capability, data processing capability, type of second device, supported protocol stack, supported topology type, supported signal type, 5GMM capability, network capability of S1 interface, security capability and radio capability ID.

[0132] In conjunction with some embodiments of the second aspect, in some embodiments, the assistance mode is determined according to capabilities of the first device and the second device, and determining the assistance mode also includes:

[0133] and determining capabilities of each other with the first device.

[0134] With reference to some embodiments of the second aspect, in some embodiments, the auxiliary manner is a first manner, and the second request corresponding to the first manner includes the first request;

[0135] The auxiliary mode is a second mode, and a second request corresponding to the second mode includes parameters used to generate the first request;

[0136] The first manner is: the second request includes the first request, and the first device sends the first request included in the second request to the network device;

[0137] The second manner is: the second request does not include the first request, and the first device generates and sends the first request on behalf of the second device.

[0138] In conjunction with some embodiments of the second aspect, in some embodiments, sending the second request to the first device further includes:

[0139] sending the third message to the first device;

[0140] sending the third message to the network device; or

[0141] Sending a fourth message to the first device;

[0142] The third message and the fourth message both indicate that the second device has completed registration in the network, and the fourth message is used to generate the third message.

[0143] In conjunction with some embodiments of the second aspect, in some embodiments, sending the third message or the fourth message also includes:

[0144] receiving a first message sent by the network device;

[0145] receiving the first message sent by the first device; or

[0146] receiving a second message sent by the first device;

[0147] The first message and the second message both indicate that the network accepts the registration of the second device, and the second message is generated by the first device according to the first message.

[0148] In conjunction with some embodiments of the second aspect, in some embodiments, sending the second request to the first device includes:

[0149] In response to a trigger by a third device, sending the second request;

[0150] The third device includes at least one of the first device, a network device, and a third-party device.

[0151] In a third aspect, an embodiment of the present disclosure provides a device registration method, which is executed by a network device and includes:

[0152] receiving a first request sent by a first device, where the first request is used to request registration of a second device in a network;

[0153] The first device includes at least one of a relay node and an auxiliary node.

[0154] In conjunction with some embodiments of the third aspect, in some embodiments, receiving a first request sent by a first device further includes:

[0155] A first message is sent to at least one of the first device and the second device, where the first message is used to indicate that the network accepts registration of the second device.

[0156] In conjunction with some embodiments of the third aspect, in some embodiments, sending a first message to at least one of the first device and the second device further includes:

[0157] receiving a third message sent by the first device; or

[0158] receiving a third message sent by the second device;

[0159] The third message indicates that the second device has completed registration in the network.

[0160] In a fourth aspect, an embodiment of the present disclosure provides a device registration method, which is applied to a communication system. The method includes:

[0161] The second device sends a second request to the first device;

[0162] The first device sends a first request to the network device according to the second request;

[0163] The network device obtains the first request;

[0164] wherein the first device comprises at least one of a relay node and an auxiliary node;

[0165] The first request is used to request registration of the second device in the network;

[0166] The second request is used by the first device to send the first request to the network device.

[0167] In a fifth aspect, an embodiment of the present disclosure provides a first device, the first device including at least one of a relay node and an auxiliary node, the first device including:

[0168] a processing module, configured to determine a first request, wherein the first request is configured to request registration of a second device in a network;

[0169] A transceiver module is used to send the first request to the network device.

[0170] In a sixth aspect, an embodiment of the present disclosure provides a second device, including:

[0171] a transceiver module, configured to send a second request to the first device;

[0172] The second request instructs the first device to send a first request to the network device, where the first request is used to request registration of the second device in the network;

[0173] The first device includes at least one of a relay node and an assist node.

[0174] In a seventh aspect, an embodiment of the present disclosure provides a network device, including:

[0175] a transceiver module, configured to receive a first request sent by a first device, wherein the first request is used to request registration of a second device in a network;

[0176] The first device includes at least one of a relay node and an auxiliary node.

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

[0178] In a ninth 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 optional implementation of the first aspect, the second aspect or the third aspect.

[0179] In a tenth 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 optional implementation manner of the first aspect, the second aspect or the third aspect.

[0180] In an eleventh aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first aspect, the second aspect, or the third aspect.

[0181] In a twelfth aspect, an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first aspect, the second aspect, or the third aspect.

[0182] It is understandable that the first device, second device, network device, communication system, storage medium, program product, computer program, chip, or chip system described above are all used to perform 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.

[0183] The present disclosure provides a device registration method, a first device, a second device, and a network device. In some embodiments, the terms "device registration method" and "information processing method" and "communication method" are interchangeable; the terms "device registration device" and "information processing device" and "communication device" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

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

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

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

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

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

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

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

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

[0192] 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 by 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.

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

[0194] In some embodiments, terms such as "time / frequency" and "time / frequency domain" refer to the time domain and / or the frequency domain.

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

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

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

[0198] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0199] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / 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)" and the like may be used interchangeably.

[0200] In some embodiments, the terms "terminal", "terminal device", "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. can be used interchangeably.

[0201] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0202] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

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

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

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

[0206] FIG1A is a schematic diagram illustrating an architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1A , a communication system 100 includes a second device 101 , a first device 102 , and a network device 103 .

[0207] In some embodiments, the second device may be an Internet of Things device.

[0208] In some embodiments, the second device may be an ambient IoT device. An ambient IoT device refers to an IoT device that supports ambient power, is powered by energy harvesting, and is either battery-free or has limited energy storage capacity (e.g., using capacitors), providing a promising solution to meet the above-mentioned unmet needs. It can communicate without a traditional power source and / or avoid human intervention for charging or replacement. It has the characteristics of low power consumption and low complexity, very small size, and longer life cycle. An ambient IoT device can be maintenance-free (e.g., no human intervention required) and have a long service life (e.g., more than 10 years).

[0209] In some embodiments, ambient IoT devices use energy harvested from wireless radio waves or any other form of energy available in a specific use case. For example, in some scenarios, ambient IoT devices can harvest energy from radio waves, which may originate from a 5G NR network entity or a user device. In other scenarios, ambient IoT devices can harvest energy from solar energy, light, motion / vibration, heat, pressure, or any other source of energy.

[0210] In some embodiments, the first device 102 may be an assisting node or a relay node. The assisting node or the relay node may be one or more base stations, terminals, relays, integrated access backhaul (IAB), etc.

[0211] In some embodiments, the network device 103 may include an access network device and a core network device.

[0212] In some embodiments, the access network device 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.

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

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

[0215] In some embodiments, the core network device may be a single device, or may be multiple devices or a group of devices. 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).

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

[0217] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or a portion thereof, but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system may include all or part of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities may be 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.

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

[0219] The embodiments of the present disclosure define connection topologies for the second device. In all of these topologies, carriers from other nodes inside or outside the topology can be provided to the second device. The links in each topology can be bidirectional or unidirectional.

[0220] Base stations, IoT devices, auxiliary nodes, or relay nodes can be multiple base stations or IoT devices, respectively. A mixed indoor and outdoor deployment of such nodes is considered a network implementation option. The potential impact on device or node complexity needs to be considered. This does not imply the presence of multiple auxiliary or relay nodes in the connectivity topology.

[0221] Please refer to Figure 1B, which exemplifies a topology provided by an embodiment of the present disclosure. As shown in the figure, a relay node is located between the second device and the base station, enabling bidirectional communication between the second device and the relay node. In this topology, the relay node can be a relay capable of implementing the Internet of Things, an IAB node, a UE, a repeater, etc. The relay node transmits information between the base station and the second device.

[0222] Please refer to Figure 1C, which exemplifies another topology provided by an embodiment of the present disclosure. As shown in the figure, the second device sends data / signaling to the base station and receives data / signaling from the auxiliary node; or the second device receives data / signaling from the base station and sends data / signaling to the auxiliary node. In this topology, the auxiliary node can be a relay, IAB, UE, repeater, etc. that can implement the Internet of Things.

[0223] Please refer to FIG. 1D , which exemplarily shows a schematic diagram of a UE registration management process in the related art. As shown in the figure, the following steps are included:

[0224] 1. The UE sends a Registration Request to the (R)AN.

[0225] 2. Select a new Access and Mobility Management Function (AMF) network element;

[0226] 3. (R)AN sends a registration request to the new AMF network element;

[0227] 4. The new AMF network element initiates the UE context transfer service operation Namf_Communication_UE ContextTranfer to the old AMF network element;

[0228] 5. The old AMF network element sends a Namf_Communication_UE ContextTranfer response to the new AMF network element;

[0229] 6. The new AMF network element sends an Identity Request to the UE;

[0230] 7. The UE sends an Identity Response to the new AMF network element;

[0231] 8. The new AMF network element selects the Authentication Server Function (AUSF) network element;

[0232] 9. The new AMF network element performs security identity authentication;

[0233] 10. The new AMF network element initiates the registration status update operation Namf_Communication_RegistrationStatusUpdate to the old AMF network element;

[0234] 11. The new AMF network element initiates an Identity Request / Response to the UE;

[0235] 12. The new AMF network element initiates identity check N5g-eir EquipmentOdemtityCheck_Get;

[0236] 13. Select the Unified Data Management (UDM) network element.

[0237] 14a. The new AMF network element calls the Nudm_UECM_Registration service of the UDM network element to register;

[0238] 14b. The new AMF network element calls the Nudm_SDM_Ge service of the UDM network element to retrieve the access and mobile subscription data in the SMF network element data;

[0239] 14c. After the new AMF NE receives a successful response, it subscribes to notifications using Nudm_SDM_Subscribe when the requested data is modified. The UDM NE can subscribe to the UDR NE using Nudr_DM_Subscribe.

[0240] 14d. The UDM network element initiates the Nudm_UECM_DeregistrationNotification service to the old AMF network element;

[0241] 14e. If the old AMF network element does not have another UE context of the access type, the old AMF network element will call the Nudm_SDM_unsubscribe service to the UDM network element to cancel the subscription;

[0242] 15. The new AMF network element selects the PCF network element;

[0243] 16. The new AMF network element executes AM Policy Association Establishment / Modification and ignores the emergency registration;

[0244] 17. The new AMF network element calls the Nsmf_PDUSession_UpdateSMContext service / Nsmf_PDUSession_ReleaseSMContext service of the SMF network element;

[0245] 18. If the new AMF network element and the old AMF network element are in the same PLMN, the new AMF network element sends a UE Context modification request to the N3IWF / TNGF / W-AGF network element;

[0246] 19. The N3IWF / TNGF / W-AGF network element sends a UE Context modification response to the new AMF network element;

[0247] 19.a. After receiving the response message from the N3IWF, the new AMF registers with the UDM using the Nudm_UECM_Registration service.

[0248] 19.b. The UDM network element initiates Nudm_UECM_DeregistrationNotify to the old AMF network element, and the old AMF network element removes the non-3GPP UE context;

[0249] 19.c. The old AMF network element uses the Nudm_SDM_Unsubscribe service to cancel the subscription;

[0250] 21. The new AMF network element sends a Registration Accept message to the UE;

[0251] 21b. The new AMF network element executes the UE Policy Association Establishment process;

[0252] 22. The UE sends a Registration Complete message to the new AMF network element;

[0253] 23. If the access and mobility subscription data provided by the UDM network element to the AMF network element in step 14b includes an indication of roaming information, which indicates that the UDM network element requests confirmation of receiving this information from the UE, the AMF network element confirms the UDM network element to the UE using Nudm_SDM_Info;

[0254] 24. The new AMF network element sends a "same type of support for IMS voice over PS session" indication to the UDM network element using Nudm_UECM_Update;

[0255] 25. Network slice specific authentication and authorization.

[0256] FIG2 is an interactive diagram of a device registration method according to an embodiment of the present disclosure. As shown in FIG2 , an embodiment of the present disclosure relates to a device registration method, which includes:

[0257] In step S2101 , the second device 101 and the first device 102 discover and determine each other's capabilities.

[0258] In some embodiments, signaling between the second device 101 and the first device 102 may be transmitted based on PC5, simplified PC5, or other new interfaces.

[0259] In some embodiments, the capabilities of the second device 101 include at least one of the following:

[0260] 1) Energy storage capacity, i.e., the ability to store energy. The second device may or may not have energy storage capacity. When it has energy storage capacity, it may further include the maximum energy storage capacity, power consumption, etc.

[0261] 2) Signal generation capability, that is, the ability to generate a signal. The signal generation capability may include at least one of the following:

[0262] a. No independent signal generation and amplification capabilities;

[0263] b. No independent signal generation capability, but with signal amplification capability;

[0264] c. Have independent signal generation capability;

[0265] 3) Data processing capability, that is, the ability to process data, such as the ability to collect environmental data, the ability to generate signaling, etc.

[0266] 4) Type of the second device. The type of the second device in the embodiment of the present disclosure includes at least one of the following:

[0267] Type A: No energy storage, no independent signal generation / amplification, i.e. backscatter transmission;

[0268] Type B: with energy storage but no independent signal generation, i.e. backscatter transmission, where the use of stored energy may include amplification of the reflected signal;

[0269] Type C: with energy storage and independent signal generation, i.e. active RF components for transmission;

[0270] 5)Supported protocol stack;

[0271] 6) Supported topology types, such as the topology shown in Figure 1B or Figure 1C;

[0272] 7) Supported signal types, such as amplitude-shift keying (ASK), on-off keying (OOK), orthogonal frequency division multiplexing (OFDM), etc.

[0273] 8) Fifth-generation mobile communication technology mobility management (5GS mobility management, 5GMM) capabilities;

[0274] 9) Network capabilities of the S1 interface;

[0275] 10) Security capabilities;

[0276] 11) Radio capability unique identification ID.

[0277] In some embodiments, the capabilities of the first device 102 may include auxiliary capabilities (downlink, uplink, or both), supported topologies (such as FIG. 1B or FIG. 1C ), and supported auxiliary modes.

[0278] In some embodiments, assistance capabilities are determined based on topology type.

[0279] In some embodiments, the assistance mode refers to a mode in which the first device assists the second device in registering in the network.

[0280] In some embodiments, the assistance manner refers to a manner in which the first device assists the second device in performing a registration management process in the network.

[0281] In some embodiments, the auxiliary mode includes a first mode, in which the first device transparently forwards (also referred to as transparent transmission) the first request of the second device (without modifying the information contained in the request), and may also add other parameters, such as the type and ID of the first device, and forward it to the network device 103. The first mode is: the second request includes the first request, and the first device forwards the first request in the second request to the network device.

[0282] In some embodiments, the auxiliary method includes a second method in which the first device generates and sends the first request on behalf of the second device. That is, in the second method, some or all of the first device's capabilities are combined with the capabilities of the second device to form a single entity and send it to the network device. The second method is where the second request does not include the first request, and the first device generates and sends the first request on behalf of the IoT device.

[0283] In some embodiments, the first device 102 or the second device 101 determines a topology type and / or an assistance method.

[0284] In some embodiments, the second device 101 or the first device 102 determines the topology type and / or the assistance mode according to the capability of at least one of the first device 102 and the second device 101 .

[0285] In some embodiments, the second device 101 or the first device 102 determines the topology type and / or the assistance mode according to common capabilities of the first device 102 and the second device 101 .

[0286] After the second device 101 determines the topology type and / or assistance mode, it notifies the first device 102 .

[0287] After determining the topology type and / or the assistance mode, the first device 102 sends a message to the surrounding second devices 101 to notify the topology type and / or the assistance mode.

[0288] In some embodiments, if the information is pre-configured for the second device and / or the first device, step S2101 may be skipped.

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

[0290] Step S2102 : The second device 101 sends a second request to the first device 102 .

[0291] In some embodiments, the first device 102 receives the second request.

[0292] In some embodiments, the second request is used to request the first device 102 to assist the second device 101 in performing a registration process in the network.

[0293] In some embodiments, the second request is used to instruct the first device 102 to send the first request to the network device 103 .

[0294] In some embodiments, the name of the second request is not limited, and it may be, for example, a "registration assistance request."

[0295] In some embodiments, the parameters in the second request include at least one of 5GS mobile identity, 5GS registration type, 5GMM capability, network capability of S1 interface, security capability, radio capability ID, preferred network behavior and assistance mode.

[0296] In some embodiments, the 5GS mobile identity provides at least one of a user concealed identifier (SUCI) of the second device, a 5G-Globally Unique Temporary UE Identity (GUTI), an International Mobile Equipment Identity (IMEI), an IMEI Software Version (IMEISV), a 5G S-Temporary Mobile Subscription Identifier (5G-S-TMSI), a Media Access Control Address (MAC) address, or a 64-bit Extended Unique Identifier (EUI-64).

[0297] In some embodiments, the second request may or may not include the first request.

[0298] In some embodiments, the second device sends a second request including the first request according to the auxiliary mode being the first mode, or does not send the second request including the first request according to the auxiliary mode being the second mode.

[0299] In some embodiments, the parameters in the first request include at least one of 5GS mobile identity, 5GS registration type, 5GMM capability, network capability of S1 interface, security capability, radio capability ID, and preferred network behavior.

[0300] In some embodiments, before the second device 101 sends the second request, it may be triggered by a third device.

[0301] In some embodiments, the third device may be the first device, a network device, a third-party device, or the like.

[0302] In some embodiments, the triggering means that the second device receives a signal sent by the third device, and then sends the second request according to the energy of the signal.

[0303] In step S2103 , the first device 102 determines the first request.

[0304] In some embodiments, the first device receives the second request.

[0305] In some embodiments, the first device determines the first request based on at least one of the assistance method and the second request.

[0306] In some embodiments, the first device obtains the first request from the second request based on the second request including the first request.

[0307] In some embodiments, the first device generates a first request based on the parameters in the second request based on the fact that the second request does not include the first request. For example, the parameters included in the second request include at least one of 5GS mobile identity, 5GS registration type, 5GMM capability, network capability of S1 interface, security capability, radio capability ID, preferred network behavior and auxiliary mode. At least one of the 5GS mobile identity, 5GS registration type, 5GMM capability, network capability of S1 interface, security capability, radio capability ID, preferred network behavior and auxiliary mode is encapsulated to generate the first request.

[0308] In some embodiments, the first device obtains the first request from the second request in a first manner according to the assistance manner.

[0309] In some embodiments, the first device generates the first request according to the second request in accordance with the auxiliary mode being the second mode.

[0310] In some embodiments, the auxiliary mode of the disclosed embodiments is synchronized between the first device and the second device. Therefore, when the first device determines that the auxiliary mode is the first mode, the second device includes the first request in the second request, allowing the first device to directly obtain the first request from the second request. When the first device determines that the auxiliary mode is the second mode, the second request sent by the second device includes the parameters used to generate the first request, allowing the first device to generate the first request based on the parameters used to generate the first request in the second request.

[0311] In some embodiments, the assistance mode is determined by any of the following methods:

[0312] A) Pre-configuration: In some embodiments, the assistance mode may be configured on the first device and the second device before step S2102;

[0313] B) indicating the auxiliary mode in the second request;

[0314] C) Determined according to capabilities of the first device and the second device.

[0315] In the embodiment of the present application, the first device can determine the assistance mode based on the capabilities of each other and inform the second device after determining the assistance mode, or the second device can determine the assistance mode based on the capabilities of each other and inform the first device of the assistance mode.

[0316] Step S2104 : The first device 102 sends a first request to the network device 103 .

[0317] In some embodiments, the first device 102 sends a first request to an access network device in the network device 103 .

[0318] In some embodiments, the first device 102 sends a fifth message to the network device 103 .

[0319] In some embodiments, the fifth message includes the first request.

[0320] In some embodiments, the fifth message includes access network parameters and the first request.

[0321] In step S2105 , the network device 103 registers the second device in the network.

[0322] In some embodiments, the registration process of the second device 101 may be performed with reference to steps 2-19 in FIG. 1D .

[0323] In some embodiments, referring to step 2-19 in FIG. 1D , the second device 101 is registered in the network.

[0324] Step S2106: The network device 103 sends a first message.

[0325] In some embodiments, the first message is sent by a core network device.

[0326] In some embodiments, the first message is used to indicate that the network accepts registration of the second device. In some embodiments, the parameters in the first message are applicable to the second device.

[0327] In some embodiments, the name of the first message is not limited, and it may be, for example, a "registration acceptance message."

[0328] In some embodiments, the network device 103 sends a first message to the first device 102 .

[0329] In some embodiments, the first device 102 receives the first message and sends the first message to the second device 101 .

[0330] In some embodiments, the first device 102 receives the first message, generates a second message based on the first message, and sends the second message to the second device, where the second message indicates that the network accepts the registration of the second device.

[0331] In some embodiments, the name of the second message is not limited, and it may be, for example, "Registration Assistance Response".

[0332] In some embodiments, the second message includes at least one of a registration result, a 5G-GUTI, and a registration area.

[0333] In some embodiments, the first device 102 stores information of the second device 101 .

[0334] In some embodiments, the network device 103 sends a first message to the second device 101 .

[0335] Step S2107: The first device 102 sends a third message.

[0336] In some embodiments, the third message is used to indicate that the second device has completed registration in the network.

[0337] In some embodiments, the name of the third message is not limited, for example, it can be a "registration completion message".

[0338] In some embodiments, the first device 102 receives the first message, generates a third message, and sends the third message to the network device 103 .

[0339] In some embodiments, the second device 101 receives the first message or the second message, generates a third message, sends the third message to the first device 102, and the first device 102 sends the third message to the network device.

[0340] In some embodiments, the second device 101 receives the first message or the second message, generates a fourth message, and sends the fourth message to the first device 102. The first device 102 generates a third message based on the fourth message, and the first device 102 sends the third message to the network device.

[0341] In some embodiments, the fourth message is used to indicate that the second device has completed registration in the network.

[0342] In some embodiments, the fourth message is used to indicate assistance completion.

[0343] In some embodiments, the name of the fourth message is not limited, for example, it can be a "registration assistance completion message".

[0344] In some embodiments, the second device 101 receives the first message or the second message, generates a third message, and the second device 101 sends the third message to the network device 103.

[0345] In some embodiments, after step S2107 , the registration process of the second device 101 may be performed with reference to steps 23 - 25 in FIG. 1D .

[0346] In some embodiments, after step S2107 , the second device 101 may be registered in the network with reference to steps 23 - 25 of FIG. 1D .

[0347] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2107. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, steps S2103 to S2105 may be implemented as independent embodiments, and steps S2106 to S2107 may be implemented as independent embodiments.

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

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

[0350] FIG3A is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a first device, and the method includes:

[0351] Step S3101: Determine the capability of the second device.

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

[0353] In some embodiments, the first device 102 receives a message sent by the second device 101 , in which the capabilities of the second device are indicated, but is not limited thereto. The first device 102 may also receive capabilities of the second device sent by other entities.

[0354] In some embodiments, the first device 102 obtains the capabilities of the second device as specified by the protocol.

[0355] In some embodiments, the first device 102 obtains the capabilities of the second device from an upper layer(s). In some embodiments, the upper layer(s) may include an application layer.

[0356] In some embodiments, the first device 102 performs processing to determine the capabilities of the second device.

[0357] In some embodiments, step S3101 is omitted, and the first device 102 autonomously determines the capabilities of the second device.

[0358] Step S3102, receiving the second request.

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

[0360] In some embodiments, the second device 101 sends a second request to the first device 102 .

[0361] In some embodiments, the second request is used to request the first device 102 to assist the second device 101 in performing a registration process.

[0362] In some embodiments, the second request is used to instruct the first device 102 to send the first request to the network device 103 .

[0363] Step S3103: Determine the first request.

[0364] The optional implementation of step S3103 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.

[0365] In some embodiments, the second request includes the first request, and the first device obtains the first request from the second request.

[0366] In some embodiments, the second request does not include the first request, and the first device generates the first request according to the parameters in the second request.

[0367] Step S3104, sending the first request.

[0368] The optional implementation of step S3104 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.

[0369] In some embodiments, the first device 102 sends a first request to the network device 103 .

[0370] In some embodiments, the first device 102 sends a fifth message to the network device 103. The fifth message includes the first request and access network parameters.

[0371] Step S3105, receiving the first message.

[0372] The optional implementation of step S3105 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.

[0373] In some embodiments, the first device 102 receives a first message from the network device 103 .

[0374] In some embodiments, the first device 102 sends a first message to the second device 101 .

[0375] Step S3106: Send at least one of the second message and the third message.

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

[0377] In some embodiments, the first device 102 obtains the third message from the second device 101 and sends the third message to the network device 103 .

[0378] In some embodiments, the first device 102 generates a third message based on receiving the first message, and sends the third message to the network device 103 .

[0379] In some embodiments, first device 102 receives the fourth message obtained by second device 101, generates a third message based on the fourth message, and sends the third message to network device 103. In some embodiments, first device 102 also sends a second message to second device 101, and the second device can determine that registration is complete based on receipt of the second message.

[0380] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3106. For example, step S3102 may be implemented as an independent embodiment, S3103 may be implemented as an independent embodiment, and steps S3102+S3103+S3104 may be implemented as independent embodiments, but are not limited thereto.

[0381] In some embodiments, steps S3101, S3105, and S3106 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0382] In some embodiments, steps S3101-S3103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0383] FIG3B is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a first device, and the method includes:

[0384] Step S3201, receiving the second request.

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

[0386] Step S3202: Determine the first request.

[0387] The optional implementation of step S3202 can refer to the optional implementation of step S2103 in Figure 2, step S3103 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0388] Step S3203: Send the first request.

[0389] The optional implementation of step S3203 can refer to the optional implementation of step S2104 in Figure 2, step S3104 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0390] Step S3204, determine the third message.

[0391] The optional implementation of step S3204 can refer to the optional implementation of step S2107 in Figure 2, the optional implementation of step S3106 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0392] In some embodiments, the first device 102 receives a third message sent by the second device 101 .

[0393] In some embodiments, the first device 102 receives the fourth message sent by the second device 101 and generates a third message according to the fourth message.

[0394] In some embodiments, after the first device 102 sends the first request to the network device 103 , the network device sends a first message to the second device 101 , and the second device 101 sends a third message or a fourth message to the first device 102 based on the first message.

[0395] Step S3205: Send the third message.

[0396] In some embodiments, the first device 102 sends a third message to the network device 103 .

[0397] The communication method according to the embodiment of the present disclosure may include at least one of steps S3201 to S3205. For example, step S3203 may be implemented as an independent embodiment, S3201 may be implemented as an independent embodiment, and steps S3201+S3202+S3203 may be implemented as independent embodiments, but are not limited thereto.

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

[0399] In some embodiments, steps S3201-S3204 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0400] In the embodiment of the present disclosure, step S3201 can be combined with step S3102 of FIG. 3 a , step S3202 can be combined with step S3104 of FIG. 3 a , and step S3203 can be combined with step S3105 of FIG. 3 a .

[0401] FIG3C is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG3C , the present disclosure embodiment relates to a device registration method, which includes:

[0402] Step S3301: Assist the second device to register in the network.

[0403] In an optional embodiment, step S3301 includes: sending a first request to the network device 103. The optional implementation method of sending the first request to the network device 103 can be found in steps S2103 and S2104 of Figure 2, steps S3103 and S3104 of Figure 3A, the optional implementation method of steps S3201 and S3203 of Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0404] In an optional embodiment, step S3301 also includes: forwarding the first message to the second device. The optional implementation method of forwarding the first message to the second device can be referred to step S2106, step S2104 of Figure 2, step S3105 of Figure 3A, and other related parts of the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0405] In an optional embodiment, step S3301 further includes: sending a third message to the network device. For optional implementation, see step S2106 of FIG. 2 and step S3206 of FIG. 3B .

[0406] The device registration method involved in the embodiment of the present disclosure may include step S3301.

[0407] In an embodiment of the present disclosure, step S3301 may be combined with step S3101 of FIG. 3A .

[0408] FIG3D is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG3D , the present disclosure embodiment relates to a device registration method, which includes:

[0409] Step S3401: Determine a first request, where the first request is used to request registration of a second device in a network;

[0410] Step S3402: Send the first request to the network device.

[0411] As an optional embodiment, the first request includes at least one of the following:

[0412] 5GS mobile identity, the fifth generation mobile communication technology system;

[0413] 5GS registration type;

[0414] the capabilities of the second device;

[0415] Preferred network behavior.

[0416] As an optional embodiment, the capability of the second device includes at least one of the following:

[0417] Energy storage capability, signal generation capability, data processing capability, type of second device, supported protocol stack, supported topology type, supported signal type, 5GMM capability, network capability of S1 interface, security capability and radio capability unique identification ID.

[0418] As an optional embodiment, before sending the first request to the network device, the method further includes:

[0419] A second request sent by the second device is received, where the second request instructs the first device to send the first request to a network device.

[0420] As an optional embodiment, the second request includes at least one of the following:

[0421] 5GS mobile identity, the fifth generation mobile communication technology system;

[0422] 5GS registration type;

[0423] the capabilities of the second device;

[0424] Preferred network behavior.

[0425] As an optional embodiment, determining the first request includes:

[0426] The first request is determined according to at least one of the second request and an auxiliary manner.

[0427] As an optional embodiment, determining the first request according to at least one of the second request and the auxiliary manner includes:

[0428] The second request includes the first request, and the first request is obtained from the second request;

[0429] The second request does not include the first request, and the first request is generated according to the second request;

[0430] The auxiliary mode is the first mode, obtaining the first request from the second request;

[0431] The auxiliary mode is the second mode, generating the first request according to the second request;

[0432] The first manner is as follows: the second request includes the first request, and the first device sends the first request in the second request to the network device;

[0433] The second manner is: the second request does not include the first request, and the first device generates and sends the first request on behalf of the second device.

[0434] As an optional embodiment, the auxiliary mode is determined by the following method:

[0435] Pre-configured;

[0436] The second request indicates an auxiliary mode, or

[0437] The method is determined according to the capabilities of the first device and the second device.

[0438] As an optional embodiment, the assistance mode is determined according to capabilities of the first device and the second device, and before determining the first request, the step further includes:

[0439] and determining the capabilities of each other with the second device.

[0440] As an optional embodiment, the sending the first request to the network device further includes:

[0441] A first message sent by the network device is received, where the first message indicates that the network accepts registration of the second device.

[0442] As an optional embodiment, the receiving the first message sent by the network device further includes:

[0443] sending the first message to the second device; or

[0444] A second message is generated according to the first message, and the second message is sent to the second device, where the second message indicates that the network accepts registration of the second device.

[0445] As an optional embodiment, the sending the first request to the network device further includes:

[0446] A third message is sent to the network device, where the third message indicates that the second device has completed registration in the network.

[0447] As an optional embodiment, before sending the third message to the network device, the method further includes:

[0448] generating the third message according to the first message;

[0449] receiving a third message sent by the second device; or

[0450] receiving a fourth message sent by the second device, and generating the third message according to the fourth message;

[0451] The fourth message indicates that the second device has completed registration in the network.

[0452] FIG4A is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a second device, and the method includes:

[0453] Step S4101: Determine the capability of the first device 102.

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

[0455] Optionally, the capability of the first device is used by the second device to determine the topology type and / or assistance mode. Optional implementations thereof can be found in the optional implementations of step S2102 of FIG. 2 and other related parts of the embodiment involved in FIG.

[0456] Step S4102: Send a second request.

[0457] The optional implementation of step S4102 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.

[0458] In some embodiments, the second device 101 sends a second request to the first device 102 .

[0459] In some embodiments, the second request is for requesting the first device 102 to assist the second device 101 in registering in the network.

[0460] In some embodiments, the second request is used to instruct the first device 102 to send the first request to the network device 103 .

[0461] In some embodiments, the second request includes the first request.

[0462] In some embodiments, the second request includes parameters used to generate the first request.

[0463] In some embodiments, the second request includes at least one of a 5GS mobile identity, a 5GS registration type, capabilities of the second device, a preferred network behavior, and an assistance method.

[0464] In some embodiments, whether the second request includes the first request is determined by the second device according to the determined assistance mode and / or topology type.

[0465] Step S4103, obtain the first message.

[0466] The optional implementation of step S4103 can refer to the optional implementation of step S2106 in Figure 2, step S3105 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0467] In some embodiments, the second device receives the first message sent by the first device.

[0468] In some embodiments, the second device receives the first message sent by the network device.

[0469] Step S4104: Send the third message or the fourth message.

[0470] The optional implementation of step S4104 can refer to the optional implementation of step S2106 in Figure 2, step S3106 in Figure 3A, and other related parts of the embodiments involved in Figure 2 and Figure 3A, which will not be repeated here.

[0471] In some embodiments, the second device 101 sends a third message to the first device 102 , and the first device 102 forwards the third message to the network device 103 .

[0472] In some embodiments, the second device 101 sends a third message to the network device 103 .

[0473] In some embodiments, the second device 101 sends a fourth message to the first device 102 , the first device 102 generates a third message based on the fourth message, and sends the third message to the network device 103 .

[0474] The communication method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4104. For example, step S4103 may be implemented as an independent embodiment, S4105 may be implemented as an independent embodiment, and steps S4101+S4102+S4103 may be implemented as independent embodiments, but are not limited thereto.

[0475] In some embodiments, steps S4101 and S4102 may be executed in an interchanged order or simultaneously.

[0476] In some embodiments, steps S4101, S4102, and S4105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0477] In some embodiments, steps S4101-S4104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0478] FIG4B is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a second device, and the method includes:

[0479] Step S4201, sending a second request.

[0480] The optional implementation of step S4201 can refer to the optional implementation of step S2103 in Figure 2, step S4102 in Figure 4A and other related parts in the embodiments involved in Figures 2, 3A, 3B and 4A, which will not be repeated here.

[0481] In some embodiments, the second device 101 sends a second request to the first device 102 .

[0482] Step S4202, receiving the second message.

[0483] The optional implementation of step S4202 can refer to the optional implementation of step S2106 in Figure 2, step S3106 in Figure 3A and other related parts in the embodiments involved in Figures 2 and 3A, and will not be repeated here.

[0484] In some embodiments, the second device 101 receives the second message sent by the first device 102 .

[0485] The communication method involved in the embodiment of the present disclosure may include at least one of steps S4201 to S4202. For example, step S4201 may be implemented as an independent embodiment, and step S4202 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0486] In some embodiments, steps S4201 and S4202 may be executed in an interchanged order or simultaneously.

[0487] FIG4C is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG4C , the embodiment of the present disclosure involves a second device, and the method includes:

[0488] Step S4301: Send a second request to the first device.

[0489] The second request instructs the first device to send a first request to the network device, where the first request is used to request registration of the second device in the network.

[0490] The first device includes at least one of a relay node and an assist node.

[0491] Based on the above embodiments, as an optional embodiment, sending the second request to the first device also includes:

[0492] Determine the assistance method;

[0493] A second request corresponding to the auxiliary mode is generated.

[0494] Based on the above embodiments, as an optional embodiment, the auxiliary mode is determined by the following method:

[0495] Pre-configured; or

[0496] The method is determined according to the capabilities of the first device and the second device.

[0497] Based on the above embodiments, as an optional embodiment, the capability of the second device includes at least one of the following:

[0498] Energy storage capability, signal generation capability, data processing capability, type of second device, supported protocol stack, supported topology type, supported signal type, 5GMM capability, network capability of S1 interface, security capability and radio capability ID.

[0499] Based on the above embodiments, as an optional embodiment, the assistance mode is determined according to the capabilities of the first device and the second device, and before determining the assistance mode, the method further includes:

[0500] and determining capabilities of each other with the first device.

[0501] Based on the above embodiments, as an optional embodiment, the auxiliary mode is the first mode, and the second request corresponding to the first mode includes the first request;

[0502] The auxiliary mode is a second mode, and a second request corresponding to the second mode includes parameters used to generate the first request;

[0503] The first manner is: the second request includes the first request, and the first device sends the first request included in the second request to the network device;

[0504] The second manner is: the second request does not include the first request, and the first device generates and sends the first request on behalf of the second device.

[0505] Based on the above embodiments, as an optional embodiment, the sending of the second request to the first device further includes:

[0506] sending a third message to the first device;

[0507] sending the third message to the network device; or

[0508] Sending a fourth message to the first device;

[0509] The third message and the fourth message both indicate that the second device has completed registration in the network, and the fourth message is used to generate the third message.

[0510] Based on the above embodiments, as an optional embodiment, sending the third message or the fourth message further includes:

[0511] receiving a first message sent by the network device;

[0512] receiving the first message sent by the first device; or

[0513] receiving a second message sent by the first device;

[0514] The first message and the second message both indicate that the network accepts the registration of the second device, and the second message is generated by the first device according to the first message.

[0515] Based on the above embodiments, as an optional embodiment, sending the second request to the first device includes:

[0516] In response to a trigger by a third device, sending the second request;

[0517] The third device includes at least one of the first device, a network device, and a third-party device.

[0518] FIG5A is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG5A , the embodiment of the present disclosure relates to a network device 103, and the method includes:

[0519] Step S5101, obtain the first request.

[0520] The optional implementation of step S5101 can refer to the optional implementation of step S2104 in Figure 2, step S3104 in Figure 3A, step S3203 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0521] In some embodiments, the network device 103 receives the first request sent by the first device 102 .

[0522] Step S5102: register the second device in the network.

[0523] The optional implementation of step S5102 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.

[0524] Step S5103, sending the first message.

[0525] The optional implementation of step S5103 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.

[0526] In some embodiments, the network device 103 sends a first message to the second device 101 .

[0527] In some embodiments, the network device 103 sends a first message to the first device 102 , and the first device 102 forwards the first message to the second device 101 .

[0528] In some embodiments, the network device 103 sends a first message to the first device 102 , and the first device 102 generates a second message based on the first message and sends the second message to the first device 102 .

[0529] Step S5104, obtain the third message.

[0530] The optional implementation of step S5104 can refer to the optional implementation of step S2106 in Figure 2, step S3106 in Figure 3A, step S3204 in Figure 3B and other related parts in the embodiments involved in Figures 2, 3A and 3B, which will not be repeated here.

[0531] In some embodiments, the network device 103 receives a third message sent by the second device 101 .

[0532] In some embodiments, the network device 103 receives the third message sent by the first device 102 .

[0533] The communication method involved in the embodiments of the present disclosure may include at least one of steps S5101 to S5104. For example, step S5101 may be implemented as an independent embodiment, S5102 may be implemented as an independent embodiment, and steps S5103+S5104 may be implemented as independent embodiments, but are not limited thereto.

[0534] In some embodiments, steps S5103 and S5104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0535] FIG5B is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG5B , the embodiment of the present disclosure relates to a network device 103, and the method includes:

[0536] Step S5201: Receive a first request sent by a first device, where the first request is used to request registration of a second device in a network;

[0537] The first device includes at least one of a relay node and an auxiliary node.

[0538] Based on the above embodiments, as an optional embodiment, receiving a first request sent by a first device further includes:

[0539] A first message is sent to at least one of the first device and the second device, where the first message is used to indicate that the network accepts registration of the second device.

[0540] Based on the above embodiments, as an optional embodiment, the sending of the first message to at least one of the first device and the second device further includes:

[0541] receiving a third message sent by the first device; or

[0542] receiving a third message sent by the second device;

[0543] The third message indicates that the second device has completed registration in the network.

[0544] Figure 6 is an interactive diagram of a device registration method according to an embodiment of the present disclosure. As shown in Figure 6, the present disclosure embodiment relates to a device registration method, which includes:

[0545] Step S6101: The first device and the second device discover and determine each other's capabilities.

[0546] The optional implementation methods of step S6101 can be found in step S2101 of Figure 2, step S3101 of Figure 3A, step S3201 of Figure 3B, step S4101 of Figure 4A, and the optional implementation methods of step S4201 of Figure 4B, as well as other related parts in the embodiments involved in Figures 2, 3A, 3B, 4A, and 4B, which will not be repeated here.

[0547] It should be noted that if the first device and the second device are pre-configured, step S6101 can be skipped.

[0548] The capabilities of the first device may include assistance capabilities (downlink, uplink, or both), supported topology types, and supported assistance methods.

[0549] The capabilities of the second device include energy storage capability, signal generation capability, data processing capability, environmental second device type, supported protocol stack, supported topology type, supported signal type, 5GMM capability, S1UE network capability, UE security capability, UE radio ID, etc.

[0550] In some embodiments, the assistance mode is used to indicate how the first device assists the second device in the registration process. For example, in the first mode, the first device transparently forwards the second request received from the IoT (without modifying the information contained in the request), and may add other parameters and package them into a message and forward it to the (R)AN. In the second mode, the first device generates the first request on behalf of the second device. If the second request is received from the IoT device, some or all of the capabilities of the first node may be combined with the capabilities of the IoT and can be treated as a whole and sent to the (R)AN.

[0551] Step S6102: The first device or the second device determines a topology type and / or an assistance mode according to capabilities of the first device and the second device.

[0552] For the optional implementation of step S6102, please refer to step S2102 in Figure 2, step S3102 in Figure 3A, step S3202 in Figure 3B, step S4102 in Figure 4A, and the optional implementation of step S4202 in Figure 4B, as well as other related parts in the embodiments involved in Figures 2, 3A, 3B, 4A, and 4B, which will not be repeated here.

[0553] The first device or the second device may determine the topology type and / or the assistance method according to the capabilities of the first device and the second device.

[0554] For example, if it is determined by the first device, the first device sends a message to the surrounding second devices to notify the determined topology type and assistance method.

[0555] It should be noted that if the topology type and / or assistance mode are pre-configured, step S6102 can be skipped.

[0556] Step S6103: The second device sends a second request to the first device.

[0557] For the optional implementation of step S6103, please refer to step S2102 of Figure 2, step S3102 of Figure 3A, step S3201 of Figure 3B, step S4102 of Figure 4A, step S4201 of Figure 4B, and other related parts in the embodiments involved in Figures 2, 3A, 3B, 4A, and 4B, which will not be repeated here.

[0558] In some embodiments, the second request includes at least one of a 5GS mobile identity, a 5GS registration type, a 5GMM capability, an S1UE network capability, a UE security capability, a UE radio capability ID, a preferred network behavior, and an auxiliary method.

[0559] In some embodiments, before the second device sends the second request, it may be triggered by a second device, such as the first device, an access network device, etc.

[0560] In some embodiments, the second request includes the first request, and the first request includes at least one of 5GS mobile identity, 5GS registration type, 5GMM capability, S1UE network capability, UE security capability, and UE radio capability ID.

[0561] In some embodiments, the second request does not include the first request.

[0562] In some embodiments, the 5GS Mobile Identity provides the SUCI, 5G-GUTI, IMEI, IMEISV, 5G-S-TMSI, MAC address, or EUI-64 of the second device.

[0563] In some embodiments, the 5GS Registration Type indicates the type of registration requested.

[0564] In some embodiments, the auxiliary mode is an auxiliary mode requested by the second device.If determined in step S6102, the second request may not include the auxiliary mode.

[0565] Step S6104: The first device sends a first request to the network device.

[0566] The optional implementation of step S6104 can be found in steps S2103 and S2104 in Figure 2, steps S3103 and S3104 in Figure 3A, steps S3202 and S3204 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0567] In some embodiments, the second device sends an access network message to the network device, where the access network message includes the first request and the access network parameter.

[0568] In some embodiments, if the second request includes the first request, or the auxiliary mode is the first mode, the first device directly sends the first request to the network device.

[0569] In some embodiments, if the second request does not include the first request, or the auxiliary mode is the second mode, the first device generates the first request according to the parameters in the second request.

[0570] In step S6105 , the network device registers the second device 101 in the network.

[0571] Optional implementations of step S6105 may refer to step S2106 in FIG. 2 , step S5102 in FIG. 5A , and other related parts in the embodiments involved in FIG. 2 and FIG. 5A , which will not be described in detail here.

[0572] In some embodiments, steps 2-19 of the registration procedure are performed, for example based on Figure 1d, as defined in 3GPP TS 23.502 clause 4.2.2.2.2-1.

[0573] Step S6106a1: The network device sends a first message to the first device.

[0574] The optional implementation of step S6106a1 can be found in step S2106 of Figure 2, step S3102 in Figure 3A, step S3102 in Figure 3B, and step S5102 in Figure 5A, as well as other related parts in the embodiments involved in Figures 2, 3A, 3B, and 5A, which will not be repeated here.

[0575] In some embodiments, the core network device sends a first message to the first device defined in step 21 of clause 4.2.2.2.2-1 of 3GPP TS 23.502.

[0576] Step S6106a2: The first device sends a second message to the second device.

[0577] The optional implementation of step S6106a2 can be found in step S2106 of Figure 2, step S3105 in Figure 3A, step S3102 in Figure 3B, and step S5102 in Figure 5A, as well as other related parts in the embodiments involved in Figures 2, 3A, 3B, and 5A, which will not be repeated here.

[0578] In some embodiments, the second message includes at least one of a registration result, a 5G-GUTI, and a registration area.

[0579] Step S6106b: The network device sends a first message to the second device.

[0580] The optional implementation of step S6106b can be found in step S2106 of FIG. 2 , step S4103 of FIG. 4A , and step S5102 of FIG. 5A , as well as other related parts in the embodiments involved in FIG. 2 , FIG. 4A , and FIG. 5A , which will not be repeated here.

[0581] Step S6106c: The network device sends a first message to the first device.

[0582] The optional implementation of step S6105c can be found in step S2106 of Figure 2, step S3105 in Figure 3A, step S5102 in Figure 5A and other related parts in the embodiments involved in Figures 2, 3A and 5A, which will not be repeated here.

[0583] In some embodiments, the core network sends a first message to the first device defined in step 21 of clause 4.2.2.2.2-1 of 3GPP TS 23.502. Parameters included in the first message are applicable to the second device.

[0584] In some embodiments, the first device stores the information of the second device without sending the first message to the second device.

[0585] Step S6107a1: The second device sends a fourth message to the first device.

[0586] Optional implementations of step S6107a1 can refer to step S2106 in FIG. 2 , step S3105 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.

[0587] Step S6107a2: The first device sends a third message to the network device.

[0588] Optional implementations of step S6107a2 can be found in step S2106 of FIG. 2 , step S3106 of FIG. 3A , S5103 of FIG. 5A , and other related parts of the embodiments involved in FIG. 2 , FIG. 3A , and FIG. 5A , which will not be described in detail here.

[0589] Step S6107b: The second device sends a third message to the network device.

[0590] Optional implementations of step S6107b can be found in step S2106 of FIG. 2 , step S4104 of FIG. 4A , step S5103 of FIG. 5A , and other related parts in the embodiments involved in FIG. 2 , FIG. 4A , and FIG. 5A , which will not be described in detail here.

[0591] Step S6107c: The first device sends a third message to the network device;

[0592] Optional implementations of step S6107c can be found in step S2106 of FIG. 2 , step S3106 of FIG. 3A , step S5103 of FIG. 5A , and other related parts of the embodiments involved in FIG. 2 , FIG. 3A , FIG. 3B , and FIG. 5A , which will not be repeated here.

[0593] Step S6108, registering the second device in the network, referring to steps 23-25 ​​in FIG. 1D ;

[0594] Step S6109: After executing step S6106c or S6107c, the first device sends a second message to the second device.

[0595] Optional embodiments of step S6109 can refer to step S2106 in FIG. 2 , step S3106 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.

[0596] It should be noted that in the embodiment of the present disclosure, if step S6106a is executed, the second device may execute step S6107a or S6107b, and if step S6106b is executed, the second device may execute step S6107a or S6107b. If step S6106c is executed, the first device may execute step S6107c and step S6109.

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

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

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

[0600] Figure 7A is a structural diagram of the first device proposed in an embodiment of the present disclosure. The first device includes a relay node or an auxiliary node. As shown in Figure 7A, the first device 7100 may include: at least one of a processing module 7101, a transceiver module 7102, etc. In some embodiments, the above-mentioned processing module is used to determine a first request, and the first request is used to request to register a second device in the network; the transceiver module is used to send the first request to the network device. Optionally, the above-mentioned transceiver module is used to execute the communication steps such as sending and / or receiving performed by the first device 102 in any of the above methods, such as step S2101 and step S2105, which are not repeated here. Optionally, the above-mentioned processing module is used to execute other steps performed by the first device 102 in any of the above methods, such as at least one of step S2104, which are not repeated here.

[0601] FIG7B is a schematic diagram of the structure of the second device proposed in an embodiment of the present disclosure. As shown in FIG7B , the second device 7200 may include: a transceiver module 7201. In some embodiments, the transceiver module is used to send a second request to the first device; the second request instructs the first device to send a first request to the network device, the first request being used to request registration of the second device in the network; the first device includes a relay node or an auxiliary node. Optionally, the transceiver module is used to execute the communication steps such as sending and / or receiving performed by the second device 101 in any of the above methods, such as step S2101 and step S2103, which will not be repeated here.

[0602] Figure 7C is a structural diagram of the network device proposed in an embodiment of the present disclosure. As shown in Figure 7C, the network device 7300 may include a transceiver module 7301. In some embodiments, the transceiver module receives a first request sent by a first device, and the first request is used to register a second device in the network; optionally, the above-mentioned transceiver module is used to execute the communication steps such as sending and / or receiving performed by the network device 103 in any of the above methods, such as step S2107 and step S2108, which are not repeated here.

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

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

[0605] Figure 8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., an access network device, a core network device, etc.), a second device, a first device, a chip, a chip system, or a processor that supports a network device in implementing any of the above methods, or a chip, a chip system, or a processor that supports a second device in implementing any of the above methods. Communication device 8100 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.

[0606] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 8100 is used to perform any of the above methods. Optionally, one or more processors 8101 are used to call instructions to enable the communication device 8100 to perform any of the above methods.

[0607] In some embodiments, the communication device 8100 further includes one or more transceivers 8102. When the communication device 8100 includes one or more transceivers 8102, the transceiver 8102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., step S2101, step S2103, step S2105, step S2107, step S2108, but not limited thereto), and the processor 8101 performs at least one of the other steps (e.g., step S2102, step S2104, step S2106, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be interchangeable, the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be interchangeable, and the terms receiver, receiving unit, receiver, and receiving circuit may be interchangeable.

[0608] In some embodiments, the communication device 8100 further includes one or more memories 8103 for storing data. Alternatively, all or part of the memories 8103 may be located outside the communication device 8100. In alternative embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuits 8104 are connected to the memory 8102 and may be configured to receive data from the memory 8102 or other devices, or to send data to the memory 8102 or other devices. For example, the interface circuits 8104 may read data stored in the memory 8102 and send the data to the processor 8101.

[0609] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8A. 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.

[0610] FIG8B is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8B , but the present disclosure is not limited thereto.

[0611] The chip 8200 includes one or more processors 8201. The chip 8200 is configured to execute any of the above methods.

[0612] In some embodiments, chip 8200 further includes one or more interface circuits 8202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 8200 further includes one or more memories 8203 for storing data. Alternatively, all or part of memory 8203 may be located external to chip 8200. Optionally, interface circuit 8202 is connected to memory 8203 and may be used to receive data from memory 8203 or other devices, or may be used to send data to memory 8203 or other devices. For example, interface circuit 8202 may read data stored in memory 8203 and send the data to processor 8201.

[0613] In some embodiments, the interface circuit 8202 performs at least one of the communication steps (e.g., steps S2101, S2103, S2105, S2107, and S2108) of the aforementioned method. The interface circuit 8202 performing the communication steps (e.g., steps S2101, S2103, S2105, S2107, and S2108) of the aforementioned method, for example, means that the interface circuit 8202 performs data exchange between the processor 8201, chip 8200, memory 8203, or a transceiver device. In some embodiments, the processor 8201 performs at least one of the other steps (e.g., steps S2102, S2104, and S2106, but not limited thereto).

[0614] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 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 temporary storage medium.

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

[0616] 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 device registration method, executed by a first device, characterized in that: The first device includes at least one of a relay node and an auxiliary node, and the method includes: Determining a first request, wherein the first request is used to request registration of a second device in a network; The first request is sent to the network device.

2. The method according to claim 1, characterized in that The first request includes at least one of the following: 5GS mobile identity, the fifth generation mobile communication technology system; 5GS registration type; the capabilities of the second device; Preferred network behavior.

3. The method according to claim 2, characterized in that The capabilities of the second device include at least one of the following: Energy storage capability, signal generation capability, data processing capability, type of second device, supported protocol stack, supported topology type, supported signal type, fifth generation mobile communication technology mobility management 5GMM capability, network capability of S1 interface, security capability and unique identification ID of radio capability.

4. The method according to any one of claims 1 to 3, characterized in that: Before sending the first request to the network device, the method further includes: A second request sent by the second device is received, where the second request instructs the first device to send the first request to a network device.

5. The method according to claim 4, characterized in that The second request includes at least one of the following: 5GS Mobile Identity; 5GS registration type; the capabilities of the second device; Preferred network behavior.

6. The method according to claim 4 or 5, characterized in that: The determining the first request comprises: The first request is determined according to at least one of the second request and an auxiliary manner.

7. The method according to claim 6, characterized in that The determining the first request according to at least one of the second request and the auxiliary manner includes: The second request includes the first request, and the first request is obtained from the second request; The second request does not include the first request, and the first request is generated according to the second request; The auxiliary method is the first method, obtaining the first request from the second request; The auxiliary mode is the second mode, generating the first request according to the second request; The first mode is: the second request includes the first request, and the first device sends the first request in the second request to the network device; The second manner is: the second request does not include the first request, and the first device generates and sends the first request on behalf of the second device.

8. The method according to claim 7, characterized in that The auxiliary mode is determined by the following method: Pre-configured; The second request indicates an auxiliary mode, or The method is determined according to the capabilities of the first device and the second device.

9. The method according to claim 8, characterized in that The assistance mode is determined according to the capabilities of the first device and the second device, and before determining the first request, the method further includes: and determining with the second device capabilities of each other.

10. The method according to any one of claims 1 to 9, characterized in that: The sending the first request to the network device further comprises: A first message sent by the network device is received, where the first message indicates that the network accepts registration of a second device.

11. The method according to claim 10, characterized in that The receiving device further comprises: sending the first message to the second device; or A second message is generated according to the first message, and the second message is sent to the second device, where the second message indicates that the network accepts registration of the second device.

12. The method according to any one of claims 1 to 11, characterized in that: The sending the first request to the network device further comprises: A third message is sent to the network device, where the third message indicates that the second device has completed registration in the network.

13. The method according to claim 12, characterized in that The sending of the third message to the network device also includes: Generate the third message according to the first message; receiving a third message sent by the second device; or receiving a fourth message sent by the second device, and generating the third message according to the fourth message; The fourth message indicates that the second device has completed registration in the network.

14. A device registration method, performed by a second device, characterized in that: The method comprises: sending a second request to the first device; The second request instructs the first device to send a first request to the network device, where the first request is used to request to register the second device in the network; The first device includes at least one of a relay node and an assist node.

15. The method according to claim 14, characterized in that The sending of the second request to the first device also includes: Determine the assistance method; A second request corresponding to the auxiliary mode is generated.

16. The method according to claim 15, characterized in that The auxiliary mode is determined by the following method: Pre-configured; or The method is determined according to the capabilities of the first device and the second device.

17. The method according to claim 16, characterized in that The capabilities of the second device include at least one of the following: Energy storage capability, signal generation capability, data processing capability, type of second device, supported protocol stack, supported topology type, supported signal type, 5GMM capability, network capability of S1 interface, security capability and radio capability ID.

18. The method according to claim 16 or 17, characterized in that The auxiliary mode is determined according to the capabilities of the first device and the second device, and before determining the auxiliary mode, the method further includes: and determining with the first device capabilities of each other.

19. The method according to any one of claims 15 to 18, characterized in that: The auxiliary mode is a first mode, and the second request corresponding to the first mode includes the first request; The auxiliary mode is a second mode, and a second request corresponding to the second mode includes parameters used to generate the first request; The first mode is: the second request includes the first request, and the first device sends the first request included in the second request to the network device; The second manner is: the second request does not include the first request, and the first device generates and sends the first request on behalf of the second device.

20. The method according to any one of claims 14 to 19, characterized in that: The sending of the second request to the first device further includes: Sending a third message to the first device; Sending the third message to the network device; or Sending a fourth message to the first device; The third message and the fourth message both indicate that the second device has completed registration in the network, and the fourth message is used to generate the third message.

21. The method according to claim 20, characterized in that Sending a third message or a fourth message, which also includes: Receiving a first message sent by the network device; receiving the first message sent by the first device; or receiving a second message sent by the first device; The first message and the second message both indicate that the network accepts the registration of the second device, and the second message is generated by the first device according to the first message.

22. The method according to any one of claims 14 to 21, characterized in that: The sending the second request to the first device includes: In response to a trigger from a third device, sending the second request; The third device includes at least one of the first device, a network device, and a third-party device.

23. A device registration method, executed by a network device, characterized in that: The method comprises: receiving a first request sent by a first device, where the first request is used to request registration of a second device in a network; The first device includes at least one of a relay node and an auxiliary node.

24. The method according to claim 23, characterized in that The step of receiving a first request sent by a first device further comprises: A first message is sent to at least one of the first device and the second device, where the first message is used to indicate that the network accepts registration of the second device.

25. The method according to claim 24, characterized in that The sending of a first message to at least one of the first device and the second device further includes: receiving a third message sent by the first device; or receiving a third message sent by the second device; The third message indicates that the second device has completed registration in the network.

26. A device registration method, characterized in that: Applied to a communication system, the method comprises: The second device sends a second request to the first device; The first device sends a first request to the network device according to the second request; The network device obtains the first request; wherein the first device comprises at least one of a relay node and an auxiliary node; The first request is used to request to register the second device in the network, The second request is used by the first device to send the first request to the network device.

27. A first device, comprising at least one of a relay node and an auxiliary node, characterized in that: The first device comprises: A processing module, configured to determine a first request, wherein the first request is configured to request registration of a second device in a network; A transceiver module is used to send the first request to the network device.

28. A second device, characterized in that: include: A transceiver module, configured to send a second request to the first device; The second request instructs the first device to send a first request to a network device, where the first request is used to request to register the second device in the network.

29. A network device, characterized in that: include: A transceiver module, configured to receive a first request sent by a first device, wherein the first request is used to request registration of a second device in a network; The first device includes at least one of a relay node and an auxiliary node.

30. A communication system, characterized in that: It includes a second device, a first device, and a network device, wherein the first device is configured to implement the device registration method described in any one of claims 1-13, the second device is configured to implement the device registration method described in any one of claims 14-22, and the network device is configured to implement the device registration method described in any one of claims 23-25.

31. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device is enabled to execute the device registration method according to any one of claims 1-13, 14-22, and 23-25.

Images