A data transmission method and device, a terminal device, and a network device

Abstract

The embodiment of the application provides a data transmission method and device, a terminal device and a network device, and the method comprises the steps that a first terminal determines a protocol data unit (PDU) session type; and the first terminal transmits data between the first terminal and a second terminal based on a PDU session corresponding to the PDU session type.

Description

Technical Field

[0001] This application relates to the field of mobile communication technology, specifically to a data transmission method and apparatus, terminal equipment, and network equipment. Background Technology

[0002] With the continuous development of fifth-generation (5G) applications, Network Controlled Interactive Services (NCIS) has been introduced into the standards as a new business model for related standardization.

[0003] NCIS services primarily target applications such as Augmented Reality (AR) / Virtual Reality (VR) and gaming, placing high demands on service quality in terms of speed, latency, packet loss rate, and high-speed encoding / decoding. A session established for NCIS services is called an NCIS session. User equipment within the same NCIS session can be considered as forming an NCIS group, similar to a team in a game.

[0004] In the 3rd Generation Partnership Project (3GPP) Release 17, 5G Proximity Services (ProSe) are used for near-field communication. ProSe includes NCIS. An important scenario for ProSe is UE-to-network (U2N) relay. U2N relay involves a relay UE relaying data to a remote UE, enabling the remote UE to communicate with the network.

[0005] In related technologies, there are instances where relay UEs cannot transmit data to the correct Protocol Data Unit (PDU) in a session corresponding to the data of remote UEs, resulting in data transmission failure. Summary of the Invention

[0006] This application provides a data transmission method and apparatus, a terminal device, and a network device.

[0007] The data transmission method provided in this application includes:

[0008] The first terminal determines the PDU session type;

[0009] The first terminal transmits data with the second terminal based on the PDU session corresponding to the PDU session type.

[0010] The data transmission method provided in this application includes:

[0011] The network device configures a first mapping rule for the first terminal; the first mapping rule is used to indicate PDU session parameters; the PDU session type information in the PDU session parameters is used by the first terminal to determine the PDU session type, the PDU session corresponding to the PDU session type is used to transmit data between the first terminal and the second terminal, and the first relay service code (RSC) corresponding to the first mapping rule is the RSC corresponding to the second terminal.

[0012] The data transmission apparatus provided in this application includes:

[0013] The unit is configured to determine the PDU session type;

[0014] The transmission unit is configured to transmit data between itself and the second terminal based on the PDU session corresponding to the PDU session type.

[0015] The data transmission apparatus provided in this application includes:

[0016] The configuration unit is configured to configure a first mapping rule for a first terminal; the first mapping rule is used to indicate PDU session parameters; the PDU session type information in the PDU session parameters is used by the first terminal to determine the PDU session type, the PDU session corresponding to the PDU session type is used to transmit data between the first terminal and the second terminal, and the first RSC corresponding to the first mapping rule is the RSC corresponding to the second terminal.

[0017] The terminal device provided in this application embodiment can be the first terminal in the above scheme. The terminal device includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute the above-described data transmission method.

[0018] The network device provided in this application includes a processor and a memory. The memory stores computer programs, and the processor calls and runs the computer programs stored in the memory to perform the data transmission method described above.

[0019] The chip provided in this application embodiment is used to implement the above-described data transmission method.

[0020] Specifically, the chip includes a processor for retrieving and running a computer program from memory, causing a device equipped with the chip to perform the aforementioned data transmission method.

[0021] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to execute the above-described data transmission method.

[0022] The computer program product provided in this application includes computer program instructions that cause a computer to execute the above-described data transmission method.

[0023] The computer program provided in this application embodiment, when run on a computer, causes the computer to execute the above-described data transmission method.

[0024] Through the above technical solution, the first terminal determines the PDU session type and transmits data between the first terminal and the second terminal based on the PDU session corresponding to the determined PDU session type, ensuring that the first terminal can map the data to be transmitted to the correct PDU session and ensuring the correctness of data transmission. Attached Figure Description

[0025] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0026] Figure 1 This is an optional schematic diagram of an application scenario according to an embodiment of this application;

[0027] Figure 2 This is a schematic diagram of an optional architecture of a 5G communication system according to an embodiment of this application;

[0028] Figure 3 This is a schematic diagram of the optional composition structure of the communication system according to an embodiment of this application;

[0029] Figure 4 This is an optional flowchart illustrating relay discovery in an embodiment of this application;

[0030] Figure 5 This is an optional flowchart illustrating relay discovery in an embodiment of this application;

[0031] Figure 6 This is an optional flowchart illustrating the data transmission method according to an embodiment of this application;

[0032] Figure 7 This is an optional flowchart illustrating the data transmission method according to an embodiment of this application;

[0033] Figure 8 This is an optional flowchart illustrating the data transmission method according to an embodiment of this application;

[0034] Figure 9This is an optional flowchart illustrating the data transmission method according to an embodiment of this application;

[0035] Figure 10 This is an optional flowchart illustrating the data transmission method according to an embodiment of this application;

[0036] Figure 11 This is an optional flowchart illustrating the data transmission method according to an embodiment of this application;

[0037] Figure 12 This is an optional flowchart illustrating the data transmission method according to an embodiment of this application;

[0038] Figure 13 This is an optional flowchart illustrating the data transmission method according to an embodiment of this application;

[0039] Figure 14 This is an optional structural schematic diagram of the data transmission apparatus according to an embodiment of this application;

[0040] Figure 15 This is an optional structural schematic diagram of the data transmission apparatus according to an embodiment of this application;

[0041] Figure 16 This is a schematic diagram of an optional structure of a communication device provided in an embodiment of this application;

[0042] Figure 17 This is an optional structural diagram of the chip according to an embodiment of this application;

[0043] Figure 18 This is a schematic block diagram of a communication system provided in an embodiment of this application. Detailed Implementation

[0044] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0045] Figure 1 This is a schematic diagram of an application scenario according to an embodiment of this application.

[0046] like Figure 1As shown, the communication system 100 may include terminal device 110 (including terminal device 110-1 and terminal device 110-2) and network device 120. Network device 120 can communicate with terminal device 110-1 via an air interface. Multi-service transmission is supported between terminal device 110-1 and network device 120. Terminal device 110-2 communicates with network device 120 through terminal device 110-1, wherein terminal device 110-1 is referred to as a relay UE, and terminal device 110-2 is referred to as a remote UE.

[0047] It should be understood that the embodiments of this application are only illustrated by way of example with communication system 100, but the embodiments of this application are not limited thereto. That is to say, the technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as New Radio (NR) communication system), or future communication systems, etc.

