METHOD OF INTERACTION BETWEEN DEVICES AND MAIN NETWORK DEVICE

MX431211BActive Publication Date: 2026-02-25VIVO MOBILE COMM CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
MX2022012340
Authority / Receiving Office
MX · MX
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-04-30
Filing Date
2022-09-30
Publication Date
2026-02-25
Estimated Expiration
2041-04-29

Smart Images

  • Figure MX431211B0
    Figure MX431211B0
Patent Text Reader

Abstract

The modalities of this application establish a method of device interaction and a core network device. The method includes: a first core network device receiving identifier information from at least one UE sent by a first device, where the at least one UE is at least one of the following: a UE that has established a UE-to-network relay connection with a first UE and a UE that is to establish a UE-to-network relay connection with the first UE; and a first core network device interacting, based on the identifier information of a second UE, with a second core network device, where the second UE is any of the at least one UE, the first core network device is a core network device serving the first UE, and the second core network device is a core network device serving the second UE.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD OF INTERACTION BETWEEN DEVICES AND MAIN NETWORK DEVICE REFERENCE TO RELATED APPLICATIONS This application claims priority to Chinese Patent Application No. 202010368326.5, filed in China on April 30, 2020, which is attached hereto in its entirety by reference. TECHNICAL FIELD The modalities of this application relate to the field of communication technologies and, in particular, to a method of device interaction and a main network device. BACKGROUND OF THE INVENTION With the development of communication technologies, in fifth generation proximity services (5G_ProSe) technology, the connection from a user equipment (UE) to a network relay (UE-to-network relay) can be implemented using a layer 2 (Layer-2) mode. In layer 2 mode, a UE-to-network relay communication architecture can include two sets of core network devices, for example, a relay Access and Mobility Management Function (AMF) entity and a remote AMF entity. However, since this communication architecture includes a relay AMF entity and a remote AMF entity, the implementation mode of the interaction between the relay AMF entity and the remote AMF entity is an urgent problem that needs to be solved. BRIEF DESCRIPTION OF THE INVENTION The purpose of the modalities in this application is to provide a method of device interaction and a main network device to resolve the implementation mode of the interaction between an AMF entity and a remote AMF entity. To resolve the aforementioned technical problem, the present request is implemented as follows. nircz ίη / ζζηζ / Ε / γίΛΐ According to a first aspect, one modality of this request establishes a method of device interaction. The method includes: a first primary network device receiving identifier information from at least one UE sent by a first device, where the at least one UE is at least one of the following: a UE that has established a UE-to-network relay connection with a first UE and a UE that will establish a UE-to-network relay connection with the first UE; and a first primary network device interacting, based on the identifier information of a second UE, with a second primary network device, where the second UE is any of the at least one UE, the first primary network device is a primary network device serving the first UE, and the second primary network device is a primary network device serving the second UE. According to a second aspect, one modality of this request establishes a primary network device. The primary network device can be a first primary network device and includes a receiver module and an interaction module. The receiver module is configured to receive identifier information from at least one User Equipment (UE) sent by a first device, where the at least one UE is at least one of the following: a UE that has established a UE-to-network relay connection with a first UE and a UE that will establish a UE-to-network relay connection with the first UE. The interaction module is configured to, after the receiver module receives the identifier information from at least one UE, interact with a second primary network device based on the identifier information of a second UE, which is one of the at least one UEs. The first primary network device is a primary network device that serves the first UE, and the second primary network device is a primary network device that serves the second UE. According to a third aspect, one embodiment of the present application provides a main network device that includes a processor, memory, and a program or instructions stored in memory and capable of execution by the processor. When the processor executes the program or instructions, the steps of the device interaction method according to the first aspect are implemented. According to a fourth aspect, one embodiment of the present application has a readable storage medium. The readable storage medium stores a program or instructions, and when a processor executes the program or instructions, the steps of the device interaction method according to either the first or second aspect are implemented. nircz ίη / ζζηζ / Ε / γίΛΐ According to a fifth aspect, an embodiment of the present application includes a chip. The chip includes a processor and a communication interface, wherein the communication interface is coupled to the processor and the processor is configured to execute a program or instructions for the purpose of implementing the steps of the device interaction method according to the first aspect. In the modalities of this application, a first primary network device may receive identifier information from at least one UE sent by a first device, where the at least one UE is at least one of the following: a UE that has established a UE-to-network relay connection with a first UE and a UE that is to establish a UE-to-network relay connection with the first UE. The first primary network device interacts with a second primary network device based on the identifier information of a second UE, where the second UE is one of at least one UE; the first primary network device is a primary network device serving the first UE and the second primary network device is a primary network device serving the second UE.With this solution, in UE-to-relay communication, a primary network device serving a UE can be determined based on the UE's identifier information. Therefore, the first primary network device can determine, based on the identifier information received from at least one UE, the second primary network device serving one of those at least one UEs, in order to interact with that second primary network device. For example, a relay primary network device can interact with a remote primary network device serving a remote UE based on the identifier information received from the remote UE, or a remote primary network device can interact with a relay primary network device serving a relay UE based on the identifier information received from the relay UE.In this way, an interaction between a main relay network device and a remote main network device can be implemented using the device interaction method of the modalities of this application. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a schematic diagram of a communication system architecture according to a modality of the present application; Figure 2 is a schematic flowchart of a device interaction method in accordance with a modality of the present application; Figure 3 is a first schematic flowchart of a request for an interaction method of 3 nircz ίη / ζζηζ / E / γίΛΐ devices in accordance with a modality of the present application; Figure 4 is a second schematic flowchart of the application of a device interaction method in accordance with a modality of the present application; Figure 5 is a third schematic flowchart of the application of a device interaction method in accordance with a modality of the present application; Figure 6 is a fourth schematic flowchart of the application of a device interaction method in accordance with a modality of the present application; Figure 7 is a schematic structural diagram of a main network device according to a modality of the present application; and Figure 8 is a schematic diagram of the hardware of a main network device according to one modality of the present application. DESCRIPTION OF THE MODALITIES The technical solutions for the variations of this application are described below clearly and completely, with reference to the accompanying drawings. The variations described appear to be some, but not all, of the variations of this application. All other variations obtained by any person with ordinary skills in the field, based on the variations of this application and without resorting to creativity, will fall within the scope of protection of this application. In this specification and in the claims of this application, the terms first, second, and so forth are used to distinguish between similar objects rather than to describe a specific order or sequence. It should be understood that, under appropriate circumstances, the data used in this manner may be interchanged so that the features of this application may be applied in orders different from the order illustrated or described herein. Furthermore, in the specification and the claims, "or" represents at least one of the connected objects, and the character 7 typically represents a disjunctive relationship between the associated objects. In the modalities of this application, the expressions "such as an example" or "for instance" are used to represent the presentation of an example, instance, or illustration. No modality or design solution described as an example or "for instance" in the modalities of this application should be considered a better or preferential option than other modalities or design solutions. To be precise, the purpose of terms such as "an example" or "for instance" is to present a related concept in a specific way. nircz ίη / ζζηζ / Ε / γίΛΐ In the descriptions of the modalities in this application, a variety means two or more, unless otherwise specified. For example, a core network device variety means two or more core network devices. The terms / substantives included in the modalities of this application are described below. Primary relay network device: A primary network device that serves a UE in UE-to-relay network communications, for example, a relay AMF entity. Relay UE (i.e., Relay UE): A UE that implements communication between a remote UE and an access network device as a relay device of the remote UE in UE-to-network relay communication, i.e., a relay UE from UE to network in UE-to-network relay communication. Remote core network device: A core network device that serves a remote UE in UE-to-network relay communications, for example, a remote AMF entity. Remote UE (i.e., Remote UE): A UE that requires relay from a relay UE to establish network relay UE communications with an access network device. Relay UE access network device: An access network device that serves a UE in network relay UE communications, for example, a 5G system node base (gNB) and an evolved NodeB (eNB). The modalities of this application establish a method of device interaction and a primary network device. A first primary network device may receive identifier information from at least one UE sent by a first device, where the at least one UE is at least one of the following: a UE that has established a UE-to-network relay connection with a first UE and a UE that is to establish a UE-to-network relay connection with the first UE. The first primary network device interacts with a second primary network device based on the identifier information of a second UE, where the second UE is any of the at least one UEs; the first primary network device is a primary network device serving the first UE and the second primary network device is a primary network device serving the second UE.With this solution, in UE-to-relay communication, a primary network device serving a UE can be determined based on the UE's identifier information. Therefore, the first primary network device can determine, based on the identifier information received from at least one UE, the second primary network device serving one of the at least one UEs, in order to interact with that second primary network device. For example, a relay primary network device can implement interaction with a remote primary network device serving a remote UE based on the identifier information received from the remote UE, or a remote primary network device can implement interaction with a relay primary network device serving a relay UE based on the identifier information received from the relay UE.In this way, an interaction between a main relay network device and a remote main network device can be implemented using the device interaction method of the modalities of this application. Figure 1 is a schematic diagram of a communication system architecture according to one modality of this application. As shown in Figure 1, the communication system may include a main relay network device 01, a relay UE 02, a remote main network device 03, a remote UE 04, and an access network device 05. The remote UE 04 can communicate with the access network device 05 via the relay UE 02. The relay UE 02 can be a relay-capable UE or another relay-capable device, for example, a Road Side Unit (RSU). It should be noted that, in this form of the present application, the connection between the devices shown in Figure 1 can be wireless or wired. A UE is a device that provides the user with data or voice connectivity. It can be a portable device with a wired / wireless connection or another processing device connected to a wireless modem. The UE can communicate with one or more core network devices via a radio access network (RAN). The UE can be a mobile terminal, such as a cell phone (also called a mobile phone) or a computer with a mobile terminal, or it can be a laptop, pocket-sized, handheld, embedded, or in-vehicle computer that exchanges voice or data with the RAN.For example, a UE is a device such as a Personal Communication Service (PCS) phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, or a Personal Digital Assistant (PDA). A UE may also be called a User Agent, terminal device, etc. The access network device is a device deployed in the RAN and configured to provide wireless communication functionality to the UE. In the modality of this application, the access network device may be a base station, and the base station may include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems using different radio access technologies, a device functioning as a base station may have different names.For example, such a device might be called a 5G system base station (gNB) in a fifth-generation (5G) mobile communications system, an evolved node B (eNB) in a fourth-generation (4G) wireless communications system, such as a Long Term Evolution (LTE) system, or a node B in a third-generation (3G) mobile communications system. As communication technologies evolve, the term "base station" may change. A primary network device can be a primary network element located at one end of the network, for example, an AME entity or a Policy Control Function (PCF) entity. The following specific usage modalities and their corresponding application situations are examples of descriptions of the device interaction method established in the modalities of this application with reference to the attached drawings. As shown in Figure 2, one embodiment of this application establishes a method for device interaction. The method can be applied to the wireless communication system of Figure 1 and may include the following steps S201 and S202. S201. A first primary network device receives identifier information from at least one UE sent by a first device. The at least one UE can be at least one of the following: a UE that has established a UE-to-network relay connection with a first UE and a UE that will establish a UE-to-network relay connection with the first UE. The first primary network device can be a primary network device that serves the first UE. S202. The first primary network device interacts with a second primary network device based on the identifier information of a second UE. The second UE can be one of at least one UE and the second primary network device can be a primary network device that serves the second UE. In this modality of the present application, in UE-to-network relay communications, the first device can transmit the first primary network device identifier data of a UE (i.e., at least one UE) that has established or will establish a UE-to-network relay connection with the first UE. In this way, after receiving the identifier information from at least one UE, the first primary network device can interact with the second primary network device serving the second UE based on the identifier information of the second UE from the at least one UE. In this modality of the present application, in a first implementation, the first main network device is a relay main network device and the first UE is a relay UE; and the second main network device can be a remote main network device and the second UE is a remote UE. In the second implementation, the first main network device is a remote main network device and the first UE is a remote UE; and the second main network device can be a relay main network device and the second UE is a relay UE. As an option, in this modality of the present application, the first main network device can be the first UE or an access network device. The access network device can service a relay UE and the relay UE can be either the first UE or the second UE. In this modality of the present application, in the case of the first implementation, the first device may be the relay UE or a relay UE access network device; and, in the case of the second implementation, the first device may be the remote UE or a relay UE access network device. As an option, in this modality of the present application, when the first main network device is a main relay network device, the at least one UE may include a remote UE that has established a network relay UE connection with the relay UE (i.e., the first UE) and a remote UE that will establish a network relay UE connection with the relay UE. In this modality of the present application, when the relay UE receives a request to establish a non-direct connection or it is necessary to establish a direct connection from a remote UE, said remote UE is a remote UE that will establish a network relay UE connection with the relay UE. It should be noted that, in this form of the present application, the application for establishment of a non-direct connection or the application for establishment of a direct connection may be used to indicate that the remote UE is requesting to establish a network relay UE connection with the relay UE. In this modality of the present application, the remote UE that has established the network relay UE connection with the relay UE may include a remote UE that is currently connected to the relay UE or that the relay UE is about to service. The remote UE that is going to establish a network relay UE connection with the relay UE may include a remote UE with which the relay UE is about to establish a connection or which the relay UE is about to service, and a remote UE with which the relay UE is establishing a connection. The remote UE that has established a network relay UE connection with the relay UE and the remote UE that is about to establish a network relay UE connection with the relay UE may be collectively referred to as remote UEs associated with the relay UE for network relay UE communications. As an option, in this modality of the present application, when the first main network device is a remote main network device, the at least one UE may include a relay UE that has established a network relay UE connection with the remote UE (i.e., the first UE). As an option, in this form of the present application, when the at least one UE is a variety of UE, the identifier information of at least one UE received by the first primary network device may be in list format. In other words, the first primary network device receives a list that includes identifier information for at least one UE. As an option, in this modality of the present application, the identifier information of at least one UE may be transmitted in a ÑAS message, an N2 interface message, or a response message corresponding to an identifier request. As an option, in this modality of the present application, when the first device is the first UE, the identifier information of at least one UE may be transmitted in a NAS message or a corresponding response message to an identifier request; and, when the first device is a relay UE access network device, the identifier information of at least one UE may be transmitted in an N2 interface message or a corresponding response message to an identifier request. Alternatively, in this form of the present application, the identifier information for one of the at least one EU member states may be one of the following: 5G Globally Unique Temporary Identifier (5GGUTI); a 5G S-temporary Mobile Subscription Identifier (5G-S-TMSI); an application layer ID; a ProSe Relay User Key Identity (PRUK ID); a Permanent Equipment Identifier (PEI); a hidden subscription identifier (Subscription Concealed Identifier; SUCI); and nircz Ln / zznz / E / YiAi a permanent subscription identifier (Subscription Permanent Identifier, SUPI). Optionally, in this modality of the present application, when the first device is the first UE, the identifier information of at least one of the UEs may be a 5G-GUTI, a 5GS-TMSI, an application layer ID, a PRUK ID, a PEI, a SUCI, or a SUPI. Alternatively, in this modality of the present application, when the first device is a relay UE access network device, the identifier information of at least one of the UEs may be a 5G-GUTI, a 5G-S-TMSI, an application layer ID, or a PRUK ID. As an option, in this modality of the present application, after receiving the identifier information of at least one UE, the first primary network device can determine the second primary network device based on the identifier information of the second UE (either of the at least one UE), so that the first primary network device can transmit a message to the second primary network device requesting context from the second UE (for example, a first request in this modality of the present application), and, after receiving the message, the second primary network device can transmit the context of the second UE to the first primary network device. In this way, the first primary network device can interact with the second primary network device. For example, in this form of the present application, to specifically implement the preceding step S202, steps S202a to S202c can be followed. S202a. The first primary network device determines the second primary network device based on the identifier information of the second UE. S202b. The first primary network device transmits a first request to the second primary network device. The first request may contain the identifier information of the second UE and may be used to request to obtain a context from the second UE. S202c. The first primary network device receives the context from the second UE, which is sent by the second primary network device. In this modality of the present application, after receiving the identifier information of at least one UE, the first primary network device can determine the second primary network device based on the identifier information of the second UE; and, after determining the second primary network device, the first primary network device transmits the first request to the second primary network device to request that it obtain the context of the second nircz Ln / zznz / E / YiAi UE. After receiving the first request, the second primary network device can transmit the context of the second UE to the first primary network device, so that the first primary network device can receive the context of the second UE. In this way, the first primary network device can interact with the second primary network device. As an option, in this modality of the present application, the first primary network device may retrieve, based on the identifier information of the second UE, information of the primary network device serving the second UE from a Network Repository Function (NRF) entity in order to determine the second primary network device. For example, if the first primary network device is assumed to be a relay AMF entity, the second UE is a remote UE, and the identifier information for the second UE is either 5G-GUTI or 5G-S-TMSI of the remote UE, the first primary network device can retrieve, based on the remote UE's 5G-GUTI or 5G-S-TMSI, information from the remote AMF entity serving the remote UE. In this way, after determining the remote AMF entity, the relay AMF entity can transmit a message to the remote AMF entity requesting it to obtain context from the remote UE (i.e., the first request) in order to interact with the remote AMF entity. It should be noted that the first primary network device may also implement any possible interaction with the second primary network device based on the identifier information of the second UE. This can be specifically determined according to the actual usage requirements and is not limited in this application. With the device interaction method established in this modality of the present application, in the communication from a UE to a network relay, a primary network device serving a UE can be determined based on the UE's identifier information. Therefore, a first primary network device can determine, based on the identifier information received from at least one UE, a second primary network device serving one of the at least one UEs, so as to interact with the second primary network device.For example, a relay main network device can implement interaction with a remote main network device serving a remote UE based on identifier information received from the remote UE, or a remote main network device can implement interaction with a relay main network device serving a relay UE based on identifier information received from the relay UE. In this way, an interaction between a relay main network device and a remote main network device can be implemented using the device interaction method of the modalities in this application. As an option, in this modality of the present application, after the preceding step S202c, the device interaction method established in this modality of the present application may also include the following step S203. S203. The first main network device determines, based on the context of the second UE, whether the second UE is granted the implementation of UE-to-network relay communication. In this application modality, after receiving the context from the second UE sent by the second primary network device, the first primary network device can authenticate the second UE based on that context. Specifically, the first primary network device can determine, based on the second UE's context, whether the second UE is granted UE-to-network relay communication. It can be understood that the context of the second EU may include concession information for the second EU. In this application, where the first main network device is the main relay network device, the first UE is the relay UE, the second UE is the remote UE, and the second UE is the UE that will establish a network UE-to-relay connection with the first UE. After receiving context from the remote UE, the main relay network device can determine whether the remote UE is granted the implementation of network UE-to-relay communication. Specifically, if the remote UE is granted the implementation of network UE-to-relay communication, the relay UE can establish a network UE-to-network connection with the remote UE; and, if the remote UE is not granted the implementation of network UE-to-relay communication, the relay UE can reject (or ignore) indirect connection establishment requests from the remote UE. It can be understood that a relay AMF entity that determines whether a remote UE is granted the implementation of a network relay UE communication can be a relay AMF entity that determines whether the remote UE can serve as the remote UE of the network relay UE connection. As an option, in this modality of the present application, before the preceding step S201, the device interaction method established in this modality of the present application may also include the following step S204. S204. The first main network device transmits an identifier request (Identifier nircz Ln / zznz / E / YiAi Request) to the first device. The identifier request can be used to request identifier information from a UE that has established or will establish a UE-to-network relay connection with the first UE. In this instance of the request, before receiving the identifier information from at least one UE sent by the first device, the first primary network device can transmit the identifier request to the first device to obtain the identifier information of the UE that has established or will establish a UE-to-network relay connection with the first UE. Then, after receiving the identifier request, the first device can transmit the identifier information of at least one UE to the first primary network device. Optionally, in this form of the present application, the identifier information of the first EU may be either the first EU's 5G-GUTI or the first EU's 5G-S-TMSI. This may be specifically determined according to the actual requirement and is not limited to this form of the present application. Optionally, in this form of the present application, the identifier application may transmit the first EU's identifier information. As an option, in this modality of the present application, if the first device is the access network device of the relay UE, the first main network device may transmit identifier information of the first UE in the identifier request in order to request the identifier information of the UE that has established or will establish a relay UE connection with the first UE. In this way, after the access network device receives the identifier request, the access network device may transmit to the first main network device the identifier information of the UE that has established or will establish a relay UE connection with the first UE (i.e., the identifier information of at least one UE). In this modality of the present application, if the first device has received the identifier request message, the first device may transmit to the first main network device the identifier information of at least one UE by means of a response message to the identifier request. As an option, in this form of the present application, the response message to the identifier request may also transmit identifier information of the first EU. In this modality of the present application, since the access network device can serve a variety of relay UEs, the access network device can clearly notify the first main network device, by having the identifier information of the first UE transmitted in the response message to the identifier request, that the second UE is specifically the UE associated with the first UE of communication from UE to network relay. For example, if the first main network device is assumed to be a relay main network device and the first device is a RAN of a relay UE, when the RAN transmits the relay main network device identifier information of a remote UE associated with the relay UE in the network UE-to-relay communication, the RAN may also transmit the relay main network device identifier information of the relay UE (for example, a 5G-GUT1 or a 5G-S-TMSI of the relay UE) in order to clearly notify the relay main network device which relay UE the remote UE is specifically associated with in the network UE-to-relay communication. As an option, in this modality of the present application, after the preceding step S201, the device interaction method established in this modality of the present application may also include the following steps S205 to S207. S205. The first primary network device transmits a second request to the third primary network device. The second request contains the identifier information of the second EU and can be used to request grant information from the second EU. S206. The first primary network device receives lease information from the second UE sent by the third primary network device. S207. The first main network device determines, based on the grant information of the second UE, whether the second UE is granted the implementation of UE-to-network relay communication. In this application, after receiving the identifier information for at least one UE, the first main network device can transmit the second request to the third main network device to obtain the grant information for the second UE. Then, after receiving the second request, the third main network device can transmit the grant information for the second UE to the first main network device. Therefore, after receiving the grant information for the second UE, the first main network device can determine whether to grant the second UE permission to implement UE-to-network relay communication. As an option, in the preceding steps S205 to S207, the identifier information of the second nircz ίη / ζζηζ / E / γίΛΐ The UE may be a SUCI of the second UE or a SUPI of the second UE. This may be specifically determined according to the actual requirement and is not limited to this modality of the present application. Alternatively, in this modality of the present application, the third primary network device may be the same device as the first primary network device or a different one. This may be specifically determined according to the actual requirement and is not limited to this modality of the present application. As an option, in this modality of the present application, the third main network device may be a Unified Data Management entity. Of course, in actual implementation, the third main network device could be any other possible entity. This can be specifically determined according to the actual use case, and this application does not limit it. For example, if the first main network device is assumed to be a relay main network device, the first device is a relay UE, and the third main network device is a UDM entity, and if the identifier information of at least one UE that the relay UE sends to the relay main network device is a SUCI or SUPI of a remote UE, the relay main network device can obtain, based on the remote UE's SUCI or SUPI, grant information from the remote UE through the UDM entity. Therefore, the relay main network device can determine, based on the remote UE's grant information, whether the remote UE is granted the implementation of UE-to-relay network communication. Specifically, when the remote UE is a UE that will establish a network relay UE connection with the relay UE, the first primary network device can determine, based on the remote UE's grant information, whether the remote UE is granted the implementation of network relay UE communication. If the remote UE is granted the implementation of network relay UE communication, the relay UE can establish a network relay UE connection with the remote UE; and, if the remote UE is not granted the implementation of network relay UE communication, the relay UE can reject (or ignore) indirect connection establishment requests from the remote UE. To describe the modalities of this application more clearly, the following modalities use Modality 1, Modality 2, Modality 3, and Modality 4 as examples to describe different application situations of the device interaction method established in the modalities of this application. Mode 1: The first main network device is a relay AMF entity and the first UE nircz ίη / ζζηζ / E / γίΛΐ is a relay UE; and the second main network device is a remote main network device, the second UE is a remote UE and the first device is the relay UE. In Mode 1, the relay AMF entity obtains remote UE identifier information from the relay UE (e.g., 5G-GUTI of the remote UE), retrieves information from the remote AMF entity based on the remote UE identifier information, and interacts with the remote AMF entity to obtain a context from the remote UE in order to authenticate the remote UE. The following describes Modality 1 with reference to Figure 3. As shown in Figure 3, in step 1, the relay UE receives a non-direct connection establishment request from the remote UE; or a network relay UE connection already exists between the relay UE and the remote UE. In one implementation, in step 2a, the relay UE transmits remote UE identifier information to the relay AMF entity using a NAS message. The remote UE identifier information can be a 5G-GUTI, a 5G-S-TMSI, a PEI, a SUCI, an application layer ID, a SUPI, a PRUK ID, or similar information from the remote UE. In another implementation, in step 2b, the relay AMF entity transmits an identifier request to the relay UE, which is used to request the relay UE to provide identifier information for a remote UE that is currently connected to or being serviced by the relay UE. In step 2b-1, after receiving the identifier request sent by the relay AMF entity, the relay UE transmits the remote UE identifier information to the relay AMF entity by means of a response message. It should be noted that, since the relay UE at that time is connected to or is servicing a variety of remote UEs, i.e., there is a variety of remote UEs, the relay UE can transmit to the relay AMF entity a list of identifier information of the variety of remote UEs. In one possible situation, in step 3a, if the remote UE identifier information provided by the relay UE is a 5G-GUTI or a 5G-S-TMSI of the remote UE, the relay AMF entity can retrieve information from the remote AMF entity based on the 5G-GUTI or 5G-S-TMSI of the remote UE, interact with the remote AMF entity based on the retrieved information to obtain a remote UE context from the remote AMF entity, and determine, based on the remote UE context, whether the remote UE is granted the implementation of a network relay UE communication. nircz ίη / ζζηζ / Ε / γίΛΐ In another possible situation, in step 3b, if the remote UE identifier information provided by the relay UE is the remote UE's SUCI or SUPI, the relay AMF entity can obtain grant information from the remote UE by interacting with a UDM entity in order to determine, based on the remote UE's grant information, whether the remote UE is granted the implementation of a network relay UE communication. Mode 2: The first main network device is a relay AMF entity and the first UE is a relay UE; and the second main network device is a remote main network device, the second UE is a remote UE and the first device is a RAN of the relay UE. In Mode 2, the relay AMF entity obtains remote UE identifier information from the RAN (e.g., remote UE 5G-GUTI), retrieves information from the remote AMF entity based on the remote UE identifier information, and interacts with the remote AMF entity to obtain remote UE context in order to authenticate the remote UE. The following describes Mode 2 with reference to Figure 4. As shown in Figure 4, in step 1, the relay UE receives a non-direct connection establishment request from the remote UE; or a network relay UE connection already exists between the relay UE and the remote UE. In one implementation, in step 2a, the RAN transmits remote UE identifier information to the relay AMF entity using an N2 interface message. The remote UE identifier information can be a 5G-GUTI, a 5G-S-TMSI, an application layer ID, or a remote UE PRUK ID. In another implementation, in step 2b, the relay AMF entity transmits to the RAN an identifier request that is used to request the RAN to provide identifier information of a remote UE that is currently associated with the relay UE for network relay UE communication; the identifier request may also transmit (include) identifier information of the relay UE, for example, a 5G-GUTI or a 5G-S-TMSI of the relay UE. In step 2b-1, after receiving the identifier request sent by the relay AMF entity, the RAN transmits to the relay AMF entity a response message that may transmit (include) remote UE identifier information or relay UE identifier information (e.g., a 5G-GUTI or a 5G-S-TMSI from the relay UE). It should be noted that, since the relay UE at that time is connected to or is servicing a variety of remote UEs, i.e., there is a variety of remote UEs, the RAN can transmit to the relay AMF entity a list of identifier information of the variety of remote UEs. In step 3, if the remote UE identifier information provided by the RAN is a 5G-GUTI or a 5G-S-TMSI of the remote UE, the relay AMF entity can retrieve information from the remote AMF entity based on the 5G-GUTI or 5G-S-TMSI of the remote UE, interact with the remote AMF entity based on the retrieved information to obtain a remote UE context from the remote AMF entity, and determine, based on the remote UE context, whether the remote UE is granted the implementation of a network relay UE communication. Mode 3: The first main network device is a remote AMF entity and the first UE is a remote UE; and the second main network device is a relay main network device, the second UE is a relay UE and the first device is the remote UE. In Mode 3, the remote AMF entity obtains relay UE identifier information from the remote UE (e.g., 5G-GUTI from the relay UE), retrieves relay AMF entity information based on the relay UE identifier information, and interacts with the relay AMF entity to obtain relay UE context in order to authenticate the relay UE. The following describes Mode 3 with reference to Figure 5. As shown in Figure 5, in step 1, the relay UE has completed the establishment of a network relay UE connection with the remote UE, i.e., a network relay UE connection already exists between the relay UE and the remote UE. In one implementation, in step 2a, the remote UE transmits relay UE identifier information to the remote AMF entity using a NAS message. The relay UE identifier information can be a 5G-GUTI, a 5G-S-TMSI, a PEI, a SUCI, an application layer ID, a PRUK ID, a SUPI, or similar identifiers from the relay UE. In another implementation, in step 2b, the remote AMF entity transmits an identifier request to the remote UE, which is used to request the remote UE to provide identifier information for a relay UE that is currently serving the remote UE. In step 2b-1, after receiving the identifier request sent by the remote AMF entity, the remote UE transmits relay UE identifier information to the remote AMF entity by means of a response message. It should be noted that, since there may be a variety of relay UE serving the remote UE, the RAN may transmit to the remote AMF entity a list of information of nircz ίη / ζζηζ / E / γίΛΐ identifier of the relay UE variety. In one possible situation, in step 3a, if the relay UE identifier information provided by the remote UE is a 5G-GUTI or 5G-S-TMSI of the relay UE, the remote AMF entity can retrieve information from the relay AMF entity based on the 5G-GUTI or 5G-S-TMSI of the relay UE, interact with the relay AMF entity based on the retrieved information to obtain a relay UE context from the relay AMF entity, and determine, based on the relay UE context, whether the relay UE is granted the implementation of a network relay UE communication. In another possible situation, in step 3b, if the relay UE identifier information provided by the remote UE is the relay UE's SUCI or SUPI, the remote AMF entity can obtain relay UE grant information by interacting with a UDM entity in order to determine, based on the relay UE grant information, whether the relay UE is granted the implementation of a network relay UE communication. Mode 4: The first main network device is a remote AMF entity and the first UE is a remote UE; and the second main network device is a relay main network device, the second UE is a relay UE and the first device is a relay UE RAN. In Mode 4, the remote AMF entity obtains relay UE identifier information from the RAN (relay UE 5G-S-TMSI), retrieves relay AMF entity information based on the relay UE identifier information, and interacts with the relay AMF entity to obtain relay UE context in order to authenticate the relay UE. The following describes Mode 4 with reference to Figure 6. As shown in Figure 6, in step 1, the relay UE has completed the establishment of a network relay UE connection with the remote UE, i.e., a network relay UE connection already exists between the relay UE and the remote UE. In one implementation, in step 2a, the RAN transmits relay UE identifier information to the remote AMF entity using an N2 interface message. The relay UE identifier information can be a 5G-GUTI, a 5G-S-TMSI, an application layer identification, or a relay UE PRUK ID. In another implementation, in step 2b, the remote AMF entity transmits an identifier request to the RAN, which is used to request the RAN to provide identifier information for a relay UE that is currently servicing the remote UE; the identifier request may also transmit (include) nircz Ln / zznz / E / YiAi identifier information from the remote UE, for example, a 5G-GUTI or a 5G-S-TMSI from the remote UE. In step 2b-1, after receiving the identifier request sent by the remote AMF entity, the RAN transmits to the remote AMF entity a response message that may transmit (include) relay UE identifier information or remote UE identifier information (e.g., a 5G-GUTI or a 5G-S-TMSI from the remote UE). It should be noted that, since there may be a variety of relay UEs serving the remote UE, the RAN may transmit to the remote AMF entity a list of identifier information for the relay UE variety. In step 3, if the relay UE identifier information provided by the RAN is a 5G-GUTI or 5G-S-TMSI of the relay UE, the remote AMF entity can retrieve information from the relay AMF entity based on the 5G-GUTI or 5G-S-TMSI of the relay UE, interact with the relay AMF entity based on the retrieved information to obtain a relay UE context from the relay AMF entity, and determine, based on the relay UE context, whether the relay UE is granted the implementation of a network relay UE communication. As shown in Figure 7, one embodiment of the present application establishes a main network device 300. The main network device 300 is a first main network device and includes a receiver module 301 and an interaction module 302.Receiver module 301 is configured to receive identifier information from at least one UE sent by a first device, where the at least one UE is at least one of the following: a UE that has established a UE-to-network relay connection with a first UE and a UE that is to establish a UE-to-network relay connection with the first UE; and interaction module 302 is configured to, after receiver module 301 receives identifier information from at least one UE, interact, based on the identifier information of a second UE, with a second primary network device, where the second UE is any one of the at least one UE, the first primary network device is a primary network device serving the first UE and the second primary network device is a primary network device serving the second UE. As an option, the interaction module may further include a determining submodule, a transmitting submodule, and a receiving submodule, where the determining submodule is configured to determine the second primary network device based on the identifier information of the second UE; the transmitting submodule is configured to transmit an initial request to the second primary network device determined by the determining submodule, where the initial request transmits the identifier information of the second UE and is used to request the retrieval of a context from the second UE; and the receiving submodule is configured to, after the transmitting submodule transmits the initial request to the second primary network device, receive the context of the second UE sent by the second primary network device. As an option, the main network device also includes a determinant module, and the determinant module is configured to, after the receiver submodule receives the context from the second UE sent by the second main network device, determine, based on the context of the second UE, whether the second UE is granted the implementation of a UE-to-network relay communication. As an option, the main network device also includes a transmitter module and the transmitter module is configured to, before the receiver module receives the identifier information from the second UE sent by the first device, transmit to the first device an identifier request that is used to request the retrieval of identifier information from the UE that has established or is going to establish a UE-to-network relay connection with the first UE. Optionally, the first device is either the first UE or an access network device, the access network device serves a relay UE, and the relay UE is either the first UE or the second UE. Optionally, the identifier information of at least one UE is transmitted in a NAS message, an N2 interface message, or a response message corresponding to an identifier request. Optionally, the identifier information of any one of the at least one UE is any of the following: a 5G-GUTI; a 5G-S-TMSI; an application layer identification; a PRUK ID; a PEI; a SUCI; and a SUPI. As an option, the first main network device further includes a transmitter module and a determinant module; the transmitter module is configured to, after the receiver module receives the identifier information of at least one UE sent by the first device, transmit to a third main network device a second request that transmits the identifier information of the second UE and is used to request the acquisition of grant information from the second UE; the receiver module is further configured to receive the grant information of the second UE sent by the third main network device; and the determinant module is configured to determine, based on the grant information of the second UE, whether the second UE is granted the implementation of a UE-to-network relay communication. The primary network device established in this modality of the present application may implement the processes carried out by the first network device described in the preceding modalities of the device interaction method and achieve the same technical effects. To avoid repetition, the details are not described herein. This modality of the present application establishes a main network device that is a first main network device and includes a receiver module and an interaction module.The receiver module is configured to receive identifier information from at least one UE sent by a first device, where the at least one UE is at least one of the following: a UE that has established a UE-to-network relay connection with a first UE and a UE that is to establish a UE-to-network relay connection with the first UE; and the interaction module is configured to, after the receiver module 301 receives the identifier information from at least one UE, interact, based on the identifier information of a second UE, with a second primary network device, where the second UE is any one of the at least one UE, the first primary network device is a primary network device serving the first UE and the second primary network device is a primary network device serving the second UE.In UE-to-relay network communication, a primary network device serving a UE can be determined based on the UE's identifier information. Therefore, a first primary network device can determine, based on identifier information received from at least one UE, a second primary network device serving one of those at least one UEs, in order to interact with the second primary network device. For example, a relay primary network device can interact with a remote primary network device serving a remote UE based on identifier information received from the remote UE, or a remote primary network device can interact with a relay primary network device serving a relay UE based on identifier information received from the relay UE.In this way, an interaction between a main relay network device and a remote main network device can be implemented using the device interaction method of the modalities of this application. Alternatively, one embodiment of the present application further specifies a main network device comprising a processor 501, a memory 502, and a program or instructions nircz ίη / ζζηζ / E / γίΛΐ stored in memory 502 and executable by the processor 501, as shown in Figure 8. When the processor 501 executes the program or instructions, the processes of the preceding embodiments of the device interaction method are applied, and the same technical effects are achieved. To avoid repetition, the details are not described herein. Figure 8 is a schematic diagram of the software of a core network device according to one modality of this application. As shown in Figure 8, the core network device 500 may include: one or more processors 501, a memory 502, and a transceiver 503. The 503 transceiver can be configured to: receive identifier information from at least one UE sent by a first device, where the at least one UE is at least one of the following: a UE that has established a UE-to-network relay connection with a first UE and a UE that is to establish a UE-to-network relay connection with the first UE; and interact, based on identifier information from a second UE, with a second primary network device, where the second UE is any of the at least one UE; where the first primary network device is a primary network device serving the first UE and the second primary network device is a primary network device serving the second UE. Optionally, processor 501 can be configured to determine, based on the identifier information of the second UE, the second primary network device; and transceiver 503 is configured to transmit a first request to the second primary network device determined by processor 501 and receive a context from the second UE sent by the second primary network device, where the first request transmits the identifier information of the second UE and is used to request obtaining a context from the second UE. As an option, the 501 processor can also be configured to, after the 503 transceiver receives the context from the second UE sent by the second main network device, determine, based on the context of the second UE, whether the second UE is granted the implementation of a UE-to-network relay communication. As an option, the 503 transceiver can also be configured to, before receiving the context from the second UE sent by the first device, transmit to the first device an identifier request that is used to request the retrieval of identifier information from a UE that has established or is going to establish a UE-to-network relay connection with the first UE. Optionally, the first device is either the first UE or an access network device, the access network device services a relay UE, and the relay UE is either the first UE or the second UE. Optionally, the identifier information for at least one UE is transmitted in a NAS message, an N2 interface message, or a response message corresponding to an identifier request. Optionally, the identifier information for any of the at least one UE is any of the following: a 5G-GUTI; a 5G-S-TMSI; an application layer identification; a PRUK ID; a PEI; a SUCI; and a SUPI. As an option, transceiver 503 can be further configured to, after receiving identifier information from at least one UE sent by the first device, transmit a second request to a third main network device and receive grant information from the second UE sent by the third main network device, wherein the second request transmits identifier information from the second UE and is used to request the obtaining of grant information from the second UE; and processor 501 is configured to determine, based on the grant information from the second UE received by transceiver 503, whether the second UE is granted the implementation of a UE-to-network relay communication. This embodiment of the present application establishes a primary network device that is a first primary network device and a transceiver of the primary network device can be configured to receive identifier information from at least one UE sent by a first device, wherein the at least one UE is at least one of the following: a UE that has established a UE-to-network relay connection with a first UE and a UE that is to establish a UE-to-network relay connection with the first UE; and interact, based on the identifier information of a second UE, with a second primary network device, wherein the second UE is any of the at least one UE; wherein the first primary network device is a primary network device serving the first UE and the second primary network device is a primary network device serving the second UE.In UE-to-relay network communication, a primary network device serving a UE can be determined based on the UE's identifier information. Therefore, a first primary network device can determine, based on identifier information received from at least one UE, a second primary network device serving one of those UEs, in order to interact with the second primary network device. For example, a relay primary network device can interact with a remote primary network device serving a remote UE based on identifier information received from the remote UE, or a remote primary network device can interact with a relay primary network device serving a relay UE based on identifier information received from the relay UE.In this way, an interaction between a main relay network device and a remote main network device can be implemented using the device interaction method of the modalities of this application. It can be understood that, in the modalities of the present application, the transceiver 503 can implement the receiver module 301, the interaction module 302 and the transmitter module of the preceding schematic structural diagram (e.g., figure 7) of the main network device; and the processor 501 can implement the determining module in the main network device. It should be noted that one of the two 501 processors in Figure 8 is shown with dashed lines to indicate that the primary network device may contain one or more 501 processors. In Figure 8, the primary network device containing two 501 processors is used as an example for the description. It can be understood that, in this modality of the present application, the main network device 500 can be a relay main network device 01 or a remote main network device 03 of the communication system shown in Figure 1 of the preceding modalities. One embodiment of the present application further establishes a readable storage medium where a program or instructions are stored, and when the processor 501 of Figure 8 executes the program or instructions, the processes executed by the first network device of the preceding embodiments of the device interaction method are applied, and the same technical effects are obtained. To avoid repetition, the details are not described herein. The processor may be a processor from a UE or a network device of the preceding modalities. The readable storage medium may be a storage medium that can be read by a computer, such as read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk. One modality of the present application further specifies a chip. The chip includes a processor and a communication interface coupled to the processor, and the processor is configured to execute a program or instructions for the purpose of implementing the processes of the preceding modalities of the device interaction method and achieving the same technical effects. To avoid repetition, the details are not described herein. nircz Ln / zznz / E / YiAi It can be understood that the chip that establishes this modality of the present application can also be called a system-level chip, chip-based system, chip-operated system, etc. It should be noted that, in this specification, the purpose of the terms "includes," "comprises," and all their variants is to encompass non-exhaustive inclusions. For example, a process, method, article, or apparatus that includes a list of elements not only includes those elements but also other elements not expressly mentioned, or includes elements inherent to said process, method, article, or apparatus. In the absence of other limitations, an element preceded by "includes a..." does not exclude the existence of other identical elements in the process, method, article, or apparatus that includes the element. Furthermore, it should be noted that the scope of the method and apparatus of the implementations in this application is not limited to the execution of functions in the order shown or explained, but may also include the execution of functions in an essentially simultaneous manner or in a reverse order, depending on the functions involved. For example, the described method may be executed in a different order than that described, or steps may be added, omitted, or combined. Likewise, the functions described with reference to some examples may be combined in other examples. Based on the preceding description of the implementations, a person skilled in the discipline can clearly understand that the method described above can be implemented using software in combination with a common hardware platform, and, alternatively, using hardware alone. However, in most cases, the first implementation is preferred. Based on this clarification, the technical solutions in this application, or at least the portion relevant to the aforementioned discipline, can essentially be implemented as a software product.The software product is stored on a storage medium (e.g., a ROM / RAM, a magnetic disk, or an optical disk) and includes several instructions to order the terminal (which may be a cell phone, a computer, an air conditioner, a network device, or a similar item) to execute the methods described in the modalities of this application. The foregoing describes the forms of this application with reference to the accompanying drawings. However, this application is not limited to the specific forms described above. The specific forms described above are illustrative rather than restrictive. As indicated in this application, a person with common skills in the discipline may develop many other forms without departing from the principles of this application and the scope of protection of the

