Method of establishing a connection and communication device

Abstract

The application provides a connection establishment method and a communication device. In the method, a remote terminal in a relay scenario and a relay terminal can establish a connection of a non-3GPP wireless access technology, so that the remote terminal and the relay terminal can transmit data through the connection of the non-3GPP wireless access technology, the advantages of a short-distance communication protocol of the non-3GPP can be effectively utilized, and the connection mode between the remote terminal and the relay terminal is more flexible.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to methods and apparatus for establishing connections. Background Technology

[0002] With the development of communication technology, the types and forms of terminal devices are becoming increasingly diverse. Some terminal devices (e.g., smartwatches, wristbands, virtual reality (VR) glasses, and other wearable devices) are limited by size and cost, and typically require powerful peripheral terminals (e.g., smartphones or customer-premises equipment (CPE)) to access network services. In this scenario, the terminal obtaining relay services can be called a remote terminal, and the terminal providing relay services can be called a relay terminal. Currently, the connection methods between remote terminals and relay terminals are relatively simple. Summary of the Invention

[0003] This application provides a method and communication device for establishing a connection, which enables more flexible connection methods between remote terminals and relay terminals in relay scenarios.

[0004] Firstly, a method for establishing a connection is provided. This method can be executed by a first terminal or by a module or unit in the first terminal. For ease of description, it will be referred to as the first terminal in the following text.

[0005] The method includes: a first terminal determining the radio access technology used for communication with a second terminal; when the radio access technology is a first non-3rd generation partnership project (3GPP) radio access technology, the first terminal obtains non-3GPP information of the second terminal during a first process of 3GPP radio access technology, the non-3GPP information being used by the first terminal and the second terminal to establish a connection of the first non-3GPP radio access technology; the first terminal establishes a connection of the first non-3GPP radio access technology with the second terminal based on the first non-3GPP information; wherein, the first terminal is a remote terminal in a relay scenario, and the second terminal is a relay terminal in a relay scenario; or, the first terminal is a relay terminal in a relay scenario, and the second terminal is a remote terminal in a relay scenario.

[0006] Through the above technical solution, in a relay scenario, the remote terminal and the relay terminal can obtain information for establishing a non-3GPP radio access technology connection during the 3GPP radio access technology process, thereby establishing a non-3GPP radio access technology connection. This allows the remote terminal and the relay terminal to transmit data through the non-3GPP radio access technology connection, effectively utilizing the advantages of non-3GPP short-range communication protocols. Compared to existing technologies where the remote terminal and the relay terminal in a relay scenario can only establish a 3GPP radio access technology connection, the connection method between the remote terminal and the relay terminal is more flexible.

[0007] In conjunction with the first aspect, in one possible implementation, the first terminal determines the wireless access technology used for communication with the second terminal, including: the first terminal determines the wireless access technology used for communication with the second terminal through a user equipment route selection policy (URSP) or a local policy.

[0008] In conjunction with the first aspect or any of its implementations, in another possible implementation, the non-3GPP information includes at least one of the following: device name, hotspot name, or address information.

[0009] In conjunction with the first aspect or any of its implementations, in another possible implementation, the first process includes at least one of the following: the process by which the first terminal discovers the second terminal through the 3GPP radio access technology discovery process, or the process by which the first terminal and the second terminal establish a 3GPP radio access technology connection.

[0010] In the above technical solutions, the discovery process and connection establishment process of 3GPP radio access technology are existing 3GPP radio access technology processes. Reusing existing 3GPP radio access technology processes, or enhancing existing 3GPP radio access technology processes, helps to reduce the impact of existing communication mechanisms.

[0011] In conjunction with the first aspect or any implementation thereof, in another possible implementation, the method further includes: the first terminal discovering the second terminal through the discovery process of 3GPP radio access technology according to the first discovery parameter; wherein, the first discovery parameter includes a relay service code (RSC), the RSC being associated with the first non-3GPP radio access technology; or the first discovery parameter includes the RSC and second information, the second information being used to indicate the first non-3GPP radio access technology.

[0012] In the above technical solution, the remote terminal and the relay terminal perform an RSC or (RSC + wireless access technology) matching process during the discovery process, so that the relay terminal can establish PDU sessions with different attributes according to the communication needs of the remote terminal to provide network services to the remote terminal.

[0013] In conjunction with the first aspect or any implementation thereof, in another possible implementation, the first discovery parameter includes RSC, and the method further includes: the first terminal receiving third information from a core network device, the third information being used to configure the first discovery parameter for the first terminal, the third information including indication information, the indication information being used to indicate that the RSC is associated with the first non-3GPP radio access technology.

[0014] In the above technical solution, the core network device sends indication information to the terminal device to indicate that the RSC is associated with the radio access technology. When the core network device sends indication information to the terminal device, the terminal sends or matches the RSC during the discovery process; when the core network device does not send indication information to the terminal device, the relay terminal sends or matches the RSC and the radio access technology during the discovery process. In this way, the terminal can use appropriate discovery parameters to perform the discovery process.

[0015] In conjunction with the first aspect or any implementation thereof, in another possible implementation, the method further includes: the first terminal reporting fourth information to the core network device, the fourth information being used to indicate non-3GPP radio access technologies supported by the first device.

[0016] In conjunction with the first aspect or any of its implementations, in another possible implementation, the first terminal establishes a connection with the second terminal using the first non-3GPP radio access technology based on the non-3GPP information, including: in response to obtaining the non-3GPP information, the 3GPP module of the first terminal triggers the non-3GPP module of the first terminal to establish a connection with the second terminal using the first non-3GPP radio access technology.

[0017] Since the aforementioned non-3GPP information is exchanged during the 3GPP radio access technology process and is a step executed by the 3GPP module of the remote terminal or relay terminal, it is necessary to enhance the internal structure of the remote terminal or relay terminal in order to establish a non-3GPP connection, so that the 3GPP module of the remote terminal or relay terminal can communicate with the non-3GPP module.

[0018] In conjunction with the first aspect or any implementation thereof, in another possible implementation, the method further includes: the non-3GPP module of the first terminal sending fifth information to the 3GPP module of the first terminal, the fifth information being used to notify that the connection of the first non-3GPP radio access technology has been successfully established, the fifth information including an identifier of the connection of the first non-3GPP radio access technology.

[0019] In conjunction with the first aspect or any implementation thereof, in another possible implementation, when the first terminal is a remote terminal in the relay scenario, the method further includes: the first terminal establishing an association between the connection of the first non-3GPP radio access technology and the application; and / or, the first terminal establishing an association between the connection of the first non-3GPP radio access technology and the connection of the 3GPP radio access technology; wherein, the connection of the 3GPP radio access technology is a connection between the first terminal and the second terminal, and the data of the application and the connection of the 3GPP radio access technology are carried on the connection of the first non-3GPP radio access technology.

[0020] Since this application aims to transmit data between the remote terminal and the relay terminal via a non-3GPP radio access technology (RANK) connection, rather than a 3GPP RANK connection, the remote terminal can establish an association between the non-3GPP RANK connection and an application and / or a 3GPP RANK connection to enable data transmission or reception via the non-3GPP RANK connection. For example, by establishing an association between the non-3GPP RANK connection and an application, the remote terminal can determine, based on this association, that data from the application is being transmitted to the relay terminal via the non-3GPP RANK connection, or that data carried on the non-3GPP RANK connection is destined for the application. Similarly, by establishing an association between the non-3GPP RANK connection and a 3GPP RANK connection, the remote terminal can determine, based on this association, that data on the 3GPP RANK connection is being transmitted or received via the non-3GPP RANK connection.

[0021] In conjunction with the first aspect or any implementation thereof, in another possible implementation, when the first terminal is a relay terminal in the relay scenario, the method further includes: the first terminal establishing an association between the connection of the first non-3GPP radio access technology and the PDU session; and / or, the first terminal establishing an association between the connection of the first non-3GPP radio access technology and the connection of the 3GPP radio access technology; wherein, the connection of the 3GPP radio access technology is the connection between the first terminal and the second terminal, the connection of the 3GPP radio access technology corresponds to the PDU session, and the PDU session is used to carry the data of the connection of the first non-3GPP radio access technology.

[0022] Since relay terminals need to forward data from non-3GPP radio access technology (3GPP) connections to the network side (e.g., UPF) via PDU sessions, and forward data from the network side to remote terminals via non-3GPP ...

[0023] In conjunction with the first aspect or any of its implementations, in another possible implementation, when the first terminal is a relay terminal in the relay scenario, the method further includes: the first terminal sending at least one of the following information to the core network equipment: sixth information, the identifier of the remote user, or information of the second terminal, wherein the sixth information is used to indicate the first non-3GPP radio access technology.

[0024] The above technical solutions facilitate legitimate eavesdropping on remote terminals by the network side.

[0025] In conjunction with the first aspect or any implementation thereof, in another possible implementation, the first non-3GPP radio access technology includes at least one of the following: WiFi, WiFi Direct, Bluetooth, Zigbee, radio frequency identification devices (RFID), infrared data association (IrDA), ultrawideband (UWB), or near-field communication (NFC); ​​and / or, the 3GPP radio access technology includes at least one of the following: device to device (D2D), sidelink, or proximity based services (ProSe).

[0026] Secondly, a method for establishing a connection is provided. This method can be executed by a first terminal or by a module or unit in the first terminal. For ease of description, it will be referred to as the first terminal in the following text.

[0027] The method includes: a first terminal determining the radio access technology used for communication with a second terminal; when the radio access technology is a first non-3GPP radio access technology, the first terminal acquires a second discovery parameter for the discovery process of the first non-3GPP radio access network technology, the second discovery parameter including at least one of the following: RSC, single network slice selection assistance information (S-NSSAI), or data network name (DNN); the first terminal discovers the second terminal through the discovery process of the first non-3GPP radio access technology according to the second discovery parameter, and establishes a connection with the second terminal for the first non-3GPP radio access technology; wherein, the first terminal is a remote terminal in a relay scenario, and the second terminal is a relay terminal in a relay scenario; or, the first terminal is a relay terminal in a relay scenario, and the second terminal is a remote terminal in a relay scenario.

[0028] Through the above technical solution, a non-3GPP radio access technology connection is established between the remote terminal and the relay terminal in a relay scenario. This allows the remote terminal and the relay terminal to transmit data through the non-3GPP radio access technology connection, effectively utilizing the advantages of non-3GPP short-range communication protocols. Compared to existing technologies where the remote terminal and the relay terminal in a relay scenario can only establish a 3GPP radio access technology connection, the connection method between the remote terminal and the relay terminal is more flexible.

[0029] In addition, during the discovery process, the remote terminal and the relay terminal perform a matching process of RSC or protocol data unit (PDU) session parameters, so that the relay terminal can establish PDU sessions with different attributes according to the communication needs of the remote terminal to provide network services to the remote terminal.

[0030] In conjunction with the second aspect, in one possible implementation, the first terminal determines the wireless access technology used for communication with the second terminal, including: the first terminal determines the wireless access technology used for communication with the second terminal through URSP or local policies.

[0031] In conjunction with the second aspect or any implementation thereof, in another possible implementation, the first terminal acquires a second discovery parameter for the discovery process of the first non-3GPP radio access network technology, including: the non-3GPP module of the first terminal acquires the second discovery parameter from the 3GPP module of the first terminal.

[0032] In conjunction with the second aspect or any implementation thereof, in another possible implementation, the method further includes: the first terminal obtaining the identifier of the 3GPP radio access technology of the second terminal during the process of establishing the connection of the first non-3GPP radio access technology; and / or, the first terminal obtaining the identifier of the 3GPP radio access technology of the second terminal through the user plane after establishing the connection of the first non-3GPP radio access technology.

[0033] In conjunction with the second aspect or any implementation thereof, in another possible implementation, the method further includes: the non-3GPP module of the first terminal sending seventh information to the 3GPP module of the first terminal, the seventh information being used to notify that the connection of the first non-3GPP radio access technology has been successfully established, the seventh information including at least one of the following: the identifier of the connection of the first non-3GPP radio access technology, the discovery parameters associated with the connection of the first non-3GPP radio access technology, or the identifier of the 3GPP radio access technology of the second terminal.

[0034] In conjunction with the second aspect or any of its implementations, in another possible implementation, when the first terminal is a remote terminal in the relay scenario, the method further includes: the first terminal establishing an association between the connection of the first non-3GPP radio access technology and the application; and / or, the first terminal establishing an association between the connection of the first non-3GPP radio access technology and the connection of the 3GPP radio access technology; wherein, the connection of the 3GPP radio access technology is a connection between the first terminal and the second terminal, and the data of the application and the connection of the 3GPP radio access technology are carried on the connection of the first non-3GPP radio access technology.