[0048] exist Figure 1 In the communication system 100 shown, network device 120 may be an access network device that communicates with terminal device 110. The access network device can provide communication coverage for a specific geographical area and can communicate with terminal device 110 (e.g., UE) located within that coverage area.

[0049] Network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, a Next Generation Radio Access Network (NG RAN) device, a base station (gNB) in an NR system, a radio controller in a Cloud Radio Access Network (CRAN), or a relay station, access point, vehicle-mounted device, wearable device, hub, switch, bridge, router, or network device in a future evolved Public Land Mobile Network (PLMN), etc.

[0050] Terminal device 110 can be any terminal device, including but not limited to terminal devices that are connected to network device 120 or other terminal devices via wired or wireless connections.

[0051] For example, the terminal device 110 can refer to an access terminal, UE, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment. The access terminal can be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, IoT device, satellite handheld terminal, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a 5G network, or terminal device in a future evolved network, etc.

[0052] Terminal device 110 can be used for device-to-device (D2D) communication.

[0053] The wireless communication system 100 may further include a core network device 130 that communicates with the base station. This core network device 130 may be a 5G core network (5G Core, 5GC) device, such as an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), a User Plane Function (UPF), or a Session Management Function (SMF). Optionally, the core network device 130 may also be an Evolved Packet Core (EPC) device for an LTE network, such as a Session Management Function + Core Packet Gateway (SMF+PGW-C) device. It should be understood that SMF+PGW-C can simultaneously implement the functions of both SMF and PGW-C. During network evolution, the aforementioned core network device may also be called by other names, or new network entities may be formed by dividing the core network functions; this embodiment does not limit this.

[0054] The various functional units in the communication system 100 can also establish connections and communicate with each other through the next generation (NG) interface.

[0055] For example, terminal devices establish an air interface connection with access network devices through the Uu interface for transmitting user plane data and control plane signaling; terminal devices can establish a control plane signaling connection with the AMF through NG interface 1 (N1); access network devices, such as next-generation radio access base stations (gNB), can establish a user plane data connection with the UPF through NG interface 3 (N3); access network devices can establish a control plane signaling connection with the AMF through NG interface 2 (N2); the UPF can establish a control plane signaling connection with the SMF through NG interface 4 (N4); the UPF can interact with the data network for user plane data through NG interface 6 (N6); the AMF can establish a control plane signaling connection with the SMF through NG interface 11 (N11); and the SMF can establish a control plane signaling connection with the PCF through NG interface 7 (N7).

[0056] Figure 1An exemplary embodiment shows a base station, a core network device, and two terminal devices. Optionally, the wireless communication system 100 may include multiple base station devices, and each base station may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.

[0057] It should be noted that, Figure 1 This application merely illustrates the system to which this application applies; of course, the methods shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to those defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems, and this application does not limit this.

[0058] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0059] The network architecture of 5G communication systems, such as Figure 2As shown, it includes: AMF, SMF, Policy Control Function, Authentication Server Function (AUSF), Unified Data Management (UDM), UPF, Network Slice Selection Function (NSSF), and Application Function (AF).

[0060] Furthermore, this network architecture also includes access network equipment ((Radio)Access Network(R)AN), UEs, and data network elements (DN). UEs can connect to the AMF, the (R)AN can also connect to the AMF, and the (R)AN can also connect to the UPF. The UPF can connect to the SMF and DN respectively. The AMF can connect to the SMF, UDM, PCF, NSSF, and AUSF respectively. The SMF connects to the PCF and UDM respectively. The PCF connects to the AF. Both the AMF and SMF can obtain data from the UDM, such as user subscription data, and both the AMF and SMF can obtain policy data from the PCF. For example, the PCF element obtains user subscription data from the UDM and sends it to the AMF and SMF, which then distribute it to the (R)AN, UE, and UPF, etc.

[0061] The AMF (Active Mobility Management Entity) is primarily used for terminal device registration, mobility management, and tracking area update processes in mobile networks. The mobility management network element terminates non-access stratum (NAS) messages, completes registration management, connection management, reachability management, allocates tracking area lists (TA lists), and performs mobility management, and transparently routes session management (SM) messages to the session management network element. In 4G communication, the AMF can be replaced by the Mobility Management Entity (MME). In future communication such as 6G communication, the AMF can still be the AMF, or a network element with other names that support mobility management functions; this invention does not limit this.

[0062] SMF (Session Management Function) is primarily used for session management in mobile networks, such as session creation, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting user plane network elements that provide packet forwarding capabilities. In 4G, SMF can be replaced by Packet Data Network Gateway (PGW). In future communications such as 6G, SMF can still be SMF, or other network elements with names that support session management functions; this invention does not limit the specific application of SMF.

[0063] The PCF (Policy and Charging Rules Function) includes user subscription data management, policy control, charging policy control, and QoS control. In 4G, the PCF can be replaced by the policy and charging rules function (PCRF). In future communications such as 6G, the PCF can still be the PCF, or other network elements that support policy control functions; this invention does not limit this.

[0064] The AUSF (Authorized Unified Authentication Server) is primarily used to authenticate service functions and store keys using an Extensible Authentication Protocol (EAP) to achieve user authentication and authorization. In 4G, the AUSF can be replaced by an authentication, authorization, and accounting server (AAA). In future communications such as 6G, the AUSF can still be an AUSF or a network element with other names that support authentication functions; this invention does not limit this.

[0065] UDM is primarily used to store user data, such as subscription information and authentication / authorization information. In 4G, UDM can be replaced by Home Subscriber Server (HSS). In future communications such as 6G, UDM can still be UDM, or other network elements with names that support data management functions; this invention does not limit this.

[0066] UPF (User Plane Function) is primarily used for user plane service processing, such as service routing, packet forwarding, anchoring, QoS mapping and enforcement, uplink identification and routing to the data network, downlink packet buffering and downlink data arrival notification triggering, and connection to external data networks. In 4G, UPF can be replaced by the user plane function of the Packet Data Network Gateway (PGW). In future communications such as 6G, UPF can still be UPF, or other network elements with names that support user plane functions; this invention does not limit this.

[0067] (R)AN is a device that provides wireless communication functions for terminal devices, including but not limited to: next-generation base stations (gnodeB, gNB) in 5G, evolved node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved nodeB, or home node B, HNB), base band unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), mobile switching center, etc.

[0068] A UE (User Equipment) is a wireless transceiver device that can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as on ships); and it can be deployed in the air (such as on airplanes, balloons, and satellites). Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, VR terminals, AR terminals, wireless terminals in industrial control, self-driving, remote medical, smart grids, transportation safety, smart cities, and smart homes, among others.