Claims

1. A method of device interaction comprising: a first main network device receiving identifier information from at least one User Equipment (UE) from a first device, further characterized in that the at least one UE consists of at least one of the following: a UE that has established a UE-to-network relay connection with a first UE and a UE that is to establish a UE-to-network relay connection with the first UE; and the first main network device interacting, based on the identifier information from the second UE, with a second main network device, further characterized in that the second UE is any one of the at least one UE, the first main network device is a main network device serving the first UE, and the second main network device is a main network device serving the second UE.

2. The method according to claim 1, further characterized in that the interaction of the first main network device, based on the identifier information of the second UE, with a second main network device consists of: the first main network device determining the second main network device based on the identifier information of the second UE; the first main network device transmitting a first request to the second main network device, further characterized in that the first request transmits the identifier information of the second UE and is used to request the obtaining of a context from the second UE; and the first main network device receiving the context of the second UE sent by the second main network device.

3. The method according to claim 2, further characterized in that, after the first main network device receives the context from the second UE sent by the second main network device, the method further consists of: the first main network device determining, based on the context from the second UE, whether the second UE is granted the implementation of UE-to-network relay communication.

4. The method according to claim 1, further characterized in that, before a first main network device receives identifier information from at least one UE sent by a first device, the method further comprises: the first main network device transmitting an identifier request to the first device, further characterized in that the identifier request is used to request the retrieval of identifier information from a UE that has established or is to establish a UE-to-network relay connection with the first UE.

