Communication method and apparatus

Abstract

The present application relates to the technical field of communications, and provides a communication method and apparatus. The method comprises: sending a first message, wherein the first message is used for requesting a first terminal and a second terminal to perform dual direction; receiving a second message, wherein the second message comprises first information, and the first information indicates that the first terminal and the second terminal allow dual direction; and performing dual direction on the basis of the first information. In the present application, a first device requests a network to enable the first terminal and the second terminal to perform dual direction, and the first device performs dual direction only when receiving the first information, i.e., when allowing the first terminal and the second terminal to perform dual direction. On this basis, it is clear that dual direction can be performed.

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on February 8, 2024, with application number 202410178289.X and application name "A Communication Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The embodiments of the present application relate to the field of communication technology, and in particular to a communication method and apparatus. Background Art

[0004] With the development of communication technology, future mobile communication devices may include two user equipment (UE) or two universal subscriber identity modules (USIM). The mobile communication device can create sessions through two UEs (or two USIMs) to connect to two radio access networks (RAN) and transmit service data through the two RANs. The mobile communication device can perform dual-directional transmission, that is, the service data of the mobile communication device can be directed to a certain UE for transmission, or switched from one UE to another UE for transmission. The relevant technology does not explain how to determine whether the mobile communication device can perform dual-directional transmission. Summary of the Invention

[0005] The present application provides a communication method and apparatus to clarify that dual-directional communication can be performed based on two UEs.

[0006] In a first aspect, the present application provides a communication method that can be performed by a first device, the first device comprising: a first terminal and a second terminal. The first terminal (or second terminal) can be the terminal itself, or a component in the terminal (e.g., a processor, a chip, or a chip system), or a logic module or software that implements all or part of the terminal functions. This application does not specifically limit this.

[0007] This method can be applied to 5G communication systems or communication systems above 5G, and can also be applied to non-terrestrial communication systems, which is not specifically limited in this application. Execution is as follows:

[0008] A first message is sent, where the first message is used to request the first terminal and the second terminal to perform bidirectional orientation; a second message is received, where the second message includes first information, where the first information indicates that the first terminal and the second terminal allow bidirectional orientation; and bidirectional orientation is performed based on the first information.

[0009] In the present application, the first device requests the network to allow the first terminal and the second terminal to perform dual orientation. The first device performs dual orientation only when it receives the first information, that is, the network (for example, the unified data management function) allows the first terminal and the second terminal to perform dual orientation. Based on this, it can be clearly stated that the first device allows the execution of dual orientation.

[0010] In an optional manner, the first device performs dual-direction based on service network capability information and the first information, where the service network capability information includes: the service network of the first terminal supports dual-direction, and / or the service network of the second terminal supports dual-direction.

[0011] Based on this, it is necessary not only to consider whether the network allows the first terminal and the second terminal to perform dual-direction, but also to consider whether the service network of the first terminal supports dual-direction and whether the service network of the second terminal supports dual-direction, so that the first device can clearly perform dual-direction.

[0012] In an optional manner, the first terminal of the first device receives second information from the first network element, the second information is used to indicate that the service network of the first terminal supports dual-direction, and the first network element is used for access management of the first terminal; and / or, the second terminal of the first device receives third information from the second network element, the third information is used to indicate that the service network of the second terminal supports dual-direction, and the second network element is used for access management of the second terminal.

[0013] Based on this, the first terminal of the first device can obtain whether the service network of the first terminal supports dual-direction based on the second information, and the second terminal of the first device can obtain whether the service network of the second terminal supports two-way based on the third information, so that the first device can obtain whether the network supports dual-direction.

[0014] In an optional manner, the first message is sent by the first terminal, and the first message includes the first identity of the second terminal.

[0015] In the present application, the first message includes the first identity identifier of the second terminal so that the network element on the core network side can determine that the request is a dual-directional request from the first terminal and the second terminal.

[0016] In an optional manner, the first message is sent by the first terminal, and the first message includes a bidirectional identifier, the bidirectional identifier is generated by the first device, or the bidirectional identifier is generated by a third network element, the third network element is used to manage data information of the second terminal, and the bidirectional identifier is associated with the second terminal.

[0017] In this application, the first message includes a dual-direction identifier associated with the second terminal so that the network element on the core network side can determine that the request is a dual-direction request from the first terminal and the second terminal. At the same time, the first identity identifier of the second terminal is avoided, which is beneficial to the information protection of the second terminal.

[0018] In an optional manner, the first message includes a dual-directional identifier, including: the first message includes a dual-directional request container, and the dual-directional request container includes the dual-directional identifier.

[0019] In the present application, the first message includes a bidirectional identifier, which can be included in a bidirectional request container, thereby ensuring the security of the bidirectional identifier information and facilitating forwarding by the first network element without requiring additional processing.

[0020] In an optional manner, the first message includes: first indication information, where the first indication information is used to request the first terminal and the second terminal to perform dual-direction.

[0021] In the present application, when the first message includes the first indication information, the network element on the core network side can directly determine based on the first indication information that the first device requests the first terminal to perform dual-direction with the second terminal.

[0022] In an optional manner, the bidirectional identifier is generated by a third network element, and the first device further receives the bidirectional identifier from the third network element.

[0023] In this application, the first device receives the bidirectional identifier from the third network element, eliminating the need for the first device to generate the bidirectional identifier, thereby reducing the processing complexity of the first device and ensuring the uniqueness of the bidirectional identifier within the third network element.

[0024] In a second aspect, the present application provides a communication method that can be performed by a third network element, the third network element being a data management network element configured to manage data information between a first terminal and a second terminal. The third network element can be the second network element itself, or a component in the third network element (e.g., a processor, chip, or chip system), or a logic module or software that implements all or part of the functions of the third network element. This application does not specifically limit this.

[0025] Receive a third message from the first network element, the third message including: the second identity of the first terminal and the second identity of the second terminal, the first network element is used for access management of the first terminal, and the third message is used to request the first terminal and the second terminal to perform dual-direction; determine first information based on the second identity of the first terminal and the second identity of the second terminal, the first information indicating that the first terminal and the second terminal allow dual-direction; send the first information to the first network element.

[0026] In this application, a third network element receives a third message from a first network element requesting that the first terminal and the second terminal perform bidirectional communication. The third message includes the second identity identifier of the first terminal and the second identity identifier of the second terminal. The third network element determines the first information based on the second identity identifier of the first terminal and the second identity identifier of the second terminal. Thereafter, the third network element sends the first information to the first network element, based on which the first network element can determine that bidirectional communication is permitted between the first terminal and the second terminal.

[0027] In an optional manner, the third network element determines the first information based on the second identity identifier of the first terminal, the second identity identifier of the second terminal, and the contract information, where the contract information indicates that the first terminal is associated with the second terminal.

[0028] In the present application, the third network element determines the first information by referring to the second identity identifier of the first terminal, the second identity identifier of the second terminal, and the contract information, which can improve data processing efficiency.

[0029] In an optional manner, the third network element determines the first information based on the second identity identifier of the first terminal, the second identity identifier of the second terminal and the service network capability information, where the service network capability information includes: the service network of the first terminal supports dual directionality, and / or the service network of the second terminal supports dual directionality.

[0030] In this application, the third network element refers to the second identity identifier of the first terminal, the second identity identifier of the second terminal and the service network capability information to determine the first information. Then, after the first terminal and / or the second terminal obtains the first information, dual-direction can be directly executed.

[0031] In an optional manner, when the service network capability information includes that the service network of the second terminal supports dual-direction, the third network element receives fourth information from the second network element, where the fourth information is used to indicate that the service network of the second terminal supports dual-direction.

[0032] Based on this, the third network element can obtain whether the service network of the second terminal supports dual-direction based on the fourth information.

[0033] In an optional manner, the third message further includes: second indication information, where the second indication information is used to request the first terminal and the second terminal to perform dual-direction.

[0034] In the present application, when the first message includes the first indication information, the third message also includes the second indication information. The third network element can directly determine to request the first terminal and the second terminal to perform dual-direction based on the second indication information.

[0035] In an optional manner, the first information is sent to a second network element, and the second network element is used for access management of the second terminal.

[0036] In the present application, the third network element sends the first information to the second network element so that the second network element can clearly know that the first terminal and the second terminal allow dual directionality.

[0037] In a third aspect, the present application provides a communication method that can be performed by a third network element, where the third network element is a data management network element and is configured to manage data information between a first terminal and a second terminal. The third network element can be the third network element itself, or a component within the third network element (e.g., a processor, chip, or chip system), or a logic module or software that implements all or part of the functions of the third network element. This application does not specifically limit this.

[0038] A third message is received from the first network element, where the third message includes: a dual-directional identifier and a second identity identifier of the first terminal, the dual-directional identifier is generated for the first terminal or the second terminal, or the dual-directional identifier is generated for the third network element, the first network element is used for access management of the first terminal, the dual-directional identifier is related to the second terminal, and the third message is used to request the first terminal and the second terminal to perform dual-directional access; first information is determined based on the dual-directional identifier and the second identity identifier of the first terminal, the first information indicating that the first terminal and the second terminal allow dual-directional access; and the first information is sent to the first network element.

[0039] In this application, a third network element receives a third message from a first network element requesting that a first terminal and a second terminal perform dual-direction communication. The third message includes the first terminal's second identity and a dual-direction identifier. The third network element determines the first information based on the first terminal's second identity and the dual-direction identifier. Subsequently, the third network element sends the first information to the first network element, based on which the first network element can clearly indicate that the first terminal and the second terminal are allowed to perform dual-direction communication. Using the dual-direction identifier avoids using the second terminal's first identity, which is beneficial for protecting the second terminal's information.

[0040] In an optional manner, the third network element also generates a dual-directional identifier based on the dual-directional capability information of the second terminal and / or the dual-directional subscription information of the second terminal; and sends the dual-directional identifier to the second network element, which is used for access management of the second terminal.

[0041] In the present application, the third network element generates a dual-directional identifier, and the first terminal or the second terminal does not need to generate a dual-directional identifier, which reduces the data processing of the first terminal or the second terminal and reduces the processing complexity of the first terminal or the second terminal.

[0042] In an optional manner, the third network element further stores a first association relationship between the bi-directional identifier and the second identity identifier of the second terminal.

[0043] In the present application, the third network element stores the first association relationship between the dual-directional identifier and the second identity identifier of the second terminal so that the third network element can determine the second identity identifier of the second terminal after receiving the dual-directional identifier.

[0044] In an optional manner, the second network element determines the first information based on the dual-directional identifier, the second identity identifier of the first terminal, and the contract information, where the contract information indicates that the first terminal is associated with the second terminal.

[0045] In the present application, the third network element determines the first information by referring to the second identity identifier, the dual-directional identifier and the contract information of the first terminal, which can improve data processing efficiency.

[0046] In an optional manner, the second network element determines the first information based on the dual-direction identifier, the second identity identifier of the first terminal and the service network capability information, and the service network capability information includes: the service network of the first terminal supports dual-direction, and / or the service network of the second terminal supports dual-direction.

[0047] In this application, the third network element refers to the second identity identifier, dual-directional identifier and service network capability information of the first terminal to determine the first information. Then, after the first terminal and / or the second terminal obtains the first information, it can directly execute dual-directional.

[0048] In an optional manner, when the service network capability information includes that the service network of the second terminal supports dual-direction, the second network element further receives fourth information from the second network element, where the fourth information is used to indicate that the service network of the second terminal supports dual-direction.

[0049] In an optional manner, the third message further includes: second indication information, where the second indication information is used to request the first terminal and the second terminal to perform dual-direction.

[0050] In an optional manner, the third network element further sends the first information to the second network element, and the second network element is used for access management of the second terminal.

[0051] In a fourth aspect, the present application provides a communication method that can be performed by a first network element, which is an access management network element of a first terminal. The first network element can be the first network element itself, or a component in the first network element (e.g., a processor, a chip, or a chip system), or a logic module or software that implements all or part of the fourth network element function. This application does not specifically limit this.

[0052] Receive a first message from a first terminal, the first message including: a first identity identifier of a second terminal, the first message being used to request the first terminal and the second terminal to perform dual-orientation; obtain a second identity identifier of the second terminal based on the first identity identifier of the second terminal; send a third message, the third message including: the second identity identifier of the first terminal and the second identity identifier of the second terminal; receive first information, the first information indicating that the first terminal and the second terminal allow dual-orientation.

[0053] In this application, the first network element obtains the second identity of the second terminal based on the first identity of the second terminal in the first message, and then sends a third message to the third network element requesting the first terminal and the second terminal to perform dual-direction. The third message includes the second identity of the first terminal and the second identity of the second terminal. The third network element determines the first information based on the second identity of the first terminal and the second identity of the second terminal. The third network element then sends the first information to the first network element, based on which the first network element can clearly indicate that the first terminal and the second terminal allow dual-direction.

[0054] In an optional manner, the first network element sends the first identity identifier of the second terminal to the fourth network element or the second network element, the fourth network element is used for authentication management of the second terminal, and the second network element is used for access management of the second terminal; and receives the second identity identifier of the second terminal from the fourth network element or the second network element.