[0069] DN is mainly used to provide services to users, such as operator services, Internet access services, and third-party services.

[0070] The core network (CN), acting as the bearer network, provides interfaces to the DN, offering communication connectivity, authentication, management, communication, and data service delivery to terminal devices. Figure 2In the network architecture shown, core network functions are divided into user plane functions and control plane functions. User plane functions are mainly responsible for packet forwarding and QoS control. Control plane functions are mainly responsible for user registration and authentication, mobility management, and issuing packet forwarding policies or QoS control policies to the UPF. The control plane functions mainly include AMF and SMF network elements. Specifically, the AMF network element is responsible for the user registration process during access and location management during user movement, as well as paging terminal devices. The SMF network element is responsible for establishing corresponding session connections on the core network side when a user initiates a service, providing specific services to the user. In 5G, CN can be the 5G core network (5GC).

[0071] like Figure 2 As shown, the interfaces and connections in the network architecture can include: Uu, N1, N2, N3, N4, N5, N6, N7, N8, N10, N11, N12, N13, N14, N15, and N22. Among them, Uu is the interface between the terminal device and the RAN; N1 is the control plane interface between the terminal device and the AMF network element, used to transmit control signaling between the user equipment and the core network control plane; specific messages in the N1 connection can be transmitted through the connection between the terminal device and the RAN, or the N2 connection between the RAN and the AMF network element; N2 is the control plane interface between the RAN and the AMF network element; N3 is the interface between the RAN and the user plane function; and N4 is the interface between the SMF network element and the user plane function, used to transmit control signaling between the SMF network element and the user plane function. N5 is the interface between PCF and AF; N6 is the interface between User Plane Function and DN; N7 is the interface between SMF and PCF; N8 is the interface between AMF and UDM; N10 is the interface between UDM and SMF; N11 is the interface between AMF and SMF; N12 is the interface between AUSF and AMF; N13 is the interface between AUSF and UDM; N14 is the interface between AMFs; N15 is the interface between AMF and PCF; and N22 is the interface between NSSF and AMF.

[0072] like Figure 3 As shown, when a UE has both the ability to connect to an external data network via a 5G network and ProSe capability, this UE can act as a relay UE. Another remote UE with ProSe capability can establish a direct connection with the Relay UE through the PC5 interface, and establish a PDU session with the 5G network (including NG-RAN and 5GC) through the Relay UE. The established PDU session is used to interact with the application server (AS) of the external network.

[0073] A PC5 link is established between the remote UE and the relay UE. The relay UE uses a PDU session to relay data between the remote UE and the relay UE. Each PDU session has a type, such as Internet Protocol version 4 (IPv4), IPv6, IPv4v6, Ethernet, or Unstructured. Only data of that type can be transmitted using the corresponding PDU session.

[0074] To enable relay communication, both the RelayUE and the remote UE need to obtain the necessary mapping rules before relay communication can commence. These mapping rules can come from the PCF, the application server, pre-configured on the terminal, or in the Subscriber Identity Module (SIM) card.

[0075] These mapping rules contain mapping relationships between RSC and PDU session parameters. For example: RSC ←→ PDU session type information, Single-Network Slice Selection Assistance Information (S-NSSAI), Data Network Name (DNN), Session and Service Continuity (SSC) mode, etc.

[0076] Before transmitting data, the remote UE needs to discover a suitable relay UE and establish a PC5 connection with it.

[0077] Remote UE discovery and relay UE relay discovery can be performed on remote UEs. Figure 4 The model shown is Model A or Figure 5 Model B is shown.

[0078] like Figure 4 As shown, UE-1 is a relay UE. UE-1 actively broadcasts announcement messages, which carry the RSC (Relay Service Code) that the relay UE can provide relay services. UE-2, UE-3, UE-4, and UE-5 monitor the RSC broadcast by UE-1.

[0079] like Figure 5 As shown, UE-1 is a remote UE. UE-1, as the discoverer, first sends the RSC it needs. UE-2, UE-3, UE-4, and UE-5, as discoverers, monitor the RSC sent by UE-1. UEs that support RSC: UE-2 and UE-3 are relay UEs, and the relay UEs reply to the remote UE.

[0080] After the process is detected, the relay UE and the remote UE establish a PC5 connection.

[0081] In related technologies, the mapping relationship between RSC and PDU session parameters means that each PDU session parameter is optional, so it may not include the PDU session type. If this is the case, the relay UE cannot map the remote UE's data to the correct PDU session, leading to data transmission failure.

[0082] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0083] This application provides a data transmission method, such as... Figure 6 As shown, it includes:

[0084] S601, The first terminal determines the PDU session type.

[0085] S602. The first terminal transmits data with the second terminal based on the PDU session corresponding to the PDU session type.

[0086] Optionally, the second terminal is a remote terminal, and the first terminal is a relay terminal between the remote terminal and the network device. Messages between the second terminal and the network device are relayed through the first terminal.

[0087] Optionally, prior to S601, the first terminal and the second terminal perform relay discovery. The RSC corresponding to the second terminal is the first RSC, and the second terminal can support the first RSC. The first RSC corresponds to the service that the second terminal needs to use. The relay discovery performed by the first terminal and the second terminal can be... Figure 4 Model A shown can also be Figure 5 As shown in Model B, this application embodiment does not impose any limitations on the relay discovery process performed by the first terminal and the second terminal.

[0088] In some embodiments, S601, the first terminal determines the PDU session type, including:

[0089] The first terminal determines the PDU session type based at least on the first mapping rule corresponding to the first RSC, wherein the first RSC is the RSC corresponding to the second terminal.

[0090] The first terminal is configured with at least one mapping rule, and different mapping rules correspond to different RSCs. The types of information included in the PDU session parameters are the same or different for different mapping rules.

[0091] Optionally, the first terminal determines the first RSC corresponding to the second terminal, and determines the first mapping rule based on the first RSC.

[0092] In one example, the mapping rules for the first terminal include: mapping rule A corresponding to RSC1 and mapping rule B corresponding to RSC2. When the first RSC is RSC 1, the first mapping rule is mapping rule A.

[0093] In some embodiments, the first mapping rule is configured by the network device for the first terminal, or pre-configured by the first terminal, or pre-stored by the first terminal.

[0094] Optionally, network devices include: PCF or application server.

[0095] Optionally, the pre-configuration is configured as a first configuration in the terminal.

[0096] Optionally, the pre-stored location can be the SIM card of the first terminal.

[0097] In some embodiments, the first terminal determines the first RSC based on a first message sent by the second terminal.