5. The method according to claim 1, further characterized in that the first device is the first UE or an access network device, further characterized in that the access network device serves a relay UE and the relay UE is the first UE or the second UE.

6. The method according to claim 1, further characterized in that the identifier information of at least one UE is transmitted in a non-access stratum (NAS) message, an N2 interface message, or a response message corresponding to an identifier request.

7. The method according to claim 1, further characterized in that the identifier information of any one of the at least one UE is any of the following elements: a 5G Globally Unique Temporary Identifier (5G-GUTI); a 5G S-temporary Mobile Subscription Identifier (5G-S-TMS1); an application layer identifier; a ProSe Relay User Key Identity (PRUK ID); a Permanent Equipment Identifier (PEI); a Subscription Concealed Identifier (SUCI); and a Subscription Permanent Identifier (SUPI).

8. The method according to claim 1, further characterized in that, after a first main network device receives the identifier information of at least one UE sent by a first device, the method further consists of: the first main network device transmitting a second request to the third main network device, further characterized in that the second request transmits the identifier information of the second UE and is used to request the acquisition of grant information from the second UE; the first main network device receiving grant information from the second UE sent by the third main network device; and the first main network device determining, based on the grant information from the second UE, whether the second UE is granted the implementation of UE-to-network relay communication.

9. A core network device, further characterized in that it is a first core network device and includes a receiver module and an interaction module; the receiver module is configured to receive identifier information from at least one User Equipment (UE) sent by a first device, further characterized in that the at least one UE is at least one of the following: a UE that has established a UE-to-network relay connection with a first UE and a UE that is to establish a UE-to-network relay connection with the first UE;and the interaction module is configured to, after the receiver module receives the identifier information from at least one UE, interact with a second primary network device based on the identifier information of a second UE, where the second UE is one of at least one UE, the first primary network device is a primary network device serving the first UE, and the second primary network device is a primary network device serving the second UE.