[0055] In this application, the first network element can send the first identity identifier of the second terminal to the fourth network element used for authentication management of the second terminal or the second network element used for access management of the second terminal to obtain the second identity identifier of the second terminal, thereby improving data processing efficiency.

[0056] In an optional manner, the first network element further stores the first information.

[0057] In the present application, the first network element stores the first information so as to allow the first terminal to establish a bi-directional session when the first terminal requests to establish a bi-directional session.

[0058] In an optional manner, the first network element further obtains bi-directional policy information according to the first information; and sends the bi-directional policy information to the first terminal.

[0059] In this application, the first network element can clarify which services need to perform dual-direction according to the dual-direction policy information.

[0060] In an optional manner, the first network element sends a policy request message to the fifth network element, and the policy request message includes: third indication information, the third indication information is used to request the first terminal and the second terminal to execute dual-directional policy information, and the fifth network element is used for policy management of the first terminal; receiving the dual-directional policy information from the fifth network element.

[0061] In an optional manner, the first network element further determines, based on the first information, that the first terminal allows establishment of a bidirectional session.

[0062] Based on this, the first network element may allow the first terminal to establish a bi-directional session when the first terminal requests to establish a bi-directional session.

[0063] In an optional manner, the first message also includes first indication information, and the first indication information is used to request the first terminal and the second terminal to perform dual-direction; the third message also includes second indication information, and the first indication information is used to request the first terminal and the second terminal to perform dual-direction.

[0064] In a fifth aspect, the present application provides a communication method that can be performed by a first network element, which is an access management network element of a first terminal. The first network element can be the first network element itself, or a component in the first network element (e.g., a processor, a chip, or a chip system), or a logic module or software that implements all or part of the fourth network element function. This application does not specifically limit this.

[0065] Receive a first message from a first terminal, the first message includes a dual-directional identifier, the dual-directional identifier is generated for the first terminal or the second terminal, or the dual-directional identifier is generated for a third network element, the third network element is used to manage data information of the second terminal, the dual-directional identifier is related to the second terminal, and the first message is used to request the first terminal and the second terminal to perform dual-directional; send a third message, the third message includes: the second identity identifier of the first terminal and the dual-directional identifier; receive the first information, the first information indicates that the first terminal and the second terminal allow dual-directional.

[0066] In this application, the first network element obtains the second identity of the second terminal based on the dual-directional identifier in the first message, and then sends a third message to the third network element requesting the first terminal and the second terminal to perform dual-directional communication. The third message includes the second identity of the first terminal and the dual-directional identifier. The third network element determines the first information based on the second identity and the dual-directional identifier of the first terminal. Afterwards, the third network element sends the first information to the first network element, based on which the first network element can clearly determine that the first terminal and the second terminal allow dual-directional communication. By using the dual-directional identifier, the use of the first identity of the second terminal can be avoided, which is beneficial to the protection of the information of the second terminal.

[0067] In an optional manner, the first message includes a dual-directional identifier, including: the first message includes a dual-directional request container, and the dual-directional request container includes the dual-directional identifier.

[0068] In an optional manner, the first network element further stores the first information.

[0069] In an optional manner, the first network element further obtains bi-directional policy information according to the first information; and sends the bi-directional policy information to the first terminal.

[0070] In an optional manner, the first network element also sends a policy request message to the fifth network element, and the policy request message includes: third indication information, the third indication information is used to request the first terminal and the second terminal to execute dual-directional policy information, and the fifth network element is used for policy management of the first terminal; receiving the dual-directional policy information from the fifth network element.

[0071] In an optional manner, the first network element further determines, based on the first information, that the first terminal allows establishment of a bidirectional session.

[0072] In an optional manner, the first message also includes first indication information, and the first indication information is used to request the first terminal and the second terminal to perform dual-direction; the third message also includes second indication information, and the first indication information is used to request the first terminal and the second terminal to perform dual-direction.

[0073] In a sixth aspect, an embodiment of the present application provides a communication device, which may be a first device (a first terminal and a second terminal), a first network element, or a third network element. The communication device has the functions of implementing the first to fifth aspects above. For example, the communication device includes modules, units, or means corresponding to the steps involved in the first to fifth aspects above. The functions, units, or means may be implemented by software, or by hardware, or may be implemented by hardware executing the corresponding software.

[0074] In one possible design, the communication device includes a processing unit and a transceiver unit, wherein the transceiver unit can be used to send and receive signals to achieve communication between the communication device and other devices, for example, the transceiver unit is used to receive a first message; the processing unit can be used to perform some internal operations of the communication device. The transceiver unit can be called an input / output unit, a communication unit, etc., and the transceiver unit can be a transceiver; the processing unit can be a processor. When the communication device is a module (such as a chip) in a communication device, the transceiver unit can be an input / output interface, an input / output circuit, or an input / output pin, etc., and can also be called an interface, a communication interface, or an interface circuit, etc.; the processing unit can be a processor, a processing circuit, or a logic circuit, etc.

[0075] In another possible design, the communication device includes a processor and may also include a transceiver, the transceiver is used to send and receive signals, and the processor executes program instructions to complete the method in any possible design or implementation of the first to fifth aspects above. The communication device may also include one or more memories, the memories are used to couple with the processor, and the memories can store the necessary computer programs or instructions for implementing the functions involved in the first aspect above. The processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the communication device implements the method in any possible design or implementation of the first to fifth aspects above.

[0076] In another possible design, the communication device includes a processor, which can be coupled to a memory. The memory can store the necessary computer programs or instructions for implementing the functions of the first to fifth aspects described above. The processor can execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the communication device implements the method of any possible design or implementation of the first to fifth aspects described above.

[0077] In another possible design, the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and execute the method in any possible design or implementation of the first to fifth aspects above.

[0078] It can be understood that in the sixth aspect above, the processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. In addition, the above processors can be one or more, and the memories can be one or more. The memory can be integrated with the processor, or the memory and the processor can be set separately. In the specific implementation process, the memory can be integrated with the processor on the same chip, or can be set on different chips respectively. The embodiment of the present application does not limit the type of memory and the setting method of the memory and the processor.

[0079] In a seventh aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned first device (first terminal and second terminal), a first network element, a second network element, a third network element, a fourth network element and a fifth network element.

[0080] In an eighth aspect, the present application provides a chip system, which includes a processor and may also include a memory, for implementing the methods described in aspects 1 to 5. The chip system may be composed of a chip or may include a chip and other discrete devices.

[0081] In a ninth aspect, the present application further provides a computer-readable storage medium, in which computer-readable instructions are stored. When the computer-readable instructions are executed on a computer, the computer executes the methods in the first to fifth aspects.

[0082] In a tenth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the methods of the embodiments of the first to fifth aspects above.

[0083] For the technical effects that can be achieved in the above-mentioned second to tenth aspects, please refer to the description of the technical effects that can be achieved by the corresponding possible design schemes in the above-mentioned first aspect, and this application will not repeat them here. BRIEF DESCRIPTION OF THE DRAWINGS

[0084] FIG1 shows a schematic diagram of a communication system provided by an embodiment of the present application;

[0085] FIG2 shows a schematic diagram of a scenario of a bidirectional conversation;

[0086] FIG3 shows a schematic flow chart of a method for bidirectional session association;

[0087] FIG4 shows a flow chart of a communication method provided in an embodiment of the present application;

[0088] FIG5 is a schematic diagram showing a flow chart of a communication method provided in an embodiment of the present application;

[0089] FIG6 shows a flow chart of a communication method provided in an embodiment of the present application;

[0090] FIG7 shows a flow chart of a communication method provided in an embodiment of the present application;

[0091] FIG8 shows a flow chart of a communication method provided in an embodiment of the present application;

[0092] FIG9 shows a flow chart of a communication method provided in an embodiment of the present application;

[0093] FIG10 shows a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0094] FIG11 shows a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0095] FIG12 shows a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0096] In order to make the purpose, technical solutions and advantages of this application clearer, the present application will be further described in detail below with reference to the accompanying drawings. The specific operating methods in the method embodiments can also be applied to the device embodiments or system embodiments. In the description of this application, unless otherwise specified, "multiple" means two or more. Therefore, the implementation of the device and method can refer to each other, and the repeated parts will not be repeated.

[0097] Figure 1 shows a schematic diagram of a mobile communication network architecture, which includes a terminal, access network equipment, access and mobility management functions, session management functions, user plane functions, policy control functions, network slice selection functions, network slice specific authentication and authorization functions, network warehouse functions, network data analysis functions, unified data management functions, unified data storage functions, authentication service functions, network capability exposure functions, terminal wireless capability management functions, binding support functions, application functions, and a data network (DN) connected to the operator's network. The terminal can access the wireless network through the access node at its current location. The terminal can send service data to the data network and receive service data from the data network through the access network equipment and user plane functions.

[0098] The access and mobility management function is mainly used for terminal attachment, mobility management, tracking area update procedures, etc. in the mobile network. In the 5G communication system, the access and mobility management function can be the access and mobility management function (AMF). In future communication systems (such as 6G communication systems), the access and mobility management function can still be AMF, or it can have other names, which is not limited in this application.

[0099] The session management function is mainly used for session management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating Internet Protocol addresses to terminals, selecting user plane functions that provide message forwarding functions, etc. In 5G communication systems, the session management function may be a session management function (SMF). In future communication systems (such as 6G communication systems), the session management function may still be SMF, or may have other names, which is not limited in this application. This application also involves a multicast / broadcast session management network element, which may be a multicast / broadcast-session management function (MB-SMF), which is mainly used for session management in mobile networks, such as session establishment, modification, and release.

[0100] The user plane function is mainly used to process user messages, such as forwarding and billing. In the 5G communication system, the user plane function can be the user plane function (UPF). In future communication systems (such as 6G communication systems), the user plane function can still be UPF, or it can have other names, which is not limited in this application.

[0101] Policy control function, including policy control function, charging policy control function, QoS control, etc. In 5G communication systems, the policy control function may be a policy control function (PCF). In future communication systems (such as 6G communication systems), the policy control function may still be PCF, or may have other names, which is not limited in this application.

[0102] The network slice selection function is mainly used to select a suitable network slice for the terminal's service. In a 5G communication system, the network slice selection function may be a network slice selection function (NSSF). In future communication systems (such as a 6G communication system), the network slice selection function may still be NSSF, or may have other names, which is not limited in this application.

[0103] The network slice-specific authentication and authorization function (NSSAAF) is mainly used for authentication and authorization of terminals accessing specific network slices.

[0104] The network repository function is mainly used to provide registration and discovery of network functions or services provided by network functions. In 5G communication systems, the network repository function can be a network repository function (NRF). In future communication systems (such as 6G communication systems), the network repository function can still be NRF, or it can have other names, which are not limited by this application.

[0105] The network data analysis function can collect data from various network functions, such as the policy control function, session management function, user plane function, access management function, and application function (through the network capability exposure function), and perform analysis and prediction. In the 5G communication system, the network data analysis function can be the network data analysis function (NWDAF). In future communication systems (such as 6G communication systems), the network data analysis function can still be NWDAF, or it can have other names, which is not limited by this application.

[0106] The unified data management function is mainly used to manage the contract information of the terminal. In the 5G communication system, the unified data management function can be a unified data management (UDM) function. In future communication systems (such as 6G communication systems), the unified data management function can still be the UDM function, or it can have other names, which is not limited by this application.

[0107] The unified data storage function is mainly used to store structured data information, including contract information, policy information, and network data or business data defined in a standard format. In the 5G communication system, the unified data storage function can be a unified data repository (UDR) function. In future communication systems (such as 6G communication systems), the unified data storage function can still be a UDR function, or it can have other names, which is not limited by this application.

[0108] The authentication service function is mainly used to perform security authentication on the terminal. In the 5G communication system, the authentication service function can be the authentication server function (AUSF). In future communication systems (such as 6G communication systems), the authentication service function can still be AUSF, or it can have other names, which is not limited by this application.

[0109] The network capability exposure function can controllably expose some network functions to applications. In 5G communication systems, the network capability exposure function can be NEF. In future communication systems (such as 6G communication systems), the network capability exposure function can still be NEF, or it can have other names, which are not limited by this application.

[0110] The terminal radio capability management function is used to store and manage the radio capabilities of terminals within the network. In 5G communication systems, the terminal radio capability management function may be the user equipment radio capability management function (UCMF). In future communication systems (such as 6G communication systems), the terminal radio capability management function may still be UCMF, or may have other names, which are not limited by this application.

[0111] The binding support function is used to maintain the correspondence between the protocol (Internet protocol, IP) addresses and service functions of the interconnected user networks. In the 5G communication system, the binding support function can be the binding support function (BSF). In future communication systems (such as 6G communication systems), the binding support function can still be BSF, or it can have other names, which is not limited by this application.

[0112] The application function can provide service data of various applications to the control plane function of the operator's communication network, or obtain network data information and control information from the control plane function of the communication network. In the 5G communication system, the application function can be an application function (AF). In future communication systems (such as 6G communication systems), the application function can still be AF, or it can have other names, which is not limited by this application.

[0113] Data networks are primarily used to provide data transmission services to terminals. They can be private networks, such as local area networks (LANs), public data networks (PDNs), such as the Internet, or proprietary networks deployed by operators, such as those configured with the Internet Protocol Multimedia Core Network Subsystem (IMS) service.