[0098] Optionally, prior to S601, the first terminal receives a first message sent by the second terminal and determines a first mapping rule based on the first RSC carried in the received first message.

[0099] In some embodiments, the first message includes one of the following:

[0100] Direct connection establishment request; a direct connection establishment request is used by a second terminal to request a first terminal to establish a direct connection.

[0101] Security mode completion message; the security mode completion message is used by the second terminal to indicate to the first terminal that the current security mode has been successfully established.

[0102] In some embodiments, the first mapping rule indicates the correspondence between the first RSC and PDU session parameters.

[0103] The mapping rule indicates the correspondence between RSC and PDU session parameters. Here, the first mapping rule is defined as the correspondence between the first RSC and the PDU session parameters.

[0104] In some embodiments, the PDU session parameters indicated by the first mapping rule are used to determine the PDU session type.

[0105] PDU session parameters include at least one of the following: PDU session type, S-NSSAI, DNN, and SSC mode.

[0106] In this embodiment of the application, the first terminal determines the PDU session type based at least on the first mapping rule corresponding to the first RSC, including:

[0107] Method 1: Determine the PDU session type based on the PDU session type information in the PDU session parameters;

[0108] Method 2: Determine the PDU session type based on at least one of the following information in the PDU session parameters: S-NSSAI, DNN, and SSC mode.

[0109] In the first determination method, the PDU session includes: PDU session type information. At this time, the first terminal determines the PDU session type based at least on the first mapping rule corresponding to the first RSC, including: the first terminal determines the PDU session type based on the PDU session type information.

[0110] Optionally, the PDU session type information in the PDU session parameters is a required parameter.

[0111] Optionally, the PDU session type information in the PDU session parameters is an optional parameter.

[0112] It should be noted that if the PDU session type information in the PDU session parameters is not specified as an optional parameter, it can be understood that the PDU session type information in the PDU session parameters is a required parameter.

[0113] When the PDU session parameters include PDU session type information, the first terminal determines the PDU session type indicated by the PDU session type information.

[0114] In some embodiments, the PDU session type information indicates a PDU session type.

[0115] In some embodiments, the first mapping rule is the same as the second mapping rule, the second mapping rule is the mapping rule of the second terminal, and the second mapping rule corresponds to the first RSC.

[0116] Here, the RSC indicated by the first mapping rule is the same as the RSC indicated by the second mapping rule, which is the first RSC, and the PDU session parameters indicated by the first mapping rule are the same as the PDU session parameters indicated by the second mapping rule; that is, the correspondence indicated by the first mapping rule is the same as the mapping relationship indicated by the second mapping rule.

[0117] The first mapping rule is the mapping rule for the first terminal, and the second mapping rule is the mapping rule for the second terminal.

[0118] Optionally, the configuration method for the first mapping rule is the same as that for the second mapping rule.

[0119] In one example, the first mapping rule is configured by the network device for the first terminal, and the second mapping rule is configured by the network device for the second terminal.

[0120] In one example, the first mapping rule is pre-configured for the first terminal, and the second mapping rule is pre-configured for the second terminal.

[0121] In one example, the first mapping rule is pre-stored on the first terminal, and the second mapping rule is pre-stored on the second terminal.

[0122] Optionally, the configuration methods for the first mapping rule and the second mapping rule are different.

[0123] In one example, the first mapping rule is configured by the network device for the first terminal, and the second mapping rule is pre-configured by the second terminal.

[0124] In one example, the first mapping rule is pre-configured for the first terminal, and the second mapping rule is pre-stored for the second terminal.

[0125] When the first mapping rule is configured for a network device, the first terminal receives the first mapping rule configured for the network device.

[0126] This application also provides a data transmission method, such as... Figure 7 As shown, it includes:

[0127] S701, The network device configures the first mapping rule for the first terminal.

[0128] The first mapping rule is used to indicate PDU session parameters; the PDU session type information in the PDU session parameters is used by the first terminal to determine the PDU session type, the PDU session corresponding to the PDU session type is used to transmit data between the first terminal and the second terminal, and the first RSC corresponding to the first mapping rule is the RSC corresponding to the second terminal.

[0129] In some embodiments, the network device configures the second mapping rule to the second terminal.

[0130] In some embodiments, the PDU session parameters further include at least one of the following:

[0131] S-NSSAI, DNN, and SSC mode.

[0132] In the second determination method, the first terminal determines the PDU session type based at least on the first mapping rule corresponding to the first RSC, including: the first terminal determines the PDU session type based on at least one of the following information in the PDU session parameters: S-NSSAI, DNN and SSC mode.

[0133] Optionally, when the PDU session parameters do not include PDU session type information, the first terminal determines the PDU session type based on the PDU type and at least one of the following: S-NSSAI, DNN, and SSC mode.

[0134] In one example, the first terminal determines the PDU session type based on the PDU type and S-NSSAI.

[0135] In one example, the first terminal determines the PDU session type based on the PDU type, S-NSSAI, DNN, and SSC mode.

[0136] In method two, the methods for obtaining the PDU type include:

[0137] Method 1: The first terminal determines the PDU type based on the first message sent by the second terminal; or,

[0138] Method 2: The first terminal determines the PDU type based on the PDU type used by the upper layer of the first terminal.

[0139] In acquisition method one, the PDU originates from the second terminal. The first terminal receives a first message sent by the second terminal, which indicates the PDU type. Optionally, the PDU type indicated by the first message is a PDU type determined by the second terminal.

[0140] In method two, the PDU originates from the upper layer of the first terminal. This upper layer can be the application layer. The first terminal determines the PDU type based on the PDU type used by the upper layer.

[0141] In practical applications, if the first terminal receives a first message sent by the second terminal and the first message carries a PDU type, then the first terminal uses the PDU type sent by the second terminal. If the first message does not carry a PDU type, then the PDU type used by the upper layer is used.

[0142] In some embodiments, the first message includes one of the following:

[0143] Direct connection establishment request;

[0144] Safe mode completed message.

[0145] In method two, the configuration methods for the first mapping rule and the second mapping rule can be the same or different.

[0146] In one example, the first mapping rule is configured for the network device, and the second mapping rule is pre-stored.

[0147] In one example, the first mapping rule is for network device configuration, and the second mapping rule is for network device configuration.

[0148] Optionally, the PDU session parameters of the first mapping rule include PDU session information, and the PDU session parameters of the second mapping rule also include PDU session information.

[0149] Optionally, the PDU session parameters of the first mapping rule do not include PDU session information, and the PDU session parameters of the second mapping rule do not include PDU session information.

[0150] In some embodiments, prior to S601, the first terminal further performs the following steps:

[0151] The first terminal receives a direct connection establishment request sent by the second terminal; the direct connection request may or may not carry the first RSC.

[0152] At this time, the interaction between the first terminal and the second terminal, such as Figure 8 As shown, it includes:

[0153] S801, The second terminal sends a direct connection establishment request to the first terminal.

[0154] At this time, the first terminal receives a direct connection establishment request sent by the second terminal.

[0155] S802, The first terminal sends a direct connection establishment acceptance message to the second terminal.

[0156] In some embodiments, when the first RSC has no security requirements, the direct connection request carries the first RSC; or when the first RSC has security requirements, the direct connection request does not carry the first RSC.

[0157] In some embodiments, when the direct connection request does not carry the first RSC, the method further includes: the first terminal sending a security mode command request to the second terminal; the first terminal receiving a security mode completion message sent by the second terminal, the security mode completion message carrying the first RSC.

[0158] At this time, the interaction between the first terminal and the second terminal, such as Figure 9 As shown, it includes:

[0159] S901, The second terminal sends a direct connection establishment request to the first terminal.

[0160] At this time, the first terminal receives a direct connection establishment request sent by the second terminal.

[0161] S902, The first terminal sends a security mode command to the second terminal.

[0162] S903, The second terminal sends the security mode to the first terminal.

[0163] S904, The first terminal sends a direct connection establishment acceptance message to the second terminal.

[0164] S902 is used for the first terminal and the second terminal to exchange security parameters.

[0165] The security mode sent in S903 has completed its use and is protected by security parameters.

[0166] In this embodiment of the application, the first message for sending the first RSC and the first message for sending the PDU type can be the same message or different messages.

[0167] In one example, the direct connection establishment request received by the first terminal carries a first RSC and PDU type.

[0168] In one example, the direct connection establishment request received by the first terminal carries a first RSC, and the received security mode completion carries a PDU type.

[0169] In some embodiments, the first terminal establishes the PDU session corresponding to the PDU session type.

[0170] Here, when the first terminal determines the PDU session type and determines that the first terminal has not established a corresponding PDU session, a PDU session corresponding to the PDU session type is established, and the established PDU session is associated with the PC5 connection between the first terminal and the second terminal.

[0171] When the first terminal determines the PDU session type and detects that the first terminal has established a PDU session corresponding to the PDU session type, the PDU session is associated with the PC5 connection between the first terminal and the second terminal.

[0172] In some embodiments, the PDU session type is one of the following: IPv4, IPv6, IPv4v6, Ethernet, Unstructured.

[0173] Taking the PDU session parameters including PDU session type information as an example, if the PDU session type information indicates that the PDU session type is IPv4, then the PDU session type is IPv4; if the PDU session type information indicates that the PDU session type is IPv6, then the PDU session type is IPv6; if the PDU session type information indicates that the PDU session type is IPv4v6, then the PDU session type includes both IPv4 and IPv6.

[0174] In some embodiments, when the PDU session type is IPv4v6, the PDU session includes:

[0175] The first PDU session with PDU session type IPv4 and the second PDU session with PDU session type IPv6.

[0176] In some embodiments, the connection between the first terminal and the second terminal includes:

[0177] The first connection corresponds to IPv4 and the second connection corresponds to IPv6. The first PDU session is used to transmit data for the first connection, and the second PDU session is used to transmit data for the second connection.

[0178] In this embodiment, if the PDU session type information indicates IPv4v6, then it needs to correspond to two PC5 connections, each corresponding to IPv4 and IPv6 respectively. These two PC5 connections exchange the same RSC during connection establishment, but their IP capabilities differ. The first terminal needs to correspond to either an IPv4v6 or IPv4+IPv6 PDU session. If the first terminal does not support IPv4v6, then it corresponds to two sessions: an IPv4 PDU session and an IPv6 PDU session, with the IPv4 PC5 connection corresponding to the IPv4 PDU session and the IPv6 PC5 connection corresponding to the IPv6 PDU session.

[0179] The data transmission method provided in this application embodiment will be further described below, taking the first terminal as a relay UE and the second terminal as a remote UE as an example.

[0180] Example 1

[0181] like Figure 10 and 11 As shown, it includes:

[0182] S1001, Remote UE receives mapping rules related to the terminal-to-network (N2W) relay from the network element.

[0183] The mapping rules include PDU session type.

[0184] S1002, relay: The UE receives the mapping rules related to N2W relay from the network element.

[0185] The mapping rules include PDU session type.

[0186] In S1001 and S1002, the mapping rules received by the remote UE and relay UE from the network element include the mapping relationship between RSC and PDU session parameters. This mapping relationship must contain PDU session type information (PDU sessiontype), which has only one type value. The session type indicated by the PDU session type can be any one of IPv4, IPv6, IPv4v6, Ethernet, or Unstructured.

[0187] Network elements can be PCF, application servers, local terminal configurations, or SIM cards.

[0188] Optionally, the mapping rule can be carried in the proximity policy sent by the network element to the remote UE. This mapping rule can be understood as an RSC-PDU session parameter mapping rule.

[0189] S1003, relay UE and remote UE perform relay discovery.

[0190] The application layer of the remote UE instructs the relay layer to require a certain RSC, and then discovers relay UEs that support that RSC. The relay discovery method can be either Model A or Model B.

[0191] S1004, relay UE and remote UE establish PC5 connection.

[0192] If RSC can be transmitted without security concerns, then signaling without security inclusions can be used, such as Figure 10 As shown, S1004 includes:

[0193] S1041A, The remote UE sends a direct link establishment request to the relay UE.

[0194] The Direct Link Establishment Request includes the relay UE ID. This is because a relay UE can support multiple Relay Controllers (RSCs), hence the inclusion of the RSC in the Direct Link Establishment Request.

[0195] S1042A, relay UE sends a direct connection acceptance to remote UE.

[0196] If there are security concerns with RSC, such as Figure 11 As shown, S1004 includes:

[0197] S1041B, the remote UE sends a Direct link establishment request to the relay UE.

[0198] The Direct link establishment request includes the relay UE ID.

[0199] S1042B, relay UE sends a security mode command to remote UE.

[0200] S1043B, The remote UE sends a "security mode complete" message to the relay UE.

[0201] The remote UE sends an RSC to the relay UE using the security-protected security mode complete.

[0202] S1044B, relay UE sends a direct connection acceptance to remote UE.

[0203] exist Figure 11 In this process, the relay UE and the remote UE obtain security parameters through the interaction of S1042B and S1043B.