[0035] Since this application aims to transmit data between the remote terminal and the relay terminal via a non-3GPP radio access technology (RANK) connection, rather than a 3GPP RANK connection, the remote terminal can establish an association between the non-3GPP RANK connection and an application and / or a 3GPP RANK connection to enable data transmission or reception via the non-3GPP RANK connection. For example, by establishing an association between the non-3GPP RANK connection and an application, the remote terminal can determine, based on this association, that data from the application is being transmitted to the relay terminal via the non-3GPP RANK connection, or that data carried on the non-3GPP RANK connection is destined for the application. Similarly, by establishing an association between the non-3GPP RANK connection and a 3GPP RANK connection, the remote terminal can determine, based on this association, that data on the 3GPP RANK connection is being transmitted or received via the non-3GPP RANK connection.

[0036] In conjunction with the second aspect or any implementation thereof, in another possible implementation, when the first terminal is a relay terminal in the relay scenario, the method further includes: the first terminal establishing an association between the connection of the first non-3GPP radio access technology and the PDU session; and / or, the first terminal establishing an association between the connection of the first non-3GPP radio access technology and the connection of the 3GPP radio access technology; wherein, the connection of the 3GPP radio access technology is the connection between the first terminal and the second terminal, the connection of the 3GPP radio access technology corresponds to the PDU session, and the PDU session is used to carry the data of the connection of the first non-3GPP radio access technology.

[0037] Since relay terminals need to forward data from non-3GPP radio access technology (3GPP) connections to the network side (e.g., UPF) via PDU sessions, and forward data from the network side to remote terminals via non-3GPP ...

[0038] In conjunction with the second aspect or any of its implementations, in another possible implementation, when the first terminal is a relay terminal in the relay scenario, the method further includes: the first terminal sending at least one of the following information to the core network equipment: sixth information, the identifier of the remote user, or information of the second terminal, wherein the sixth information is used to indicate the first non-3GPP radio access technology.

[0039] The above technical solutions facilitate legitimate eavesdropping on remote terminals by the network side.

[0040] In conjunction with the second aspect or any implementation thereof, in another possible implementation, the first non-3GPP radio access technology includes at least one of the following: WiFi, WiFi Direct, Bluetooth, Zigbee, RFID, IrDA, UWB, or NFC; and / or, the 3GPP radio access technology includes at least one of the following: D2D, sidelink, or ProSe.

[0041] Thirdly, a method for establishing a connection is provided. This method can be executed by a core network device or by a module or unit within the core network device. For ease of description, it will be referred to as a core network device in the following text.

[0042] The method includes: a core network device receiving fourth information reported by a first terminal, the fourth information indicating a non-3GPP radio access technology supported by the first device; the core network device sending third information to the first terminal, the third information configuring a first discovery parameter for the first terminal, the first discovery parameter including an RSC, the third information including indication information indicating that the RSC is associated with a first non-3GPP radio access technology.

[0043] Optionally, the core network equipment may be a policy control function (PCF).

[0044] In the above technical solution, the core network device sends indication information to the terminal device to indicate that the RSC is associated with the radio access technology. When the core network device sends indication information to the terminal device, the terminal sends or matches the RSC during the discovery process; when the core network device does not send indication information to the terminal device, the relay terminal sends or matches the RSC and the radio access technology during the discovery process. In this way, the terminal can use appropriate discovery parameters to perform the discovery process.

[0045] Fourthly, this application provides a communication device for performing the method provided by any of the above aspects or their implementations. Specifically, the device may include units and / or modules for performing the method provided by any of the above aspects or their implementations, such as processing units and / or communication units.

[0046] In one implementation, the device is a first terminal or a core network device. When the device is a first terminal or a core network device, the communication unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver is a transceiver circuit. Optionally, the input / output interface is an input / output circuit.

[0047] In another implementation, the device is a chip, chip system, or circuit used in a first terminal or core network device. When the device is a chip, chip system, or circuit used in a first terminal or core network device, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit may be at least one processor, processing circuit, or logic circuit.

[0048] Fifthly, this application provides a communication device comprising: a memory for storing a program; and at least one processor for executing the computer program or instructions stored in the memory to perform the method provided in any of the foregoing aspects or their implementations.

[0049] In one implementation, the device is a first terminal or a core network device.

[0050] In another implementation, the device is a chip, chip system, or circuit used in a first terminal or core network device.

[0051] Sixthly, this application provides a processor for performing the methods provided in the foregoing aspects.

[0052] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0053] In a seventh aspect, this application provides a computer-readable storage medium storing program code for execution by a device, the program code including a method for performing any of the foregoing aspects or their implementations.

[0054] Eighthly, this application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the method provided by any of the above aspects or their implementations.

[0055] Ninthly, this application provides a chip, which includes a processor and a communication interface. The processor reads instructions stored in a memory through the communication interface and executes the method provided in any of the above aspects or their implementations.

[0056] Optionally, as one implementation, the chip also includes a memory that stores computer programs or instructions. The processor is used to execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the processor is used to perform the methods provided by any of the above aspects or their implementations.

[0057] In a tenth aspect, this application provides a communication system, including the first terminal or core network equipment mentioned above. Attached Figure Description

[0058] Figure 1 This is a schematic diagram of a network architecture to which the technical solution of this application can be applied.

[0059] Figure 2 This is a schematic diagram of another network architecture that can apply the technical solutions of this application.

[0060] Figure 3 This is a schematic flowchart of a Layer 3 relay.

[0061] Figure 4 This is a schematic diagram of a connection establishment method 400 provided in this application.

[0062] Figure 5 This is a schematic diagram of another method 500 for establishing a connection provided in this application.

[0063] Figure 6 This is a schematic diagram of the overall process of the connection establishment method provided in this application.

[0064] Figure 7 This is an example of the method for establishing a connection provided in this application.

[0065] Figure 8 This is a schematic diagram of the internal enhancements of remote terminals and relay terminals.

[0066] Figure 9 This is another schematic diagram of the overall process of the connection establishment method provided in this application.

[0067] Figure 10 This is another example of the method for establishing a connection provided in this application.

[0068] Figure 11 This is another schematic diagram of the overall process of the connection establishment method provided in this application.

[0069] Figure 12 This is another example of the method for establishing a connection provided in this application.

[0070] Figure 13 This is another schematic diagram of the internal enhancements of remote terminals and relay terminals.

[0071] Figure 14 This is a schematic diagram of the structure of an apparatus provided in an embodiment of this application.

[0072] Figure 15 This is another schematic diagram of the device provided in the embodiments of this application. Detailed Implementation

[0073] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0074] The technical solution provided in this application can be applied to various communication systems, such as: fifth generation (5G) thThe technical solutions provided in this application can also be applied to future communication systems, such as sixth-generation mobile communication systems. Furthermore, the technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0075] First, let me briefly introduce the network architecture applicable to this application.

[0076] As an example, Figure 1 A schematic diagram of a network architecture is shown.

[0077] like Figure 1 As shown, this network architecture is based on the 5G system (the 5G). thTaking a generation system (5GS) as an example, this network architecture can include three parts: user equipment (UE), data network (DN), and operator network. The operator network can include one or more of the following network elements: radio access network (RAN) equipment, user plane function (UPF) network elements, authentication server function (AUSF) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, service communication proxy (SCP), network slice selection function (NSSF) network elements, network exposure function (NEF) network elements, network repository function (NRF) network elements, policy control function (PCF) network elements, unified data management (UDM) network elements, and application function (AF) network elements. In the aforementioned operator network, the portion excluding the RAN portion can be referred to as the core network portion. In this application, user equipment, (radio)access network equipment, UPF network element, AUSF network element, AMF network element, SMF network element, SCP network element, NSSF network element, NEF network element, NRF network element, PCF network element, UDM network element, and AF network element are respectively abbreviated as UE, (R)AN equipment, UPF, AUSF, UDR, AMF, SMF, SCP, NSSF, NEF, NRF, PCF, UDM, and AF.

[0078] The following is about Figure 1 A brief description of each network element involved is provided.

[0079] 1. UE

[0080] The UE primarily accesses the 5G network and obtains services through the radio air interface. The UE interacts with the RAN through the air interface and with the AMF of the core network through non-access stratum signaling (NAS).

[0081] In the embodiments of this application, the UE can also be referred to as terminal equipment, user, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device. UE can be a cellular phone, smartwatch, wireless data card, mobile phone, tablet computer, personal digital assistant (PDA) computer, wireless modem, handheld device, laptop computer, machine type communication (MTC) terminal, computer with wireless transceiver capability, Internet of Things (IoT) terminal, virtual reality terminal device, augmented reality terminal device, wearable device, vehicle, terminal in device-to-device (D2D) communication, terminal in vehicle-to-everything (V2X) communication, terminal in machine-type communication (MTC), terminal in Internet of Things (IoT), terminal in smart office, terminal in industrial control, terminal in autonomous driving, terminal in remote surgery, terminal in smart grid, terminal in transportation safety, terminal in smart city, terminal in smart home, or terminal in satellite communication (e.g., satellite phone or satellite terminal). UE can also be customer-premises equipment (CPE), telephone, router, network switch, residential gateway (RG), set-top box, fixed-mobile converged product, home network adapter, and Internet access gateway.

[0082] The embodiments of this application do not limit the specific technology or device form used by the UE.

[0083] 2. (R)AN equipment

[0084] (R)AN devices can provide access to a communication network for authorized users in a specific area. Specifically, they can include wireless network equipment in 3GPP (3rd Generation Partnership Project) networks or access points in non-3GPP networks. For ease of description, AN devices will be used in the following text.

[0085] AN devices can employ different radio access technologies. Currently, there are two types of radio access technologies: 3GPP access technologies (e.g., those used in 3rd generation (3G), 4th generation (4G), or 5G systems) and non-3GPP access technologies. 3GPP access technologies refer to access technologies that conform to 3GPP standards and specifications. For example, access network equipment in a 5G system is called a next-generation NodeBase station (gNB) or RAN equipment. Non-3GPP access technologies can include air interface technologies such as access points (APs) in Wireless Fidelity (WiFi), Worldwide Interoperability for Microwave Access (WiMAX), and Code Division Multiple Access (CDMA). AN devices can allow terminal devices and the 3GPP core network to interconnect using non-3GPP technologies.

[0086] The AN device is responsible for functions such as radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. The AN device provides access services to terminal devices, thereby completing the forwarding of control signals and user data between the terminal devices and the core network.

[0087] AN devices may include, but are not limited to: macro base stations, micro base stations (also known as small stations), radio network controllers (RNCs), Node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home-evolved Node Bs, or home Node Bs, HNBs), baseband units (BBUs), access points (APs) in WiFi systems, base stations (BSs) in WiMAX, wireless relay nodes, wireless backhaul nodes, transmission points (TPs), or transmission and reception points (TRPs), and may also be gNBs or transmission points (TRPs or TPs) in 5G (e.g., NR) systems, one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or network nodes constituting gNBs or transmission points, such as distributed units (DUs), or base stations in next-generation communication 6G systems, etc.

[0088] This application does not limit the specific technology or device form used in the AN device.

[0089] 3. UPF

[0090] UPF is primarily responsible for managing user plane paths and distributing data, including managing terminal IP addresses, tunnel information, traffic detection, user plane forwarding, and billing. For example, UPF can receive user plane data from the DN and send it to the terminal device through the AN device. UPF can also receive user plane data from the terminal device through the AN device and forward it to the DN.

[0091] 4. DN

[0092] DN is primarily used in operator networks that provide data services to UEs. Examples include the Internet, third-party service networks, and IP Multimedia Service (IMS) networks.

[0093] 5. AUSF

[0094] AUSF is mainly used for user authentication, etc.

[0095] 6. AMF

[0096] AMF primarily provides functions such as mobility management, lawful surveillance, access authorization, and authentication.

[0097] 7. SMF

[0098] SMF is mainly used to implement session and bearer management, address allocation, etc.

[0099] 8. NEF

[0100] The NEF is primarily used to securely expose services and capabilities provided by 3GPP network functions to the outside world.

[0101] 9. NRF

[0102] NRF is primarily used to store information about network functional entities and the services they provide.

[0103] 10. PCF

[0104] PCF is primarily used as a unified policy framework to guide network behavior, providing policy rule information to control plane network elements (such as AMF, SMF, etc.).

[0105] 11. UDM

[0106] UDM is mainly used for UE subscription data management, including the storage and management of UE identifiers and UE access authorization.

[0107] 12. AF

[0108] An application server (AF) primarily provides server-side support for a specific type of service to users; therefore, it can also be called an application server or a service server. An AF can be deployed within the operator's network itself or be a third-party AF.

[0109] exist Figure 1 In the network architecture shown, network elements can communicate with each other via interfaces. These interfaces can be point-to-point or service-oriented; this application does not impose any restrictions.

[0110] It should be understood that the network architecture shown above is merely an illustrative example, and the network architecture applicable to the embodiments of this application is not limited thereto. Any network architecture capable of realizing the functions of the above-described network elements is applicable to the embodiments of this application.