[0114] It should be noted that in the embodiments of the present application, functions may also be referred to as network elements, network functions, functional entities, devices, etc. For example, the access and mobility management function may also be referred to as an access and mobility management network element, an access and mobility management network function, or an access and mobility management functional entity, etc. The names of the various functions are not limited in this application. Those skilled in the art may replace the names of the aforementioned functions with other names while still performing the same functions, and all such changes fall within the scope of protection of this application.

[0115] To facilitate understanding of the embodiments of the present application, the following briefly describes the terms or processing procedures involved in the embodiments of the present application.

[0116] 1) First device

[0117] The first device includes: at least two terminals, and / or at least two user identification modules (e.g., universal subscriber identity modules (USIM) cards). For example, the first device includes terminal 1 and terminal 2; or, the first device includes USIM card 1 and USIM card 2; or, the first device includes terminal 1, terminal 2, and terminal 3; or, the first device includes USIM card 1, USIM card 2, and USIM card 3. These are merely exemplary and not limiting. Optionally, the first device includes at least two protocol stacks, with terminal 1 replaced by protocol stack 1 and terminal 2 replaced by protocol stack 2.

[0118] In the embodiment of the present application, the two terminals included in the first device are taken as an example for illustration, and the two terminals can be two devices / apparatuses. Alternatively, the two UEs included in the first device can be two USIMs, for example, the first UE can be the first USIM, and the second UE can be the second USIM. Alternatively, the first device is a terminal, and the terminal includes two USIMs, the first UE corresponds to the first USIM, and the second UE corresponds to the second USIM. Accordingly, in the embodiment of the present application, the first device can be replaced by a terminal, the UE is replaced by a USIM, the first UE is replaced by the first USIM, and the second UE is replaced by the second USIM. Alternatively, the first device is a dual-directional device, and the dual-directional device includes two USIMs, the first UE corresponds to the first USIM, and the second UE corresponds to the second USIM. Accordingly, in the embodiment of the present application, the first device can be replaced by a dual-directional device, the UE is replaced by a USIM, the first UE is replaced by the first USIM, and the second UE is replaced by the second USIM.

[0119] 2) Dual Direction

[0120] The first device includes terminal 1 and terminal 2. The first device can be dual-directed, that is, the service data of the first device can be directed to be transmitted through terminal 1 or terminal 2, or switched from being transmitted through terminal 1 to being transmitted through terminal 2. Alternatively, terminal 1 and terminal 2 belong to the same user, and the service data of the user can be directed to be transmitted through terminal 1 or terminal 2, or switched from being transmitted through terminal 1 to being transmitted through terminal 2.

[0121] 3) DualSteer Session (also known as Inter-UE Associated Session)