[0204] In Example 1, the relay and remote UEs share the same mapping relationship, and each RSC has a corresponding PDUsession type. The relay UE can determine the appropriate PDUsession type for the PC5 connection based on the received RSC and the mapping relationship. For example, if RSC 1 corresponds to IPv4, the relay will look for an IPv4 PDU session to transmit the data for the PC5 connection.

[0205] If the PDU session type corresponding to the RSC is IPv4v6, then the RSC needs to correspond to two PC5 connections, each corresponding to IPv4 and IPv6 respectively. These two PC5 connections exchange the same RSC during connection establishment, but their IP capabilities differ. The relay UE needs to correspond to either an IPv4v6 or IPv4+IPv6 PDU session (if none exists, establish the corresponding PDU session).

[0206] If the PDU session type corresponding to RSC cannot be IPv4v6, then only IPv4 PC5 connections correspond to IPv4 PDU sessions, and IPv6 PC5 connections correspond to IPv6 PDU sessions.

[0207] In Example 1, the Relay UE can definitely find the correct PDU session by using the PDU session type corresponding to the RSC, thus ensuring correct data transmission.

[0208] Example 2

[0209] like Figure 12 and 13 As shown, it includes:

[0210] S1201, The remote UE receives the mapping rules related to the N2W relay from the network element.

[0211] The mapping rules may or may not include the PDU session type.

[0212] S1202, relay: The UE receives the mapping rules related to N2W relay from the network element.

[0213] The mapping rules may or may not include the PDU session type.

[0214] In S1201 and S1202, the mapping rules received by the remote UE and relay UE from the network element include: the mapping relationship between RSC and PDU session parameters. This mapping relationship may or may not include a PDU session type. If it does, the PDU session type has only one type value. The session type indicated by the PDU session type can be any one of IPv4, IPv6, IPv4v6, Ethernet, or Unstructured.

[0215] Network elements can be PCF, application servers, local terminal configurations, or SIM cards.

[0216] Optionally, the mapping rule can be carried in the proximity policy sent by the network element to the remote UE. This mapping rule can be understood as an RSC-PDU session parameter mapping rule.

[0217] S1203, relay UE and remote UE perform relay discovery.

[0218] The application layer of the remote UE instructs the relay layer to require a certain RSC, and then discovers relay UEs that support that RSC. The relay discovery method can be either Model A or Model B.

[0219] S1204, relay UE and remote UE establish PC5 connection.

[0220] If RSC can be transmitted without security concerns, then signaling without security inclusions can be used, such as Figure 12 As shown, S1204 includes:

[0221] S1241A, the remote UE sends a Direct link establishment request to the relay UE.

[0222] The Direct Link Establishment Request includes the relay UE ID. Because a relay UE can support multiple RSCs, the Direct Link Establishment Request includes the RSC. If the RSC does not have a corresponding PDU session type, the PDU type for the PC5 connection can also be included.

[0223] S1242A, relay UE sends a direct connection acceptance to remote UE.

[0224] If there are security concerns with RSC, such as Figure 13 As shown, S1204 includes:

[0225] S1241B, the remote UE sends a Direct link establishment request to the relay UE.

[0226] The Direct link establishment request includes the relay UE ID.

[0227] S1242B, relay UE sends security mode command to remote UE.

[0228] S1243B, The remote UE sends a "security mode complete" message to the relay UE.

[0229] The remote UE sends an RSC to the relay UE using the security-protected security mode complete. If the RSC does not have a corresponding PDU session type, it can also include the PDU type of the PC5 connection.

[0230] S1244B, relay UE sends a direct connection acceptance to remote UE.

[0231] exist Figure 13 In this process, the relay UE and the remote UE obtain security parameters through the interaction of S1242B and S1243B.

[0232] In S1204, if the Relay UE receives a PDU type, it uses that PDU type and RSC to determine the corresponding PDU session type. If it does not receive a PDU type and the RSC does not have a corresponding PDU session type, the Relay UE determines the PDU type of the PC5 connection based on the PDU type used by its upper layer, and then uses that PDU type and RSC to determine the corresponding PDU session type.

[0233] If the PDU type is IPv4, the corresponding PDU session type is IPv4 or IPv4v6; if the PDU type is IPv6, the corresponding PDU session type is IPv6 or IPv4v6.

[0234] In Example 2, the Relay UE determines the PDU type corresponding to the PC5 connection and then uses the RSC to find the correct PDU session, thereby ensuring correct data transmission.

[0235] The preferred embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solutions of this application, and these simple modifications all fall within the protection scope of this application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately. Furthermore, various different embodiments of this application can also be arbitrarily combined, as long as they do not violate the spirit of this application, they should also be considered as the content disclosed in this application. Moreover, without conflict, the various embodiments and / or the technical features in the various embodiments described in this application can be arbitrarily combined with the prior art, and the resulting technical solutions should also fall within the protection scope of this application.

[0236] It should also be understood that in the various method embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. Furthermore, in the embodiments of this application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data. "Downlink" indicates that the transmission direction of signals or data is a first direction from the site to the user equipment in the cell; "uplink" indicates that the transmission direction of signals or data is a second direction from the user equipment in the cell to the site; and "sidelink" indicates that the transmission direction of signals or data is a third direction from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. Additionally, in the embodiments of this application, the term "and / or" is merely a description of the association relationship between related objects, indicating that three relationships can exist. Specifically, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0237] This application embodiment also provides a data transmission device 1400, such as... Figure 14 As shown, it is applied to the first terminal and includes:

[0238] Unit 1401 is configured to determine the PDU session type;

[0239] The transmission unit 1402 is configured to transmit data between itself and the second terminal based on the PDU session corresponding to the PDU session type.

[0240] In some embodiments, the determining unit 1401 is further configured to determine the PDU session type based at least on a first mapping rule corresponding to a first relay service code (RSC), wherein the first RSC is the RSC corresponding to the second terminal.

[0241] In some embodiments, the first mapping rule is configured by the network device for the first terminal, or pre-configured by the first terminal, or pre-stored by the first terminal.

[0242] In some embodiments, the determining unit 1401 is further configured to determine the first RSC based on the first message sent by the second terminal.

[0243] In some embodiments, the first mapping rule indicates the correspondence between the first RSC and PDU session parameters.

[0244] In some embodiments, the PDU session parameters indicated by the first mapping rule are used to determine the PDU session type.

[0245] In some embodiments, the determining unit 1401 is further configured to determine the PDU session type based on the PDU session type information included in the PDU session parameters.

[0246] In some embodiments, the PDU session type information indicates a PDU session type.

[0247] In some embodiments, the first mapping rule is the same as the second mapping rule, the second mapping rule is the mapping rule of the second terminal, and the second mapping rule corresponds to the first RSC.