[0111] It should also be understood that Figure 1The functions or network elements shown, such as AMF, SMF, UPF, PCF, UDM, AUSF, NEF, NRF, and AF, can be understood as network elements used to implement different functions, such as network slices that can be combined as needed. These network elements can be independent devices or integrated into the same device to implement different functions. They can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform). This application does not limit the specific form of the above network elements.

[0112] It should also be understood that the above naming is defined solely for the purpose of distinguishing different functions and should not constitute any limitation on this application. This application does not preclude the possibility of using other naming conventions in 6G networks and other future networks. For example, in 6G networks, some or all of the above-mentioned network elements may use the terminology from 5G, or they may use other names, etc.

[0113] The technical solution provided in this application can be applied to relay scenarios where remote terminals connect to a network via relay terminals. For example, the technical solution provided in this application can be applied to scenarios such as extended reality (XR), VR, augmented reality (AR), or mixed reality (MR). As a remote terminal, devices in XR, VR, AR, or MR (such as wearable helmets, glasses, etc.) can use the technical solution of this application to establish a connection with the relay terminal, making the connection method between devices in XR, VR, AR, or MR and the relay terminal more flexible and facilitating the application of XR, VR, AR, or MR.

[0114] As an example, Figure 2 A schematic diagram of a network architecture in a relay scenario is shown. Figure 2 The network architecture shown can be based on Figure 1 The 5G architecture shown is not limited to this.

[0115] like Figure 2 As shown, the network architecture includes remote terminals, relay terminals, a data network component, and an operator network component (e.g., Figure 2 The RAN portion and 5G core network (5G core, 5GC) portion of the network, with the data network and operator portions referencing [the relevant documentation / references]. Figure 1The descriptions in the previous section will not be repeated here. The remote terminal interacts with the data network through a relay terminal, RAN (e.g., NG-RAN), and 5GC. Specifically, the remote terminal and the relay terminal can communicate via, for example, a PC5 interface. The relay terminal and the RAN can communicate via, for example, a Uu interface. The 5GC, for example, a UPF, can communicate with the data network via, for example, an N6 interface.

[0116] In this application, the connection between the remote terminal and the relay terminal can be a 3GPP connection or a non-3GPP connection.

[0117] It should be noted that the embodiments of this application can be applied to Figure 1 The network architecture shown and Figure 2 The network architecture shown is not limited to this.

[0118] To facilitate understanding of the embodiments of this application, the terms or technologies involved in this application will be briefly explained.

[0119] 1. Remote terminal

[0120] In this application, the terminal that obtains relay services is referred to as a remote terminal, which may also be referred to as a remote UE, etc., and will be uniformly referred to as a remote terminal below. This application does not specifically limit the type and implementation method of the remote terminal. For example, the remote terminal can be a wearable device such as a watch, a bracelet, augmented reality (AR) glasses / virtual reality (VR) glasses, etc.

[0121] 2. Relay Terminal

[0122] In this application, the terminal providing relay services is referred to as a relay terminal. A relay terminal may also be referred to as a relay UE, or a layer 3 UE-to-network relay, etc., and will be uniformly referred to as a relay terminal below. This application does not specifically limit the type and implementation method of the relay terminal. For example, a relay terminal may be a smartphone, a CPE, etc.

[0123] 3. Layer 3 (L3) relay

[0124] Layer 3 relay refers to a relay terminal performing network layer (e.g., IP layer) relay for a remote terminal. Specifically, the relay terminal receives uplink IP packets from the remote terminal and forwards these packets to the UPF (User Platform Provider) via its own network connection. Conversely, when the relay terminal receives downlink IP packets from the UPF, it forwards them to the remote terminal, where they are ultimately processed by the remote terminal's application layer.

[0125] Figure 3 This is a schematic flowchart of a Layer 3 relay.

[0126] Step 1a: Authorize the relay terminal and provide authorization information.

[0127] The authorization information may include the relay service code (RSC) configured for the relay terminal, and the protocol data unit (PDU) session parameters corresponding to each RSC. The RSC identifies a relay connection; for the relay terminal, the RSC identifies a connection service provided to the remote terminal. The PDU session parameters corresponding to the RSC may include at least one of the following: PDU session type, data network name (DNN), session and service continuity (SSC) mode, single network slice selection assistance information (S-NSSAI), or access type preference.

[0128] Step 1b: Authorize the remote terminal and provide authorization information.

[0129] The authorization information may include the relay service code (RSC) configured for the remote terminal, and the PDU session parameters corresponding to each RSC. The RSC identifies a relay connection; for the remote terminal, the RSC can identify the connection it is interested in or desires. The PDU session parameters corresponding to the RSC may include at least one of the following: PDU session type, DNN, SSC mode, S-NSSAI, or access type preference.

[0130] Step 2: The relay terminal establishes a PDU session.

[0131] Specifically, the relay terminal sends a PDU session establishment request message to the SMF through the RAN and AMF, and the SMF sends a PDU session establishment receive message to the UE through the AMF and RAN.

[0132] It should be noted that step 2 is an optional step.

[0133] Step 3: The remote terminal performs the relay UE discovery procedure.

[0134] One possible implementation involves the application (APP) starting on the remote terminal. If the UE route selection policy (URSP) determines that the APP can use Layer 3 trunk services, the remote terminal performs a trunk terminal discovery process. For example, in mode A, the trunk terminal broadcasts the RSC(s) of the connection services it can provide to the remote terminal. When the connection desired by the remote terminal matches the RSC broadcast by the trunk terminal, the remote terminal discovers the trunk terminal. Similarly, in mode B, the remote terminal broadcasts its desired RSC. When the RSC of the connection services the trunk terminal can provide to the remote terminal matches the RSC broadcast by the remote terminal, the trunk terminal responds to the remote terminal, and the remote terminal and the trunk terminal then perform the trunk terminal discovery process.

[0135] Step 4: The remote terminal selects a relay terminal and establishes a connection with the selected relay terminal for unicast mode communication.

[0136] Optionally, the relay terminal determines whether to create a new PDU session based on the correspondence between RSC and PDU session parameters, i.e., whether the PDU session in step 2 meets the PDU session parameters associated with RSC. If the PDU session in step 2 does not meet the PDU session parameters associated with RSC, the relay terminal establishes a new PDU session; if the PDU session in step 2 meets the PDU session parameters associated with RSC, the relay terminal does not need to establish a new PDU session.

[0137] Step 5: The relay terminal performs the IP router function to assign an IP address or prefix to the remote terminal.

[0138] It should be noted that step 5 is an optional step.

[0139] Step 6: If the remote terminal has special quality of service (QoS) requirements, the remote terminal can request to create or modify a QoS flow.

[0140] Specifically, the remote terminal sends a link modification request message to the relay terminal, which carries PC5 QoS parameters. The relay terminal maps the PC5 QoS parameters to Uu QoS parameters and determines whether a new or modified QoS flow needs to be created or modified. If the relay terminal determines that a new or modified QoS flow needs to be created or modified, it performs PDU session modification to create or modify the QoS flow; if the relay terminal determines that a new or modified QoS flow does not need to be created or modified, it does not perform PDU session modification.

[0141] Step 7: The relay terminal sends a remote terminal report to the SMF, which is used by the network side to perform legitimate monitoring on the remote terminal.

[0142] The remote terminal report may include at least one of the following: the remote user ID and the remote UE info.

[0143] Figure 3 The Layer 3 relay shown is a type of relay communication in a 5G ProSe communication scenario. Step 3 corresponds to PC5 discovery (PC5-D), and steps 3, 4, and 5 correspond to PC5 signaling (PC5-S), where PC5 is the interface between terminals. A more detailed description of Layer 3 relay can be found in section 3GPP TS23.304, and will not be elaborated here.

[0144] It should be noted that the embodiments of this application can be applied to the above-mentioned Layer 3 relay scenario, or other relay scenarios, without limitation.

[0145] The terminology used in this application has been briefly explained above, and will not be repeated in the following embodiments.

[0146] To facilitate understanding of the embodiments of this application, the following points will be explained before introducing the embodiments of this application.

[0147] First, in this application, lay 3 can also be in the form of L3, lay-3, lay3, Lay-3, or Lay3, etc., and this application does not make a specific limitation. Layer 2 is similar to layer 3, and will not be described in detail again.

[0148] Second, in this application, a 3GPP connection can be understood as a connection using 3GPP protocols, 3GPP interfaces, or 3GPP radio access technologies, hereinafter referred to as a 3GPP connection. For example, a 3GPP connection can be a connection that uses or meets communication protocols or standards such as D2D, sidelink, or ProSe. A non-3GPP connection can be understood as a connection that uses non-3GPP protocols, non-3GPP interfaces, or non-3GPP radio access technologies, hereinafter referred to as a non-3GPP connection. For example, a non-3GPP connection can be a connection that uses or meets short-range communication protocols such as WiFi (also known as wireless local area network, WLAN) hotspots, WiFi Direct, Bluetooth, Zigbee, radio frequency identification devices (RFID), infrared data association (IrDA), ultra-wideband (UWB), or near-field communication (NFC).

[0149] Third, in this application, the 3GPP module can be a module or unit used to implement communication using 3GPP radio access technology, such as a 3GPP modem. The non-3GPP module can be a module or unit used to implement communication using non-3GPP radio access technology, such as a Bluetooth module or a WiFi module.

[0150] Fourth, in this application, "for indicating" or "indication" can include both direct and indirect indication, or in other words, "for indicating" or "indication" can be explicit and / or implicit. For example, when describing information as indicating information I, it can include whether the information directly indicates I or indirectly indicates I, without implying that the information necessarily carries I. As another example, implicit indication can be based on the location and / or resources used for transmission; explicit indication can be based on one or more parameters, and / or one or more indices, and / or one or more bit patterns they represent.

[0151] Fifth, the definitions listed in this application for many features are only used to explain the function of the feature by way of example, and the details can be found in the prior art.

[0152] Sixth, in the embodiments shown below, the terms "first," "second," "third," "fourth," and various numerical designations are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, they may be used to distinguish different fields or different indication information.

[0153] Seventh, "predefined" can be achieved by pre-storing corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including terminals and network devices). This application does not limit the specific implementation method. "Storing" can refer to storing in one or more memories. These memories can be separate installations or integrated into the encoder, decoder, processor, or communication device. Alternatively, some memories can be separate installations, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0154] Eighth, the “protocol” involved in the embodiments of this application may refer to standard protocols in the field of communication, such as LTE protocol, NR protocol and related protocols applied to future communication systems, and this application does not limit it.

[0155] Ninth, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Here, a, b, and c can be single or multiple.

[0156] The method for establishing a connection provided by the embodiments of this application will be described in detail below with reference to the accompanying drawings. The embodiments provided by this application can be applied to the above-described embodiments. Figure 1 or Figure 2 The network architecture shown is not limited to this one.

[0157] Figure 4 This is a schematic diagram of a connection establishment method 400 provided in this application. Without loss of generality, the connection establishment method of this application is described in an interactive manner in method 400. Method 400 may include at least some of the following:

[0158] Step 401: The remote terminal determines the wireless access technology used for communication with the relay terminal.

[0159] The wireless communication technology here can be either 3GPP radio access technology or non-3GPP wireless communication technology.

[0160] In this application, there are many ways for the remote terminal to determine the wireless access technology used for communication with the relay terminal, and no restriction is imposed.

[0161] One possible implementation is that the remote terminal can determine the wireless access technology used to communicate with the relay terminal through a local policy.

[0162] Another possible implementation is that the remote terminal can determine the wireless access technology used to communicate with the relay terminal through the URSP. In this case, the URSP needs to be enhanced, for example, by adding PC5 RAT preference to the route selection components of the route selection descriptor. Table 1 below is an example of the route selection descriptor of this application.

[0163] Table 1

[0164]

[0165]

[0166] Step 402: The relay terminal determines the wireless access technology used to communicate with the remote terminal.

[0167] The method by which the relay terminal determines the wireless access technology used for communication with the remote terminal is the same as the method by which the remote terminal determines the wireless access technology used for communication with the relay terminal. You can refer to step 401, and it will not be repeated here.

[0168] Step 403: When using non-3GPP radio access technology, the remote terminal and the relay terminal can exchange non-3GPP information used to establish a non-3GPP connection through the process of 3GPP radio access technology.

[0169] Non-3GPP information may include at least one of the following: device name, hotspot name, or address information.

[0170] Specifically, the remote terminal sends non-3GPP information to the relay terminal through the 3GPP radio access technology process, and receives non-3GPP information from the relay terminal; the relay terminal sends non-3GPP information to the remote terminal through the 3GPP radio access technology process, and receives non-3GPP information from the remote terminal.

[0171] One possible implementation involves the remote terminal and the relay terminal exchanging non-3GPP information during the discovery process of 3GPP radio access technology, for example... Figure 3 The discovery process is shown in step 3.

[0172] Another possible implementation involves the remote terminal and the relay terminal exchanging non-3GPP information during the establishment of a 3GPP connection, for example... Figure 3 The connection establishment process is shown in step 4.