[0122] Here, the example in which the first device includes two UEs (UE1 and UE2) or two USIM cards (USIM card 1 and USIM card 2) is used for illustration. Figure 2 shows that the PDU session of UE1 (PDU Session ID#1) and the PDU session of UE2 (PDU Session ID#2) share the same IP address. UE1 creates PDU Session ID#1 through RAN1, and UE2 creates PDU Session ID#2 through RAN2. RAN1 and RAN2 are 3GPP access types (3GPP Access Type). RAN1 and RAN2 may have the same (or different) radio access technology type (RAT Type). RAT Type may be 5G NR, 5G NR (satellite), or 6G RAT. For example, RAN1 is 5G NR and RAN2 is 6G RAT.

[0123] Before the service is switched between UE1 and UE2, the service data corresponding to the IP is transmitted through UE1's PDU Session ID#1 (that is, the PDU layer is associated with UE1's transmission channel (UE1-RAN1 channel (ye)). After the service is switched between UE1 and UE2, the service data corresponding to the IP is transmitted through UE2's PDU Session ID#2 (that is, the PDU layer is associated with UE2's transmission channel (UE2-RAN2 channel (ye)). Before and after the service is switched between UE1 and UE2, the connection between the PDU layer and the application layer (App layer) (for example, the socket connection) does not change, that is, the IP address used by the application does not change, and service continuity is not affected. Furthermore, the activation of UE2's PDU Session ID#2 may also trigger the deactivation or release of UE1's PDU Session ID#1.

[0124] Bidirectionality can be an attribute or purpose of a PDU session, for example, the type of the PDU session is bidirectionality or the PDU session is used to provide a bidirectional function. The service data carried by the PDU session can be directed to the first terminal or the second terminal.

[0125] By creating a dual-directional PDU session, the latency of service switching between different UEs can be reduced, improving the user experience. Refer to Figure 3 to understand the association of UE sessions. The following solution for the association of UE sessions is explained by combining the data interaction between UE1, UE2, AMF1, AMF2, SMF, and UDM.

[0126] In step 300A, UE1 and UE2 register to join the network respectively.

[0127] Step 300B: UDM stores the association relationship between UE1 and UE2.

[0128] For example, the association between SUPI1 (identity of UE1) and SUPI2 (identity of UE2). It should be understood that the association between the two UEs exists during the operator's account opening process for the UE (for example, UE1 and UE2 both belong to the same user), so the UDM can store the association between SUPI1 and SUPI2.

[0129] In step 301, UE1 sends an X1 message to AMF1. The X1 message includes: UE1's PDU session establishment request message and a bidirectional session identifier. Accordingly, AMF1 receives the X1 message.

[0130] It should be noted that, in step 301, the identifier of the bidirectional session may be generated by UE1 or UE2, which is not specifically limited here.

[0131] When executing step 301, UE1 may forward the X1-th message to AMF1 through RAN1.

[0132] In step 302, AMF1 sends an X2 message to SMF, where the X2 message includes: UE1's PDU session establishment request message and the identifier of the bidirectional session. Accordingly, SMF receives the X2 message.

[0133] Optionally, AMF1 selects an SMF that supports bidirectionality based on the identifier of the bidirectional session.

[0134] In addition, AMF1 performs step 303 only if it determines that UE1 supports dual-directional according to step 300A; otherwise, it sends a rejection message to UE1.

[0135] Step 303: The SMF sends the X3 message to the UDM. The X3 message includes: the identifier of the bidirectional session and the identifier of the SMF. Correspondingly, the UDM receives the X3 message.

[0136] In addition, the SMF performs step 303 only if it determines according to step 300A that UE1 supports dual-directional support; otherwise, it sends a rejection message to UE1.

[0137] Step 304A: The SMF stores the association between the identifier of the bi-directional session and the PDU session of UE1.

[0138] In addition, SMF also selects UPF for UE1's PDU session, allocates an IP address to UE1, and allocates N4 Session ID for UE1's PDU session, where N4 Session ID is used for interaction between SMF and UPF.

[0139] Step 304B: The UDM stores the association between the identifier of the bi-directional session and the identifier of the SMF.

[0140] In step 305, the UDM sends the X4th message to the AMF2, where the X4th message includes the SMF identifier. Accordingly, the AMF2 receives the X4th message.

[0141] For example, the UDM may determine UE2 based on the association relationship between UE1 and UE2 in step 300B, and determine AMF2 based on the registration information of UE2 in step 300A.

[0142] Step 306: SMF sends UE1's PDU session establishment accept message to UE1.

[0143] For example, the establishment acceptance message includes the IP address allocated by the SMF to UE1.

[0144] In step 307, UE2 sends the X5th message, which includes: UE2's PDU session establishment request message and the bidirectional session identifier (the same as the bidirectional session identifier in step 301). Accordingly, AMF2 receives the X5th message.

[0145] When executing step 307, UE2 may forward the X5th message to AMF2 via RAN2.

[0146] Step 308: AMF2 determines the SMF based on the association between the identifier of the bidirectional session and the identifier of the SMF.

[0147] In step 309, AMF2 sends the X6th message to SMF, which includes the PDU session establishment request message of UE2 and the identifier of the bidirectional session. Accordingly, SMF receives the X6th message.

[0148] Step 310: The SMF creates a first association relationship between the PDU session of UE1 and the PDU session of UE2 according to the identifier of the bidirectional session.

[0149] For example, the SMF searches for the association between the identifier of the bidirectional session stored in step 304A and the PDU session of UE1 based on the identifier of the bidirectional session received in step 309, obtains the identifier of PDU session 1, and creates a first association relationship between the identifier of PDU session 1 and the identifier of PDU session 2.

[0150] Based on this, the identifier of UE1's PDU session 1 and the identifier of UE2's PDU session 2 are associated. However, the related art does not explain how to determine whether to execute the process in Figure 3 (or how to determine whether to execute dual-direction). Based on this, the present application provides a communication method to clarify how to determine whether a first device can execute dual-direction. This method can be illustrated by taking the data interaction between a first terminal, a second terminal, a first network element, a second network element, and a third network element as an example. The first terminal and the second terminal can be terminals or USIM cards in the first device. The first terminal and the second terminal can also be different devices that can share an IP address. For example, if user A's mobile phone and car are in the same spatial location (the mobile phone is in the car, or the distance between the mobile phone and the car is within a distance threshold), the mobile phone and the car can share the same IP address. In this case, the mobile phone can be understood as the first terminal, and the car can be understood as the second terminal. Alternatively, if user A's mobile phone and tablet are in the same spatial location (the distance between the mobile phone and the tablet is within a distance threshold), the mobile phone and the tablet can share the same IP address. In this case, the mobile phone can be understood as the first terminal, and the tablet can be understood as the second terminal. This application does not specifically limit whether the first terminal and the second terminal are in the same device or in different devices. In specific applications, other terminals may be involved. This application does not limit the number of terminals, as long as the terminals share the same IP address. This application uses the first terminal and the second terminal as an example for illustration.

[0151] The first and second network elements are used for terminal attachment, mobility management, and tracking area update procedures in the mobile network. For example, the first network element is the AMF. The third network element is used to manage terminal subscription information. For example, the third network element is the UDM. This can be understood by referring to the following two specific embodiments.

[0152] Example 1

[0153] In Figure 4, the first terminal and the second terminal are located in the first device. The first network element is used for access management of the first terminal, and the first network element is AMF1. The second network element is used for access management of the second terminal, and the second network element is AMF2. The third network element is UDM. The execution is as follows:

[0154] In step 401, a first terminal sends a first message including a first identity of a second terminal, requesting the first terminal to perform a bidirectional call with the second terminal (i.e., the bidirectional call session described above). Accordingly, AMF1 receives the first message.

[0155] It should be noted that the first message can be a new type of message associated with bidirectional communication, and the request for bidirectional communication can be determined based on the first message. Alternatively, the first message can reuse an existing NAS message, and by carrying information such as bidirectional communication request information in the NAS message, the core network element can determine whether to execute bidirectional communication. This is not specifically limited here.

[0156] The first terminal sends the first message, which can be understood as the first device sending the first message through the first terminal.

[0157] In order to facilitate the use of the AMF1 first message to request the first terminal and the second terminal to perform dual-direction, the first message includes the first identity of the second terminal. The first identity can be the identity of the terminal interacting between the core network device and the access network device, for example, a subscription concealed identifier (SUCI) or a 5G-GUTI (5G globally unique temporary identity). This is only an example and does not specifically limit the form of the first identity. In addition, the first message including the first identity of the second terminal can also be understood as the first message including a dual-direction request container, which includes the first identity of the second terminal.

[0158] In addition, the first message may further include first indication information, where the first indication information is used to request the first terminal to perform dual-steering with the second terminal or to request the first device to be in dual-steering mode. The first indication information may be dual-steering request indication information (for example, a dual-steering request, an association request, or a dual-steering mode). The first indication information may be indicated by a parameter, such as indicating by parameter 1 that the first terminal is requested to perform dual-steering with the second terminal.

[0159] In addition, when the first message is a NAS message, the NAS message may be a registration request message or a service request message, and the NAS message includes the first indication message and the first identity of the second terminal. The NAS message may also include a PDU session establishment request message of UE1. This application does not specifically limit this.

[0160] It should also be noted that, in addition to including the first identity identifier of the second terminal, the first message generally also includes the first identity identifier of the first terminal.

[0161] In step 402, AMF1 obtains the second identity identifier of the second terminal according to the first identity identifier of the second terminal.

[0162] The second identity identifier may be an identity identifier of a terminal for interaction between core network devices, such as a user permanent identifier (SUPI).

[0163] For example, when executing step 402, AMF1 may send the first identity of the second terminal to a fourth network element (the fourth network element is used for authentication management of the second terminal, for example, the fourth network element is an AUSF). After the fourth network element parses the second identity of the second terminal, it sends the second identity of the second terminal to AMF1. For example, AMF1 requests the AUSF to convert SUCI2 (the first identity of the second terminal) into SUPI2 (the second identity of the second terminal).

[0164] Alternatively, AMF1 may send the first identity of the second terminal to AMF2 (AMF2 stores the second identity of the second terminal in the context of the second terminal during the registration process of the second terminal). After AMF2 parses the second identity of the second terminal, it sends the second identity of the second terminal to AMF1. When the first identity of the second terminal is 5G-GUTI, AMF1 stores the second identity of the second terminal in the context of the second terminal according to the structure of 5G-GUTI.<AMF Region ID><AMF Set ID><AMF Pointer> The identifier of AMF2 can be determined. Based on this, AMF1 requests AMF2 to obtain the second identity identifier SUPI2 of the second terminal.

[0165] In step 403, AMF1 sends a third message. This message includes the second identity of the first terminal (which AMF1 obtains by searching the first terminal's context) and the second identity of the second terminal. The third message requests that the first terminal perform bidirectional communication with the second terminal. In response, the UDM receives the third message.

[0166] It should be noted that, when the third message includes the second identity of the second terminal, it can be understood that the third message is used to request the first terminal to perform bi-directional communication with the second terminal.

[0167] In addition, when the first message includes the first indication information, the third message includes second indication information, where the second indication information is used to request the first terminal to perform bi-directional directionality with the second terminal. The second indication information can be the same as the first indication information. In addition to the first indication information, the second indication information can also include information added by AMF1, such as the location of the first terminal, etc., which is not specifically limited in this application.

[0168] Step 404: The UDM determines first information according to the second identity of the first terminal and the second identity of the second terminal, where the first information indicates that the first terminal and the second terminal allow bi-directional communication.

[0169] In one embodiment, the UDM may determine the first information based on the second identity of the first terminal, the second identity of the second terminal, and the contract information received from the AMF1. The contract information includes the contract information between the first terminal and the network, and the contract information between the second terminal and the network, indicating that the second identity of the first terminal and the second identity of the second terminal are associated. For example, when the first terminal signs a contract with a carrier, the user belonging to the first terminal is user 1, and when the second terminal signs a contract with the carrier, the user belonging to the second terminal is user 1. In this case, the UDM may associate the second identity of the first terminal with the second identity of the second terminal. Based on the association between the second identity of the first terminal and the second terminal, the UDM determines the first information, indicating that the first and second terminals can perform dual-direction. For another example, if the first terminal and the second terminal belong to the same user, when the user signs a contract with the carrier, the carrier may store the association between the second identity of the first terminal and the second terminal. For another example, if the contract data of the first terminal includes the second identity of the second terminal, or if the contract data of the second terminal includes the second identity of the first terminal, the second identity of the first terminal and the second terminal are considered to be associated.

[0170] In another embodiment, the UDM may also determine the first information based on the second identity of the first terminal, the second identity of the second terminal, and the service network capability information received from AMF1. The service network capability information includes: whether the service network of the first terminal supports dual-direction, and / or whether the service network of the second terminal supports dual-direction. It should be noted that the UDM may request the service network capability of the first terminal from AMF1, and the UDM may request the service network capability of the second terminal from AMF2. Alternatively, the UDM pre-configures the service network capability of the first terminal and pre-configures the service network capability of the second terminal.

[0171] In the embodiment of FIG4 , since the UDM receives a third message from AMF1 requesting the first terminal to perform bidirectional routing with the second terminal, it is assumed that AMF1 supports bidirectional routing (i.e., the first terminal's service network supports bidirectional routing). The UDM only needs to determine whether the second terminal's service network supports bidirectional routing. For example, the UDM may request AMF2 whether the second terminal's service network supports bidirectional routing, and AMF2 may send a fourth message to the UDM, which may indicate that the second terminal's service network supports bidirectional routing.

[0172] In another embodiment, the UDM may further determine the first information based on the second identity of the first terminal, the second identity of the second terminal, the subscription information, and the service network capability information received from the AMF1. For example, the UDM may determine, based on the subscription information, that the second identity of the first terminal is associated with the second identity of the second terminal, and then determine the first information based on whether the service network of the first terminal supports dual-directionality and whether the service network of the second terminal supports dual-directionality.

[0173] It should be noted that the first information may indicate authorization to associate the first terminal with the second terminal, authorization to perform dual-steer, permission to operate the first terminal and the second terminal in dual-steer mode, or permission to operate the first device in dual-steer mode. The first information may be indicated by "DualSteer authorized" or "DualSteer allowed."

[0174] Optionally, the UDM determines fifth information based on the second identity of the first terminal and the second identity of the second terminal, where the fifth information indicates that bidirectional communication between the first terminal and the second terminal is not allowed. Alternatively, the UDM may determine the fifth information based on the second identity of the first terminal, the second identity of the second terminal, and the contract information.

[0175] Optionally, the UDM further stores the first information or the fifth information, which facilitates the UDM to process subsequent bidirectional related actions, for example, in the case of storing the first information, coordinating the session management of the first terminal and the second terminal.

[0176] In step 405, the UDM sends the first information to the AMF1. In response, the AMF1 receives the first information.

[0177] For example, after receiving the first information, AMF1 determines based on the first information that the first terminal allows establishment of a bidirectional session.

[0178] The AMF1 may store the first information to determine that the first terminal is allowed to request to perform bidirectional communication (ie, to create a bidirectional session).

[0179] It should be noted that the UDM also sends the first information to the AMF2 so that the AMF2 can determine, based on the first information, whether the second terminal allows the establishment of a bidirectional session. Accordingly, the AMF2 can also store the first information to determine whether the second terminal is allowed to request the execution of bidirectional (i.e., to establish a bidirectional session).

[0180] In addition, AMF1 may also obtain bidirectional policy information based on the first information and send the bidirectional policy information to the first terminal. The bidirectional policy information may indicate the service type requiring bidirectional use. For example, if the bidirectional policy information indicates that service 1 requires bidirectional use and service 2 does not, then when service 1 is triggered, the first terminal determines to use bidirectional use based on the bidirectional policy information. Furthermore, the bidirectional policy information may indicate service directionality or a handover policy. For example, service 1 is directed to the first terminal or service 2 is directed to the second terminal, or service 1 allows handover between the first terminal and the second terminal, or service 1 allows handover between the first terminal and the second terminal. For example, AMF1 may send a policy request message to a fifth network element (the fifth network element is used for bidirectional policy management or policy management for the first terminal, such as a PCF). The policy request message includes third indication information, which is used to request that the first terminal and the second terminal implement the bidirectional policy information. AMF1 may then receive the bidirectional policy information from the fifth network element. Optionally, the third indication information is used to request implementation of the bidirectional policy information, or the third indication information is the first information. Specifically, the third indication information may be DualSteer operation, DualSteer indication, DualSteer authorized, or DualSteer allowed.

[0181] In step 406, AMF1 sends a second message to the first terminal, where the second message includes the first information, and the first information indicates that the first terminal and the second terminal allow bidirectional communication. In response, the first terminal receives the second message.

[0182] It should be noted that if the UDM determines the fifth information based on the second identity of the first terminal, the second identity of the second terminal, and the contract information in step 404, then the UDM sends the fifth information to AMF1 in step 405, and the second message in step 406 includes the fifth information, and step 407 below is not performed. Furthermore, AMF1 may not obtain bidirectional policy information based on the fifth information. AMF1 may also determine, based on the fifth information, that the first terminal's request for bidirectional execution is not permitted.

[0183] The first terminal receives the second message, which can be understood as the first device receiving the second message through the first terminal.

[0184] Step 407: The first terminal and the second terminal perform bi-directional direction-finding based on the first information.

[0185] It should be noted that, when the first terminal and the second terminal determine that the service network of the first terminal and the service network of the second terminal support dual-directionality, the first terminal and the second terminal may directly perform dual-directionality based on the first information.

[0186] The first terminal and the second terminal perform dual orientation based on the first information, which can be understood as the first device performing dual orientation for the first terminal and the second terminal based on the first information, or the first device performing dual orientation based on the first information, which is used for the first terminal and the second terminal.

[0187] In an optional embodiment, the first terminal and the second terminal perform dual-direction based on the service network capability information and the first information. Specifically, the first terminal needs to obtain the service network capability information of the first terminal, and the second terminal needs to obtain the service network capability information of the second terminal. For example, before executing step 401, the first terminal may register its dual-direction capability information with AMF1, and AMF1 may provide feedback to the first terminal on whether the first terminal's service network supports dual-direction. The second terminal may register its dual-direction capability information with AMF2, and AMF2 may provide feedback to the second terminal on whether the second terminal's service network supports dual-direction. Based on this, the first terminal determines that the first terminal's service network supports dual-direction, and the second terminal determines that the second terminal's service network supports dual-direction. Alternatively, before executing step 407, the first terminal requests the service network capability information of the first terminal from AMF1 and receives second information from AMF1, wherein the second information indicates that the first terminal's service network supports dual-direction. The second terminal requests the service network capability information of the second terminal from AMF2 and receives third information from AMF2, wherein the third information indicates that the second terminal's service network supports dual-direction. Alternatively, the first device requests the capability information of the service network of the first terminal from AMF1 through the first terminal, and the first device receives the second information from AMF1 through the first terminal; the first device requests the capability information of the service network of the second terminal from AMF2 through the second terminal, and the first device receives the third information from AMF2 through the second terminal.

[0188] Optionally, after step 407, if the terminals in the first device change, for example, the first device includes a first terminal and a third terminal, the first device needs to request the first terminal and the third terminal to perform bidirectional positioning, and then determine whether to perform bidirectional positioning based on the authorization result sent by the network (for example, whether the first terminal and the third terminal allow bidirectional positioning or the first terminal and the third terminal do not allow bidirectional positioning). If the first terminal and the third terminal allow bidirectional positioning, the first device performs bidirectional positioning. If the first terminal and the third terminal do not allow bidirectional positioning, the first device does not perform bidirectional positioning.

[0189] It should be noted that the message / information transmission between the above-mentioned terminals and network elements, and between network elements, may be direct transmission or indirect transmission via other network elements or devices, and this application does not specifically limit this. For example, the transmission of a first message between a first terminal and AMF1 can be understood as the first terminal transmitting the first message to AMF1 via RAN1, or it can also be understood as the first terminal transmitting the first message directly to AMF1. The transmission of a third message between AMF1 and UDM can be understood as AMF1 transmitting the third message to UDM via SMF, or AMF1 transmitting the third message directly to UDM. This is for illustrative purposes only.

[0190] In this application, the first device requests the network to allow the first terminal and the second terminal to perform dual orientation. The first device performs dual orientation only when it receives the first information, that is, the network (for example, UDM) allows the first terminal and the second terminal to perform dual orientation. Based on this, it can be clearly stated that the first device allows dual orientation to be performed.

[0191] The following describes the solution of the present application in combination with data interaction between UE1 (ie, the first terminal), UE2 (ie, the second terminal), AMF1 (ie, the first network element), AMF2 (ie, the second network element), and UDM (ie, the third network element). The details are as follows:

[0192] Case 1: UE1 / UE2 requests UDM to perform dual-orientation between UE1 and UE2. After UDM allows UE1 and UE2 to perform dual-orientation, UE1 / UE2 determines whether to perform dual-orientation based on the capability information of the service network supported by UE1 / UE2.

[0193] Refer to Figure 5 and execute as follows:

[0194] Step 500: UDM stores the association between UE1 and UE2.

[0195] For example, the second identity identifier (SUPI1) of UE1 and the second identity identifier (SUPI2) of UE2 are stored in association. It should be understood that the association between the two UEs exists during the operator's account opening process for the UE (for example, UE1 and UE2 both belong to the same user), so the UDM can store the association relationship between SUPI1 and SUPI2.

[0196] Step 501: UE2 sends a registration request message to AMF2, where the registration request message includes the dual-directional capability information of UE2. Accordingly, AMF2 receives the registration request message.

[0197] For example, if UE2 supports dual-steering, the registration request message may carry DualSteer support.

[0198] In addition, the registration request message may also carry the first identity of UE2, for example, SUCI2 or 5G-GUTI2.

[0199] Step 502: AMF2 sends capability information of UE2's service network to UE2.

[0200] For example, if AMF2 supports dual-steering, it sends DualSteer support to UE2.

[0201] In step 503, UE1 sends a first message to AMF1. The first message includes the first identity of UE2 (SUCI or 5G-GUTI1). The first message is used to request the first terminal to perform bidirectional communication with the second terminal. Accordingly, AMF1 receives the first message.

[0202] For example, the first message may directly include the first identity of UE2, or may include a dual-directional request container. The dual-directional request container carries the first identity of UE2. This can be understood by referring to the description of step 401 above and will not be repeated here.

[0203] Optionally, the first message further includes: first indication information, where the first indication information is used to request UE1 and UE2 to perform dual-steering. The first indication information may be dual-steering request indication information (DualSteer request or Association request).

[0204] Optionally, the first message may be a NAS message. The NAS message may be a registration request message or a service request message, and the NAS message includes the first indication message and the first identity of UE2. When the NAS message is a registration request message, it may also include capability information of UE2.

[0205] Optionally, the NAS message may also include a PDU session establishment request message (PDU establishment request) of UE1. This application does not specifically limit this.

[0206] It should be noted that, in addition to including the first identity identifier of the second terminal, the first message generally also includes the first identity identifier of the first terminal.

[0207] It should also be noted that step 503 is performed only if UE1's serving network supports bidirectionality and UE2's serving network also supports bidirectionality. Furthermore, when UE2's serving network supports bidirectionality, there is no need to determine whether UE2's serving network supports bidirectionality. Since AMF2 can process the first message from UE2, it is assumed that UE2's serving network supports bidirectionality.

[0208] In addition, when UE1 and UE2 are in the first device and the first device turns on the dual-directional mode (DualSteer mode) (ie, a mode that adopts dual-directional transmission of service data), the above-mentioned step 503 is performed.

[0209] Step 504: AMF1 obtains the second identity of UE2 (for example, SUPI2) according to the first identity of UE2.

[0210] For example, AMF1 may send SUCI2 to a fourth network element (for example, the fourth network element is an AUSF), which parses SUCI2 to obtain SUPI2 and then sends it to AMF1. Alternatively, AMF1 may send 5G-GUTI2 to AMF2 (during the registration process of the second terminal, AMF2 stores the second identity of UE2 in the context of UE2), which parses 5G-GUTI2 to obtain SUPI2 and then sends it to AMF1. This can be understood with reference to the description of step 402 above and will not be repeated here.

[0211] In step 505, AMF1 sends a third message, which includes the second identity of UE1 (obtained by searching UE1's context) and the second identity of UE2. The third message is used to request UE1 to perform bidirectional communication with UE2. Accordingly, the UDM receives the third message.

[0212] In addition, when the first message includes the first indication information, the third message includes the second indication information, and the second indication information is used to request the first terminal to perform bidirectional communication with the second terminal. This can be understood by referring to the description of step 403 above, which is not repeated here.

[0213] Step 506: The UDM determines first information according to the second identity of UE1, the second identity of UE2, and the subscription information. The first information indicates that bidirectional communication is allowed between UE1 and UE2.

[0214] The first information may indicate authorization for association between UE1 and UE2, or authorization for UE1 and UE2 to perform dual-steering. The first information may be indicated by DualSteer authorized or DualSteer allowed.

[0215] In step 507A, the UDM sends the first information to the AMF1, and the AMF1 receives the first information accordingly.

[0216] In step 507B, the UDM sends the first information to the AMF2. Correspondingly, the AMF1 receives the first information.

[0217] The execution order of the above steps 507A and 507B is not limited.

[0218] In step 508A, AMF1 stores the first information.

[0219] AMF1 stores the first information to determine that UE1 is allowed to request to perform bidirectional communication (ie, to create a bidirectional session).

[0220] In step 508B, AMF2 stores the first information.

[0221] AMF2 stores the first information to determine that UE2 is allowed to request to perform bidirectional directionality.

[0222] Optionally, AMF2 obtains dual-directional policy information (Dual Steer policy) from PCF based on the first information (DualSteer authorized), sends the Dual Steer policy to UE2, and UE2 further uses the Dual Steer policy for the first device. For example, when AMF2 receives DualSteer authorized, AMF2 sends an AMPolicyControl_Create / Update message to PCF, and the message includes third indication information (Dual Steer indication). PCF sends the Dual Steer policy to AMF2 based on the Dual Steer indication. The Dual Steer policy is used by the first device to determine how the service is directed to UE1 for transmission or UE2 for transmission. For example, the Dual Steer policy includes which services are transmitted through UE1 and which services are transmitted through UE2. For another example, the Dual Steer policy includes whether all services of the Dual Steer are preferentially transmitted through UE1 or UE2. This is only an example and does not specifically limit the dual-directional policy information.

[0223] The execution order of the above steps 508A and 508B is not limited.

[0224] In step 509, AMF1 sends a second message to UE1, where the second message includes the first information, and the first information indicates that UE1 and UE2 allow bidirectional communication. UE1 receives the second message accordingly.

[0225] In step 510, UE1 and UE2 perform dual-directional communication based on the first information.

[0226] In the embodiment of FIG. 5 , in step 502, AMF2 sends UE2 the capability information of UE2's serving network, thereby obtaining the capability information of UE2's serving network. In step 503, UE1 sends a first message to AMF1, and AMF1 processes the first message, thereby obtaining the information that UE1's serving network supports bidirectionality. Therefore, step 510 is performed only after UE1 receives the first message and determines that both UE1's and UE2's serving networks support bidirectionality.

[0227] Optionally, if UE1 receives DualSteer unauthorized or does not receive DualSteer authorized, the first device (when UE1 and UE2 are in the first device) may be in MUSIM mode (a mode that does not use dual-directional transmission of service data). If UE1 receives DualSteer authorized, the first device may be in DualSteer mode.

[0228] In this embodiment, a UE in the first device initiates a DualSteer request, and the UDM determines the first information based only on the subscription information (SUPI association). If the first information is obtained and the serving networks of both UEs in the first device support dual steering, the first device performs dual steering.

[0229] Case 2: UE1 / UE2 requests UDM to perform dual-directional communication between UE1 and UE2. UDM determines that UE1 and UE2 are allowed to perform dual-directional communication based on the capability information of the service network supported by UE1 / UE2 and the association between UE1 and UE2. UE1 and UE2 perform dual-directional communication.

[0230] Refer to Figure 6 and execute as follows:

[0231] The execution process of step 600 is the same as that of step 500, which will not be described in detail here. You can refer to it for understanding.

[0232] The execution process of step 601 is the same as that of step 501, which will not be described in detail here. You can refer to it for understanding.

[0233] Optionally, the UDM determines the capability information of the serving network of UE 1 by executing the following step 602. For example, this step may not be executed in the example shown in FIG6 .

[0234] Step 602: AMF2 sends the service network capability information of UE2 to UDM. Correspondingly, UDM receives the service network capability information of AMF2.

[0235] For example, if AMF2 supports dual-directional, it sends DualSteer support to UE2. For example, AMF2 can send GUAMI to UE2, where GUAMI includes PLMN information. <guami> :＝ <mcc> <mnc><AMF Region ID><AMF Set ID><AMF Pointer>, MCC and MNC represent PLMN information. UE1 can obtain PLMN information by parsing GUANI.

[0236] In addition, AMF2 also sends the second identity of UE2 (for example, SUPI2) and the identity of AMF2 to UE2 in step 602.

[0237] The execution process of step 603 is the same as that of step 502, which will not be described in detail here. You can refer to it for understanding.

[0238] The execution process of steps 604 to 606 is the same as that of steps 503 to 505, which will not be described in detail here. You can refer to them for understanding.

[0239] Step 607: The UDM determines first information according to the second identity of UE1, the second identity of UE2, subscription information, and service network capability information. The first information indicates that bi-directional communication is allowed between UE1 and UE2.

[0240] The first information described above may indicate authorization for association between UE1 and UE2, or authorization for UE1 and UE2 to perform dual-steering. The first information may be indicated by "DualSteer authorized" or "DualSteer allowed." It should be noted that the UDM may request the serving network capabilities of UE1 from AMF1, and the UDM may request the serving network capabilities of UE2 from AMF2. Alternatively, the UDM may pre-configure the serving network capabilities of UE1 and pre-configure the serving network capabilities of UE2.

[0241] In the embodiment of FIG6 , since AMF2 sends the capability information of UE2's service network to UDM in step 602, the capability information of UE2's service network can be obtained based on this. Since UE1 sends a first message to AMF1 in step 604, AMF1 can process the first message and thus obtain that UE1's service network supports dual-directional.

[0242] The execution process of steps 608A to 610 is the same as that of steps 507A to 509, which will not be described in detail here. You can refer to them for understanding.

[0243] Step 611: UE1 and UE2 perform bi-directional communication based on the first information.

[0244] If UE1 receives the DualSteer authorized message, the first device may perform dual-steering.

[0245] In this embodiment, a UE in the first device initiates a DualSteer request, and the UDM determines first information based on subscription information (SUPI association) and whether the service networks of both UEs support dual-steering. If the first information is obtained, the first device performs dual-steering.

[0246] Case 3: UE1 / UE2 requests UDM to perform dual-direction between UE1 and UE2. UDM determines that dual-direction between UE1 and UE2 is not allowed based on the capability information of the service network supported by UE1 / UE2 and the association between UE1 and UE2.

[0247] Refer to Figure 7 and execute as follows:

[0248] The execution process of step 700 is the same as that of step 500 and step 600, which will not be described in detail here. You can refer to them for understanding.

[0249] The execution process of step 701 is the same as that of step 501 and step 601, which will not be described in detail here. You can refer to them for understanding.

[0250] Step 702: AMF2 sends the capability information of UE2's service network to UDM. AMF2 does not support dual-direction.

[0251] The execution process of step 703 is the same as that of step 502 and step 603, which will not be described in detail here. You can refer to them for understanding.

[0252] The execution process of steps 704 to 706 is the same as that of steps 503 to 505 and steps 604 to 606, and will not be described in detail here. You can refer to them for understanding.

[0253] Step 707 : The UDM determines whether bi-directional directionality is not allowed between UE1 and UE2 based on the second identity of UE1, the second identity of UE2, subscription information, and service network capability information.

[0254] It should be noted that the UDM may request the serving network capabilities of UE1 from AMF1, and the UDM may request the serving network capabilities of UE2 from AMF2. Alternatively, the UDM pre-configures the serving network capabilities of UE1 and pre-configures the serving network capabilities of UE2.

[0255] In the embodiment of FIG. 7 , in step 702, AMF2 sends the UDM the capability information of UE2's serving network. Based on this, it can be determined that UE2's serving network does not support bidirectional orientation. In step 704, UE1 sends a first message to AMF1, and AMF1 processes the first message. Based on this, it can be determined that UE1's serving network supports bidirectional orientation. Therefore, the UDM determines that UE1 and UE2 do not allow bidirectional orientation.

[0256] In step 708A, the UDM sends an indication message (eg, Dual Steer Not Support) to AMF1 indicating that UE1 and UE2 do not allow dual-steer support. Accordingly, AMF1 receives the indication message indicating that UE1 and UE2 do not allow dual-steer support.

[0257] In step 708B, the UDM sends an indication message (eg, Dual Steer Not Support) to AMF2 indicating that UE1 and UE2 do not allow dual-steer support. Accordingly, AMF1 receives the indication message indicating that UE1 and UE2 do not allow dual-steer support.

[0258] The execution order of the above steps 708A and 708B is not limited.

[0259] Optionally, perform the following steps 709A and 709B.

[0260] In step 709A, AMF1 stores the indication information that UE1 and UE2 do not allow bi-directional directionality.

[0261] In step 709B, AMF2 stores the indication information that UE1 and UE2 do not allow bi-directional directionality.

[0262] The execution order of the above steps 709A and 709B is not limited.

[0263] In step 710, AMF1 sends an indication message indicating that bi-directional directionality is not allowed to UE1.

[0264] Optionally, since the serving network of UE2 does not support bi-directional orientation, based on the triggering of step 710 , UE2 may reselect a serving network that supports bi-directional orientation, so that UE1 and UE2 can perform bi-directional orientation.

[0265] Example 2

[0266] In Figure 8, the first terminal and the second terminal are located in the first device. The first network element is used for access management of the first terminal. The first network element is AMF1. The second network element is used for access management of the second terminal. The second network element is AMF2. The third network element is UDM, which is used to manage the data information of the second terminal and the data information of the first terminal. The execution is as follows:

[0267] In step 801, a first terminal sends a first message. The first message includes a bidirectional identifier, which is generated by the first terminal or the second terminal, or generated by the UDM and is associated with the second terminal. The first message is used to request the first terminal to perform bidirectional communication with the second terminal. In response, AMF1 receives the first message.

[0268] The bidirectional identifier is related to the second terminal, which can be understood as the bidirectional identifier being a temporary identifier of the second terminal, or the bidirectional identifier being used to represent the second terminal.

[0269] The first terminal sends the first message, which can be understood as the first device sending the first message through the first terminal.

[0270] It should be noted that the first message can be a new type of message associated with bidirectional communication, and the request for bidirectional communication can be determined based on the first message. Alternatively, the first message can reuse an existing NAS message, and by carrying information such as bidirectional communication request information in the NAS message, the core network element can determine whether to execute bidirectional communication. This is not specifically limited here.

[0271] Among them, when the first device generates a dual-directional identifier, the uniqueness within the first device should be guaranteed. Different first devices can generate different dual-directional identifiers, and how the dual-directional identifier is constructed is not specifically limited here. For example, when the first device is in dual-directional mode or the first device is allowed to perform dual-directional, the first device generates a dual-directional identifier. If the first terminal and the second terminal are not in the same device, the dual-directional identifier can be generated by the first terminal or the second terminal, or, if negotiated by the first terminal and the second terminal, the dual-directional identifier can be shared between the first terminal and the second terminal. It should be understood that in this step 801, the dual-directional identifier is associated with the second terminal, so that the second identity identifier of the second terminal can be determined based on the dual-directional identifier.

[0272] The dual-directional identifier can also be a dual-directional identifier received by the first device from the UDM, and the dual-directional identifier is assigned by the UDM. For example, when AMF2 sends a request to the UDM for the first terminal and the second terminal to perform dual-directional communication or when AMF2 registers with the UDM, the UDM can generate a dual-directional identifier based on the dual-directional capability information of the second terminal and / or the dual-directional subscription information of the second terminal, and send the dual-directional identifier to UE2 through AMF2. For example, when the UDM receives the dual-directional capability information of the second terminal from AMF2, a dual-directional identifier is generated for the second terminal. For another example, when the subscription information of the second terminal stored in the UDM includes allowing dual-directional communication, a dual-directional identifier is generated for the second terminal. In addition, the UDM can also store a first association relationship between the dual-directional identifier and the second identity identifier of the second terminal, so that the dual-directional identifier received from other terminals can create an association between the other terminal and the second terminal.

[0273] In addition, the fact that the first message includes the bidirectional identifier can also be understood as the first message including a bidirectional request container, and the bidirectional request container includes the bidirectional identifier.

[0274] In addition, the first message may further include first indication information, where the first indication information is used to request the first terminal to perform dual-steering with the second terminal or to request the first device to be in dual-steering mode. The first indication information may be dual-steering request indication information (for example, a dual-steering request, an association request, or a dual-steering mode). The first indication information may be indicated by a parameter, such as indicating by parameter 1 that the first terminal is requested to perform dual-steering with the second terminal.

[0275] In addition, when the first message is a NAS message, the NAS message may be a Registration Request message or a Service Request message, and the NAS message includes the first indication message and a bidirectional identifier. The NAS message may also include a PDU Session Establishment Request message of UE1. This application does not specifically limit this.

[0276] It should also be noted that, in addition to the bidirectional identifier, the first message generally also includes the first identity identifier of the first terminal.

[0277] In step 802, AMF1 sends a third message including the second identity of the first terminal and a bidirectional identification, and the third message is used to request the first terminal to perform bidirectional communication with the second terminal. Accordingly, the UDM receives the third message.

[0278] In addition, when the first message includes the first indication information, the third message includes second indication information, where the second indication information is used to request the first terminal to perform bi-directional directionality with the second terminal. The second indication information can be the same as the first indication information. In addition to the first indication information, the second indication information can also include information added by AMF1, such as the location of the first terminal, etc., which is not specifically limited in this application.

[0279] If the bidirectional identifier is included in the bidirectional request container in the first message, the third message includes the second identity of the first terminal and the bidirectional request container. It should be understood that AMF1 receives the bidirectional request container in the first message and then places it in the third message. In this case, AMF1 does not need to process the bidirectional identifier and only needs to forward the bidirectional request container.

[0280] Step 803: The UDM determines first information according to the dual-direction identifier and the second identity identifier of the first terminal, where the first information indicates that the first terminal and the second terminal allow dual-direction.

[0281] In one embodiment, the UDM may determine the first information based on the second identity of the first terminal, the bidirectional identifier, and the contract information received from the AMF1, wherein the contract information is the contract information between the first terminal and the network and the contract information between the second terminal and the network, and the contract information indicates that the second identity of the first terminal is associated with the second identity of the second terminal. For example, when the first terminal contracts with the operator, the user belonging to the first terminal is user 1, and when the second terminal contracts with the operator, the user belonging to the second terminal is user 1. In this case, the UDM may associate the second identity of the first terminal with the second identity of the second terminal. For another example, if the first terminal and the second terminal belong to the same user, when the user signs a contract with the operator, the operator may store the association between the second identity of the first terminal and the second identity of the second terminal. For another example, if the contract data of the first terminal includes the second identity of the second terminal, or if the contract data of the second terminal includes the second identity of the first terminal, it is considered that the second identity of the first terminal is associated with the second identity of the second terminal.

[0282] In addition, after the UDM stores the first association between the bidirectional identifier and the second identity of the second terminal, the UDM may determine the second identity of the second terminal based on the bidirectional identifier received from AMF1 and the first association. Subsequently, based on the contract information, it is determined that the second identity of the first terminal is associated with the second identity of the second terminal, and based on this, the first information may be obtained.

[0283] In another embodiment, the UDM may also determine the first information based on the second identity identifier, dual-directional identifier, and service network capability information of the first terminal received from AMF1. The service network capability information includes: whether the service network of the first terminal supports dual-directional, and / or whether the service network of the second terminal supports dual-directional. It should be noted that the UDM may request the service network capability of the first terminal from AMF1, and the UDM may request the service network capability of the second terminal from AMF2. Alternatively, the UDM pre-configures the service network capability of the first terminal and pre-configures the service network capability of the second terminal.

[0284] In the embodiment of FIG8 , since the UDM receives a third message from AMF1 requesting the first terminal to perform bidirectional routing with the second terminal, it is assumed that AMF1 supports bidirectional routing (i.e., the first terminal's service network supports bidirectional routing). The UDM only needs to determine whether the second terminal's service network supports bidirectional routing. For example, the UDM may request AMF2 whether the second terminal's service network supports bidirectional routing, and AMF2 may send a fourth message to the UDM, which may indicate that the second terminal's service network supports bidirectional routing.

[0285] In another embodiment, the UDM may further determine the first information based on the second identity identifier of the first terminal, the dual-directional identifier, the subscription information, and the service network capability information received from the AMF1. For example, the UDM may determine, based on the subscription information and the dual-directional identifier, that the second identity identifier of the first terminal is associated with the second identity identifier of the second terminal, and then determine the first information based on whether the service network of the first terminal supports dual-directional and whether the service network of the second terminal supports dual-directional.

[0286] It should be noted that the first information may indicate authorization to associate the first terminal with the second terminal, authorization to perform dual-steer, permission to operate the first terminal and the second terminal in dual-steer mode, or permission to operate the first device in dual-steer mode. The first information may be indicated by "DualSteer authorized" or "DualSteer allowed."

[0287] Optionally, the UDM determines fifth information based on the second identity of the first terminal and the dual-directional identifier, where the fifth information indicates that the first terminal and the second terminal do not allow dual-directional communication. Alternatively, the UDM may determine the fifth information based on the second identity of the first terminal, the dual-directional identifier, and the contract information.

[0288] In step 804, the UDM sends the first information to the AMF1. In response, the AMF1 receives the first information.

[0289] The above step 405 can be referred to for understanding and will not be described in detail here.

[0290] In step 805, AMF1 sends a second message to the first terminal, where the second message includes the first information indicating that the first terminal and the second terminal allow bidirectional communication. Accordingly, the first terminal receives the second message.

[0291] It should be noted that if the UDM determines the fifth information based on the second identity identifier, the bidirectional identifier, and the subscription information of the first terminal in step 803, then the UDM sends the fifth information to AMF1 in step 804, and the second message in step 805 includes the fifth information, and the following step 806 is not executed.

[0292] The first terminal receives the second message, which can be understood as the first device receiving the second message through the first terminal.

[0293] Step 806: The first terminal and the second terminal perform bi-directional direction-finding based on the first information.

[0294] It should be noted that, when the first terminal and the second terminal determine that the service network of the first terminal and the service network of the second terminal support dual-directionality, the first terminal and the second terminal may directly perform dual-directionality based on the first information.

[0295] The first terminal and the second terminal perform dual orientation based on the first information, which can be understood as the first device performing dual orientation for the first terminal and the second terminal based on the first information, or the first device performing dual orientation based on the first information, which is used for the first terminal and the second terminal.

[0296] In an optional embodiment, the first terminal and the second terminal perform dual-direction based on the service network capability information and the first information. Specifically, the first terminal needs to obtain the service network capability information of the first terminal, and the second terminal needs to obtain the service network capability information of the second terminal. For example, before executing step 801, the first terminal may register its dual-direction capability information with AMF1, and AMF1 may provide feedback to the first terminal on whether the first terminal's service network supports dual-direction. The second terminal may register its dual-direction capability information with AMF2, and AMF2 may provide feedback to the second terminal on whether the second terminal's service network supports dual-direction. Based on this, the first terminal determines that the first terminal's service network supports dual-direction, and the second terminal determines that the second terminal's service network supports dual-direction. Alternatively, before executing step 806, the first terminal requests the service network capability information of the first terminal from AMF1 and receives second information from AMF1, wherein the second information indicates that the first terminal's service network supports dual-direction. The second terminal requests the service network capability information of the second terminal from AMF2 and receives third information from AMF2, wherein the third information indicates that the second terminal's service network supports dual-direction. Alternatively, the first device requests the capability information of the service network of the first terminal from AMF1 through the first terminal, and the first device receives the second information from AMF1 through the first terminal; the first device requests the capability information of the service network of the second terminal from AMF2 through the second terminal, and the first device receives the third information from AMF2 through the second terminal.

[0297] Optionally, after step 806, if the terminals in the first device change, for example, the first device includes a second terminal and a third terminal, the first device needs to request the second terminal and the third terminal to perform bidirectional navigation, and then determine whether to perform bidirectional navigation based on the authorization result sent by the network (for example, whether the second terminal and the third terminal allow bidirectional navigation or the second terminal and the third terminal do not allow bidirectional navigation). If the second terminal and the third terminal allow bidirectional navigation, the first device performs bidirectional navigation. If the second terminal and the third terminal do not allow bidirectional navigation, the first device does not perform bidirectional navigation.

[0298] It should be noted that the message / information transmission between the above-mentioned terminals and network elements, and between network elements, may be direct transmission or indirect transmission via other network elements or devices, and this application does not specifically limit this. For example, the transmission of a first message between a first terminal and AMF1 can be understood as the first terminal transmitting the first message to AMF1 via RAN1, or it can also be understood as the first terminal transmitting the first message directly to AMF1. The transmission of a third message between AMF1 and UDM can be understood as AMF1 transmitting the third message to UDM via SMF, or AMF1 transmitting the third message directly to UDM. This is for illustrative purposes only.

[0299] In this application, a third network element receives a third message from a first network element requesting that a first terminal and a second terminal perform dual-direction communication. The third message includes the first terminal's second identity and a dual-direction identifier. The third network element determines the first information based on the first terminal's second identity and the dual-direction identifier. Subsequently, the third network element sends the first information to the first network element, based on which the first network element can clearly indicate that the first terminal and the second terminal are allowed to perform dual-direction communication. Using the dual-direction identifier avoids using the second terminal's first identity, which is beneficial for protecting the second terminal's information.

[0300] The following describes the solution of the second embodiment in combination with data interaction between UE1 (ie, the first terminal), UE2 (ie, the second terminal), AMF1 (ie, the first network element), AMF2 (ie, the second network element), and UDM (ie, the third network element), as follows:

[0301] Refer to Figure 9 and execute as follows:

[0302] In step 900 , the UDM stores the association between UE1 and UE2.

[0303] For example, the second identity identifier (SUPI1) of UE1 and the second identity identifier (SUPI2) of UE2 are stored in association. It should be understood that the association between the two UEs exists during the operator's account opening process for the UE (for example, UE1 and UE2 both belong to the same user), so the UDM can store the association relationship between SUPI1 and SUPI2.

[0304] Step 901: UE2 sends a registration request message to AMF2, where the registration request message includes UE2's dual-directional request information (DualSteer request or DualSteer mode). Accordingly, AMF2 receives the registration request message.

[0305] For example, if UE2 supports dual-steering, the registration request message may carry DualSteer support.

[0306] In addition, the registration request message may also carry the first identity of UE2, for example, SUCI2 or 5G-GUTI2.

[0307] In step 902A, AMF2 sends UE2's dual-directional request information (DualSteer request or DualSteer mode) to UDM. Correspondingly, UDM receives UE2's dual-directional request information.

[0308] In addition, AMF2 also sends the second identity of UE2 (for example, SUPI2) and the identity of AMF2 to UE2 in step 902.

[0309] In step 902B, the UDM generates a bidirectional identifier based on the bidirectional request information and sends the bidirectional identifier to the AMF 2. Accordingly, the AMF 2 receives the bidirectional identifier.

[0310] Step 903: The UDM stores a first association relationship between the bi-directional identifier and the second identity identifier of UE2.

[0311] In step 904, AMF2 sends a dual-directional identifier to UE2. Accordingly, UE2 receives the dual-directional identifier and shares it with UE1.

[0312] Optionally, AMF2 further sends capability information of UE2's service network to UE2 through step 904. For example, if AMF2 supports dual-steering, it sends DualSteer support to UE2.

[0313] In step 905, UE1 sends a first message to AMF1, where the first message includes a bidirectional identification and is used to request the first terminal to perform bidirectional communication with the second terminal. Accordingly, AMF1 receives the first message.

[0314] For example, the first message may directly include the dual-directional identifier, or may include a dual-directional request container. The dual-directional identifier is carried by the dual-directional request container. This can be understood by referring to the description of step 801 above and will not be repeated here.

[0315] Optionally, the first message further includes: first indication information, where the first indication information is used to request UE1 and UE2 to perform dual-steering. The first indication information may be dual-steering request indication information (DualSteer request or Association request).

[0316] Optionally, the first message may be a NAS message. The NAS message may be a registration request message or a service request message, and the NAS message includes the first indication message and a bidirectional identifier. When the NAS message is a registration request message, it may also include capability information of UE2.

[0317] Optionally, the NAS message may also include a PDU session establishment request message (PDU establishment request) of UE1. This application does not specifically limit this.

[0318] It should be noted that the first message usually also includes the first identity of the first terminal.

[0319] It should be noted that step 905 is performed only if UE1's serving network supports bidirectionality and UE2's serving network also supports bidirectionality. Furthermore, when UE2's serving network supports bidirectionality, there is no need to determine whether UE2's serving network supports bidirectionality. Since AMF2 can process the first message from UE2, it is assumed that UE2's serving network supports bidirectionality.

[0320] In addition, when UE1 and UE2 are in the first device and the first device turns on the dual-directional mode (DualSteer mode) (ie, a mode that adopts dual-directional transmission of service data), the above-mentioned step 905 is performed.

[0321] In step 906, AMF1 sends a third message, which includes UE1's second identity (obtained by searching UE1's context) and a bidirectional identification. The third message is used to request UE1 to perform bidirectional communication with UE2. Accordingly, the UDM receives the third message.

[0322] In addition, when the first message includes the first indication information, the third message includes the second indication information, where the second indication information is used to request the first terminal to perform bi-directional communication with the second terminal. This can be understood by referring to the description of step 802 above and will not be repeated here.

[0323] Step 907: The UDM determines first information according to the dual-directional identification, the second identity identification of UE1 and the subscription information. The first information indicates that UE1 and UE2 allow dual-directional communication.

[0324] The first information may indicate authorization of association between UE1 and UE2, or authorization of dual-steering between UE1 and UE2. The first information may be indicated by "DualSteer authorized" or "DualSteer allowed." This may be understood with reference to step 803 above and will not be described in detail here.

[0325] In step 908A, the UDM sends the first information to the AMF1, and the AMF1 receives the first information accordingly.

[0326] In step 908B, the UDM sends the first information to the AMF2. In response, the AMF1 receives the first information.

[0327] The execution order of the above steps 908A and 908B is not limited.

[0328] In step 909A, AMF1 stores the first information.

[0329] AMF1 stores the first information to determine that UE1 is allowed to request to perform bidirectional communication (ie, to create a bidirectional session).

[0330] Step 909B: AMF2 stores the first information.

[0331] This can be understood by referring to the description at step 508B, which will not be repeated here.

[0332] The execution order of the above steps 909A and 909B is not limited.

[0333] In step 910, AMF1 sends a second message to UE1, where the second message includes the first information indicating that UE1 and UE2 allow bidirectional communication. UE1 receives the second message accordingly.

[0334] Step 911: UE1 and UE2 perform dual-direction communication based on the first information.

[0335] In the embodiment of FIG. 9 , in step 904, AMF2 sends UE2 the capability information of UE2's serving network, thereby obtaining the capability information of UE2's serving network. In step 905, UE1 sends a first message to AMF1, and AMF1 processes the first message, thereby obtaining the information that UE1's serving network supports bidirectional communication. Therefore, step 910 is performed only after UE1 receives the first message and determines that both UE1's and UE2's serving networks support bidirectional communication.

[0336] Optionally, if UE1 receives DualSteer unauthorized or does not receive DualSteer authorized, the first device (when UE1 and UE2 are in the first device) may be in MUSIM mode (a mode that does not use dual-directional transmission of service data). If UE1 receives DualSteer authorized, the first device may be in DualSteer mode.

[0337] In this embodiment, a UE carries a dual-directional identification when initiating a dual-directional request, and the UDM determines the first information based on the subscription information (SUPI association) and the dual-directional identification. If the first information is obtained and the service networks of both UEs support dual-directional, the two UEs perform dual-directional.

[0338] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of device interaction. It is understandable that, in order to implement the above functions, each device may include a hardware structure and / or software module that performs each function. Those skilled in the art should easily appreciate that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0339] In the embodiments of the present application, the functional units of the device can be divided according to the above method examples. For example, each functional unit can be divided according to each function, or two or more functions can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or software functional units.

[0340] In the case of adopting an integrated unit, Figure 10 shows a possible exemplary block diagram of the communication device involved in the embodiments of the present application. As shown in Figure 10, the communication device 1000 may include: a processing unit 1001 and a transceiver unit 1002. The processing unit 1001 is used to control and manage the actions of the communication device 1000. The transceiver unit 1002 is used to support communication between the communication device 1000 and other devices. Optionally, the transceiver unit 1002 may include a receiving unit and / or a sending unit, which are used to perform receiving and sending operations respectively. Optionally, the communication device 1000 may also include a storage unit for storing program code and / or data of the communication device 1000. The transceiver unit may be referred to as an input / output unit, a communication unit, etc., and the transceiver unit may be a transceiver; the processing unit may be a processor. When the communication device is a module (such as a chip) in a communication device, the transceiver unit may be an input / output interface, an input / output circuit, or an input / output pin, etc., and may also be referred to as an interface, a communication interface, or an interface circuit, etc.; the processing unit may be a processor, a processing circuit, or a logic circuit, etc. For example, the device may be the aforementioned terminal, network equipment, etc.

[0341] In one embodiment, the communication device 1000 is a first device, the transceiver unit 1002 is used to send a first message, the first message is used to request the first terminal and the second terminal to perform dual-direction; receive a second message, the second message includes first information, the first information indicates that the first terminal and the second terminal allow dual-direction; the processing unit 1001 is used to perform dual-direction based on the first information.

[0342] In an optional manner, the processing unit 1001 is specifically configured to perform dual-direction based on service network capability information and the first information, where the service network capability information includes: the service network of the first terminal supports dual-direction, and / or the service network of the second terminal supports dual-direction.

[0343] In an optional manner, the transceiver unit 1002 is also used to receive second information from the first network element, the second information is used to indicate that the service network of the first terminal supports dual-direction, and the first network element is used for access management of the first terminal; and / or, to receive third information from the second network element, the third information is used to indicate that the service network of the second terminal supports dual-direction, and the second network element is used for access management of the second terminal.

[0344] In an optional manner, the first message is sent by the first terminal, and the first message includes the first identity of the second terminal.

[0345] In an optional manner, the first message is sent by the first terminal, and the first message includes a bidirectional identifier, the bidirectional identifier is generated by the first device, or the bidirectional identifier is generated by a third network element (UDM), the third network element is used to manage data information of the second terminal, and the bidirectional identifier is associated with the second terminal.

[0346] In an optional manner, the first message includes a bidirectional identifier, including:

[0347] The first message includes a bidirectional request container, and the bidirectional request container includes a bidirectional identifier.

[0348] In an optional manner, the first message includes: first indication information, where the first indication information is used to request the first terminal and the second terminal to perform dual-direction.

[0349] In an optional manner, the bidirectional identifier is generated by a third network element, and the transceiver unit 1002 is further configured to receive the bidirectional identifier from the third network element.

[0350] In another embodiment, the communication device 1000 is a third network element, and the transceiver unit 1002 is used to receive a third message from the first network element, the third message including: the second identity identifier of the first terminal and the second identity identifier of the second terminal, the first network element is used for access management of the first terminal, and the third message is used to request the first terminal and the second terminal to perform dual-direction; the processing unit 1001 is used to determine the first information based on the second identity identifier of the first terminal and the second identity identifier of the second terminal, the first information indicating that the first terminal and the second terminal allow dual-direction; the transceiver unit 1002 is also about sending the first information to the first network element.

[0351] In an optional manner, the processing unit 1001 is specifically configured to determine the first information based on the second identity identifier of the first terminal, the second identity identifier of the second terminal, and contract information, where the contract information indicates that the first terminal is associated with the second terminal.

[0352] In an optional manner, the processing unit 1001 is specifically used to determine the first information based on the second identity identifier of the first terminal, the second identity identifier of the second terminal and the service network capability information, where the service network capability information includes: the service network of the first terminal supports dual-direction, and / or the service network of the second terminal supports dual-direction.

[0353] In an optional manner, when the service network capability information includes that the service network of the second terminal supports dual-direction, the transceiver unit 1002 is further used to receive fourth information from the second network element, where the fourth information is used to indicate that the service network of the second terminal supports dual-direction.

[0354] In an optional manner, the third message further includes: second indication information, where the second indication information is used to request the first terminal and the second terminal to perform dual-direction.

[0355] In an optional manner, the transceiver unit 1002 is further configured to send the first information to a second network element, where the second network element is configured to manage access of the second terminal.

[0356] In another embodiment, the communication device 1000 is a third network element, and the transceiver unit 1002 is used to receive a third message from the first network element, the third message including: a dual-directional identifier, a second identity identifier of the first terminal, the dual-directional identifier is generated for the first terminal or the second terminal, or the dual-directional identifier is generated for the third network element, the first network element is used for access management of the first terminal, the dual-directional identifier is related to the second terminal, and the third message is used to request the first terminal and the second terminal to perform dual-directional communication; the processing unit 1001 is used to determine the first information based on the dual-directional identifier and the second identity identifier of the first terminal, the first information indicating that the first terminal and the second terminal allow dual-directional communication; the transceiver unit 1002 is also used to send the first information to the first network element.

[0357] In an optional manner, the processing unit 1001 is also used to generate a dual-directional identifier based on the dual-directional capability information of the second terminal and / or the dual-directional subscription information of the second terminal, and the second network element is used for access management of the second terminal; and send the dual-directional identifier to the second network element.

[0358] In an optional manner, the processing unit 1001 is further configured to store a first association relationship between the bi-directional identifier and the second identity identifier of the second terminal.

[0359] In an optional manner, the processing unit 1001 is further configured to determine the first information based on the dual-directional identifier, the second identity identifier of the first terminal, and the contract information, where the contract information indicates that the first terminal is associated with the second terminal.

[0360] In an optional manner, the processing unit 1001 is also used to determine the first information based on the dual-direction identifier, the second identity identifier of the first terminal and the service network capability information, and the service network capability information includes: the service network of the first terminal supports dual-direction, and / or, the service network of the second terminal supports dual-direction.

[0361] In an optional manner, when the service network capability information includes that the service network of the second terminal supports dual-direction, the transceiver unit 1002 is further used to receive fourth information from the second network element, where the fourth information is used to indicate that the service network of the second terminal supports dual-direction.

[0362] In an optional manner, the third message further includes: second indication information, where the second indication information is used to request the first terminal and the second terminal to perform dual-direction.

[0363] In an optional manner, the transceiver unit 1002 is further configured to send the first information to a second network element, where the second network element is configured to manage access of the second terminal.

[0364] In another embodiment, the communication device is a first network element, and the transceiver unit 1002 is used to receive a first message from the first terminal, the first message including: the first identity of the second terminal, and the first message is used to request the first terminal and the second terminal to perform dual-direction; the processing unit 1001 is used to obtain the second identity of the second terminal based on the first identity of the second terminal; the transceiver unit 1002 is also used to send a third message, the third message including: the second identity of the first terminal and the second identity of the second terminal; receive the first information, the first information indicates that the first terminal and the second terminal allow dual-direction.

[0365] In an optional manner, the transceiver unit 1002 is used to send the first identity identifier of the second terminal to the fourth network element or the second network element, the fourth network element is used for authentication management of the second terminal, and the second network element is used for access management of the second terminal; and receive the second identity identifier of the second terminal from the fourth network element or the second network element.

[0366] In an optional manner, the processing unit 1001 is further configured to store the first information.

[0367] In an optional manner, the processing unit 1001 is further configured to obtain bi-directional policy information according to the first information; and send the bi-directional policy information to the first terminal.

[0368] In an optional manner, the transceiver unit 1002 is also used to send a policy request message to the fifth network element, the policy request message including: third indication information, the third indication information is used to request the first terminal and the second terminal to execute dual-directional policy information, the fifth network element is used for policy management of the first terminal; receive dual-directional policy information from the fifth network element.

[0369] In an optional manner, the processing unit 1001 is further configured to determine, based on the first information, whether the first terminal allows establishment of a bidirectional session.

[0370] In an optional manner, the first message also includes first indication information, and the first indication information is used to request the first terminal and the second terminal to perform dual-direction; the third message also includes second indication information, and the first indication information is used to request the first terminal and the second terminal to perform dual-direction.

[0371] In another embodiment, the communication device is a first network element, and the transceiver unit 1002 is used to receive a first message from the first terminal, the first message includes a dual-directional identifier, the dual-directional identifier is generated for the first terminal or the second terminal, or the dual-directional identifier is generated for a third network element, the third network element is used to manage data information of the second terminal, the dual-directional identifier is related to the second terminal, and the first message is used to request the first terminal and the second terminal to perform dual-directional; send a third message, the third message includes: the second identity identifier of the first terminal and the dual-directional identifier; receive the first information, the first information indicates that the first terminal and the second terminal allow dual-directional.

[0372] In an optional manner, the first message includes a dual-directional identifier, including: the first message includes a dual-directional request container, and the dual-directional request container includes the dual-directional identifier.

[0373] In an optional manner, the processing unit 1002 is configured to store the first information.

[0374] In an optional manner, the processing unit 1002 is further configured to obtain bi-directional policy information according to the first information; and send the bi-directional policy information to the first terminal.

[0375] In an optional manner, the transceiver unit 1001 is also used to send a policy request message to the fifth network element, the policy request message including: third indication information, the third indication information is used to request the first terminal and the second terminal to execute dual-directional policy information, the fifth network element is used for policy management of the first terminal; receive the dual-directional policy information from the fifth network element.

[0376] In an optional manner, the processing unit 1002 is further configured to determine, according to the first information, whether the first terminal allows establishment of a bidirectional session.

[0377] In an optional manner, the first message also includes first indication information, and the first indication information is used to request the first terminal and the second terminal to perform dual-direction; the third message also includes second indication information, and the first indication information is used to request the first terminal and the second terminal to perform dual-direction.

[0378] As shown in Figure 11, this application also provides a communication device 1100. Communication device 1100 can be a chip or a chip system. The communication device can be located in the device involved in any of the above method embodiments, such as an access network device or a first core network device, to perform the corresponding actions of the device.

[0379] Optionally, the chip system may consist of the chip, or may include the chip and other discrete devices.

[0380] The communication device 1100 includes a processor 1110 .

[0381] The processor 1110 is configured to execute the computer program stored in the memory 1120 to implement the actions of each device in any of the above method embodiments.

[0382] The communication device 1100 may further include a memory 1120 for storing computer programs.

[0383] Optionally, memory 1120 and processor 1110 are coupled. Coupling is an indirect coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. Optionally, memory 1120 and processor 1110 are integrated.

[0384] The processor 1110 and the memory 1120 can be one or more without limitation.

[0385] Optionally, in actual applications, the communication device 1100 may or may not include a transceiver 1130, as illustrated by a dashed box in the figure. The communication device 1100 can exchange information with other devices via the transceiver 1130. The transceiver 1130 can be a circuit, a bus, a transceiver, or any other device capable of exchanging information.

[0386] The specific connection medium between the transceiver 1130, processor 1110, and memory 1120 is not limited in the embodiments of the present application. In FIG11 , the memory 1120, processor 1110, and transceiver 1130 are connected via a bus. The bus is represented by a bold line in FIG11 . The connection between other components is for illustrative purposes only and is not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, FIG11 uses only a single bold line, but this does not imply that there is only one bus or a single type of bus. In the embodiments of the present application, the processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present application can be directly executed by a hardware processor or by a combination of hardware and software modules within the processor.

[0387] In an embodiment of the present application, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), such as a random-access memory (RAM). The memory may also be any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in an embodiment of the present application may also be a circuit or any other device that can implement a storage function, for storing computer programs, program instructions and / or data.

[0388] Based on the above embodiments, referring to FIG12 , the embodiment of the present application also provides another communication device 1200, including: an interface circuit 1210 and a logic circuit 1220; the interface circuit 1210 can be understood as an input and output interface, which can be used to execute the receiving and sending steps of each device in any of the above method embodiments, and the logic circuit 1220 can be used to run code or instructions to execute the method executed by each device in any of the above embodiments, which will not be repeated.

[0389] Based on the above embodiments, embodiments of the present application further provide a computer-readable storage medium storing instructions that, when executed, cause the method executed by each device in any of the above method embodiments to be implemented. The computer-readable storage medium may include any medium capable of storing program code, such as a USB flash drive, a mobile hard drive, a read-only memory, a random access memory, a magnetic disk, or an optical disk.

[0390] Based on the above embodiments, an embodiment of the present application provides a communication system, which includes the first device (first terminal and second terminal), first network element, second network element, third network element, fourth network element and fifth network element mentioned in any of the above method embodiments, and can be used to execute the method executed by each device in any of the above method embodiments.

[0391] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0392] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0393] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0394] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.< / mnc> < / mcc> < / guami>