10. The main network device according to claim 9, further characterized in that the interaction module comprises a determining submodule, a transmitting submodule, and a receiving submodule; the determining submodule is configured to determine the second main network device based on the identifier information of the second UE; the transmitting submodule is configured to transmit a first request to the second main network device as determined by the determining submodule, further characterized in that the first request transmits the identifier information of the second UE and is used to request the acquisition of a context from the second UE; and the receiving submodule is configured to, after the transmitting submodule transmits the first request to the second main network device, receive the context of the second UE sent by the second main network device.

11. The main network device according to claim 10, further characterized in that the main network device further comprises a determining module; and the determining module is configured to, after the receiving submodule receives the context of the second UE sent by the second main network device, determine, based on the context of the second UE, whether the second UE is granted the implementation of a UE-to-network relay communication.

12. The main network device according to claim 9, further characterized in that the main network device further comprises a transmitter module; and the transmitter module is configured so that, before the receiver module receives the identifier information from at least one UE sent by the first device, it transmits to the first device an identifier request to be used to request the retrieval of identifier information from the UE that has established or will establish a UE-to-network relay connection with the first UE.

13. The main network device according to claim 9, further characterized in that the first device is the first UE or an access network device, the access network device serves a relay UE and the relay UE is the first UE or the second UE.