[0173] Step 404: The remote terminal and the relay terminal establish a non-3GPP connection.

[0174] Specifically, the remote terminal establishes a non-3GPP connection with the relay terminal based on the non-3GPP information of the relay terminal; the relay terminal establishes a non-3GPP connection with the remote terminal based on the non-3GPP information of the remote terminal.

[0175] Since the aforementioned non-3GPP information is exchanged during the 3GPP radio access technology process, and is a step executed by the 3GPP module of the remote terminal or relay terminal, communication between the 3GPP module and the non-3GPP module is required to establish a non-3GPP connection. Specifically, taking the remote terminal as an example, in response to obtaining the non-3GPP information from the relay terminal, the remote terminal's 3GPP module triggers the remote terminal's non-3GPP module to establish a non-3GPP connection with the relay terminal. The implementation method for the relay terminal is similar and will not be elaborated further.

[0176] Optionally, after the non-3GPP connection is established, the non-3GPP module of the remote terminal can send a fifth message to the 3GPP module of the remote terminal. The fifth message is used to notify that the non-3GPP connection has been successfully established, and includes the identifier of the non-3GPP connection. The implementation method of the relay terminal is similar and will not be described in detail.

[0177] Optionally, method 400 further includes steps 405 and 406.

[0178] Step 405: The remote terminal establishes an association between the non-3GPP connection and the application, and / or, the remote terminal establishes an association between the non-3GPP connection and the 3GPP connection (e.g., generating an association between the identifier of the non-3GPP connection and the PC5 QoS flow identifier (PFI) of the 3GPP connection). Here, the 3GPP connection is the connection between the remote terminal and the relay terminal.

[0179] In one scenario, a 3GPP connection is established between the remote terminal and the relay terminal in addition to a non-3GPP connection. For example, if the remote terminal and the relay terminal exchange non-3GPP information during the establishment of a 3GPP connection, then both a non-3GPP connection and a 3GPP connection exist between them. Since this application aims to transmit data between the remote terminal and the relay terminal via a non-3GPP connection instead of a 3GPP connection, the remote terminal can establish an association between the non-3GPP connection and an application and / or a 3GPP connection to send or receive data via the non-3GPP connection. For example, if an association is established between the non-3GPP connection and an application, the remote terminal can determine, based on this association, that data from the application is being transmitted to the relay terminal via the non-3GPP connection, or that data carried on the non-3GPP connection is destined for the application. Similarly, if an association is established between the non-3GPP connection and a 3GPP connection, the remote terminal can determine, based on this association, that data on the 3GPP connection is being sent or received via the non-3GPP connection.

[0180] When a remote terminal establishes an association between a non-3GPP connection and a 3GPP connection's PFI, since the PFI is associated with the PDU session, establishing an association between the non-3GPP connection and the 3GPP connection's PFI also means establishing an association with the PDU session. This allows for better utilization of the existing 3GPP relay mechanism.

[0181] In another scenario, a non-3GPP connection is established between the remote terminal and the relay terminal, but not a 3GPP connection. For example, if the remote terminal and the relay terminal exchange non-3GPP information during the 3GPP discovery process, a 3GPP connection may not be established between them. Since no 3GPP connection exists between the remote terminal and the relay terminal, the remote terminal can establish an association with the application through the non-3GPP connection to send or receive data.

[0182] Step 406: The relay terminal establishes an association between the non-3GPP connection and the PDU session, and / or, the relay terminal establishes an association between the non-3GPP connection and the 3GPP connection (e.g., generating an association between the identifier of the non-3GPP connection and the PFI of the 3GPP connection). Here, the 3GPP connection is the connection between the remote terminal and the relay terminal.

[0183] In one scenario, a 3GPP connection is established between the remote terminal and the relay terminal, in addition to a non-3GPP connection. This occurs when the remote terminal and relay terminal exchange non-3GPP information during the establishment of a 3GPP connection. Since the relay terminal needs to forward data from the non-3GPP connection to the network side (e.g., UPF) via a PDU session, and forward data from the network side to the remote terminal via the non-3GPP connection, it can achieve this forwarding process by establishing an association between the non-3GPP connection and the PDU session and / or the 3GPP connection. For example, if an association is established between the non-3GPP connection and the PDU session, the relay terminal can determine, based on this association, whether to send data from the network side to the remote terminal via the non-3GPP connection or to determine whether data carried on the non-3GPP connection should be sent via the PDU session associated with that non-3GPP connection. For example, if an association is established between a non-3GPP connection and a 3GPP connection, the remote terminal can determine, based on the association, whether the data of the 3GPP connection is sent or received through the non-3GPP connection.

[0184] When a remote terminal establishes an association between a non-3GPP connection and a 3GPP connection's PFI, since the PFI is associated with the PDU session, establishing an association between the non-3GPP connection and the 3GPP connection's PFI also means establishing an association with the PDU session. This allows for better utilization of the existing 3GPP relay mechanism.

[0185] In another scenario, a non-3GPP connection is established between the remote terminal and the relay terminal, but a 3GPP connection is not established. For example, if the remote terminal and the relay terminal exchange non-3GPP information during the 3GPP discovery process, a 3GPP connection may not be established between them. Since no 3GPP connection exists between the remote terminal and the relay terminal, the relay terminal can establish a non-3GPP connection and associate it with the PDU session.

[0186] Optionally, after the remote terminal and the relay terminal establish a non-3GPP connection, method 400 further includes step 407.

[0187] Step 407, the relay terminal sends at least one of the following information to the core network equipment: sixth information indicating the non-3GPP radio access technology determined in step 402, the identifier of the remote user, or the information of the remote terminal, so that the network side can perform legitimate interception of the remote terminal.

[0188] Optionally, prior to step 404, the remote terminal and relay terminal may perform the 3GPP radio access technology discovery process. Figure 3The discovery process shown in step 3 differs in that the discovery parameters used by the remote terminal and the relay terminal fall into the following two categories:

[0189] Scenario 1: The parameters found include RSC, which is associated with the wireless access technology determined in step 401.

[0190] In other words, RSC is associated not only with PDU session parameters but also with wireless access technology. Thus, during the discovery process, the remote terminal selects a relay terminal whose PDU session parameters and wireless access technology both match.

[0191] In this scenario, the remote terminal can send an RSC via a discovery message (in mode A) or match the RSC sent by the relay terminal (in mode B). The relay terminal can match the RSC sent by the remote terminal (in mode A) or send an RSC to the remote terminal via a discovery message (in mode B).

[0192] RSCs are associated with wireless access technologies; each RSC corresponds to a specific wireless access technology. Different RSCs may correspond to the same or different wireless access technologies.

[0193] Scenario 2: The parameters found include RSC and second information used to indicate the wireless access technology determined in step 401.

[0194] Since RSC is not related to wireless access technology, in order for the remote terminal to select a relay terminal that matches both the PDU session parameters and the wireless access technology during the discovery process, the aforementioned second information needs to be added to the discovery parameters.

[0195] In this scenario, the remote terminal can send an RSC and second message via a discovery message (in mode A) or match the RSC and second message sent by the relay terminal (in mode B). The relay terminal can match the RSC and second message sent by the remote terminal (in mode A) or send an RSC and second message to the remote terminal via a discovery message (in mode B).

[0196] In this application, the RSC is associated with a wireless access technology and may be indicated to a remote terminal or relay terminal by a core network device such as a PCF. In this case, method 400 may also include steps 408 and 409.

[0197] In step 408, the core network equipment sends information to the remote terminal indicating the association of the RSC with the radio access technology. Accordingly, the remote terminal receives the information from the core network equipment.

[0198] One possible implementation involves the core network device sending third information to the remote terminal. This third information is used to configure discovery parameters for the remote terminal during the 3GPP discovery process. The third information includes indication information indicating that the RSC is associated with the radio access technology determined in step 401.

[0199] Thus, when the third information includes indication information, the remote terminal sends or matches an RSC during the discovery process; when the third information does not include indication information, the remote terminal sends or matches an RSC and wireless access technology during the discovery process.

[0200] In step 409, the core network equipment sends information to the relay terminal indicating the association of the RSC with the radio access technology. Accordingly, the relay terminal receives the information from the core network equipment.

[0201] One possible implementation involves the core network device sending third information to the relay terminal. This third information is used to configure discovery parameters for the relay terminal during the 3GPP discovery process. The third information includes indication information indicating that the RSC is associated with the radio access technology determined in step 401.

[0202] Thus, when the third information includes indication information, the relay terminal sends or matches an RSC during the discovery process; when the third information does not include indication information, the relay terminal sends or matches an RSC and wireless access technology during the discovery process.

[0203] Optionally, method 400 may further include steps 410 and / or 411, whereby the remote terminal and / or relay terminal may report fourth information, namely the radio access technologies they support, to a core network device such as the PCF. One possible implementation is that the remote terminal sends the radio access technologies it supports to the AMF; the AMF then forwards the supported radio access technologies to the PCF. The implementation for relay terminals is similar and will not be described further.

[0204] Thus, in relay scenarios, method 400 enables remote terminals and relay terminals to transmit data via non-3GPP connections, effectively leveraging the advantages of non-3GPP short-range communication protocols and making the connection between the remote and relay terminals more flexible. Furthermore, in method 400, the remote terminal and relay terminal perform an RSC or (RSC + radio access technology) matching process during the discovery process, allowing the relay terminal to establish PDU sessions with different attributes based on the communication needs of the remote terminal to provide network services.

[0205] Figure 5This is a schematic diagram of another method 500 for establishing a connection provided in this application. Without loss of generality, the method for establishing a connection in this application is described in an interactive manner in method 500. Method 500 may include at least some of the following:

[0206] Step 501: The remote terminal determines the wireless access technology used for communication with the relay terminal.

[0207] Step 502: The relay terminal determines the wireless access technology used for communication with the remote terminal.

[0208] Steps 501-502 and Figure 4 Steps 401-402 are the same as those in the previous steps, and can be referred to in the description of steps 401-402, which will not be detailed here.

[0209] Step 503: When using non-3GPP radio access technology, the remote terminal can obtain the discovery parameters used in the discovery process of non-3GPP radio access technology.

[0210] The discovery parameter includes part or all of the RSC or the PDU session parameters corresponding to the RSC. The PDU session parameters corresponding to the RSC may include at least one of the following: PDU session type, DNN, SSC mode, S-NSSAI, or access type preference. For the remote terminal, the RSC here may be the RSC expected by the remote terminal.

[0211] One possible implementation is that the non-3GPP module of the remote terminal obtains the discovery parameters for the discovery process of non-3GPP radio access technologies from the 3GPP module of the remote terminal. Here, "obtaining" can be done actively by the non-3GPP module or passively by the non-3GPP module; there is no restriction.

[0212] Step 504: When using non-3GPP radio access technology, the relay terminal can obtain discovery parameters for the discovery process of non-3GPP radio access technology.

[0213] The discovery parameter includes part or all of the RSC or the PDU session parameters corresponding to the RSC. The PDU session parameters corresponding to the RSC may include at least one of the following: PDU session type, DNN, SSC mode, S-NSSAI, or access type preference. For the relay terminal, the RSC here can be an RSC that the relay terminal can provide.

[0214] One possible implementation is that the non-3GPP module of the relay terminal obtains the discovery parameters for the discovery process of non-3GPP radio access technologies from the 3GPP module of the relay terminal. Similarly, "obtaining" here can be either actively obtained by the non-3GPP module or passively received by the non-3GPP module; there is no restriction.

[0215] In step 505, the remote terminal and the relay terminal perform the discovery process for non-3GPP radio access technology based on the discovery parameters obtained in steps 503 and 504, and establish a non-3GPP connection.

[0216] Optionally, since the remote terminal and relay terminal do not perform 3GPP-related procedures (such as the 3GPP discovery process or connection establishment process), after the remote terminal and relay terminal establish a non-3GPP connection, the 3GPP module of the remote terminal is unaware of the 3GPP-related information of the relay terminal connected to it, and the 3GPP module of the relay terminal is also unaware of the 3GPP-related information of the remote terminal connected to it. In this case, after the non-3GPP connection is established, the non-3GPP module of the remote terminal can send a seventh message to the 3GPP module of the remote terminal. The seventh message is used to notify that the non-3GPP connection has been successfully established, and the seventh message includes at least one of the following: the identifier of the non-3GPP connection, the discovery parameters associated with the non-3GPP connection, or the 3GPP identifier of the relay terminal. The implementation method of the relay terminal is similar, except that the non-3GPP module of the relay terminal sends the 3GPP identifier of the remote terminal to the 3GPP module of the relay terminal, which will not be described in detail here.

[0217] Optionally, method 500 further includes at least one of steps 506, 507, 508, 509, 510, 511, and 512. Steps 506-512 are related to... Figure 4 Steps 405-411 are the same as those in the previous steps, and can be referred to the description of steps 405-411, which will not be repeated here.