[0248] In some embodiments, the first mapping rule is configured by the network device for the first terminal; the second mapping rule is configured by the network device for the second terminal.

[0249] In some embodiments, the determining unit 1401 is further configured to determine the PDU session type based on at least one of the following information: S-NSSAI, DNN, and SSC mode, and the PDU session parameters.

[0250] In some embodiments, the device 1400 further includes:

[0251] The sending unit is configured to determine the PDU type based on a first message sent by the second terminal; or,

[0252] The type determination unit is configured to determine the PDU type based on the PDU type used by the upper layer of the first terminal.

[0253] In some embodiments, the first message includes one of the following:

[0254] Direct connection establishment request;

[0255] Safe mode completed message.

[0256] In some embodiments, the device 1400 further includes:

[0257] The receiving unit is configured to receive a direct connection establishment request sent by the second terminal; the direct connection request may or may not carry the first RSC.

[0258] In some embodiments, when the first RSC has no security requirements, the direct connection request carries the first RSC; or when the first RSC has security requirements, the direct connection request does not carry the first RSC.

[0259] In some embodiments, the device 1400 further includes:

[0260] The sending unit is configured to send a security mode command request to the second terminal;

[0261] The receiving unit is further configured to receive a security mode completion message sent by the second terminal, wherein the security mode completion message carries the first RSC.

[0262] In some embodiments, the apparatus 1400 further includes: an establishment unit configured to establish the PDU session corresponding to the PDU session type.

[0263] In some embodiments, the PDU session type is one of the following: Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), IPv4v6, Ethernet, or Unstructured.

[0264] In some embodiments, when the PDU session type is IPv4v6, the PDU session includes:

[0265] The first PDU session with PDU session type IPv4 and the second PDU session with PDU session type IPv6.

[0266] In some embodiments, the connection between the first terminal and the second terminal includes:

[0267] The first connection corresponds to IPv4 and the second connection corresponds to IPv6. The first PDU session is used to transmit data for the first connection, and the second PDU session is used to transmit data for the second connection.

[0268] This application also provides a data transmission device, applied to network devices, such as... Figure 15 As shown, it includes:

[0269] Configuration unit 1501 is configured to configure a first mapping rule to a first terminal; the first mapping rule is used to indicate PDU session parameters, the PDU session type information in the PDU session parameters is used by the first terminal to determine the PDU session type, the PDU session corresponding to the PDU session type is used to transmit data between the first terminal and the second terminal, and the first RSC corresponding to the first mapping rule is the RSC corresponding to the second terminal.

[0270] In some embodiments, the first mapping rule indicates the correspondence between the first RSC and PDU session parameters.

[0271] In some embodiments, the PDU session type information indicates a PDU session type.

[0272] In some embodiments, the first mapping rule is the same as the second mapping rule, the second mapping rule is the mapping rule of the second terminal, and the second mapping rule corresponds to the first RSC.

[0273] In some embodiments, the configuration unit 1501 is further configured to configure the second mapping rule to the second terminal.

[0274] In some embodiments, the PDU session parameters further include at least one of the following:

[0275] Single network slice selection auxiliary information S-NSSAI, data network name DNN, and session and service continuity mode SSC mode.

[0276] In some embodiments, the PDU session type includes one of the following: Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), IPv4v6, Ethernet, and Unstructured.

[0277] In some embodiments, when the PDU session type is IPv4v6, the PDU session includes:

[0278] The first PDU session with PDU session type IPv4 and the second PDU session with PDU session type IPv6.

[0279] In some embodiments, the connection between the first terminal and the second terminal includes:

[0280] The first PDU session corresponds to an IPv4 connection, and the second PDU session corresponds to an IPv6 connection. The first PDU session is used to transmit data for the first connection, and the second PDU session is used to transmit data for the second connection.

[0281] Those skilled in the art should understand that the description of the data transmission device in the embodiments of this application can be understood with reference to the description of the data transmission method in the embodiments of this application.

[0282] Figure 16 This is a schematic structural diagram of a communication device 1600 provided in an embodiment of this application. This communication device can be a terminal device or a network device. Figure 16 The communication device 1600 shown includes a processor 1610, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0283] Optionally, such as Figure 16 As shown, the communication device 1600 may further include a memory 1620. The processor 1610 can retrieve and run computer programs from the memory 1620 to implement the methods described in this embodiment.

[0284] The memory 1620 can be a separate device independent of the processor 1610, or it can be integrated into the processor 1610.

[0285] Optionally, such as Figure 16 As shown, the communication device 1600 may also include a transceiver 1630, and the processor 1610 may control the transceiver 1630 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0286] The transceiver 1630 may include a transmitter and a receiver. The transceiver 1630 may further include an antenna, and the number of antennas may be one or more.

[0287] Optionally, the communication device 1600 may specifically be a network device in the embodiments of this application, and the communication device 1600 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0288] Optionally, the communication device 1600 may specifically be a mobile terminal / terminal device in the embodiments of this application, and the communication device 1600 may implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0289] Figure 17 This is a schematic structural diagram of the chip according to an embodiment of this application. Figure 17 The chip 1700 shown includes a processor 1710, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0290] Optionally, such as Figure 17 As shown, chip 1700 may further include memory 1720. Processor 1710 can retrieve and run computer programs from memory 1720 to implement the methods described in this embodiment.

[0291] The memory 1720 can be a separate device independent of the processor 1710, or it can be integrated into the processor 1710.

[0292] Optionally, the chip 1700 may also include an input interface 1730. The processor 1710 can control the input interface 1730 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0293] Optionally, the chip 1700 may also include an output interface 1740. The processor 1710 can control the output interface 1740 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0294] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0295] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0296] Figure 18 This is a schematic block diagram of a communication system 1800 provided in an embodiment of this application. Figure 18 As shown, the communication system 1800 includes a terminal device 1810 and a network device 1820.

[0297] Specifically, the terminal device 1810 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1820 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, further details are omitted here.

[0298] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0299] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0300] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0301] This application also provides a computer-readable storage medium for storing computer programs.

[0302] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0303] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0304] This application also provides a computer program product, including computer program instructions.

[0305] Optionally, the computer program product can be applied to the network device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0306] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0307] This application also provides a computer program.

