WO2021056573A1 - 建立会话的方法和终端设备 - Google Patents

建立会话的方法和终端设备 Download PDF

Info

Publication number
WO2021056573A1
WO2021056573A1 PCT/CN2019/109217 CN2019109217W WO2021056573A1 WO 2021056573 A1 WO2021056573 A1 WO 2021056573A1 CN 2019109217 W CN2019109217 W CN 2019109217W WO 2021056573 A1 WO2021056573 A1 WO 2021056573A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
pdu session
relay terminal
message
remote terminal
Prior art date
Application number
PCT/CN2019/109217
Other languages
English (en)
French (fr)
Inventor
杨皓睿
***
卢前溪
Original Assignee
Oppo广东移动通信有限公司
Oppo广东移动通信有限公司深圳分公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司, Oppo广东移动通信有限公司深圳分公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2019/109217 priority Critical patent/WO2021056573A1/zh
Priority to CN201980095066.4A priority patent/CN113678506B/zh
Publication of WO2021056573A1 publication Critical patent/WO2021056573A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding

Definitions

  • This application relates to the field of communications, and in particular to a method and terminal device for establishing a session.
  • the 3rd Generation Partnership Project 3rd Generation Partnership Project, 3GPP
  • 3rd Generation Partnership Project 3rd Generation Partnership Project
  • 3GPP 3rd Generation Partnership Project
  • the remote terminal device may have multiple data of different services that need to be relayed by the relay terminal device, and the data of different services needs to use the correct packet data unit (PDU) session (session) for transmission to ensure the normal operation of the service.
  • PDU packet data unit
  • the embodiment of the present application provides a method and terminal device for establishing a session, so that the relay terminal device can correspond to the data of the remote terminal device to a correct PDU session.
  • a method for establishing a session includes: a relay terminal device receives a first message sent by a remote terminal device, the first message includes the remote terminal device requesting the relay Characteristic parameters of the PDU session of the packet data unit used by the terminal device;
  • the relay terminal device uses an established PDU session or establishes a new PDU session based on the characteristic parameter.
  • a method for establishing a session includes: a remote terminal device sends a first message to a relay terminal device, the first message including the remote terminal device requesting the relay terminal The characteristic parameter of the packet data unit PDU session used by the device.
  • a terminal device which is used to execute the method in the above-mentioned first aspect or each of its implementation manners.
  • the terminal device includes a functional module for executing the method in the foregoing first aspect or each of its implementation manners.
  • a terminal device which is used to execute the method in the above second aspect or each of its implementation manners.
  • the network device includes a functional module for executing the method in the above-mentioned second aspect or each of its implementation manners.
  • a terminal device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned first aspect or each of its implementation manners.
  • a terminal device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned second aspect or each implementation manner thereof.
  • a device for implementing any one of the above-mentioned first aspect to the second aspect or the method in each of its implementation manners.
  • the device includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the device executes any one of the above-mentioned first aspect to the second aspect or any of the implementations thereof method.
  • the device is a chip.
  • a computer-readable storage medium for storing a computer program that enables a computer to execute any one of the above-mentioned first to second aspects or the method in each implementation manner thereof.
  • a computer program product including computer program instructions that cause a computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.
  • a computer program which when running on a computer, causes the computer to execute any one of the above-mentioned first to second aspects or the method in each of its implementation manners.
  • the relay terminal device when the remote terminal device has business data that needs to be relayed by the relay terminal device, the relay terminal device can use the established PDU session or establish a new PDU session according to the characteristic parameters of the PDU session sent by the remote terminal device, thereby The relay terminal device can correspond the data of the remote terminal device to the correct PDU session according to the business.
  • Fig. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application.
  • Fig. 2 is a schematic diagram of a relay communication system architecture according to an embodiment of the present application.
  • Fig. 3 is a schematic flowchart of a method for establishing a session according to an embodiment of the present application.
  • Fig. 4 is a schematic flowchart of a method for establishing a session according to an embodiment of the present application.
  • Fig. 5 is a schematic flowchart of another method for establishing a session according to an embodiment of the present application.
  • Fig. 6 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • Fig. 7 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • Fig. 8 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • Fig. 9 is a schematic block diagram of a device according to an embodiment of the present application.
  • Fig. 10 is a schematic diagram of a communication system according to an embodiment of the present application.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System of Mobile Communication
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • UMTS Universal Mobile Telecommunication System
  • UMTS Universal Mobile Telecommunication System
  • NCIS Network Controlled Interactive Services
  • the NCIS business is mainly aimed at applications such as Augmented Reality (AR)/Virtual Reality (VR), games, etc. It has high requirements for service quality such as speed, delay, packet loss rate, and high-speed codec. For example: For VR games, the rate of 10Gbps needs to be reached, and the packet loss rate cannot exceed 10E-4.
  • the session established for the NCIS service is an NCIS session, and terminal devices in the same NCIS session can be considered to form a service application group, for example, teaming in a game.
  • the terminal devices in the NCIS group have the following possible communication methods, which can be used in combination:
  • the terminal devices in the group can come from the same public land mobile network (Public Land Mobile Network, PLMN) or from different PLMNs.
  • PLMN Public Land Mobile Network
  • FIG. 1 of the embodiment of the present application is a communication architecture diagram of a 5G system.
  • the communication system may include access and mobility management functions (Access and Mobility Management Function, AMF), session management functions (Session Management Function, SMF), policy control functions (Policy Control Function, PCF), Application layer function (Application Function, AF), terminal equipment (User Equipment, UE), access network (Access Network, AN or Radio Access Network, RAN), user plane function (User Plane Function, UPF), data network (Data Network, DN), Network Slice Selection Function (NSSF), Authentication Server Function (AUSF), and Unified Data Management (UDM).
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • Policy Control Function Policy Control Function
  • PCF Policy Control Function
  • Application layer function Application Function
  • AF Application Function
  • UPF User Plane Function
  • UPF data network
  • Data Network Data Network
  • DN Network Slice Selection Function
  • AUSF Authentication Server Function
  • UDM Unified Data Management
  • AMF is responsible for mobility management and is connected to terminal equipment and RAN
  • SMF is responsible for session management, connected to UPF or UDM
  • PCF is responsible for policy control, and can be connected to SMF, AF, and AMF
  • UDM is responsible for contract data management.
  • N1 is the interface between the terminal device and AMF
  • N2 is the interface between AMF and AN or RAN
  • N3 is the interface between AN or RAN and UPF
  • N4 is the interface between SMF and UPF
  • N5 is the interface between PCF and AF
  • N6 is the interface between UPF and DN
  • N7 is the interface between SMF and PCF
  • N8 is the interface between AMF and UDM
  • N9 is the interface between UPF
  • 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.
  • N14 is the interface between AMF
  • N15 is the interface between AMF and PCF
  • N22 is the interface between NSSF and AMF
  • Uu interface is the interface between UE and AN or RAN.
  • the remote terminal device (ie terminal device A) can be communicated through relay.
  • the communication architecture diagram is as shown in Figure 2 of the embodiment of this application. Show. In Figure 2, the relay terminal device is within the coverage area relative to the network device, and the remote terminal device is outside the coverage area. The remote terminal device communicates with the network device through the relay terminal device.
  • the relay terminal device can be connected to the network device through the Uu interface.
  • the Evolved Packet Core (EPC) is connected to the public safety application server (AS) through the SGi interface.
  • AS public safety application server
  • the network device in the communication architecture shown in FIG. 1 and FIG. 2 may be a device that communicates with a terminal device (or called a communication terminal or a terminal).
  • the network device can provide communication coverage for a specific geographic area, and can communicate with terminal devices located in the coverage area.
  • the network equipment may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station ( Evolutional Node B, eNB or eNodeB), or a wireless controller in Cloud Radio Access Network (CRAN), or the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, or a wireless controller in a cloud radio access network (CRAN).
  • the terminal devices in the communication architecture shown in Figures 1 and 2 may include but are not limited to being connected via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL) , Digital cable, direct cable connection; and/or another data connection/network; and/or via wireless interface, such as for cellular network, wireless local area network (WLAN), digital TV such as DVB-H network Network, satellite network, AM-FM broadcast transmitter; and/or another terminal device that is set to receive/send communication signals; and/or Internet of Things (IoT) equipment.
  • a terminal device set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal” or a "mobile terminal".
  • Examples of mobile terminals include, but are not limited to, satellite or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio telephone transceivers Electronic device.
  • Terminal equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile equipment, user terminals, terminals, wireless communication equipment, user agents, or User device.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in the future evolution of PLMN, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the main process of communication between the remote terminal device and the relay terminal device may be: after the relay terminal device is registered to the core network, it discovers each other with the remote terminal device and establishes a PC5 connection. While establishing a connection between the relay terminal device and the remote terminal device, in order to transmit the relay data of the remote terminal device, the relay terminal device may request the network device to establish a Packet Data Network (PDN) connection. Among them, which PDN connection is used to transmit the relay data is determined by the relay terminal device. In general, the relay terminal device can use all relay data for a dedicated PDN connection for transmission. If the communication address between the relay terminal device and the remote terminal device is an Internet Protocol (IP) address, the relay terminal device can also assign an IP address to the remote terminal device. After that, the relay terminal device and the remote terminal device can perform Business transmission.
  • IP Internet Protocol
  • each PDU session is related to the data network name (Data Network Name, DNN) and the Single-Network Slice Selection Assistance Information (S-NSSAI), which means that each PDU Conversation and business related.
  • the remote terminal device may have multiple data of different services that need to be relayed by the relay terminal device. The data of different services needs to be transmitted using the correct PDU session to ensure the normal operation of the service.
  • how the relay terminal device corresponds to the data of the remote terminal device to the correct PDU session has not yet been clearly defined.
  • the embodiment of the present application provides a method for establishing a session, so that the relay terminal device can map the data of the remote terminal device to the correct PDU session.
  • FIG. 3 of the embodiment of the present application is a schematic flowchart of a method 100 for establishing a session. As shown in FIG. 3, the method 100 may include at least part of the following content.
  • the remote terminal device sends a first message to the relay terminal device, where the first message includes the characteristic parameter of the PDU session that the remote terminal device requests the relay terminal device to use.
  • the relay terminal device receives the first message sent by the remote terminal device
  • the relay terminal device uses an established PDU session or establishes a new PDU session based on characteristic parameters.
  • the characteristic parameter may include a routing descriptor (Route Selecting Descriptor, RSD) and/or a traffic descriptor (Traffic Descriptor).
  • RSD routing descriptor
  • Traffic Descriptor Traffic Descriptor
  • the embodiments of the present application refer to the RSD and TrafficDescriptor in the characteristic parameters as the target RSD and the target TrafficDescriptor, respectively. If the remote terminal device has the data of the first service and needs to be relayed by the relay terminal device, the characteristic parameter is the characteristic parameter of the PDU session used to transmit the data of the first service.
  • the first service may be the NCIS service mentioned above, or the first service may also be Ultra Reliable Low Latency Communication (URLLC) service, Industrial Internet (Industrial Interest of Things, IIoT) business, Time Sensitive Network (TSN) business), vertical industry business, etc.
  • URLLC Ultra Reliable Low Latency Communication
  • Industrial Internet Industrial Interest of Things, IIoT
  • TSN Time Sensitive Network
  • the user equipment routing policy may include at least one URSP rule, that is, the URSP may include URSP rule 1, ..., URSP rule n, where n is a positive integer.
  • a URSP rule can include at least one of the priority of the URSP rule, Traffic Descriptor, RSD list, etc.
  • Each Traffic Descriptor can correspond to one or more RSD lists, which are used by the terminal device to select which parameters in the RSD list to determine Traffic Descriptor The binding relationship between the corresponding application and the session, or used to determine what PDU session the terminal device needs to establish to satisfy this binding relationship.
  • the URSP may be data sent by the network device to the terminal device for the terminal device to match the application data according to the policy.
  • the terminal device can select a route for the application according to at least one URSP rule, that is, bind different applications to sessions with different attribute parameters for data transmission.
  • an 8-bit RSD list may include at least one of the following parameters:
  • Session and service continuity (SSC) mode 0 0 0 0 0 0 0 0 1 Session and service continuity (SSC) mode
  • Preferred access type Preferred access type
  • Non-seamless non-3GPP offload indication type (Non-seamless non-3GPP offload indication type)
  • the TrafficDescriptor in URSP can be used to describe a specific service, that is, to match the service.
  • the microblog business can be described by IP@1 ⁇ 9.
  • the 8-bit TrafficDescriptor may include at least one of the following parameters:
  • OS Operating System
  • APP Application, APP
  • OS Id+OS AppId type OS Id+OS AppId type
  • IPv4 remote address type IPv4 remote address type
  • IPv6 remote address or prefix length type IPv6 remote address/prefix length type
  • Protocol identifier/next header type Protocol identifier/next header type
  • Remote port range type (Remote port range type)
  • MAC address type Destination Media Access Control (MAC) address type (Destination MAC address type)
  • OS App ID type OS App ID type
  • each RSD can correspond to one or more parameter combinations, and each parameter combination constitutes a set of PDU session characteristics.
  • the service data corresponding to Traffic Descriptor can be transmitted in the PDU session corresponding to a certain parameter combination of the RSD.
  • the terminal device can select a parameter combination according to the component value in the corresponding RSD, and use the parameter combination to initiate a PDU session establishment request to the network device.
  • the remote terminal device when it sends the first message to the relay terminal device, it may use a D2D connection or a PC5 connection establishment request message to send.
  • the remote terminal device may send the first message to the relay terminal device through new signaling.
  • the remote terminal device may determine the characteristic parameter based on the first service and the local configuration (Local Configuration) or URSP of the remote terminal device.
  • the characteristic parameters include target RSD and target Traffic Descriptor.
  • the local configuration of the remote terminal device may be pre-configured on the remote terminal device, and the local configuration of the remote terminal device may include RSD and Traffic Descriptor.
  • the remote terminal device can use the URSP rule in the URSP to check whether the first service matches the Traffic Descriptor of a certain rule in the URSP rule.
  • the Traffic Descriptor in the URSP rule is the target Traffic Descriptor.
  • the remote terminal device may determine the target RSD in at least one RSD corresponding to the target Traffic Descriptor.
  • remote terminal device uses the URSP rule to check whether the first service matches the Traffic Descriptor of a certain rule in the URSP rule
  • the embodiment of the present application does not limit the viewing order.
  • remote terminal devices can be viewed randomly, or can be viewed in the order of the TrafficDescriptor priority in the URSP rule.
  • the remote may send the determined target RSD and target TrafficDescriptor to the relay terminal device, requesting the relay terminal device to send the target RSD and target TrafficDescriptor data representing the first service.
  • the relay terminal device After the relay terminal device receives the target RSD and target TrafficDescriptor, it can perform the following actions according to the target RSD and target TrafficDescriptor:
  • the relay terminal device judges whether there is a PDU session that meets the target RSD and the target Traffic Descriptor in the current at least one PDU session. If there is a PDU session that meets the target RSD and the target Traffic Descriptor (for the convenience of description, it is called the first PDU session). ), the relay terminal device can use the first PDU session to transmit the data of the first service.
  • the first PDU session satisfies the target RSD and the target TrafficDescriptor can be understood as: the service transmitted by the first PDU session is the same as the first service, and the RSD corresponding to the first PDU session is the same as the target RSD or includes the target RSD.
  • the relay terminal device When the relay terminal device judges whether there is a PDU session that meets the target RSD in at least one existing PDU session, the relay terminal device can compare the RSD corresponding to the existing at least one PDU session with the target RSD, and determine whether the existing at least one PDU session is at least Whether the RSD corresponding to the PDU session is the same as the target RSD or contains the target RSD in a PDU session.
  • the relay terminal device can use the target RSD to establish a new PDU session.
  • the relay terminal device may match the configured TrafficDescriptor of the relay terminal device with the target TrafficDescriptor (referred to as the second TrafficDescriptor for the convenience of description), and the RSD corresponding to the second TrafficDescriptor is the second RSD. .
  • the second RSD and the second Traffic Descriptor may be included in the URSP of the relay terminal device.
  • the second RSD and the second Traffic Descriptor may be included in the local configuration of the relay terminal device.
  • the relay terminal device may establish a new PDU session based on the second RSD corresponding to the second Traffic Descriptor that is successfully matched.
  • the relay terminal device may compare the second RSD with the target RSD, and then, the relay terminal device may establish a new PDU session based on the first RSD.
  • the first RSD corresponds to the first Traffic Descriptor that is successfully matched, and the first RSD includes the target RSD or has the largest intersection with the target RSD.
  • the relay terminal device can match its own URSP according to the target TrafficDescriptor. If there is a matching URSP rule, the relay terminal device can use the RSD in the successfully matched URSP rule to compare with the target RSD. After that, the relay terminal device can establish a new PDU session based on the first RSD. Wherein, the successfully matched URSP rule includes the first RSD, and the first RSD includes the target RSD.
  • the relay terminal device may also associate the second address with the first address and/or the PDU session ID.
  • the first address is the address corresponding to the established PDU session used by the relay terminal device or the address corresponding to the new PDU session established for the relay terminal device
  • the second address is the address for communication between the relay terminal device and the remote terminal device.
  • the second address may be an address assigned to the D2D connection between the relay terminal device and the remote terminal device.
  • the relay terminal device when the relay terminal device receives the data packet of the remote terminal device, it can find the correct PDU session according to the association relationship of the address to transmit the data of the first service.
  • the relay terminal device may allocate a new port number to the remote terminal device, and associate the allocated new port number with the first address.
  • the second address may be, but is not limited to, a media access control (Media Access Control, MAC) address.
  • Media Access Control Media Access Control
  • the method 100 may further include: relaying the terminal device to update the second address. For example, if the relay terminal device has previously allocated an address for the D2D connection to the remote terminal device, the relay terminal device may update the second address and send the updated address to the remote terminal device.
  • the relay terminal device may send a third message to the remote terminal device, and the third message is used to notify the remote terminal device that a PDU session has been established.
  • the established PDU session here may mean that the relay terminal device uses an existing PDU session or has established a new PDU session.
  • the remote terminal device After receiving the third message, the remote terminal device can start data transmission.
  • the relay terminal device may also send a fourth message to the remote terminal device, where the fourth message includes the value of the reason for the unsuccessful establishment of the PDU session.
  • the reason value for the unsuccessful establishment of a PDU session can be, but is not limited to, at least one of the following: network congestion; the network refuses to establish the PDU session; the relay terminal device has no matching UPSP rules or matching local configuration; non-relay terminal device Sign up.
  • third message and the fourth message may be the same message or not the same message, which is not specifically limited in the embodiment of the present application.
  • the time interval for the remote terminal device to send the first message twice may be greater than the preset time interval. That is, after sending the first message, the remote terminal device cannot repeatedly request the same RSD and TrafficDescriptor within a preset time interval.
  • the preset time interval may be preset on the remote terminal device as stipulated in the protocol.
  • the relay terminal device may send configuration information of the timer to the remote terminal device, where the configuration information is used to indicate that the remote terminal device is prohibited from sending the first message again during the running period of the timer.
  • the duration of the timer is a preset time interval.
  • the remote terminal device may start or restart the timer each time after sending the first message.
  • Embodiment 1 The technical solution of Embodiment 1 will be exemplarily described below in conjunction with FIG. 4 of the embodiment of the present application.
  • Step 1 The remote terminal device sends a first message to the relay terminal device.
  • the first message includes the target RSD and the target TrafficDescriptor.
  • Step 2 The relay terminal device matches the current PDU session according to the target Traffic Descriptor and the target RSD.
  • the relay terminal device determines that there is currently no PDU session matching the target Traffic Descriptor and the target RSD, and then uses the target RSD to establish a new PDU session.
  • Step 3 The relay terminal device establishes a new PDU session with the SMF.
  • Step 4 The relay terminal device sends a third message to the remote terminal device, where the third message is used to notify the remote terminal device that a new PDU session has been established.
  • the relay terminal device may send a second message to the remote terminal device, and the second message includes the local configuration of the relay terminal device or URSP.
  • the D2D connection establishment may be used to receive the message transmission.
  • the relay terminal device may send the second message to the remote terminal device through new signaling.
  • the remote terminal device After the remote terminal device receives the local configuration or URSP of the relay terminal device, it can use the local configuration of the relay terminal device or URSP to match the first service. For example, use the local configuration of the relay terminal device or the Traffic Descriptor in the URSP to match the first service. One service to obtain the target RSD corresponding to the first service. Then, the remote terminal device may send a first message to the relay terminal device, where the first message includes the target RSD.
  • the relay terminal device After the relay terminal device receives the target RSD, it can determine whether there is a satisfactory PDU session in at least one current PDU session according to the target RSD. That is, the relay terminal device can determine whether there is a PDU session that meets the target RSD in at least one current PDU session. If there is a PDU session that meets the target RSD, the relay terminal device can use the PDU session that meets the target RSD to transmit data.
  • the relay terminal device can establish a new PDU session according to the target RSD.
  • Embodiment 1 and Embodiment 2 are described above respectively, this does not mean that Embodiment 1 and Embodiment 2 are independent, and the description of the two embodiments may refer to each other. For example, the related description in Embodiment 1 can be applied to Embodiment 2.
  • the relay terminal device when the remote terminal device has business data that needs to be relayed by the relay terminal device, the relay terminal device can use the established PDU session or establish a new PDU session according to the characteristic parameters of the PDU session sent by the remote terminal device. Therefore, the relay terminal device can correspond the data of the remote terminal device to the correct PDU session according to the service.
  • the size of the sequence number of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not be implemented in this application.
  • the implementation process of the example constitutes any limitation.
  • FIG. 6 of the embodiment of the present application shows a schematic block diagram of a terminal device 200.
  • the terminal device 200 includes:
  • the communication unit 210 is configured to receive a first message sent by a remote terminal device, where the first message includes characteristic parameters of a packet data unit PDU session that the remote terminal device requests the relay terminal device to use;
  • the processing unit 220 is configured to use an established PDU session or establish a new PDU session based on the characteristic parameter.
  • the characteristic parameter includes a routing descriptor RSD and/or a service descriptor.
  • the communication unit 210 is further configured to: send a second message to the remote terminal device, where the second message includes the user equipment routing policy of the relay terminal device URSP or local configuration.
  • the processing unit 220 is specifically configured to: determine whether there is a PDU session that meets the characteristic parameter in the current at least one PDU session; if there is a PDU session that meets the characteristic parameter, Use the PDU session that satisfies the characteristic parameter to transmit data.
  • the processing unit 220 is further configured to: if there is no PDU session that meets the characteristic parameter, compare the service descriptor in the characteristic parameter with the relay terminal device's Match the service descriptor in the URSP or the local configuration; compare the RSD corresponding to the service descriptor in the URSP or the local configuration that is successfully matched with the RSD in the characteristic parameter; establish a new PDU based on the first RSD A session, wherein the first RSD corresponds to a successfully matched service descriptor in the URSP or local configuration, and the first RSD includes the RSD in the characteristic parameter.
  • the processing unit 220 is further configured to: if there is no PDU session meeting the characteristic parameter, establish a new PDU session based on the RSD in the characteristic parameter.
  • the processing unit 220 is further configured to: associate a first address with a second address; wherein, the first address is an established PDU session used by the relay terminal device The address or the address of a new PDU session established by the relay terminal device, and the second address is an address for communication between the relay terminal device and the remote terminal device.
  • the communication unit 210 is further configured to: send a third message to the remote terminal device, and the third message is used to notify the remote terminal device that a PDU session has been established .
  • the processing unit 220 is further configured to: update a new second address, where the second address is the communication between the relay terminal device and the remote terminal device the address of.
  • the communication unit 210 is further configured to: if the relay terminal device does not successfully establish the PDU session, send a fourth message to the remote terminal device.
  • the fourth message includes the value of the reason why the PDU session was not successfully established.
  • the communication unit 210 is further configured to: send a timer configuration message to the remote terminal device, where the configuration message is used to indicate that during the running period of the timer The remote terminal device is prohibited from sending the first message again.
  • terminal device 200 may correspond to the terminal device in the method 100, and can implement corresponding operations of the terminal device in the method 100. For the sake of brevity, details are not described herein again.
  • FIG. 7 of the embodiment of the present application shows a schematic block diagram of a terminal device 300.
  • the terminal device 300 includes:
  • the communication unit 310 is configured to send a first message to the relay terminal device, where the first message includes the characteristic parameters of the packet data unit PDU session that the remote terminal device requests the relay terminal device to use.
  • the characteristic parameter includes a routing descriptor RSD and/or a service descriptor.
  • the terminal device 300 further includes: a processing unit 320, configured to determine based on the first service and the user equipment routing strategy URSP or local configuration of the remote terminal device The characteristic parameters.
  • the communication unit 310 is further configured to: receive a second message sent by the relay terminal device, the second message including the URSP or local configuration of the relay terminal device .
  • the terminal device 300 further includes a processing unit 320 configured to match the URSP of the relay terminal device or the service descriptor in the local configuration with the first service to obtain the RSD in the characteristic parameter.
  • the configured RSD and service descriptor of the relay terminal device are included in the URSP or local configuration of the relay terminal device.
  • the communication unit 310 is further configured to: receive a third message sent by the relay terminal device, and the third message is used to notify the remote terminal device that a PDU has been established Conversation.
  • the communication unit 310 is further configured to: if the relay terminal device does not successfully establish a PDU session, receive a fourth message sent by the relay terminal device, and the fourth message The message includes the value of the reason why the PDU session was not successfully established.
  • the communication unit 310 is further configured to: receive a timer configuration message sent by the relay terminal device, where the configuration message is used to indicate that the timer is running The remote terminal device is prohibited from sending the first message again.
  • terminal device 300 may correspond to the terminal device in the method 100, and can implement the corresponding operations of the terminal device in the method 100. For the sake of brevity, details are not described herein again.
  • FIG. 8 is a schematic structural diagram of a terminal device 400 provided by an embodiment of the present application.
  • the terminal device 400 shown in FIG. 8 includes a processor 410, and the processor 410 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the terminal device 400 may further include a memory 420.
  • the processor 410 may call and run a computer program from the memory 420 to implement the method in the embodiment of the present application.
  • the memory 420 may be a separate device independent of the processor 410, or may be integrated in the processor 410.
  • the terminal device 400 may further include a transceiver 430, and the processor 410 may control the transceiver 430 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 430 may include a transmitter and a receiver.
  • the transceiver 430 may further include an antenna, and the number of antennas may be one or more.
  • the terminal device 400 may specifically be the remote terminal device of the embodiment of the present application, and the terminal device 400 may implement the corresponding process implemented by the remote terminal device in each method of the embodiment of the present application. For the sake of brevity, it is not here. Go into details again.
  • the terminal device 400 may specifically be the relay terminal device of the embodiment of the present application, and the terminal device 400 may implement the corresponding process implemented by the relay terminal device in each method of the embodiment of the present application. For the sake of brevity, it is not here. Go into details again.
  • Fig. 9 is a schematic structural diagram of a device according to an embodiment of the present application.
  • the apparatus 500 shown in FIG. 9 includes a processor 510, and the processor 510 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the apparatus 500 may further include a memory 520.
  • the processor 510 may call and run a computer program from the memory 520 to implement the method in the embodiment of the present application.
  • the memory 520 may be a separate device independent of the processor 510, or may be integrated in the processor 510.
  • the device 500 may further include an input interface 530.
  • the processor 510 can control the input interface 530 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the device 500 may further include an output interface 540.
  • the processor 510 can control the output interface 540 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the device can be applied to the remote terminal device in the embodiment of the present application, and the device can implement the corresponding process implemented by the remote terminal device in each method of the embodiment of the present application.
  • the device can implement the corresponding process implemented by the remote terminal device in each method of the embodiment of the present application.
  • the device can be applied to the relay terminal device in the embodiment of the present application, and the device can implement the corresponding process implemented by the relay terminal device in the various methods of the embodiment of the present application.
  • the device can implement the corresponding process implemented by the relay terminal device in the various methods of the embodiment of the present application.
  • details are not described herein again.
  • the device 500 may be a chip. It should be understood that the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip, etc.
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • DDR SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM, ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • Synchronous Link Dynamic Random Access Memory Synchronous Link Dynamic Random Access Memory
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.
  • FIG. 10 is a schematic block diagram of a communication system 600 according to an embodiment of the present application. As shown in FIG. 10, the communication system 600 includes a remote terminal device 610 and a relay terminal device 620.
  • the remote terminal device 610 can be used to implement the corresponding function implemented by the remote terminal device in the above method
  • the relay terminal device 620 can be used to implement the corresponding function implemented by the relay terminal device in the above method.
  • the remote terminal device 610 can be used to implement the corresponding function implemented by the remote terminal device in the above method
  • the relay terminal device 620 can be used to implement the corresponding function implemented by the relay terminal device in the above method.
  • the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium can be applied to the remote terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the remote terminal device in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the remote terminal device in each method of the embodiment of the present application.
  • the computer-readable storage medium can be applied to the relay terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the relay terminal device in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the relay terminal device in each method of the embodiment of the present application.
  • the embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the remote terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the remote terminal device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the remote terminal device in each method of the embodiment of the present application.
  • the computer program product can be applied to the relay terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the relay terminal device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the relay terminal device in each method of the embodiment of the present application.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the remote terminal device in the embodiment of the present application.
  • the computer program runs on the computer, the computer executes the corresponding process implemented by the remote terminal device in each method of the embodiment of the present application.
  • I will not repeat them here.
  • the computer program can be applied to the relay terminal device in the embodiment of the present application.
  • the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the relay terminal device in each method of the embodiment of the present application.
  • I will not repeat them here.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例涉及一种建立会话的方法和终端设备，该方法包括：中继终端设备接收远端终端设备发送的第一消息，所述第一消息包括所述远端终端设备请求所述中继终端设备使用的分组数据单元PDU会话的特征参数；所述中继终端设备基于所述特征参数，使用已建立的PDU会话或建立新的PDU会话。本申请实施例的建立会话的方法和终端设备，可以使得relay终端设备将remote终端设备的数据对应到正确的PDU会话上。