Claims

1. A communication method, characterized in that: Applied to a first device, the first device including: a first terminal and a second terminal, the method including: Sending a first message, where the first message is used to request the first terminal to perform bi-directional direction-finding with the second terminal; receiving a second message, where the second message includes first information, where the first information indicates that the first terminal and the second terminal allow bidirectional directionality; Bidirectional orientation is performed based on the first information.

2. The method according to claim 1, characterized in that The performing bi-directional orientation based on the first information includes: Based on service network capability information and the first information, dual-direction is performed, where the service network capability information includes: the service network of the first terminal supports dual-direction, and / or the service network of the second terminal supports dual-direction.

3. The method according to claim 2, characterized in that The method further comprises: receiving second information from a first network element, where the second information is used to indicate that a service network of the first terminal supports dual-direction, and the first network element is used for access management of the first terminal; and / or, Receive third information from a second network element, where the third information is used to indicate that a service network of the second terminal supports dual-direction, and the second network element is used for access management of the second terminal.

4. The method according to any one of claims 1 to 3, characterized in that The first message is sent by the first terminal, and the first message includes the first identity of the second terminal.

5. The method according to any one of claims 1 to 3, characterized in that: The first message is sent by the first terminal, and the first message includes a bidirectional identifier, the bidirectional identifier is generated by the first device, or the bidirectional identifier is generated by a third network element, the third network element is used to manage the data information of the second terminal, and the bidirectional identifier is associated with the second terminal.