[0218] Thus, in relay scenarios, method 500 enables remote terminals and relay terminals to transmit data via non-3GPP connections, effectively leveraging the advantages of non-3GPP short-range communication protocols and making the connection between the remote and relay terminals more flexible. Furthermore, in method 500, the remote and relay terminals perform RSC or PDU session parameter matching during the discovery process, allowing the relay terminal to establish PDU sessions with different attributes based on the communication needs of the remote terminal to provide network services.

[0219] The above combination Figure 4 and Figure 5The technical solution of this application has been given a general overview. The technical solution of this application will now be described in detail with specific examples. In the following examples, NG-RAN will be used as an example.

[0220] In the following examples, the PC5 radio access technology type can correspond to the radio access technology mentioned above, the L2 connection can correspond to the 3GPP connection mentioned above, and the ProSe discovery process can correspond to the 3GPP discovery process mentioned above.

[0221] Example 1

[0222] Figure 6 This is a schematic diagram of the overall process of the connection establishment method provided in this application.

[0223] pass Figure 6 As shown in the process, the remote terminal and the relay terminal can communicate via a non-3GPP connection (such as Bluetooth, WiFi Direct, or WiFi).

[0224] 1) Remote terminal

[0225] Step 1: Start the application on the remote terminal.

[0226] Step 2: The remote terminal determines through URSP that the application can use Layer 3 relay services.

[0227] Step 3: The remote terminal determines the type of radio access technology (RAT) used for communication with the relay terminal.

[0228] Optionally, the remote terminal can determine the PC5 RAT type locally.

[0229] Optionally, the remote terminal can determine the PC5 RAT type through URSP. In this case, URSP needs to be enhanced, for example, by adding PC5 RAT preference to the routing component of the routing descriptor, as detailed in Table 1 above.

[0230] Step 4: The remote terminal determines the RSC.

[0231] If the RSC and PC5 RAT type are related, the remote terminal can consider the corresponding PC5 RAT type when determining the RSC. The PC5 RAT type corresponding to the determined RSC is consistent with the PC5 RAT type determined in step 3.

[0232] If the RSC and PC5 RAT type are not associated, the remote terminal can determine the RSC using existing technology, that is, the remote terminal does not consider the association between the RSC and PC5 RAT type when determining the RSC.

[0233] Step 5: The remote terminal performs a proximity-based services (ProSe) discovery process, which is the relay terminal discovery process performed by the remote terminal.

[0234] If the RSC is associated with the PC5 RAT type, the remote terminal can send (in mode A) or match (in mode B) the RSC.

[0235] If the RSC and PC5 RAT types are not associated, the remote terminal can send (in mode A) or match (in mode B) the RSC and PC5 RAT types.

[0236] Step 6: The remote terminal establishes an L2 connection with the relay terminal. During the L2 connection establishment process, the remote terminal sends its non-3GPP information to the relay terminal and retrieves the relay terminal's non-3GPP information. The non-3GPP information may include at least one of the following: device name, hotspot name, media access control (MAC) address, etc.

[0237] Step 7: The 3GPP module of the remote terminal triggers the non-3GPP module to discover the relay terminal, and the non-3GPP module establishes a non-3GPP connection with the relay terminal.

[0238] Step 8: The remote terminal binds the non-3GPP connection to the application or PFI.

[0239] This refers to the establishment of non-3GPP connections and associations between remote terminals and applications or PFIs.

[0240] 2) Relay terminal

[0241] Step 1: The relay terminal performs the ProSe discovery process.

[0242] If the RSC is associated with the PC5 RAT type, the relay terminal can send (in mode B) or match (in mode A) the RSC.

[0243] If the RSC and PC5 RAT types are not associated, the remote terminal can send (in mode B) or match (in mode A) the RSC and PC5 RAT types.

[0244] Step 2: The relay terminal establishes an L2 connection with the remote terminal.

[0245] During the establishment of an L2 connection between a relay terminal and a remote terminal, the relay terminal sends non-3GPP information to the remote terminal and retrieves non-3GPP information from the remote terminal. This non-3GPP information may include at least one of the following: device name, hotspot name, MAC address, etc.

[0246] Step 3: The 3GPP module of the relay terminal triggers the non-3GPP module to open a non-3GPP connection.

[0247] Open non-3GPP connections here can include, for example, enabling a relay terminal to enter a discoverable state, broadcasting a hotspot, connecting to a specified hotspot, or connecting to a specified device.

[0248] Step 4: The relay terminal verifies the remote terminal and establishes a non-3GPP connection with the remote terminal when the remote terminal passes the verification.

[0249] Step 5: The relay terminal establishes a PDU session.

[0250] Step 5 is optional. For example, if the relay terminal determines, based on the correspondence between RSC and PDU session parameters, that an existing PDU session does not meet the PDU session parameters associated with RSC, then the relay terminal establishes a PDU session; if the relay terminal determines, based on the correspondence between RSC and PDU session parameters, that an existing PDU session meets the PDU session parameters associated with RSC, then the relay terminal does not need to establish a PDU session.

[0251] Step 6: The relay terminal establishes associations with non-3GPP connections and PDU sessions, packet filters, or PFIs.

[0252] Step 7: The relay terminal can begin relaying data.

[0253] It should be noted that the relay terminal can also perform steps 3 and 4 as the remote terminal does. The difference is that the relay terminal determines the RSC by obtaining the RSC that the relay terminal can provide.

[0254] The overall process of establishing a connection provided in this application has been described above. The following is a detailed description of the connection establishment method provided in this application.

[0255] Figure 7 This is an example of the method for establishing a connection provided in this application.

[0256] Step 701a: Authorize the relay terminal and provide authorization information.

[0257] The authorization information may include the RSC configured for the relay terminal and the PDU session parameters corresponding to each RSC. The RSC identifies a relay connection; for the relay terminal, the RSC identifies a connection service provided to the remote terminal. The PDU session parameters corresponding to the RSC may include at least one of the following: PDU session type, DNN, SSC mode, S-NSSAI, or access type preference.

[0258] This application can enhance step 701a by including: the relay terminal sending the PC5 RAT type supported by the relay terminal to the AMF; the AMF forwarding the PC5 RAT type supported by the relay terminal to the PCF; and the PCF configuring discovery parameters for the relay terminal, including the PC5 RAT type. The PC5 RAT type indicates the RAT type used by the PC5 interface in the relay service provided by RSC, i.e., the connection type that needs to be established at the underlying level. The PC5 RAT type in the discovery parameters can belong to the PC5 RAT type supported by the relay terminal, and is the PC5 RAT type used in the relay service.

[0259] Taking 5G ProSe UE-to-network relay discovery parameters as an example, the PCF can configure discovery parameters for relay terminals, including: user info ID, RSC(s), UE-to-network relay layer indicator(s), and PC5 RAT type.

[0260] The PC5 RAT type in step 701a can be 3GPP, non-3GPP, or both, or it can be a specific type such as WiFi or WLAN hotspot, WiFi Direct, Bluetooth, etc. This application does not limit it.

[0261] With the enhancements made to step 701a as described above, RSCs are associated with PC5 RAT types. For example, each RSC corresponds to one PC5 RAT type, and different RSCs may correspond to the same or different PC5 RAT types. As another example, one or more RSCs configured by the PCF for a relay terminal may correspond to the same PC5 RAT type.

[0262] It should be noted that the above enhancements to step 701a are optional.

[0263] Step 701b: Authorize the remote terminal and provide authorization information.

[0264] The enhancement of step 701b in this application is the same as step 701a, namely, the remote terminal sends the PC5 RAT type supported by the remote terminal to the AMF; the AMF forwards the PC5 RAT type supported by the remote terminal to the PCF; the PCF configures discovery parameters for the remote terminal, which include the PC5 RAT type. The PC5 RAT type indicates the RAT type used by the PC5 interface in the relay service provided by RSC, i.e., the connection type that needs to be established at the underlying level. A detailed description can be found in step 701a, and will not be repeated here.

[0265] Step 702: The relay terminal establishes a PDU session.

[0266] Specifically, the relay terminal sends a PDU session establishment request message to the SMF via NG-RAN and AMF, and the SMF sends a PDU session establishment receive message to the UE via AMF and NG-RAN.

[0267] Step 702 is an optional step.

[0268] Step 703: The remote terminal performs the relay terminal discovery process.

[0269] If an RSC is associated with a PC5 RAT type, it will be included in the discovery process messages (e.g., announcement messages, solicitation messages, etc.). For example, in the discovery process of Mode A, the solicitation message broadcast by the remote terminal includes an RSC. When the RSC of the connection service that the relay terminal can provide to the remote terminal matches the RSC broadcast by the remote terminal, the relay terminal responds to the remote terminal, and the remote terminal and the relay terminal execute the relay terminal discovery process. As another example, in the discovery process of Mode B, the announcement message broadcast by the relay terminal includes an RSC of the connection service that the relay terminal can provide to the remote terminal. When the RSC expected by the remote terminal matches the RSC broadcast by the relay terminal, the remote terminal has discovered the relay terminal.

[0270] If the RSC and PC5 RAT types are not associated, then the messages during the discovery process (such as notification messages, solicitation messages, etc.) include both the RSC and PC5 RAT types. For example, in the discovery process of Mode A, the remote terminal determines its desired PC5 RAT type, i.e., the RAT the remote terminal expects to use in PC5. The solicitation message broadcast by the remote terminal includes the desired RSC and PC5 RAT types. When the RSC of the connection service that the relay terminal can provide to the remote terminal matches the RSC broadcast by the remote terminal and supports the PC5 RAT type expected by the remote terminal, the relay terminal responds to the remote terminal, and the remote terminal and the relay terminal execute the relay terminal discovery process. As another example, in the discovery process of Mode B, the notification message broadcast by the relay terminal may include both the RSC and PC5 RAT types. The remote terminal determines its desired RAT in PC5, and the remote terminal selects a relay terminal whose RSC and PC5 RAT types both match.

[0271] Step 704: The remote terminal establishes a 3GPP layer 2 connection with the relay terminal.

[0272] During the establishment of a 3GPP Layer 2 connection between a remote terminal and a relay terminal, the two terminals exchange non-3GPP information. For example, the remote terminal sends its non-3GPP information to the relay terminal and receives its non-3GPP information from the relay terminal. Conversely, the relay terminal sends its non-3GPP information to the remote terminal and receives its non-3GPP information from the remote terminal.

[0273] Non-3GPP information may include at least one of the following: device name, hotspot name, MAC address, etc.

[0274] Step 705a: When the PC5 RAT type is non-3GPP, the 3GPP module of the remote terminal triggers the non-3GPP module to establish the corresponding underlying connection, such as a connection using short-range communication protocols such as WiFi or WLAN hotspot, WiFi Direct, or Bluetooth.

[0275] Specifically, the 3GPP module of the remote terminal triggers the non-3GPP module to open a non-3GPP connection. Opening a non-3GPP connection here can be, for example, enabling the remote terminal to enter a discoverable state, broadcasting a hotspot, connecting to a specified hotspot, or connecting to a specified device.

[0276] Step 705b: When the PC5 RAT type is non-3GPP, the 3GPP module of the relay terminal triggers the non-3GPP module to establish the corresponding underlying connection, such as a connection using short-range communication protocols such as WiFi or WLAN hotspot, WiFi Direct, or Bluetooth.

[0277] Specifically, the 3GPP module of the relay terminal triggers the non-3GPP module to open a non-3GPP connection. Opening a non-3GPP connection here can be, for example, enabling the relay terminal to enter a discoverable state, broadcasting a hotspot, connecting to a specified hotspot, or connecting to a specified device.

[0278] In steps 705a and 705b, the specific operations for the remote terminal to open a non-3GPP connection correspond to those for the relay terminal. For example, if the remote terminal enters a discoverable state, the relay terminal can connect to a designated device. Or, if the remote terminal broadcasts a hotspot, the relay terminal can connect to that hotspot.

[0279] Step 706: The remote terminal establishes a non-3GPP connection with the relay terminal.

[0280] Step 707a: When the non-3GPP module of the remote terminal determines that the connected peer UE is the device specified by the 3GPP module, the non-3GPP module notifies the 3GPP module that the peer terminal has successfully connected and the identifier of the non-3GPP connection.

[0281] Step 707b: When the non-3GPP module of the relay terminal determines that the connected peer terminal is the device specified by the 3GPP module, the non-3GPP module notifies the 3GPP module that the peer terminal has successfully connected and the identifier of the non-3GPP connection.

[0282] Step 708: The relay terminal establishes a new PDU session.

[0283] Step 708 is an optional step. For example, if the relay terminal determines, based on the correspondence between RSC and PDU session parameters, that an existing PDU session (e.g., the PDU session established in step 702) does not meet the PDU session parameters associated with RSC, then the relay terminal establishes a new PDU session, and the session parameters of the new PDU session can be determined based on RSC; if the relay terminal determines, based on the correspondence between RSC and PDU session parameters, that an existing PDU session (e.g., the PDU session established in step 702) meets the PDU session parameters associated with RSC, then the relay terminal does not need to create a new PDU session.