Description

建立会话的方法和终端设备 技术领域
本申请涉及通信领域，具体涉及一种建立会话的方法和终端设备。
背景技术
在新无线(New Radio，NR)***中，第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)引入了终端设备到网络的中继功能，即远端(remote)终端设备可以通过中继(relay)终端设备接入网络。
Remote终端设备可能有多个不同业务的数据需要relay终端设备来中继，不同业务的数据需要使用正确的分组数据单元(Packet Data Unit，PDU)会话(session)来传输才能保证业务的正常进行。
因此，relay终端设备如何将remote终端设备的数据对应到正确的PDU会话，是一项亟待解决的问题。
发明内容
本申请实施例提供一种建立会话的方法和终端设备，可以使得relay终端设备将remote终端设备的数据对应到正确的PDU会话上。
第一方面，提供了一种建立会话的方法，所述方法包括：中继终端设备接收远端终端设备发送的第一消息，所述第一消息包括所述远端终端设备请求所述中继终端设备使用的分组数据单元PDU会话的特征参数；
所述中继终端设备基于所述特征参数，使用已建立的PDU会话或建立新的PDU会话。
第二方面，提供了一种建立会话的方法，所述方法包括：远端终端设备向中继终端设备发送第一消息，所述第一消息包括所述远端终端设备请求所述中继终端设备使用的分组数据单元PDU会话的特征参数。
第三方面，提供了一种终端设备，用于执行上述第一方面或其各实现方式中的方法。
具体地，该终端设备包括用于执行上述第一方面或其各实现方式中的方法的功能模块。
第四方面，提供了一种终端设备，用于执行上述第二方面或其各实现方式中的方法。
具体地，该网络设备包括用于执行上述第二方面或其各实现方式中的方法的功能模块。
第五方面，提供了一种终端设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第一方面或其各实现方式中的方法。
第六方面，提供了一种终端设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第二方面或其各实现方式中的方法。
第七方面，提供了一种装置，用于实现上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
具体地，该装置包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该装置的设备执行如上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
可选地，该装置为芯片。
第八方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第九方面，提供了一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第十方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
上述技术方案，在remote终端设备有业务的数据需要relay终端设备来中继时，relay终端设备可以根据remote终端设备发送的PDU会话的特征参数使用已建立的PDU会话或建立新的PDU会话，从而relay终端设备可以将remote终端设备的数据根据业务对应到正确的PDU会话。
附图说明
图1是根据本申请实施例的一种通信***架构的示意性图。
图2是根据本申请实施例的relay通信***架构的示意性图。
图3是根据本申请实施例的建立会话的方法的示意性流程图。
图4是根据本申请实施例的一个建立会话的方法的示意性流程图。
图5是根据本申请实施例的另一个建立会话的方法的示意性流程图。
图6是根据本申请实施例的终端设备的示意性框图。
图7是根据本申请实施例的终端设备的示意性框图。
图8是根据本申请实施例的终端设备的示意性框图。
图9是根据本申请实施例的装置的示意性框图。
图10是根据本申请实施例的通信***的示意性图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信***，例如：全球移动通讯(Global System of Mobile communication，GSM)***、码分多址(Code Division Multiple Access，CDMA)***、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)***、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)***、LTE频分双工(Frequency Division Duplex，FDD)***、LTE时分双工(Time Division Duplex，TDD)、先进的长期演进(Advanced long term evolution，LTE-A)***、新无线(New Radio，NR)***、NR***的演进***、免授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)***、免授权频谱上的NR(NR-based access to unlicensed spectrum，NR-U)***、通用移动通信***(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信***、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、下一代通信***或其他通信***等。
随着5G应用的不断发展，网络控制互动服务(Network Controlled Interactive Services，NCIS)业务作为一个新的业务形态被引入到标准中进行相关的标准化业务。
NCIS业务主要针对增强现实(Augmented Reality，AR)/虚拟现实(Virtual Reality，VR)、游戏等应用，对速率、时延、丢包率、高速编解码等业务质量有很高的要求。例如：对于VR游戏，需要达到10Gbps速率，丢包率不可超过10E-4。
针对NCIS业务建立的会话为NCIS会话，在相同NCIS会话的终端设备可以认为组成一个业务应用组，例如：游戏中组队。NCIS组内的终端设备有以下可能的通信方式，可以组合使用：
(a)彼此邻近，例如，使用设备到设备(Device-to-Device，D2D)技术进行广播或组播，或建立侧行链路(sidelink)(也称为使用PC5接口)进行1对1通信(单播)。
(b)远离彼此，例如使用终端设备-网络-服务器-对端网络-对端自动化设备(也称为使用Uu接口)。
组内的终端设备可以来自相同的公共陆地移动网络(Public Land Mobile Network，PLMN)，也可以来自不同的PLMN。举例来说，一个NCIS组中有5个终端设备，其中3个可以是PLMN 1的终端设备，2个可以是PLMN 2的终端设备，3个PLMN 1的终端设备可以使用D2D技术在PC5接口互相直接通信，同时又与2个PLMN 2的终端设备使用网络进行通信。
本申请实施例的图1为5G***的通信架构图。如图1所示，该通信***可以包括接入和移动性管理功能(Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)、策略控制功能(Policy Control Function，PCF)、应用层功能(Application Function，AF)、终端设备(User Equipment，UE)、接入网(Access Network，AN或Radio Access Network，RAN)、用户平面功能(User Plane Function，UPF)、数据网络(Data Network，DN)、网络切片选择功能(Network Slice Selection Function，NSSF)、鉴权服务功能(Authentication Server Function，AUSF)以及统一数据管理(Unified Data Management，UDM)。
其中，AMF负责移动性管理，并与终端设备和RAN相连，SMF负责会话管理，与UPF或UDM相连，PCF负责策略控制，可与SMF、AF、以及AMF相连，UDM负责用于签约数据管理。
各个设备之间可以具有不同的接口，例如，N1是连接终端设备和AMF之间的接口，N2是连接AMF和AN或RAN之间的接口，N3是连接AN或RAN和UPF之间的接口，N4是连接SMF和UPF之间的接口，N5是连接PCF和AF之间的接口，N6是连接UPF和DN之间的接口，N7是连接SMF和PCF之间的接口，N8是连接AMF和UDM之间的接口，N9是UPF之间的接口，N10是连接UDM和SMF之间的接口，N11是连接AMF和SMF之间的接口，N12是连接AUSF和AMF之间的接口，N13是连接AUSF和UDM之间的接口，N14是AMF之间的接口，N15是AMF和PCF之间的接口，N22是连接NSSF和AMF之间的接口，Uu接口是连接UE和AN或RAN之间的接口。
针对覆盖不好的区域，如终端设备A在无网络服务区，则可以通过relay的方式来实现remote终端设备(即终端设备A)的通信，其通信架构图如本申请实施例的图2所示。在图2中，relay终端设备相对于网络设备来说在覆盖范围内，remote终端设备在覆盖范围之外。remote终端设备与网络设备之间通过relay终端设备进行通信。relay终端设备可以通过Uu接口连接到网络设备。演进型分组核心网(Evolved Packet Core，EPC)通过SGi接口与公共安全应用服务器(AS)连接。
可选地，图1和图2所示的通信架构中的网络设备可以是与终端设备(或称为通信终端、终端)通信的设备。网络设备可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。可选地，该网络设备可以是GSM***或CDMA***中的基站(Base Transceiver Station，BTS)，也可以是WCDMA***中的基站(NodeB，NB)，还可以是LTE***中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来演进的PLMN中的网络设备等。
图1和图2所示的通信架构中的终端设备可以是包括但不限于经由有线线路连接，如经由公共交换电话网络(Public Switched Telephone Networks，PSTN)、数字用户线路(Digital Subscriber Line，DSL)、数字电缆、直接电缆连接；和/或另一数据连接/网络；和/或经由无线接口，如，针对蜂窝网络、无线局域网(Wireless Local Area Network， WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器；和/或另一终端设备的被设置成接收/发送通信信号的装置；和/或物联网(Internet of Things，IoT)设备。被设置成通过无线接口通信的终端设备可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话；可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信***(Personal Communications System，PCS)终端；可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位***(Global Positioning System，GPS)接收器的PDA；以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端设备可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
应理解，本文中术语“***”和“网络”在本文中常被可互换使用。
针对图2所示的relay通信方式，remote终端设备和relay终端设备之间通信的主要流程可以为：relay终端设备注册到核心网后，和remote终端设备之间互相发现，并建立PC5连接。在relay终端设备和remote终端设备之间建立连接的同时，relay终端设备为了传输remote终端设备的中继数据，可以向网络设备请求建立分组数据网络(Packet Data Network，PDN)连接。其中，使用哪个PDN连接来传输中继数据是由relay终端设备确定的。一般情况下，relay终端设备可以将所有的中继数据都用于一个专门的PDN连接来传输。若relay终端设备和remote终端设备之间的通信地址是互联网协议(Internet Protocol，IP)地址的话，则relay终端设备还可以为remote终端设备分配IP地址，之后，relay终端设备和remote终端设备可以进行业务传输。
5G网络中，每个PDU会话是与数据网络名称(Data Network Name，DNN)和单一网络切片选择辅助信息(Single-Network Slice Selection Assistance Information，S-NSSAI)等相关的，也就是说每个PDU会话和业务相关。remote终端设备可能有多个不同业务的数据需要relay终端设备来中继，不同业务的数据需要使用正确PDU会话来传输才能保证业务的正常进行。但是，在5G中，relay终端设备如何将remote终端设备的数据对应到正确的PDU会话上，还没有明确的规定。
鉴于此，本申请实施例提供了一种建立会话的方法，使得relay终端设备可以将remote终端设备的数据对应到正确的PDU会话上。
本申请实施例的图3是建立会话的方法100的示意性流程图。如图3所示，该方法100可以包括以下内容中的至少部分内容。
在110中，remote终端设备向relay终端设备发送第一消息，该第一消息包括remote终端设备请求relay终端设备使用的PDU会话的特征参数。
在120中，relay终端设备接收remote终端设备发送的第一消息
在130中，relay终端设备基于特征参数，使用已建立的PDU会话或建立新的PDU会话。
其中，特征参数可以包括路由选择描述符(Route Selecting Descriptor，RSD)和/或业务描述符(Traffic Descriptor)。为了后文描述方便，本申请实施例将特征参数中的RSD和Traffic Descriptor分别称为目标RSD和目标Traffic Descriptor。若remote终端设备有第一业务的数据需要relay终端设备来中继，则该特征参数为用于传输第一业务的数据的PDU会话的特征参数。
可选地，第一业务可以为上文提到的NCIS业务，或者，第一业务也可以为超可靠 低时延通信(Ultra Reliable Low Latency Communication，URLLC)业务、工业互联网(Industrial Interest of Things，IIoT)业务，时间敏感网络(Time Sensitive Network，TSN)业务)、垂直行业业务等。
为了便于对方案的理解，下面对RSD和Traffic Descriptor进行简单介绍。
用户设备路由选择策略(UE Route Selection Policy，URSP)可以包括至少一个URSP规则，即URSP可以包括URSP规则1、……、URSP规则n，n为正整数。一个URSP规则可以包括URSP规则的优先级、Traffic Descriptor、RSD列表等中的至少一个，每一个Traffic Descriptor可以对应一个或多个RSD列表，用于终端设备选择使用RSD列表中的哪些参数确定Traffic Descriptor对应的应用与会话的绑定关系，或者用于决定终端设备需要建立什么样的PDU会话来满足这种绑定关系。
其中，URSP可以是网络设备发送给终端设备的，用于终端设备根据策略匹配应用的数据。
终端设备可以根据至少一个URSP规则为应用选择路由，即将不同应用绑定到具有不同属性参数的会话上进行数据传输。其中，一个8比特的RSD列表可以包括以下至少一个参数：
0 0 0 0 0 0 0 1 会话和服务连续性(session and service continuity，SSC)模式
0 0 0 0 0 0 1 0 S-NSSAI类型
0 0 0 0 0 1 0 0 DNN类型
0 0 0 0 1 0 0 0 PDU会话类型
0 0 0 1 0 0 0 0 首选接入类型(Preferred access type)
0 0 0 1 0 0 0 1 多接入优先级类型(Multi-access preference type)
0 0 1 0 0 0 0 0 非无缝非3GPP卸载指示(Non-seamless non-3GPP offload indication type)
URSP中的Traffic Descriptor可用于描述一种具体地业务，即用于匹配业务。比如微博业务可以用IP@1～9来描述。8比特的Traffic Descriptor可以包括以下至少一个参数：
0 0 0 0 0 0 0 1 全部匹配类型(Match-all type)
0 0 0 0 1 0 0 0 操作***(Operating System，OS)标识+OS应用程序(Application，APP)标识类型(OS Id+OS App Id type)
0 0 0 1 0 0 0 0 IPv4远端地址类型(IPv4remote address type)
0 0 1 0 0 0 0 1 IPv6远端地址或前缀长度类型(IPv6remote address/prefix length type)
0 0 1 1 0 0 0 0 协议标识符/下一个标题类型(Protocol identifier/next header type)
0 1 0 1 0 0 0 0 单个远程端口类型(Single remote port type)
0 1 0 1 0 0 0 1 远程端口范围类型(Remote port range type)
0 1 1 0 0 0 0 0 安全参数索引类型(Security parameter index type)
0 1 1 1 0 0 0 0 服务类型/流量类别类型(Type of service/traffic class type)
1 0 0 0 0 0 0 0 流标签类型(Flow label type)
1 0 0 0 0 0 0 1 目的媒体接入控制(Media Access Control，MAC)地址类型(Destination MAC address type)
1 0 0 0 0 0 1 1 802.1Q C-TAG VID类型(802.1Q C-TAG VID type)
1 0 0 0 0 1 0 0 802.1Q S-TAG VID类型(802.1Q S-TAG VID type)
1 0 0 0 0 1 0 1 802.1Q C-TAG PCP/DEI类型(802.1Q C-TAG PCP/DEI type)
1 0 0 0 0 1 1 0 802.1Q S-TAG PCP/DEI类型(802.1Q S-TAG PCP/DEI type)
1 0 0 0 0 1 1 1 以太网类型(Ethertype type)
1 0 0 0 1 0 0 0 DNN类型
1 0 0 1 0 0 0 0 连接能力类型(Connection capabilities type)
1 0 0 1 0 0 0 1 目标全限定域名(Fully Qualified Domain Name，FQDN)(Destination FQDN)
1 0 1 0 0 0 0 0 OS App标识类型(OS App Id type)
一个Traffic Descriptor下面可以有一个或多个RSD。一个RSD中S-NSSAI的值和DNN的值可以是一个也可以是多个，其他参数只包含一个值，S-NSSAI和DNN的一个值可以和其他参数的值组成一个参数组合。因此，每一个RSD可以对应一个或多个参数组合，每个参数组合构成一套PDU会话的特征，Traffic Descriptor对应的业务数据可以在RSD的某一个参数组合对应的PDU会话中进行传输。当有Traffic Descriptor的应用数据流出现时，终端设备可以根据对应的RSD中的组合(component)值选取一个参数组合，并使用该参数组合向网络设备发起PDU会话建立请求。
可选地，在本申请实施例中，remote终端设备向relay终端设备发送第一消息时，可以使用D2D连接或PC5连接建立请求消息发送。
可选地，remote终端设备可以通过新的信令向relay终端设备发送第一消息。
下面结合两个实施例，对本申请实施例的建立会话的方法进行详细描述。
实施例1
remote终端设备在发送第一消息之前，可以基于第一业务，以及基于remote终端设备的本地配置(Local Configuration)或URSP，确定特征参数。该特征参数包括目标RSD和目标Traffic Descriptor。其中，remote终端设备的本地配置可以是预配置在remote终端设备上的，remote终端设备的本地配置可以包括RSD和Traffic Descriptor。
举例说明，remote终端设备有第一业务的数据需要relay终端设备中继时，remote终端设备可以使用URSP中的URSP规则来查看第一业务是否匹配到了URSP规则中的某一个规则的Traffic Descriptor上。当第一业务匹配到一个URSP规则时，该URSP规则中的Traffic Descriptor即为目标Traffic Descriptor。此外，Remote终端设备可以在目标Traffic Descriptor对应的至少一个RSD中确定目标RSD。
应理解，在remote终端设备使用URSP规则来查看第一业务是否匹配到了URSP规则中的某一个规则的Traffic Descriptor上时，本申请实施例对查看顺序不作限定。比如，remote终端设备可以随机查看，或者，可以按照URSP规则中Traffic Descriptor的优先级的顺序查看。
之后，remote可以将确定的目标RSD和目标Traffic Descriptor发送给relay终端设备，请求relay终端设备发送目标RSD和目标Traffic Descriptor表征的第一业务的数据。relay终端设备接收到目标RSD和目标Traffic Descriptor后，可以根据目标RSD和目标Traffic Descriptor执行以下动作：
(1)relay终端设备判断当前的至少一个PDU会话中是否存在满足目标RSD和目标Traffic Descriptor的PDU会话，若存在满足目标RSD和目标Traffic Descriptor的PDU会话(为了描述方便，称为第一PDU会话)，则relay终端设备可以使用第一PDU会话传输第一业务的数据。
可选地，第一PDU会话满足目标RSD和目标Traffic Descriptor可以理解为：第一PDU会话传输的业务与第一业务相同，且第一PDU会话对应的RSD与目标RSD相同或者包含目标RSD。
relay终端设备在判断现有的至少一个PDU会话中是否存在满足目标RSD的PDU会话时，relay终端设备可以将现有的至少一个PDU会话对应的RSD与目标RSD进行比较，判断在现有的至少一个PDU会话中是否有PDU会话对应的RSD与目标RSD相同或包含目标RSD。
(2)若当前的不存在满足目标RSD和Traffic Descriptor的PDU会话，则作为一种示例，relay终端设备可以使用目标RSD，建立新的PDU会话。
作为另一种示例，relay终端设备可以将relay终端设备的被配置的Traffic Descriptor 与目标Traffic Descriptor(为了描述方便，称为第二Traffic Descriptor)进行匹配，第二Traffic Descriptor对应的RSD为第二RSD。
可选地，第二RSD和第二Traffic Descriptor可以包含在relay终端设备的URSP中。
可选地，第二RSD和第二Traffic Descriptor可以包含在relay终端设备的本地配置中。
接下来，relay终端设备可以基于匹配成功的第二Traffic Descriptor对应的第二RSD建立新的PDU会话。
或者，relay终端设备可以将第二RSD和目标RSD进行比较，然后，relay终端设备可以基于第一RSD，建立新的PDU会话。其中，第一RSD与匹配成功的第一Traffic Descriptor对应，且第一RSD包括目标RSD或者与目标RSD的交集最大。
例如，relay终端设备可以根据目标Traffic Descriptor匹配自己的URSP，如果有匹配的URSP规则，则relay终端设备可以使用匹配成功的URSP规则中的RSD和目标RSD进行比较。之后，relay终端设备可以基于第一RSD，建立新的PDU会话。其中，匹配成功的URSP规则中包括第一RSD，且第一RSD包括目标RSD。
在一种实现方式中，relay终端设备使用已建立的PDU会话或建立新的PDU会话后，relay终端设备还可以将第二地址与第一地址和/或该PDU会话ID关联。其中，第一地址为relay终端设备使用的已建立的PDU会话对应的地址或为relay终端设备建立的新的PDU会话对应的地址，第二地址为relay终端设备和remote终端设备之间通信的地址。比如，第二地址可以为relay终端设备分给和remote终端设备之间的D2D连接的地址。
如此，relay终端设备在接收到remote终端设备的数据包时，可以根据地址的关联关系找到正确的PDU会话来传输第一业务的数据。
可选地，如果第二地址是IP地址，则relay终端设备可以为remote终端设备分配新的端口号，并将分配的新的端口号与第一地址关联起来。
可选地，如果第二地址是非IP地址，则第二地址可以是但不限于媒体接入控制(Media Access Control，MAC)地址。
可选地，方法100还可以包括：relay终端设备更新第二地址。例如，若relay终端设备之前已为remote终端设备分配了D2D连接的地址，则relay终端设备可以更新第二地址，并向remote终端设备发送更新后的地址。
在relay将第一地址和第二地址关联起来之后，relay终端设备可以向remote终端设备发送第三消息，该第三消息用于通知remote终端设备已建立PDU会话。应理解，此处的已建立PDU会话可以表示relay终端设备使用现有的PDU会话或已建立新的PDU会话。
remote终端设备在接收到第三消息后，可以开始数据传输。
在另一种实现方式中，若relay终端设备未成功建立PDU会话，则relay终端设备还可以向remote终端设备发送第四消息，该第四消息包括PDU会话未成功建立的原因值。
PDU会话未成功建立的原因值可以为但不限于以下中的至少一项：网络拥塞；网络拒绝建立该PDU会话；relay终端设备没有匹配的UPSP规则或没有匹配的本地配置；非relay终端设备的签约。
需要说明的是，第三消息和第四消息可以是同一条消息，也可以不是同一条消息，本申请实施例对此不做具体限定。
可选地，在relay终端设备未成功建立PDU会话的情况下，remote终端设备两次发送第一消息的时间间隔可以大于预设时间间隔。也就是说，remote终端设备在发送完第一消息后，在预设时间间隔内不可重复请求相同的RSD和Traffic Descriptor。
其中，预设时间间隔可以是协议规定预设在remote终端设备上的。
或者，relay终端设备可以向remote终端设备发送定时器的配置信息，该配置信息用于指示在定时器的运行期间内禁止remote终端设备再次发送第一消息。可以看到，定时器的时长为预设时间间隔。
可选地，在remote终端设备配置了定时器的情况下，remote终端设备可以在每次发送完第一消息后，启动或重启定时器。
下面结合本申请实施例的图4，对实施例1的技术方案进行示例性说明。
步骤1：remote终端设备向relay终端设备发送第一消息，第一消息包括目标RSD和目标Traffic Descriptor。
步骤2：relay终端设备根据目标Traffic Descriptor和目标RSD匹配当前的PDU会话。relay终端设备确定当前没有匹配目标Traffic Descriptor和目标RSD的PDU会话，则使用目标RSD建立新的PDU会话。
步骤3：relay终端设备建立与SMF之间的新的PDU会话。
步骤4：relay终端设备向remote终端设备发送第三消息，该第三消息用于通知remote终端设备已建立新的PDU会话。
实施例2
如本申请实施例的图5所示，在remote终端设备向relay终端设备发送第一消息前，relay终端设备可以向remote终端设备发送第二消息，该第二消息包括relay终端设备的本地配置或URSP。
可选地，relay终端设备向remote终端设备发送第二消息时，可以使用D2D连接建立接收消息发送。或者，relay终端设备可以通过新的信令向remote终端设备发送第二消息。
remote终端设备在接收到relay终端设备的本地配置或URSP后，可以使用relay终端设备的本地配置或URSP来匹配第一业务，比如，使用relay终端设备的本地配置或URSP中的Traffic Descriptor来匹配第一业务，以获得第一业务对应的目标RSD。然后，remote终端设备可以向relay终端设备发送第一消息，该第一消息包括目标RSD。
relay终端设备接收到目标RSD后，可以根据目标RSD判断当前的至少一个PDU会话中是否有满足的PDU会话。即relay终端设备可以判断当前的至少一个PDU会话中是否存在满足目标RSD的PDU会话。如果存在满足目标RSD的PDU会话，则relay终端设备可以使用满足目标RSD的PDU会话传输数据。
如果不存在满足目标RSD的PDU会话，则relay终端设备可以根据目标RSD建立新的PDU会话。
应理解，以上虽然分别描述了实施例1和实施例2，但是这并不意味着实施例1和实施例2是独立的，两个实施例的描述可以相互参考。例如，实施例1中的相关描述可以适用于实施例2。
还应理解，应理解，在本申请实施例中，“第一”、“第二”和“第三”等仅仅为了区分不同的对象，但并不对本申请实施例的范围构成限制。
本申请实施例，在remote终端设备有业务的数据需要relay终端设备来中继时，relay终端设备可以根据remote终端设备发送的PDU会话的特征参数使用已建立的PDU会话或建立新的PDU会话，从而relay终端设备可以将remote终端设备的数据根据业务对应到正确的PDU会话。
以上结合附图详细描述了本申请的优选实施方式，但是，本申请并不限于上述实施方式中的具体细节，在本申请的技术构思范围内，可以对本申请的技术方案进行多种简单变型，这些简单变型均属于本申请的保护范围。
例如，在上述具体实施方式中所描述的各个具体技术特征，在不矛盾的情况下，可以通过任何合适的方式进行组合，为了避免不必要的重复，本申请对各种可能的组合方式不再另行说明。
又例如，本申请的各种不同的实施方式之间也可以进行任意组合，只要其不违背本申请的思想，其同样应当视为本申请所公开的内容。
应理解，在本申请的各种方法实施例中，上述各过程的序号的大小并不意味着执行 顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
上文中详细描述了根据本申请实施例的建立会话的方法，下面将结合图6-图8，描述根据本申请实施例的通信装置，方法实施例所描述的技术特征适用于以下装置实施例。
本申请实施例的图6示出了终端设备200的示意性框图。如图6所示，该终端设备200包括：
通信单元210，用于接收远端终端设备发送的第一消息，所述第一消息包括所述远端终端设备请求所述中继终端设备使用的分组数据单元PDU会话的特征参数；
处理单元220，用于基于所述特征参数，使用已建立的PDU会话或建立新的PDU会话。
可选地，在本申请实施例中，所述特征参数包括路由选择描述符RSD和/或业务描述符。
可选地，在本申请实施例中，所述通信单元210还用于：向所述远端终端设备发送第二消息，所述第二消息包括所述中继终端设备的用户设备路由选择策略URSP或本地配置。
可选地，在本申请实施例中，所述处理单元220具体用于：判断当前的至少一个PDU会话中是否存在满足所述特征参数的PDU会话；若存在满足所述特征参数的PDU会话，使用所述满足所述特征参数的PDU会话，以传输数据。
可选地，在本申请实施例中，所述处理单元220还用于：若不存在满足所述特征参数的PDU会话，将所述特征参数中的业务描述符与所述中继终端设备的URSP或本地配置中的业务描述符进行匹配；将匹配成功的所述URSP或本地配置中的业务描述符对应的RSD和所述特征参数中的RSD进行比较；基于第一RSD，建立新的PDU会话，其中，所述第一RSD与所述URSP或本地配置中匹配成功的业务描述符对应，且所述第一RSD包括所述特征参数中的RSD。
可选地，在本申请实施例中，所述处理单元220还用于：若不存在满足所述特征参数的PDU会话，基于所述特征参数中的RSD，建立新的PDU会话。
可选地，在本申请实施例中，所述处理单元220还用于：关联第一地址和第二地址；其中，所述第一地址为所述中继终端设备使用的已建立的PDU会话的地址或为所述中继终端设备建立的新的PDU会话的地址，所述第二地址为所述中继终端设备和所述远端终端设备之间通信的地址。
可选地，在本申请实施例中，所述通信单元210还用于：向所述远端终端设备发送第三消息，所述第三消息用于通知所述远端终端设备已建立PDU会话。
可选地，在本申请实施例中，所述处理单元220还用于：更新新第二地址，其中，所述第二地址为所述中继终端设备和所述远端终端设备之间通信的地址。
可选地，在本申请实施例中，所述通信单元210还用于：若所述中继终端设备未成功建立所述PDU会话，向所述远端终端设备发送第四消息，所述第四消息包括PDU会话未成功建立的原因值。
可选地，在本申请实施例中，所述通信单元210还用于：向所述远端终端设备发送定时器的配置消息，所述配置消息用于指示在所述定时器的运行期间内禁止所述远端终端设备再次发送所述第一消息。
应理解，该终端设备200可对应于方法100中的终端设备，可以实现该方法100中的终端设备的相应操作，为了简洁，在此不再赘述。
本申请实施例的图7示出了终端设备300的示意性框图。如图7所示，该终端设备300包括：
通信单元310，用于向中继终端设备发送第一消息，所述第一消息包括所述远端终端设备请求所述中继终端设备使用的分组数据单元PDU会话的特征参数。
可选地，在本申请实施例中，所述特征参数包括路由选择描述符RSD和/或业务描述符。
可选地，在本申请实施例中，所述终端设备300还包括：处理单元320，用于基于第一业务，以及基于所述远端终端设备的用户设备路由选择策略URSP或本地配置，确定所述特征参数。
可选地，在本申请实施例中，所述通信单元310还用于：接收所述中继终端设备发送的第二消息，所述第二消息包括所述中继终端设备的URSP或本地配置。
所述终端设备300还包括：处理单元320，用于将所述中继终端设备的URSP或本地配置中的业务描述符与第一业务进行匹配，以获得所述特征参数中的RSD。
可选地，在本申请实施例中，所述中继终端设备的被配置的RSD和业务描述符包含在所述中继终端设备的URSP或本地配置中。
可选地，在本申请实施例中，所述通信单元310还用于：接收所述中继终端设备发送的第三消息，所述第三消息用于通知所述远端终端设备已建立PDU会话。
可选地，在本申请实施例中，所述通信单元310还用于：若所述中继终端设备未成功建立PDU会话，接收所述中继终端设备发送的第四消息，所述第四消息包括PDU会话未成功建立的原因值。
可选地，在本申请实施例中，所述通信单元310还用于：接收所述中继终端设备发送的定时器的配置消息，所述配置消息用于指示在所述定时器的运行期间内禁止所述远端终端设备再次发送所述第一消息。
应理解，该终端设备300可对应于方法100中的终端设备，可以实现该方法100中的终端设备的相应操作，为了简洁，在此不再赘述。
图8是本申请实施例提供的一种终端设备400示意性结构图。图8所示的终端设备400包括处理器410，处理器410可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图8所示，终端设备400还可以包括存储器420。其中，处理器410可以从存储器420中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器420可以是独立于处理器410的一个单独的器件，也可以集成在处理器410中。
可选地，如图8所示，终端设备400还可以包括收发器430，处理器410可以控制该收发器430与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器430可以包括发射机和接收机。收发器430还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该终端设备400具体可为本申请实施例的remote终端设备，并且该终端设备400可以实现本申请实施例的各个方法中由remote终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该终端设备400具体可为本申请实施例的relay终端设备，并且该终端设备400可以实现本申请实施例的各个方法中由relay终端设备实现的相应流程，为了简洁，在此不再赘述。
图9是本申请实施例的装置的示意性结构图。图9所示的装置500包括处理器510，处理器510可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图9所示，装置500还可以包括存储器520。其中，处理器510可以从存储器520中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器520可以是独立于处理器510的一个单独的器件，也可以集成在处理器510中。
可选地，该装置500还可以包括输入接口530。其中，处理器510可以控制该输入接 口530与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该装置500还可以包括输出接口540。其中，处理器510可以控制该输出接口540与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该装置可应用于本申请实施例中的remote终端设备，并且该装置可以实现本申请实施例的各个方法中由remote终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该装置可应用于本申请实施例中的relay终端设备，并且该装置可以实现本申请实施例的各个方法中由relay终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该装置500可以为芯片。应理解，本申请实施例提到的芯片还可以称为***级芯片，***芯片，芯片***或片上***芯片等。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的***和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
图10是本申请实施例提供的一种通信***600的示意性框图。如图10所示，该通信***600包括remote终端设备610和relay终端设备620。
其中，该remote终端设备610可以用于实现上述方法中由remote终端设备实现的相应的功能，以及该relay终端设备620可以用于实现上述方法中由relay终端设备实现的相应的功能为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选地，该计算机可读存储介质可应用于本申请实施例中的remote终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由remote终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的relay终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由relay终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选地，该计算机程序产品可应用于本申请实施例中的remote终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由remote终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的relay终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由relay终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选地，该计算机程序可应用于本申请实施例中的remote终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由remote终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的relay终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由relay终端设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该 计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (46)

  1. 一种建立会话的方法，其特征在于，所述方法包括：
    中继终端设备接收远端终端设备发送的第一消息，所述第一消息包括所述远端终端设备请求所述中继终端设备使用的分组数据单元PDU会话的特征参数；
    所述中继终端设备基于所述特征参数，使用已建立的PDU会话或建立新的PDU会话。
  2. 根据权利要求1所述的方法，其特征在于，所述特征参数包括路由选择描述符RSD和/或业务描述符。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述中继终端设备向所述远端终端设备发送第二消息，所述第二消息包括所述中继终端设备的用户设备路由选择策略URSP或本地配置。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述中继终端设备基于所述特征参数，使用已建立的PDU会话或建立新的PDU会话，包括：
    所述中继终端设备判断当前的至少一个PDU会话中是否存在满足所述特征参数的PDU会话；
    若存在满足所述特征参数的PDU会话，所述中继终端设备使用所述满足所述特征参数的PDU会话，以传输数据。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    若不存在满足所述特征参数的PDU会话，所述中继终端设备将所述特征参数中的业务描述符与所述中继终端设备的URSP或本地配置中的业务描述符进行匹配；
    所述中继终端设备将所述URSP或本地配置中匹配成功的业务描述符对应的RSD和所述特征参数中的RSD进行比较；
    所述中继终端设备基于第一RSD，建立新的PDU会话，其中，所述第一RSD与所述URSP或本地配置中匹配成功的业务描述符对应，且所述第一RSD包括所述特征参数中的RSD。
  6. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    若不存在满足所述特征参数的PDU会话，所述中继终端设备基于所述特征参数中的RSD，建立新的PDU会话。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述方法还包括：
    所述中继终端设备关联第一地址和第二地址；
    其中，所述第一地址为所述中继终端设备使用的已建立的PDU会话的地址或为所述中继终端设备建立的新的PDU会话的地址，所述第二地址为所述中继终端设备和所述远端终端设备之间通信的地址。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    所述中继终端设备向所述远端终端设备发送第三消息，所述第三消息用于通知所述远端终端设备已建立PDU会话。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述方法还包括：
    所述中继终端设备更新第二地址，其中，所述第二地址为所述中继终端设备和所述远端终端设备之间通信的地址。
  10. 根据权利要求1至6中任一项所述的方法，其特征在于，所述方法还包括：
    若所述中继终端设备未成功建立所述PDU会话，所述中继终端设备向所述远端终端设备发送第四消息，所述第四消息包括PDU会话未成功建立的原因值。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    所述中继终端设备向所述远端终端设备发送定时器的配置消息，所述配置消息用于指示在所述定时器的运行期间内禁止所述远端终端设备再次发送所述第一消息。
  12. 一种建立会话的方法，其特征在于，所述方法包括：
    远端终端设备向中继终端设备发送第一消息，所述第一消息包括所述远端终端设备请求所述中继终端设备使用的分组数据单元PDU会话的特征参数。
  13. 根据权利要求12所述的方法，其特征在于，所述特征参数包括路由选择描述符RSD和/或业务描述符。
  14. 根据权利要求12或13所述的方法，其特征在于，所述方法还包括：
    所述远端终端设备基于第一业务，以及基于所述远端终端设备的用户设备路由选择策略URSP或本地配置，确定所述特征参数。
  15. 根据权利要求12或13所述的方法，其特征在于，所述方法还包括：
    所述远端终端设备接收所述中继终端设备发送的第二消息，所述第二消息包括所述中继终端设备的URSP或本地配置；
    所述远端终端设备将所述中继终端设备的URSP或本地配置中的业务描述符与第一业务进行匹配，以获得所述特征参数中的RSD。
  16. 根据权利要求12至15中任一项所述的方法，其特征在于，所述方法还包括：
    所述远端终端设备接收所述中继终端设备发送的第三消息，所述第三消息用于通知所述远端终端设备已建立PDU会话。
  17. 根据权利要求12至16中任一项所述的方法，其特征在于，所述方法还包括：
    若所述中继终端设备未成功建立PDU会话，所述远端终端设备接收所述中继终端设备发送的第四消息，所述第四消息包括PDU会话未成功建立的原因值。
  18. 根据权利要求17所述的方法，其特征在于，所述方法还包括：
    所述远端终端设备接收所述中继终端设备发送的定时器的配置消息，所述配置消息用于指示在所述定时器的运行期间内禁止所述远端终端设备再次发送所述第一消息。
  19. 一种终端设备，其特征在于，所述终端设备为中继终端设备，包括：
    通信单元，用于接收远端终端设备发送的第一消息，所述第一消息包括所述远端终端设备请求所述中继终端设备使用的分组数据单元PDU会话的特征参数；
    处理单元，用于基于所述特征参数，使用已建立的PDU会话或建立新的PDU会话。
  20. 根据权利要求19所述的终端设备，其特征在于，所述特征参数包括路由选择描述符RSD和/或业务描述符。
  21. 根据权利要求19或20所述的终端设备，其特征在于，所述通信单元还用于：
    向所述远端终端设备发送第二消息，所述第二消息包括所述中继终端设备的用户设备路由选择策略URSP或本地配置。
  22. 根据权利要求19至21中任一项所述的终端设备，其特征在于，所述处理单元具体用于：
    判断当前的至少一个PDU会话中是否存在满足所述特征参数的PDU会话；
    若存在满足所述特征参数的PDU会话，使用所述满足所述特征参数的PDU会话，以传输数据。
  23. 根据权利要求22所述的终端设备，其特征在于，所述处理单元还用于：
    若不存在满足所述特征参数的PDU会话，将所述特征参数中的业务描述符与所述中继终端设备的URSP或本地配置中的业务描述符进行匹配；
    将匹配成功的所述URSP或本地配置中的业务描述符对应的RSD和所述特征参数中的RSD进行比较；
    基于第一RSD，建立新的PDU会话，其中，所述第一RSD与所述URSP或本地配置中匹配成功的业务描述符对应，且所述第一RSD包括所述特征参数中的RSD。
  24. 根据权利要求22所述的终端设备，其特征在于，所述处理单元还用于：
    若不存在满足所述特征参数的PDU会话，基于所述特征参数中的RSD，建立新的PDU会话。
  25. 根据权利要求19至24中任一项所述的终端设备，其特征在于，所述处理单元还用于：
    关联第一地址和第二地址；
    其中，所述第一地址为所述中继终端设备使用的已建立的PDU会话的地址或为所述中继终端设备建立的新的PDU会话的地址，所述第二地址为所述中继终端设备和所述远端终端设备之间通信的地址。
  26. 根据权利要求19至25中任一项所述的终端设备，其特征在于，所述通信单元还用于：
    向所述远端终端设备发送第三消息，所述第三消息用于通知所述远端终端设备已建立PDU会话。
  27. 根据权利要求19至26中任一项所述的终端设备，其特征在于，所述处理单元还用于：
    更新第二地址，其中，所述第二地址为所述中继终端设备和所述远端终端设备之间通信的地址。
  28. 根据权利要求19至24中任一项所述的终端设备，其特征在于，所述通信单元还用于：
    若所述中继终端设备未成功建立所述PDU会话，向所述远端终端设备发送第四消息，所述第四消息包括PDU会话未成功建立的原因值。
  29. 根据权利要求28所述的终端设备，其特征在于，所述通信单元还用于：
    向所述远端终端设备发送定时器的配置消息，所述配置消息用于指示在所述定时器的运行期间内禁止所述远端终端设备再次发送所述第一消息。
  30. 一种终端设备，其特征在于，所述终端设备为远端终端设备，包括：
    通信单元，用于向中继终端设备发送第一消息，所述第一消息包括所述远端终端设备请求所述中继终端设备使用的分组数据单元PDU会话的特征参数。
  31. 根据权利要求30所述的终端设备，其特征在于，所述特征参数包括路由选择描述符RSD和/或业务描述符。
  32. 根据权利要求30或31所述的终端设备，其特征在于，所述终端设备还包括：
    处理单元，用于基于第一业务，以及基于所述远端终端设备的用户设备路由选择策略URSP或本地配置，确定所述特征参数。
  33. 根据权利要求30或31所述的终端设备，其特征在于，所述通信单元还用于：
    接收所述中继终端设备发送的第二消息，所述第二消息包括所述中继终端设备的URSP或本地配置；
    所述终端设备还包括：
    处理单元，用于将所述中继终端设备的URSP或本地配置中的业务描述符与第一业务进行匹配，以获得所述特征参数中的RSD。
  34. 根据权利要求30至33中任一项所述的终端设备，其特征在于，所述通信单元还用于：
    接收所述中继终端设备发送的第三消息，所述第三消息用于通知所述远端终端设备已建立PDU会话。
  35. 根据权利要求30至34中任一项所述的终端设备，其特征在于，所述通信单元还用于：
    若所述中继终端设备未成功建立PDU会话，接收所述中继终端设备发送的第四消息，所述第四消息包括PDU会话未成功建立的原因值。
  36. 根据权利要求35所述的终端设备，其特征在于，所述通信单元还用于：
    接收所述中继终端设备发送的定时器的配置消息，所述配置消息用于指示在所述定时器的运行期间内禁止所述远端终端设备再次发送所述第一消息。
  37. 一种终端设备，其特征在于，包括：处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至11中任一项所述的方法。
  38. 一种终端设备，其特征在于，包括：处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求12至18中任一项所述的方法。
  39. 一种装置，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至11中任一项所述的方法。
  40. 一种装置，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求12至18中任一项所述的方法。
  41. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至11中任一项所述的方法。
  42. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求12至18中任一项所述的方法。
  43. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至11中任一项所述的方法。
  44. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求12至18中任一项所述的方法。
  45. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1至11中任一项所述的方法。
  46. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求12至18中任一项所述的方法。
PCT/CN2019/109217 2019-09-29 2019-09-29 建立会话的方法和终端设备 WO2021056573A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2019/109217 WO2021056573A1 (zh) 2019-09-29 2019-09-29 建立会话的方法和终端设备
CN201980095066.4A CN113678506B (zh) 2019-09-29 2019-09-29 建立会话的方法和终端设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/109217 WO2021056573A1 (zh) 2019-09-29 2019-09-29 建立会话的方法和终端设备

Publications (1)

Publication Number Publication Date
WO2021056573A1 true WO2021056573A1 (zh) 2021-04-01

Family

ID=75165396

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/109217 WO2021056573A1 (zh) 2019-09-29 2019-09-29 建立会话的方法和终端设备

Country Status (2)

Country Link
CN (1) CN113678506B (zh)
WO (1) WO2021056573A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022206662A1 (zh) * 2021-04-01 2022-10-06 维沃移动通信有限公司 中继pdu会话建立的确定方法及装置、终端
WO2023283901A1 (zh) * 2021-07-15 2023-01-19 Oppo广东移动通信有限公司 一种数据传输方法及装置、终端设备、网络设备
WO2023098704A1 (zh) * 2021-12-01 2023-06-08 中国电信股份有限公司 设备到设备通信方法、装置、设备、介质及程序产品

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106160951A (zh) * 2015-04-09 2016-11-23 上海贝尔股份有限公司 用于中继用户设备和远端用户设备之间的d2d通信的方法
CN108024295A (zh) * 2016-11-03 2018-05-11 中兴通讯股份有限公司 中继转移方法及装置、终端、基站
US20190174449A1 (en) * 2018-02-09 2019-06-06 Intel Corporation Technologies to authorize user equipment use of local area data network features and control the size of local area data network information in access and mobility management function

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110121897B (zh) * 2017-08-15 2021-09-17 华为技术有限公司 一种会话建立的方法及设备
WO2019127038A1 (zh) * 2017-12-26 2019-07-04 Oppo广东移动通信有限公司 用于数据传输的方法、终端设备和网络设备
CN110278619B (zh) * 2018-03-13 2021-02-09 华为技术有限公司 一种pdu会话建立的方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106160951A (zh) * 2015-04-09 2016-11-23 上海贝尔股份有限公司 用于中继用户设备和远端用户设备之间的d2d通信的方法
CN108024295A (zh) * 2016-11-03 2018-05-11 中兴通讯股份有限公司 中继转移方法及装置、终端、基站
US20190174449A1 (en) * 2018-02-09 2019-06-06 Intel Corporation Technologies to authorize user equipment use of local area data network features and control the size of local area data network information in access and mobility management function

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
INTEL: "Solution of 5GC Capable UE behind 5G-RG connected to 5GC via NG-RAN/W- 5GAN", 3GPP DRAFT; S2-1810426-5WWC-5G-RG-RELAYUE-V3, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Dongguan, China; 20181015 - 20181019, 9 October 2018 (2018-10-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 9, XP051539407 *
INTEL: "Solution of 5GC Capable UE behind 5G-RG connected to 5GC via NG-RAN/W- 5GAN", 3GPP DRAFT; S2-186846-5WWC-5G-RG-RELAYUE-V6, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Newport Beach, California, USA; 20180528 - 2018060, 1 July 2018 (2018-07-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051469988 *
OPPO: "Clarification on using user preference", 3GPP DRAFT; S2-187812 CLARIFICATION ON USER PREFERENCE -CR R2, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Sophia Antipolis, France; 20180820 - 20180824, 14 August 2018 (2018-08-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051536775 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022206662A1 (zh) * 2021-04-01 2022-10-06 维沃移动通信有限公司 中继pdu会话建立的确定方法及装置、终端
WO2023283901A1 (zh) * 2021-07-15 2023-01-19 Oppo广东移动通信有限公司 一种数据传输方法及装置、终端设备、网络设备
WO2023098704A1 (zh) * 2021-12-01 2023-06-08 中国电信股份有限公司 设备到设备通信方法、装置、设备、介质及程序产品

Also Published As

Publication number Publication date
CN113678506B (zh) 2023-09-26
CN113678506A (zh) 2021-11-19

Similar Documents

Publication Publication Date Title
CN114287142B (zh) 一种通信方法及装置、网络设备、终端设备
WO2021007785A1 (zh) 一种策略映射方法及装置、终端
US11811670B2 (en) Packet delay parameter obtaining method, system, and apparatus
JP7401567B2 (ja) 無線通信の方法および装置
WO2020107751A1 (zh) 一种数据传输方法及装置、终端
WO2021217412A1 (zh) 一种确定终端策略行为的方法及装置、网络设备
WO2021056573A1 (zh) 建立会话的方法和终端设备
WO2021030989A1 (zh) 一种路径选择方法及装置、终端
US20220210849A1 (en) Methods for service transmission, terminal device and amf
US11877326B2 (en) Wireless communication method and communication device
WO2020252710A1 (zh) 无线通信方法和设备
WO2021226937A1 (zh) 一种多路径传输方法及装置、网络设备、终端
WO2021031010A1 (zh) 通信方法、终端设备和网络设备
WO2022006828A1 (zh) 无线通信方法和设备
WO2020164078A1 (zh) 用于传输数据的方法及设备
WO2020199215A1 (zh) 传输数据的方法、终端设备和核心网设备
US20220210690A1 (en) Data transmission method and apparatus, system, and storage medium
WO2022147836A1 (zh) 一种连接建立方法及装置、网络设备
WO2020103050A1 (zh) 一种数据通道的建立方法及装置、网络设备
WO2020164054A1 (zh) 业务处理方法、装置、芯片及计算机程序
WO2020077543A1 (zh) 一种处理帧头的方法及装置、通信设备
WO2020087546A1 (zh) 一种网络信息传输方法、获取方法、网络设备及终端设备
US20230144620A1 (en) Method and electronic device for session establishment, and storage medium
WO2023134295A1 (zh) 数据传输方法及相关设备、计算机可读存储介质、计算机程序产品
WO2023088118A1 (zh) 数据传输方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19947183

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19947183

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 19947183

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 16/09/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 19947183

Country of ref document: EP

Kind code of ref document: A1