6. The method according to claim 5, characterized in that The first message includes a dual-directional identifier, including: The first message includes a bidirectional request container, and the bidirectional request container includes the bidirectional identifier.

7. The method according to any one of claims 1 to 6, characterized in that: The first message includes: first indication information, where the first indication information is used to request the first terminal to perform dual-direction with the second terminal.

8. The method according to claim 5 or 6, characterized in that The bi-directional identifier is generated by a third network element, and the method further includes: The bi-directional identification is received from a third network element.

9. A communication method, characterized in that: Applied to a third network element, the method includes: receiving a third message from a first network element, the third message including: a second identity identifier of the first terminal and a second identity identifier of the second terminal, the first network element being used for access management of the first terminal, and the third message being used to request the first terminal to perform bi-directional directionality with the second terminal; Determining first information according to the second identity identifier of the first terminal and the second identity identifier of the second terminal, where the first information indicates that the first terminal and the second terminal allow dual-direction; Send the first information to the first network element.

10. The method according to claim 9, characterized in that The determining the first information according to the second identity identifier of the first terminal and the second identity identifier of the second terminal includes: The first information is determined according to the second identity identifier of the first terminal, the second identity identifier of the second terminal, and contract information, where the contract information indicates that the first terminal is associated with the second terminal.

11. The method according to claim 9 or 10, characterized in that The determining the first information according to the second identity identifier of the first terminal and the second identity identifier of the second terminal includes: The first information is determined according to the second identity identifier of the first terminal, the second identity identifier of the second terminal and the service network capability information, wherein the service network capability information includes: the service network of the first terminal supports dual-direction, and / or the service network of the second terminal supports dual-direction.