[0284] Step 709: If the remote terminal has special QoS requirements, the remote terminal may request the relay terminal to modify the 3GPP layer 2 connection in order to create or modify the QoS flow.

[0285] Specifically, the remote terminal sends a connection modification request message to the relay terminal, which carries PC5 QoS parameters.

[0286] Step 710: The relay terminal maps the PC5 QoS parameters to Uu QoS parameters and determines whether a new or modified QoS flow needs to be created or modified. If the relay terminal determines that a new or modified QoS flow needs to be created or modified, the relay terminal performs PDU session modification to create or modify the QoS flow; if the relay terminal determines that a new or modified QoS flow does not need to be created or modified, the relay terminal does not perform PDU session modification.

[0287] Steps 709 and 710 are optional.

[0288] Step 711a: The remote terminal establishes a data mapping relationship.

[0289] Specifically, the remote terminal will bind the application to the non-3GPP connection or establish a mapping between the PC5 QoS flow identifier (PFI) and the identifier of the non-3GPP connection.

[0290] Step 711b: The relay terminal establishes a data mapping relationship for mapping uplink and downlink data.

[0291] Specifically, the relay terminal establishes an association between the identifier of a non-3GPP connection and the PDU session, PFI, or packet filter. For example, the relay terminal can enhance QoS rules, which include the association between the identifier of a non-3GPP connection and the packet filter. Another example is the relay terminal establishing a mapping between the PFI and the identifier of a non-3GPP connection.

[0292] Step 712: The relay terminal sends a remote terminal report to the SMF, which is used by the network side to perform legitimate monitoring on the remote terminal.

[0293] The remote terminal report may include at least one of the following: PC5 RAT type, remote user ID, and remote terminal information.

[0294] Subsequently, data can be transmitted between the remote terminal and the relay terminal via a non-3GPP connection, and the relay terminal can also forward data from the remote terminal.

[0295] It should be noted that, in Figure 7 The process of determining the PC5 RAT type and the RSC is not shown in the document.

[0296] Figure 6 and Figure 7 The method described requires internal enhancements to both the remote terminal and the relay terminal to enable interaction and data forwarding between the aforementioned 3GPP module and non-3GPP module.

[0297] Figure 8This is a schematic diagram of the internal enhancements of remote terminals and relay terminals.

[0298] Figure 8 Figure (a) illustrates the internal enhancements required for both the remote terminal and the relay terminal. For example... Figure 8 As shown in Figure (a), the terminal internally includes a Layer 3 Relay-PC5 service SDK module. This module is responsible for the interaction between 3GPP modules and non-3GPP modules. For example, the 3GPP module triggers the non-3GPP module to open a non-3GPP connection, and the non-3GPP module notifies the 3GPP module of the successful connection of the peer terminal and the identifier of the non-3GPP connection.

[0299] Figure 8 Figure (b) illustrates the additional internal enhancements required for the relay terminal. For example... Figure 8 As shown in Figure (b), the Layer 3 relay PC5 service SDK module added inside the terminal is also responsible for data forwarding between non-3GPP modules and 3GPP modules.

[0300] Of course, remote terminals can also perform this. Figure 8 The enhancements shown in Figure (b) are not limited in this application.

[0301] Thus, in Example 1, the remote terminal and the relay terminal exchange non-3GPP information to establish a non-3GPP connection through the 3GPP ProSe layer 2 connection establishment process, triggering the establishment of the non-3GPP connection. This allows the remote terminal and the relay terminal to transmit data via the non-3GPP connection. Furthermore, Example 1 enhances the internal workings of the terminal, enabling interaction and data forwarding between the 3GPP and non-3GPP modules within the terminal.

[0302] Example 2

[0303] Figure 9 This is another schematic diagram of the overall process of the connection establishment method provided in this application.

[0304] pass Figure 9 As shown in the process, the remote terminal and the relay terminal can communicate via a non-3GPP connection (such as Bluetooth, WiFi Direct, or WiFi).

[0305] 1) Remote terminal

[0306] Step 1: Start the application on the remote terminal.

[0307] Step 2: The remote terminal determines through URSP that the application can use Layer 3 relay services.

[0308] Step 3: The remote terminal determines the PC5 RAT type used for communication with the relay terminal.

[0309] Step 4: The remote terminal determines the RSC.

[0310] Figure 9 Steps 1 to 4 in the middle Figure 6 Steps 1 through 4 are the same, you can refer to them. Figure 6 The relevant descriptions will not be elaborated here.

[0311] Step 5: The remote terminal performs the ProSe discovery process, which is the relay terminal discovery process performed by the remote terminal.

[0312] If the RSC is associated with the PC5 RAT type, the remote terminal can send (in mode A) or match (in mode B) the RSC.

[0313] If the RSC and PC5 RAT types are not associated, the remote terminal can send (in mode A) or match (in mode B) the RSC and PC5 RAT types.

[0314] Unlike Example 1, in the ProSe discovery process, the remote terminal sends its non-3GPP information to the relay terminal and retrieves the relay terminal's non-3GPP information. This non-3GPP information may include at least one of the following: device name, hotspot name, MAC address, etc.

[0315] Step 7: The 3GPP module of the remote terminal triggers the non-3GPP module to discover the relay terminal, and the non-3GPP module establishes a non-3GPP connection with the relay terminal.

[0316] Step 8: The remote terminal binds the non-3GPP connection to the application or PFI.

[0317] This refers to the establishment of non-3GPP connections and associations between remote terminals and applications or PFIs.

[0318] 2) Relay terminal

[0319] Step 1: The relay terminal performs the ProSe discovery process.

[0320] If the RSC is associated with the PC5 RAT type, the relay terminal can send (in mode B) or match (in mode A) the RSC.

[0321] If the RSC and PC5 RAT types are not associated, the remote terminal can send (in mode B) or match (in mode A) the RSC and PC5 RAT types.

[0322] Unlike Example 1, in the ProSe discovery process, the relay terminal sends its non-3GPP information to the remote terminal and obtains the remote terminal's non-3GPP information. This non-3GPP information may include at least one of the following: device name, hotspot name, MAC address, etc.

[0323] Step 3: The 3GPP module of the relay terminal triggers the non-3GPP module to open a non-3GPP connection.

[0324] Step 4: The relay terminal verifies the remote terminal and establishes a non-3GPP connection with the remote terminal when the remote terminal passes the verification.

[0325] Step 5: The relay terminal establishes a PDU session.

[0326] Step 6: The relay terminal establishes associations between the non-3GPP connection and the PDU session, PFI, or packet filter.

[0327] Step 7: The relay terminal can begin relaying data. Figure 9 Steps 2 to 6 in the middle Figure 6 Steps 3 through 7 are the same and can be referred to. Figure 6 The relevant descriptions will not be elaborated here.

[0328] It should be noted that the relay terminal can also perform steps 3 and 4 as the remote terminal does. The difference is that the relay terminal determines the RSC by obtaining the RSC that the relay terminal can provide.

[0329] The overall process of establishing a connection provided in this application has been described above. The connection establishment method provided in this application will be described in detail below.

[0330] Figure 10 This is another example of the method for establishing a connection provided in this application.

[0331] Step 1001a: Authorize the relay terminal and provide authorization information.

[0332] Step 1001b: Authorize the remote terminal and provide authorization information.

[0333] Step 1002: The relay terminal establishes a PDU session.

[0334] Figure 10 Steps 1001a to 1002 in the middle Figure 7 Steps 701a to 702 are the same and can be referred to. Figure 7 The relevant descriptions will not be elaborated here.

[0335] Step 1003: The remote terminal performs the relay terminal discovery process.

[0336] If the RSC is associated with a PC5 RAT type, it will be included in the discovery process messages (e.g., notification messages, solicitation messages, etc.). For example, in the discovery process of Mode A, the solicitation message broadcast by the remote terminal includes an RSC. When the RSC that the relay terminal can provide for the connection service to the remote terminal matches the RSC broadcast by the remote terminal, the relay terminal responds to the remote terminal, and the remote terminal and the relay terminal execute the relay terminal discovery process. As another example, in the discovery process of Mode B, the notification message broadcast by the relay terminal includes an RSC that the relay terminal can provide for the connection service to the remote terminal. When the RSC expected by the remote terminal matches the RSC broadcast by the relay terminal, the remote terminal discovers the relay terminal.

[0337] If the RSC and PC5 RAT types are not associated, then the messages during the discovery process (such as notification messages, solicitation messages, etc.) include both the RSC and PC5 RAT types. For example, in the discovery process of Mode A, the remote terminal determines its desired PC5 RAT type, i.e., the RAT the remote terminal expects to use in PC5. The solicitation message broadcast by the remote terminal includes the desired RSC and PC5 RAT types. When the RSC of the connection service that the relay terminal can provide to the remote terminal matches the RSC broadcast by the remote terminal and supports the PC5 RAT type expected by the remote terminal, the relay terminal responds to the remote terminal, and the remote terminal and the relay terminal execute the relay terminal discovery process. As another example, in the discovery process of Mode B, the notification message broadcast by the relay terminal may include both the RSC and PC5 RAT types. The remote terminal determines its desired RAT in PC5, and the remote terminal selects a relay terminal whose RSC and PC5 RAT types both match.

[0338] Unlike Example 1, during the ProSe discovery process, the remote terminal and the relay terminal also exchange non-3GPP information. Specifically, the remote terminal sends its own non-3GPP information to the relay terminal and retrieves the relay terminal's non-3GPP information; the relay terminal sends its own non-3GPP information to the remote terminal and retrieves the remote terminal's non-3GPP information. This non-3GPP information may include at least one of the following: device name, hotspot name, MAC address, etc.

[0339] For example, during the discovery process in Mode A, the relay terminal includes the PC5 RAT type in the broadcast notification message. After the remote terminal selects the relay terminal, it requests additional parameters from the relay terminal. The relay terminal then sends its non-3GPP information to the remote terminal using these additional parameters.

[0340] For example, during the discovery process of Mode B, the remote terminal includes the desired PC5RAT type and the remote terminal's non-3GPP information in the broadcast solicitation message, and the relay terminal sends the relay terminal's non-3GPP information to the remote terminal through a response message.

[0341] Step 10054a: When the PC5 RAT type is non-3GPP, the 3GPP module of the remote terminal triggers the non-3GPP module to establish the corresponding underlying connection.

[0342] Step 1004b: When the PC5 RAT type is non-3GPP, the 3GPP module of the relay terminal triggers the non-3GPP module to establish the corresponding underlying connection.

[0343] Step 1005: The remote terminal establishes a non-3GPP connection with the relay terminal.

[0344] Step 1006a: When the non-3GPP module of the remote terminal determines that the connected peer terminal is the device specified by the 3GPP module, the non-3GPP module notifies the 3GPP module that the peer terminal has successfully connected and the identifier of the non-3GPP connection.

[0345] Step 1006b: When the non-3GPP module of the relay terminal determines that the connected peer terminal is the device specified by the 3GPP module, the non-3GPP module notifies the 3GPP module that the peer terminal has successfully connected and the identifier of the non-3GPP connection.

[0346] Step 1007: The relay terminal establishes a new PDU session.

[0347] Step 1008a: The remote terminal establishes a data mapping relationship.

[0348] Step 1008b: The relay terminal establishes a data mapping relationship for mapping uplink and downlink data.

[0349] Step 1009: The relay terminal sends a remote terminal report to the SMF, which is used by the network side to perform legitimate monitoring on the remote terminal.

[0350] Figure 10 Steps 1004a to 1007 in Figure 7 Steps 705a to 708 are the same, and steps 1008a to 1009 are the same. Figure 7 Steps 711a to 712 are the same and can be referred to. Figure 7 The relevant descriptions will not be elaborated here.

[0351] Subsequently, data can be transmitted between the remote terminal and the relay terminal via a non-3GPP connection, and the relay terminal can also forward data from the remote terminal.

[0352] It should be noted that, in Figure 10 The process of determining the PC5 RAT type and the RSC is not shown in the document.

[0353] Figure 9 and Figure 10 The method described requires internal enhancements to both the remote terminal and the relay terminal to enable interaction and data forwarding between the 3GPP module and non-3GPP modules. Internal enhancements for the remote terminal and relay terminal can be found in [reference needed]. Figure 8 Related descriptions.

[0354] Thus, in Example 2, the remote terminal and the relay terminal exchange non-3GPP information through the 3GPP ProSe discovery process to establish a non-3GPP connection, thereby triggering the establishment of the non-3GPP connection. This allows the remote terminal and the relay terminal to transmit data via the non-3GPP connection. Furthermore, Example 2 enhances the internal workings of the terminal, enabling interaction and data forwarding between the 3GPP module and the non-3GPP module within the terminal.

[0355] Example 3

[0356] Figure 11 This is another schematic diagram of the overall process of the connection establishment method provided in this application.