14. The main network device according to claim 9, further characterized in that the identifier information of at least one UE is transmitted in a non-access layer (NAS) message, an N2 interface message, or a corresponding response message to an identifier request.

15. The main network device according to claim 9, further characterized in that the identifier information of any one of the at least one UE is any of the following elements: a 5G Globally Unique Temporary Identifier (5G-GUTI); a 5G S-temporary Mobile Subscription Identifier (5G-S-TMSI); an application layer identifier; a ProSe Relay User Key Identity (PRUK id); a Permanent Equipment Identifier (PEI); a Subscription Concealed Identifier (SUCI); and a Subscription Permanent Identifier (SUPI).

16. The main network device according to claim 9, further characterized in that the first main network device further comprises a transmitter module and a determinant module; the transmitter module is configured to, after the receiver module receives the identifier information of at least one UE sent by the first device, transmit a second request to a third main network device, further characterized in that the second request transmits the identifier information of the second UE and is used to request the acquisition of grant information from the second UE; the receiver module is further configured to, after the transmitter module transmits the second request, receive the grant information of the second UE sent by the third main network device;and the determining module is configured to determine, based on the grant information from the second UE received by the receiving module, whether the second UE is granted the implementation of a UE-to-network relay communication.

17. A main network device, comprising a processor, a memory, and a program or instructions stored in the memory and capable of execution by the processor, and, when the processor executes the program or instructions, the steps of the device interaction method according to any one of claims 1 to 8 are applied. nircz ίη / ζζηζ / E / γίΛΐ 18. A readable storage medium, further characterized by storing a program or instructions and, when a processor executes the program or instructions, the steps of the device interaction method according to any of claims 1 to 8 are applied.

19. A computer program, further characterized in that at least one processor executes it to implement the device interaction method according to any of claims 1 to 8.

20. A main network device, further characterized by being configured to execute the steps of the device interaction method according to any of claims 1 to 8.