12. The method according to claim 11, characterized in that When the service network capability information includes that the service network of the second terminal supports dual-direction, the method further includes: Fourth information is received from the second network element, where the fourth information is used to indicate that a service network of the second terminal supports dual-direction.

13. The method according to any one of claims 9 to 12, characterized in that: The third message further includes: second indication information, where the second indication information is used to request the first terminal and the second terminal to perform dual-direction.

14. The method according to any one of claims 9 to 13, characterized in that: The method further comprises: The first information is sent to a second network element, where the second network element is used for access management of the second terminal.

15. A communication method, characterized in that: Applied to a third network element, the method includes: receiving a third message from a first network element, the third message including: a dual-directional identifier and a second identity identifier of the first terminal, the dual-directional identifier being generated for the first terminal or the second terminal, or being generated for the third network element, the first network element being used for access management of the first terminal, the dual-directional identifier being related to the second terminal, and the third message being used to request the first terminal to perform dual-directional communication with the second terminal; Determining first information according to the dual-direction identifier and the second identity identifier of the first terminal, where the first information indicates that the first terminal and the second terminal allow dual-direction; Sending first information to the first network element.

16. The method according to claim 15, characterized in that The method further comprises: generating the bidirectional identification according to the bidirectional capability information of the second terminal and / or the bidirectional subscription information of the second terminal; The dual-directional identifier is sent to a second network element, where the second network element is used for access management of the second terminal.