[0357] pass Figure 11 As shown in the process, the remote terminal and the relay terminal can communicate via a non-3GPP connection (such as Bluetooth, WiFi Direct, or WiFi).

[0358] 1) Remote terminal

[0359] Step 1: Start the application on the remote terminal.

[0360] Step 2: The remote terminal determines through URSP that the application can use Layer 3 relay services.

[0361] Step 3: The remote terminal determines the PC5 RAT used for communication with the relay terminal.

[0362] Step 4: The remote terminal determines the RSC.

[0363] Figure 11 Steps 1 to 4 in the middle Figure 6 Steps 1 through 4 are the same, you can refer to them. Figure 6 The relevant descriptions will not be elaborated here.

[0364] Step 5: The remote terminal performs a non-3GPP discovery process.

[0365] Discovery parameters carried in messages outside of the 3GPP discovery process (such as beacon messages and service discovery messages) include RSC or the corresponding PDU session parameters. These PDU session parameters can include at least one of the following: PDU session type, DNN, SSC mode, S-NSSAI, or access type preference.

[0366] During non-3GPP discovery, the remote terminal sends or matches the RSC or the PDU session parameters corresponding to the RSC.

[0367] Step 6: The remote terminal establishes a non-3GPP connection with the relay terminal.

[0368] Step 7: The remote terminal binds the non-3GPP connection to the application or PFI.

[0369] This refers to the establishment of non-3GPP connections and associations between remote terminals and applications or PFIs.

[0370] 2) Relay terminal

[0371] Step 1: The relay terminal performs a non-3GPP discovery process.

[0372] Discovery parameters carried in messages during non-3GPP discovery processes (such as beacon messages and service discovery messages) include RSC or the corresponding PDU session parameters. The corresponding PDU session parameters can include at least one of the following: PDU session type, DNN, SSC mode, S-NSSAI, or access type preference.

[0373] During non-3GPP discovery, the relay terminal sends or matches the RSC or the PDU session parameters corresponding to the RSC.

[0374] Step 2: The relay terminal establishes a non-3GPP connection with the remote terminal.

[0375] Step 3: The relay terminal obtains the 3GPP identifier of the remote terminal.

[0376] The relay terminal can obtain the 3GPP identifier of the remote terminal during or after the establishment of a non-3GPP connection, so as to relay the data of the remote terminal.

[0377] Step 4: The relay terminal establishes a PDU session.

[0378] Step 4 is optional. For example, if the relay terminal determines, based on the correspondence between RSC and PDU session parameters, that an existing PDU session does not meet the PDU session parameters associated with RSC, then the relay terminal establishes a PDU session; if the relay terminal determines, based on the correspondence between RSC and PDU session parameters, that an existing PDU session meets the PDU session parameters associated with RSC, then the relay terminal does not need to establish a PDU session.

[0379] Step 5: The relay terminal establishes associations between the non-3GPP connection and the PDU session, PFI, or packet filter.

[0380] Step 6: The relay terminal can begin relaying data.

[0381] It should be noted that the relay terminal can also perform steps 3 and 4 as the remote terminal does. The difference is that the relay terminal determines the RSC by obtaining the RSC that the relay terminal can provide.

[0382] The overall process of establishing a connection provided in this application has been described above. The following is a detailed description of the connection establishment method provided in this application.

[0383] Figure 12 This is another example of the method for establishing a connection provided in this application.

[0384] Step 1201a: Authorize the relay terminal and provide authorization information.

[0385] Step 1201b: Authorize the remote terminal and provide authorization information.

[0386] Step 1202: The relay terminal establishes a PDU session.

[0387] Figure 12 Steps 1201a to 1202 in the middle Figure 7 Steps 701a to 702 are the same and can be referred to. Figure 7 The relevant descriptions will not be elaborated here.

[0388] Step 1203a: When the PC5 RAT type is non-3GPP, the 3GPP module of the remote terminal sends the discovery parameters for non-3GPP discovery and the 3GPP identifier of the remote terminal to the non-3GPP module, thereby triggering the non-3GPP discovery process.

[0389] The discovery parameters used for non-3GPP discovery may include RSC or the PDU session parameters corresponding to RSC. The PDU session parameters corresponding to RSC may include at least one of the following: PDU session type, DNN, SSC mode, S-NSSAI, or access type preference. The 3GPP identifier of the remote terminal may include the remote terminal's GUTI and / or ProSe UE ID.

[0390] Step 1203b: When the PC5 RAT type is non-3GPP, the 3GPP module of the relay terminal sends the discovery parameters for non-3GPP discovery and the 3GPP identifier of the relay terminal to the non-3GPP module, thereby triggering the non-3GPP discovery process.

[0391] The discovery parameters used for non-3GPP discovery may include RSC or the PDU session parameters corresponding to RSC. The PDU session parameters corresponding to RSC may include at least one of the following: PDU session type, DNN, SSC mode, S-NSSAI, or access type preference. The 3GPP identifier of the relay terminal may include the relay terminal's GUTI and / or ProSe UE ID.

[0392] Step 1204: The remote terminal and the relay terminal perform a non-3GPP discovery process.

[0393] The discovery parameters used for non-3GPP discovery are carried in the messages during the non-3GPP discovery process.

[0394] For example, when the non-3GPP discovery process is a WiFi Direct discovery process, a relay service can be defined, and the discovery parameters used for non-3GPP discovery mentioned above can be included in the service discovery message. Optionally, the relay service can be identified through reserved fields in the service discovery message.

[0395] For example, when the non-3GPP discovery process is a Bluetooth or WiFi discovery process, the discovery parameters used for non-3GPP discovery can be carried in the reserved field of the beacon message.

[0396] Step 1205: The remote terminal and the relay terminal establish a non-3GPP connection.

[0397] It should be noted that during or after the aforementioned non-3GPP discovery process, the remote terminal and the relay terminal can exchange 3GPP identifiers. For example, the remote terminal and the relay terminal can exchange their 3GPP identifiers through the user plane.

[0398] Step 1206a: The non-3GPP module of the remote terminal notifies the 3GPP module of the successful connection of the peer terminal, the identifier of the non-3GPP connection, the discovery parameters associated with the non-3GPP connection (i.e. the actual discovery parameters), and the 3GPP identifier of the peer terminal (optional).

[0399] Step 1206b: The non-3GPP module of the relay terminal notifies the 3GPP module of the successful connection of the peer terminal, the identifier of the non-3GPP connection, the discovery parameters associated with the non-3GPP connection (i.e. the actual discovery parameters), and the 3GPP identifier of the peer terminal.

[0400] Step 1207: The relay terminal establishes a new PDU session.

[0401] Step 1208a: The remote terminal establishes a data mapping relationship.

[0402] Step 1208b: The relay terminal establishes a data mapping relationship for mapping uplink and downlink data.

[0403] Step 1209: The relay terminal sends a remote terminal report to the SMF, which is used by the network side to perform legitimate monitoring on the remote terminal.

[0404] Figure 12 Step 1207 and Figure 6 Step 708 is the same as step 1208a, and steps 1208a to 1209 are the same as step 1208a. Figure 7 Steps 711a to 712 are the same and can be referred to. Figure 7 The relevant descriptions will not be elaborated here.

[0405] Subsequently, data can be transmitted between the remote terminal and the relay terminal via a non-3GPP connection, and the relay terminal can also forward data from the remote terminal.

[0406] It should be noted that, in Figure 12 The process of determining the PC5 RAT type and the RSC is not shown in the document.

[0407] Figure 11 and Figure 12 The method described requires internal enhancements to both the remote terminal and the relay terminal to enable interaction and data forwarding between the aforementioned 3GPP module and non-3GPP module.

[0408] Figure 13 This is another schematic diagram of the internal enhancements of remote terminals and relay terminals.

[0409] Figure 13 Figure (a) illustrates the internal enhancements required for both the remote terminal and the relay terminal. For example... Figure 13As shown in Figure (a), a Layer 3 Relay PC5 Service SDK module has been added internally to the terminal. This module is responsible for the interaction between the 3GPP module and the non-3GPP module. For example, the 3GPP module sends discovery parameters for non-3GPP discovery to the non-3GPP module, and the non-3GPP module notifies the 3GPP module of the successful connection of the peer terminal, the 3GPP identifier of the peer terminal, the discovery parameters associated with the non-3GPP connection, and the identifier of the non-3GPP connection.

[0410] Figure 13 Figure (b) illustrates the additional internal enhancements required for the relay terminal. For example... Figure 13 As shown in Figure (b), the Layer 3 relay PC5 service SDK module added inside the terminal is also responsible for data forwarding between non-3GPP modules and 3GPP modules.

[0411] Of course, remote terminals can also perform this. Figure 13 The enhancements shown in Figure (b) are not limited in this application.

[0412] Thus, in Example 3, the remote terminal and the relay terminal exchange parameters for establishing a non-3GPP connection through a non-3GPP discovery process, triggering the establishment of the non-3GPP connection and enabling data transmission between the remote terminal and the relay terminal via the non-3GPP connection. Furthermore, Example 3 enhances the internal workings of the terminal, enabling interaction and data forwarding between the 3GPP module and the non-3GPP module within the terminal.

[0413] The above text combined Figures 4 to 13 The method provided in this application is described in detail below, and will be combined with... Figures 14 to 15 The present application describes the device embodiments in detail. It is understood that, in order to achieve the functions described in the above embodiments, Figure 9 or Figure 10 The apparatus includes hardware structures and / or software modules corresponding to perform various functions. Those skilled in the art will readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0414] Figure 14 and Figure 15 The diagram illustrates the possible structures of apparatuses provided for embodiments of this application. These apparatuses can be used to implement the functions of the first terminal or core network equipment in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0415] like Figure 14As shown, the device 1400 includes a transceiver unit 1410 and a processing unit 1420.

[0416] In some implementations, when device 1400 is used to implement the function of the first terminal in the above method embodiments, processing unit 1420 is used to: determine the wireless access technology used for communication with the second terminal. Transceiver unit 1410 is used to: when the wireless access technology is a first non-3GPP wireless access technology, obtain non-3GPP information of the second terminal during the first process of 3GPP wireless access technology, the non-3GPP information being used by the first terminal and the second terminal to establish a connection of the first non-3GPP wireless access technology. Processing unit 1420 is also used to: establish a connection of the first non-3GPP wireless access technology with the second terminal based on the first non-3GPP information. Wherein, the first terminal is a remote terminal in a relay scenario, and the second terminal is a relay terminal in a relay scenario; or, the first terminal is a relay terminal in a relay scenario, and the second terminal is a remote terminal in a relay scenario.

[0417] Optionally, the processing unit 1420 is specifically configured to: determine the wireless access technology used for communicating with the second terminal through URSP or local policies.

[0418] Optionally, the non-3GPP information includes at least one of the following: device name, hotspot name, or address information.

[0419] Optionally, the first process includes at least one of the following: the process by which the first terminal discovers the second terminal through the 3GPP radio access technology discovery process, or the process by which the first terminal and the second terminal establish a 3GPP radio access technology connection.

[0420] Optionally, the processing unit 1420 is specifically configured to: discover the second terminal through the discovery process of 3GPP radio access technology according to a first discovery parameter; wherein the first discovery parameter includes RSC, the RSC being associated with the first non-3GPP radio access technology; or the first discovery parameter includes the RSC and second information, the second information being used to indicate the first non-3GPP radio access technology.

[0421] Optionally, the first discovery parameter includes RSC, and the transceiver unit 1410 is further configured to: receive third information from the core network equipment, the third information being used to configure the first discovery parameter for the first terminal, the third information including indication information, the indication information being used to indicate that the RSC is associated with the first non-3GPP radio access technology.

[0422] Optionally, the transceiver unit 1410 is further configured to: report fourth information to the core network device, the fourth information being used to indicate non-3GPP radio access technologies supported by the first device.

[0423] Optionally, the processing unit 1420 is specifically configured to: in response to acquiring the non-3GPP, the 3GPP module triggers the non-3GPP module to establish a connection with the second terminal using the first non-3GPP radio access technology.

[0424] Optionally, the transceiver unit 1410 is further configured to: send fifth information from the non-3GPP module to the 3GPP module, the fifth information being used to notify that the connection of the first non-3GPP radio access technology has been successfully established, the fifth information including an identifier of the connection of the first non-3GPP radio access technology.

[0425] Optionally, when the first terminal is a remote terminal in the relay scenario, the processing unit 1420 is further configured to: establish an association between the connection of the first non-3GPP radio access technology and the application; and / or, establish an association between the connection of the first non-3GPP radio access technology and the connection of the 3GPP radio access technology; wherein the connection of the 3GPP radio access technology is the connection between the first terminal and the second terminal, and the data of the application and the connection of the 3GPP radio access technology are carried on the connection of the first non-3GPP radio access technology.