[0308] Optionally, the computer program can be applied to the network device in the embodiments of this application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0309] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0310] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0311] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0312] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0313] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0314] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0315] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0316] 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 data transmission method, the method comprising: The first terminal receives a direct connection establishment request sent by the second terminal, wherein the direct connection establishment request carries a first relay service code (RSC). The first terminal determines the Protocol Data Unit (PDU) session type based at least on the first mapping rule corresponding to the first RSC, where the first RSC is the RSC sent by the second terminal. The first terminal relays data between the network device and the second terminal based on the PDU session corresponding to the PDU session type. The first mapping rule is pre-stored by the first terminal. The first mapping rule indicates the correspondence between the first RSC and the PDU session parameters. The PDU session parameters include: PDU session type information, wherein the first terminal determines the PDU session type based at least on the first mapping rule corresponding to the first RSC, including: The first terminal determines the PDU session type based on the PDU session type information; The PDU session type is one of the following: Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), IPv4v6, Ethernet, or Unstructured. Wherein, the first terminal determines the PDU session type based at least on the first mapping rule corresponding to the first RSC, including: The first terminal determines the PDU session type based on at least one of the following information and the PDU session parameters: Single Network Slice Selection Auxiliary Information (S-NSSAI), Data Network Name (DNN), and Session and Service Continuity Mode (SSCmode).

2. The method according to claim 1, wherein, The method further includes: The first terminal determines the first RSC based on the first message sent by the second terminal. The first message includes: the direct connection establishment request.

3. The method according to claim 1, wherein, The PDU session parameters indicated by the first mapping rule are used to determine the PDU session type.

4. The method according to claim 1, wherein, The PDU session type information indicates a PDU session type.

5. The method according to claim 1, wherein, The first mapping rule is the same as the second mapping rule, which is the mapping rule for the second terminal and corresponds to the first RSC.

6. The method according to claim 5, wherein, The first mapping rule is configured by the network device for the first terminal; the second mapping rule is configured by the network device for the second terminal.

7. The method according to claim 1, wherein, The method further includes: The first terminal determines the PDU type based on the first message sent by the second terminal; or, The first terminal determines the PDU type based on the PDU type used by the upper layer of the first terminal. The first message includes: the direct connection establishment request.

8. The method according to claim 2, wherein, The first message also includes: Safe mode completed message.

9. The method according to claim 7, wherein, The first message also includes: Safe mode completed message.

10. The method according to any one of claims 1 to 9, wherein, The method further includes: The first terminal establishes the PDU session corresponding to the PDU session type.

11. The method according to claim 1, wherein, When the PDU session type is IPv4v6, the PDU session includes: The first PDU session with PDU session type IPv4 and the second PDU session with PDU session type IPv6.

12. The method according to claim 11, wherein, The connection between the first terminal and the second terminal includes: The first connection corresponds to IPv4 and the second connection corresponds to IPv6. The first PDU session is used to transmit data for the first connection, and the second PDU session is used to transmit data for the second connection.

13. An information processing method, the method comprising: The network device configures the first mapping rule to the first terminal; The first mapping rule is used to indicate Protocol Data Unit (PDU) session parameters. The PDU session type information in the PDU session parameters is used by the first terminal to determine the PDU session type. The PDU session corresponding to the PDU session type is used to relay data between the first terminal and the second terminal. The first relay service code (RSC) corresponding to the first mapping rule is the RSC sent by the second terminal. The first RSC is carried in the direct connection establishment request sent by the second terminal to the first terminal. The first mapping rule indicates the correspondence between the first RSC and the PDU session parameters. The PDU session type is one of the following: Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), IPv4v6, Ethernet, or Unstructured. The PDU session parameters also include at least one of the following: Single network slice selection auxiliary information S-NSSAI, data network name DNN, and session and service continuity mode SSCmode.

14. The method according to claim 13, wherein, The PDU session type information indicates a PDU session type.

15. The method according to claim 13, wherein, The first mapping rule is the same as the second mapping rule, which is the mapping rule for the second terminal and corresponds to the first RSC.

16. The method according to claim 15, wherein, The method further includes: The network device configures the second mapping rule to the second terminal.

17. The method according to claim 13, wherein, When the PDU session type is IPv4v6, the PDU session includes: The first PDU session with PDU session type IPv4 and the second PDU session with PDU session type IPv6.

18. The method according to claim 17, wherein, The connection between the first terminal and the second terminal includes: The first connection corresponds to IPv4 and the second connection corresponds to IPv6. The first PDU session is used to transmit data for the first connection, and the second PDU session is used to transmit data for the second connection.

19. A data transmission apparatus, comprising: The receiving unit is configured to receive a direct connection establishment request sent by a second terminal, wherein the direct connection establishment request carries a first relay service code (RSC). The determining unit is configured to determine the protocol data unit (PDU) session type based at least on the first mapping rule corresponding to the first RSC, wherein the first RSC is the RSC sent by the second terminal; The transmission unit is configured to relay data between the network device and the second terminal based on the PDU session corresponding to the PDU session type. The first mapping rule is pre-stored by the first terminal. The first mapping rule indicates the correspondence between the first RSC and the PDU session parameters. The PDU session parameters include: PDU session type information, wherein the first terminal determines the PDU session type based at least on the first mapping rule corresponding to the first RSC, including: The first terminal determines the PDU session type based on the PDU session type information; The PDU session type is one of the following: Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), IPv4v6, Ethernet, or Unstructured. Wherein, the first terminal determines the PDU session type based at least on the first mapping rule corresponding to the first RSC, including: The first terminal determines the PDU session type based on at least one of the following information and the PDU session parameters: Single Network Slice Selection Auxiliary Information (S-NSSAI), Data Network Name (DNN), and Session and Service Continuity Mode (SSCmode).

20. A data transmission apparatus, comprising: The configuration unit is configured to configure the first mapping rule to the first terminal; The first mapping rule is used to indicate the session parameters of the Protocol Data Unit (PDU); The PDU session type information in the PDU session parameters is used by the first terminal to determine the PDU session type. The PDU session corresponding to the PDU session type is used to relay data between the first terminal and the second terminal. The first relay service code (RSC) corresponding to the first mapping rule is the RSC sent by the second terminal. The first RSC is carried in the direct connection establishment request sent by the second terminal to the first terminal. The first mapping rule indicates the correspondence between the first RSC and the PDU session parameters. The PDU session type is one of the following: Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), IPv4v6, Ethernet, or Unstructured. The PDU session parameters also include at least one of the following: Single network slice selection auxiliary information S-NSSAI, data network name DNN, and session and service continuity mode SSCmode.

21. A terminal device, comprising: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 12.

22. A network device, comprising: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 13 to 18.

23. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 12.

24. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 13 to 18.

25. A computer-readable storage medium for storing a computer program that causes a computer to perform the method as claimed in any one of claims 1 to 12.

26. A computer-readable storage medium for storing a computer program that causes a computer to perform the method as claimed in any one of claims 13 to 18.

Images