17. The method according to claim 15 or 16, characterized in that The method further comprises: A first association relationship between the bi-directional identifier and the second identity identifier of the second terminal is stored.

18. The method according to any one of claims 15 to 17, characterized in that: The determining the first information according to the dual-directional identifier and the second identity identifier of the first terminal includes: The first information is determined based on the dual-directional identifier, the second identity identifier of the first terminal, and the contract information, where the contract information indicates that the first terminal is associated with the second terminal.

19. The method according to any one of claims 15 to 18, characterized in that: The determining the first information according to the dual-directional identifier and the second identity identifier of the first terminal includes: The first information is determined according to the dual-direction identifier, the second identity identifier of the first terminal and the service network capability information, where the service network capability information includes: the service network of the first terminal supports dual-direction, and / or the service network of the second terminal supports dual-direction.

20. The method according to claim 19, characterized in that When the service network capability information includes that the service network of the second terminal supports dual-direction, the method further includes: Fourth information is received from the second network element, where the fourth information is used to indicate that a service network of the second terminal supports dual-direction.

21. The method according to any one of claims 15 to 20, characterized in that: The third message further includes: second indication information, where the second indication information is used to request the first terminal and the second terminal to perform dual-direction.

22. The method according to any one of claims 15 to 21, characterized in that: The method further comprises: The first information is sent to a second network element, where the second network element is used for access management of the second terminal.

23. A communication method, characterized in that: Applied to a first network element, the method includes: Receiving a first message from a first terminal, the first message including: a first identity identifier of a second terminal, the first message being used to request the first terminal to perform bi-directional direction-finding with the second terminal; Acquire a second identity identifier of the second terminal according to the first identity identifier of the second terminal; Sending a third message, where the third message includes: the second identity identifier of the first terminal and the second identity identifier of the second terminal; First information is received, where the first information indicates that the first terminal and the second terminal allow dual directionality.

24. The method according to claim 23, wherein The acquiring the second identity identifier of the second terminal according to the first identity identifier of the second terminal includes: Sending the first identity of the second terminal to a fourth network element or a second network element, the fourth network element being used for authentication management of the second terminal, and the second network element being used for access management of the second terminal; Receive a second identity of the second terminal from the fourth network element or the second network element.

25. The method according to claim 23 or 24, characterized in that The method further comprises: The first information is stored.

26. The method according to any one of claims 23 to 25, characterized in that The method further comprises: Obtaining bi-directional strategy information according to the first information; The bi-directional policy information is sent to the first terminal.

27. The method according to claim 26, characterized in that The obtaining of bi-directional policy information includes: Sending a policy request message to a fifth network element, the policy request message including: third indication information, the third indication information being used to request the first terminal and the second terminal to execute bi-directional policy information, the fifth network element being used for policy management of the first terminal; The bi-directional policy information is received from the fifth network element.

28. The method according to any one of claims 23 to 27, characterized in that: The method further comprises: It is determined, based on the first information, that the first terminal allows establishment of a bidirectional session.

29. The method according to any one of claims 23 to 28, characterized in that: The first message further includes first indication information, and the first indication information is used to request the first terminal and the second terminal to perform dual-direction; the third message further includes second indication information, and the first indication information is used to request the first terminal and the second terminal to perform dual-direction.

30. A communication method, characterized in that: Applied to a first network element, the method includes: receiving a first message from a first terminal, the first message including a bidirectional identification, the bidirectional identification being generated by the first terminal or the second terminal, or the bidirectional identification being generated by a third network element, the third network element being configured to manage data information of the second terminal, the bidirectional identification being associated with the second terminal, and the first message being used to request the first terminal to perform bidirectional communication with the second terminal; Sending a third message, the third message including: the second identity identifier of the first terminal and the dual-directional identifier; First information is received, where the first information indicates that the first terminal and the second terminal allow dual directionality.

31. The method according to claim 30, wherein The first message includes a dual-directional identifier, including: The first message includes a bidirectional request container, and the bidirectional request container includes the bidirectional identifier.

32. The method according to claim 30 or 31, characterized in that The method further comprises: The first information is stored.

33. The method according to any one of claims 30 to 32, characterized in that: The method further comprises: Obtaining bi-directional strategy information according to the first information; The bi-directional policy information is sent to the first terminal.

34. The method according to claim 33, wherein The obtaining of bi-directional policy information includes: Sending a policy request message to a fifth network element, the policy request message including: third indication information, the third indication information being used to request the first terminal and the second terminal to execute bi-directional policy information, the fifth network element being used for policy management of the first terminal; The bi-directional policy information is received from the fifth network element.

35. The method according to any one of claims 30 to 34, characterized in that: The method further comprises: It is determined, based on the first information, that the first terminal allows establishment of a bidirectional session.

36. The method according to any one of claims 30 to 35, characterized in that The first message further includes first indication information, and the first indication information is used to request the first terminal and the second terminal to perform dual-direction; the third message further includes second indication information, and the first indication information is used to request the first terminal and the second terminal to perform dual-direction.

37. A communication device, characterized in that: include: A functional module for implementing the method according to any one of claims 1 to 36.

38. A communication device, characterized in that: include: at least one processor and memory; The memory is used to store computer programs or instructions; The at least one processor is configured to execute the computer program or instructions so that the method according to any one of claims 1 to 36 is performed.

39. A chip system, characterized in that: The chip system includes: a processing circuit; the processing circuit is coupled to a storage medium; The processing circuit is used to execute part or all of the computer programs or instructions in the storage medium, and when the part or all of the computer programs or instructions are executed, it is used to implement the method according to any one of claims 1 to 36.

40. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, and when the instructions are executed by a computer, the method according to any one of claims 1 to 36 is performed.

41. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is run on a computer, the method according to any one of claims 1 to 36 is performed.

Images