[0426] Optionally, when the first terminal is a relay terminal in the relay scenario, the processing unit 1420 is further configured to: establish an association between the connection of the first non-3GPP radio access technology and the PDU session; and / or establish an association between the connection of the first non-3GPP radio access technology and the connection of the 3GPP radio access technology; wherein the connection of the 3GPP radio access technology is the connection between the first terminal and the second terminal, the connection of the 3GPP radio access technology corresponds to the PDU session, and the PDU session is used to carry the data of the connection of the first non-3GPP radio access technology.

[0427] Optionally, when the first terminal is a relay terminal in the relay scenario, the transceiver unit 1410 is further configured to: send at least one of the following information to the core network equipment: sixth information, the identifier of the remote user, or the information of the second terminal, wherein the sixth information is used to indicate the first non-3GPP radio access technology.

[0428] Optionally, the first non-3GPP radio access technology includes at least one of the following: WiFi, WiFi Direct, Bluetooth, Zigbee, RFID, IrDA, UWB, or NFC; and / or, the 3GPP radio access technology includes at least one of the following: D2D, sidelink, or ProSe.

[0429] In some implementations, when device 1400 is used to implement the function of the first terminal in the above method embodiments, processing unit 1420 is used to: determine the wireless access technology used for communication with the second terminal. Transceiver unit 1410 is used to: when the wireless access technology is a first non-3GPP wireless access technology, acquire second discovery parameters for the discovery process of the first non-3GPP wireless access network technology, the second discovery parameters including at least one of the following: RSC, S-NSSAI, or DNN. Processing unit 1420 is also used to: discover the second terminal through the discovery process of the first non-3GPP wireless access technology according to the second discovery parameters, and establish a connection with the second terminal using the first non-3GPP wireless access technology. Wherein, the first terminal is a remote terminal in a relay scenario, and the second terminal is a relay terminal in a relay scenario; or, the first terminal is a relay terminal in a relay scenario, and the second terminal is a remote terminal in a relay scenario.

[0430] Optionally, the processing unit 1420 is specifically used to: determine the wireless access technology used for communicating with the second terminal through the User Equipment Routing Policy (URSP) or a local policy.

[0431] Optionally, the transceiver unit 1410 is specifically used for: non-3GPP modules to obtain the second discovery parameter from 3GPP modules.

[0432] Optionally, the transceiver unit 1410 is further configured to: obtain the identifier of the 3GPP radio access technology of the second terminal during the process of establishing the connection of the first non-3GPP radio access technology; and / or, obtain the identifier of the 3GPP radio access technology of the second terminal through the user plane after the connection of the first non-3GPP radio access technology is established.

[0433] Optionally, the transceiver unit 1410 is further configured to: send a seventh message from the non-3GPP module to the 3GPP module, the seventh message being used to notify that the connection of the first non-3GPP radio access technology has been successfully established, the seventh message including at least one of the following: the identifier of the connection of the first non-3GPP radio access technology, the discovery parameters associated with the connection of the first non-3GPP radio access technology, or the identifier of the 3GPP radio access technology of the second terminal.

[0434] Optionally, when the first terminal is a remote terminal in the relay scenario, the processing unit 1420 is further configured to: establish an association between the connection of the first non-3GPP radio access technology and the application; and / or, establish an association between the connection of the first non-3GPP radio access technology and the connection of the 3GPP radio access technology; wherein the connection of the 3GPP radio access technology is the connection between the first terminal and the second terminal, and the data of the application and the connection of the 3GPP radio access technology are carried on the connection of the first non-3GPP radio access technology.

[0435] Optionally, when the first terminal is a relay terminal in the relay scenario, the processing unit 1420 is further configured to: establish an association between the connection of the first non-3GPP radio access technology and the PDU session; and / or establish an association between the connection of the first non-3GPP radio access technology and the connection of the 3GPP radio access technology; wherein the connection of the 3GPP radio access technology is the connection between the first terminal and the second terminal, the connection of the 3GPP radio access technology corresponds to the PDU session, and the PDU session is used to carry the data of the connection of the first non-3GPP radio access technology.

[0436] Optionally, when the first terminal is a relay terminal in the relay scenario, the transceiver unit 1410 is further configured to: send at least one of the following information to the core network equipment: sixth information, the identifier of the remote user, or the information of the second terminal, wherein the sixth information is used to indicate the first non-3GPP radio access technology.

[0437] Optionally, the first non-3GPP radio access technology includes at least one of the following: WiFi, WiFi Direct, Bluetooth, Zigbee, RFID, IrDA, UWB, or NFC; and / or, the 3GPP radio access technology includes at least one of the following: D2D, sidelink, or ProSe.

[0438] When device 1400 is used to implement the functions of the core network device in the above method embodiment, transceiver unit 1410 is used to: receive fourth information reported by the first terminal, the fourth information being used to indicate the non-3GPP radio access technology supported by the first device; send third information to the first terminal, the third information being used to configure a first discovery parameter for the first terminal, the first discovery parameter including RSC, the third information including indication information, the indication information being used to indicate that the RSC is associated with a first non-3GPP radio access technology.

[0439] For a more detailed description of the transceiver unit 1410 and the processing unit 1420, please refer to the relevant descriptions in the above method embodiments, which will not be repeated here.

[0440] like Figure 15 As shown, device 1500 includes a processor 1510 and an interface circuit 1520. The processor 1510 and the interface circuit 1520 are coupled to each other. It is understood that the interface circuit 1520 can be a transceiver or an input / output interface. Optionally, device 1500 may further include a memory 1530 for storing instructions executed by the processor 1510, or storing input data required by the processor 1510 to execute instructions, or storing data generated after the processor 1510 executes instructions. When device 1500 is used to implement the method described above, the processor 1510 is used to implement the function of the processing unit 1420, and the interface circuit 1520 is used to implement the function of the transceiver unit 1410.

[0441] When device 1500 is a chip applied to the first terminal, the chip implements the functions of the first terminal in the above method embodiments. The chip receives information from other modules (such as radio frequency modules or antennas) in the first terminal, which is sent to the first terminal by other devices; or, the chip sends information to other modules (such as radio frequency modules or antennas) in the first terminal, which is sent to other devices by the first terminal.

[0442] When device 1500 is a chip used in core network equipment, the chip implements the functions of the core network equipment in the above method embodiments. The chip receives information from other modules (such as radio frequency modules or antennas) in the core network equipment, which is sent to the core network equipment by other devices; or, the chip sends information to other modules (such as radio frequency modules or antennas) in the core network equipment, which is sent to other devices by the core network equipment.

[0443] This application also provides a communication device including a processor coupled to a memory for storing computer programs or instructions and / or data. The processor is configured to execute the computer programs or instructions stored in the memory, or to read the data stored in the memory, to perform the methods described in the above-described method embodiments. Optionally, there may be one or more processors. Optionally, the communication device includes a memory. Optionally, there may be one or more memories. Optionally, the memory may be integrated with the processor or may be separately configured.

[0444] This application also provides a computer-readable storage medium having computer instructions stored thereon for implementing the methods executed by a first terminal or core network device in the above-described method embodiments.

[0445] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods performed by a first terminal or core network device in the above-described method embodiments.

[0446] This application also provides a communication system, which includes a first terminal or core network device in the embodiments described above.

[0447] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0448] It is understood that the processor in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0449] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Furthermore, the ASIC can reside in a first terminal or core network device. Alternatively, the processor and storage medium can exist as discrete components in the first terminal or core network device.

[0450] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive.

[0451] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0452] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0453] Unless otherwise stated, all technical and scientific terms used in the embodiments of this application have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in this application is for the purpose of describing specific embodiments only and is not intended to limit the scope of this application. It should be understood that the above are illustrative examples, and the examples above are merely to help those skilled in the art understand the embodiments of this application, and are not intended to limit the embodiments of the application to the specific numerical values ​​or specific scenarios exemplified. Those skilled in the art can obviously make various equivalent modifications or variations based on the examples given above, and such modifications and variations also fall within the scope of the embodiments of this application.

[0454] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for establishing a connection, characterized in that, The method is executed by a first terminal or a chip in the first terminal, the method comprising: The second terminal is discovered through the discovery process of the 3GPP radio access technology under the 3rd Generation Partnership Project, based on the first discovery parameter. The first discovery parameter includes a relay service code (RSC) associated with a first non-3GPP radio access technology, or the first discovery parameter includes the RSC and second information, the second information being used to indicate the first non-3GPP radio access technology. Determine the wireless access technology used for communication with the second terminal; When the wireless access technology is the first non-3GPP wireless access technology, the non-3GPP information of the second terminal is obtained in the first process of the 3GPP wireless access technology. The non-3GPP information is used for the first terminal and the second terminal to establish a connection of the first non-3GPP wireless access technology. The first process includes at least one of the following: the process of the first terminal discovering the second terminal through the discovery process of the 3GPP wireless access technology, or the process of the first terminal and the second terminal establishing a connection of the 3GPP wireless access technology. Based on the first non-3GPP information, establish a connection with the second terminal using the first non-3GPP radio access technology. Wherein, the first terminal is a remote terminal in a relay scenario, and the second terminal is a relay terminal in a relay scenario; or, the first terminal is a relay terminal in a relay scenario, and the second terminal is a remote terminal in a relay scenario.

2. The method according to claim 1, characterized in that, The determination of the wireless access technology used for communication with the second terminal includes: The wireless access technology used for communication with the second terminal is determined by the User Equipment Routing Policy (URSP) or the local policy.

3. The method according to claim 1 or 2, characterized in that, The non-3GPP information includes at least one of the following: device name, hotspot name, or address information.

4. The method according to claim 1 or 2, characterized in that, The first discovery parameter includes RSC, and the method further includes: The system receives third information from a core network device. The third information is used to configure the first discovery parameter for the first terminal. The third information includes indication information, which is used to indicate that the RSC is associated with the first non-3GPP radio access technology.

5. The method according to claim 4, characterized in that, The method further includes: The fourth information is reported to the core network device, which is used to indicate the non-3GPP radio access technology supported by the first terminal.

6. The method according to claim 1 or 2, characterized in that, The step of establishing a connection with the second terminal using the first non-3GPP radio access technology based on the non-3GPP information includes: In response to obtaining the non-3GPP information, the 3GPP module of the first terminal triggers the non-3GPP module of the first terminal to establish a connection with the second terminal using the first non-3GPP radio access technology.

7. The method according to claim 1 or 2, characterized in that, The method further includes: The non-3GPP module of the first terminal sends a fifth message to the 3GPP module of the first terminal. The fifth message is used to notify that the connection of the first non-3GPP radio access technology has been successfully established. The fifth message includes the identifier of the connection of the first non-3GPP radio access technology.

8. The method according to claim 1 or 2, characterized in that, When the first terminal is a remote terminal in the relay scenario, the method further includes: Establish the connection and application association relationship of the first non-3GPP radio access technology; and / or, Establish the association between the connection of the first non-3GPP radio access technology and the connection of the 3GPP radio access technology; The 3GPP radio access technology connection is the connection between the first terminal and the second terminal, and the data of the application and the 3GPP radio access technology connection is carried on the first non-3GPP radio access technology connection.

9. The method according to claim 1 or 2, characterized in that, When the first terminal is a relay terminal in the relay scenario, the method further includes: Establish the association between the connection and PDU session of the first non-3GPP radio access technology; and / or, Establish the association between the connection of the first non-3GPP radio access technology and the connection of the 3GPP radio access technology; The 3GPP radio access technology connection is the connection between the first terminal and the second terminal. The 3GPP radio access technology connection corresponds to the PDU session, and the PDU session is used to carry the data of the first non-3GPP radio access technology connection.

10. The method according to claim 1 or 2, characterized in that, When the first terminal is a relay terminal in the relay scenario, the method further includes: Send at least one of the following information to the core network equipment: sixth information, identifier of the remote user, or information of the second terminal, wherein the sixth information is used to indicate the first non-3GPP radio access technology.

11. The method according to claim 1 or 2, characterized in that, The first non-3GPP radio access technology includes at least one of the following: WiFi, WiFi Direct, Bluetooth, Zigbee, RFID, IrDA, UWB, or NFC; and / or, The 3GPP radio access technologies include at least one of the following: end-to-end D2D, sidelink, or near-field based services ProSe.

12. A communication device, characterized in that, The communication device is a first terminal or a chip in the first terminal, and the communication device includes: A processor for executing a computer program stored in memory to cause the apparatus to perform the method as described in any one of claims 1 to 11.

13. The apparatus according to claim 12, characterized in that, The device also includes the memory.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed on a first terminal or a chip in the first terminal, causes the first terminal or the chip in the first terminal to perform the method as described in any one of claims 1 to 11.

15. A computer program product, characterized in that, The computer program product includes instructions for performing the method as described in any one of claims 1 to 11.

16. A communication system, characterized in that, include: A first terminal, the first terminal being configured to perform the method as described in any one of claims 1 to 11.

17. A communication device, characterized in that, It includes units and / or modules for performing the method as described in any one of claims 1 to 11.

Images