WO2019196078A1 - 建立传输路径的方法和设备 - Google Patents

建立传输路径的方法和设备 Download PDF

Info

Publication number
WO2019196078A1
WO2019196078A1 PCT/CN2018/082922 CN2018082922W WO2019196078A1 WO 2019196078 A1 WO2019196078 A1 WO 2019196078A1 CN 2018082922 W CN2018082922 W CN 2018082922W WO 2019196078 A1 WO2019196078 A1 WO 2019196078A1
Authority
WO
WIPO (PCT)
Prior art keywords
core network
network device
transmission path
terminal device
information
Prior art date
Application number
PCT/CN2018/082922
Other languages
English (en)
French (fr)
Inventor
刘建华
Original Assignee
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广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to EP18914216.9A priority Critical patent/EP3780743B1/en
Priority to KR1020207031690A priority patent/KR20200142531A/ko
Priority to AU2018418065A priority patent/AU2018418065A1/en
Priority to CN201880092308.XA priority patent/CN111972005B/zh
Priority to PCT/CN2018/082922 priority patent/WO2019196078A1/zh
Publication of WO2019196078A1 publication Critical patent/WO2019196078A1/zh
Priority to US17/034,797 priority patent/US20210014766A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices

Definitions

  • Embodiments of the present application relate to the field of communications and, more particularly, to a method and apparatus for establishing a transmission path.
  • IoT Internet of Things
  • NAS Non-Access Stratum
  • PDU Protocol Data Unit
  • the embodiment of the present application provides a method and a device for establishing a transmission path, which can implement data transmission without establishing a PDU session connection.
  • the first aspect provides a method for establishing a transmission path, where the first core network device receives a first request message, where the first request message is used to request the first core network device to be a non-protocol to be established.
  • the terminal device sends a request message to the core network device to register on different core network devices.
  • the registered core network device serves as a transmission node of the target transmission path, so that in the absence of a PDU session connection, the terminal device can still perform data transmission through the target transmission path, that is, through the registered transmission nodes.
  • the determining, by the first core network device, as a transit node of the target transmission path includes:
  • the first core network device determines a transmission node that is the target transmission path:
  • the target network slice to which the target transmission path is applied is a network slice signed by the terminal device, an external server to which the external transmission server applied by the target transmission path is contracted, and an external service applied by the target transmission path.
  • the function is an external service function signed by the terminal device.
  • the method further includes: the first core network device selecting from a unified data management UDM or a network slice In the function NSSF, the information of the network slice signed by the terminal device, the information of the external server subscribed by the terminal device, and the information of the external service function signed by the terminal device are obtained.
  • the method further includes: the first core network device selects a second core network device; the first core network device sends a second request message to the second core network device, where the second request message is used to request the The second core network device serves as a transmission node of the target transmission path to be established.
  • the first core network device selects the second core network device, including: the first core network The device selects the second core network device according to the first request message, where the first request message carries at least one of the following information: information of a target network slice to which the target transmission path is applied, The data network name DNN information of the terminal device and the service network identification information of the terminal device.
  • the first core network device selects the second core network device, including: the first core network The device selects the second core network device according to the local configuration of the first core network device and/or the subscription information of the terminal device.
  • the subscription information of the terminal device includes at least one of the following information: information of a network slice subscribed by the terminal device, information of an external server subscribed by the terminal device, and a subscription of the terminal device.
  • the information of the external service function, the local configuration of the first core network device includes information of a second core network device capable of communicating with the first core network device.
  • the first core network device receives the first request message, including: the first core network device Receiving the first request message sent by the terminal device.
  • the method further includes: the first core network device receiving the transmission by using the target transmission path After the downlink data, the downlink data is sent to the terminal device.
  • the first core network device receives the first request message, including: the first core network device Receiving the first request message sent by the third core network device.
  • the method further includes: the first core network device receiving the transmission by using the target transmission path After the downlink data, the downlink data is sent to the terminal device by using the third core network device.
  • the first core network device sends, by using the third core network device, the terminal device Before the downlink data is described, the method further includes: the first core network device acquiring information about the third core network device, and determining the third core network device according to the information of the third core network device.
  • the first core network device acquiring information of the third core network device includes: The first core network device obtains information about the third core network device from the UDM device; or the first core network device acquires information about the third core network device stored in the first core network device .
  • the method further includes: the first core network device sending, for the first request message, In response to the message, the response message is used to indicate whether the target transmission path is established or not.
  • the third core network device is any one of the following: access and mobility management The function AMF device, the session management function SMF device, the user plane function UPF device, the device with the SMF and the UPF, and the gateway connecting the external network element.
  • the second core network device is any one of the following: an AMF device, an SMF device, UPF devices, devices with SMF and UPF, and gateways connected to external network elements.
  • the first core network device is any one of the following: an AMF device, an SMF device, UPF devices, devices with SMF and UPF, and gateways connected to external network elements.
  • the second aspect provides a method for establishing a transmission path, where the terminal device sends a first request message to the first core network device, where the first request message is used to request the first core network device to be established.
  • a transport node of a target transmission path based on a non-protocol data unit PDU session connection.
  • the terminal device sends a request message to the core network device to register on different core network devices.
  • the registered core network device serves as a transmission node of the target transmission path, so that in the absence of a PDU session connection, the terminal device can still perform data transmission through the target transmission path, that is, through the registered transmission nodes.
  • the first request message carries at least one of the following information: information of a target network slice to which the target transmission path is applied, the terminal The data network name DNN information of the device and the service network identification information of the terminal device.
  • the method further includes: the terminal device receiving the response message sent by the first core network device The response message is used to indicate whether the target transmission path is established or not.
  • the method further includes: the terminal device receiving, by the first core network device, The downlink data transmitted by the target transmission path.
  • the first core network device is any one of the following: access and mobility management The function AMF device, the session management function SMF device, the user plane function UPF device, the device with the SMF and the UPF, and the gateway connecting the external network element.
  • a core network device in a third aspect, can perform the operations of the core network device in the foregoing first aspect or any optional implementation manner of the first aspect.
  • the core network device may include a first core network device for performing the foregoing first aspect or any possible implementation of the first aspect.
  • a fourth aspect provides a terminal device, which can perform the operations of the terminal device in any of the foregoing optional implementations of the second aspect or the second aspect.
  • the terminal device may include a terminal device in any of the possible implementation manners of the second aspect or the second aspect described above.
  • a core network device comprising: a processor, a transceiver, and a memory.
  • the processor, the transceiver, and the memory communicate with each other through an internal connection path.
  • the memory is for storing instructions for executing instructions stored by the memory.
  • a terminal device comprising: a processor, a transceiver, and a memory.
  • the processor, the transceiver, and the memory communicate with each other through an internal connection path.
  • the memory is for storing instructions for executing instructions stored by the memory.
  • the processor executes the instruction stored by the memory, the executing causes the terminal device to perform the method in any of the possible implementations of the second aspect or the second aspect, or the execution causes the terminal device to implement the terminal provided by the fourth aspect device.
  • a system chip in a seventh aspect, includes an input interface, an output interface, a processor, and a memory, the processor is configured to execute an instruction stored by the memory, and when the instruction is executed, the processor can implement the foregoing The method of any of the first aspect or any of the possible implementations of the first aspect.
  • a system chip in an eighth aspect, includes an input interface, an output interface, a processor, and a memory, the processor is configured to execute an instruction stored by the memory, and when the instruction is executed, the processor can implement the foregoing The method of any of the second aspect or any possible implementation of the second aspect.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any of the first aspect or the first aspect of the first aspect.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any of the above-described second or second aspect of the second aspect.
  • FIG. 1 is a schematic diagram of a possible wireless communication system applied in an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a method for establishing a transmission path according to an embodiment of the present application.
  • FIG. 3 is a flow diagram of a process for establishing a transmission path according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a method for establishing a transmission path according to an embodiment of the present application.
  • FIG. 5 is a schematic block diagram of a core network device 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 structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a system chip 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
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UPD Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • FIG. 1 shows a wireless communication system 100 to which an embodiment of the present application is applied.
  • the wireless communication system 100 can include an access network device 110.
  • Access network device 110 may be a device that communicates with the terminal device.
  • Access network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices (e.g., UEs) located within the coverage area.
  • the access network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or may be a base station (NodeB, NB) in a WCDMA system, or may be an evolution in an LTE system.
  • BTS Base Transceiver Station
  • NodeB NodeB
  • a type of base station (Evolutional NodeB, eNB or eNodeB), or a wireless controller in a Cloud Radio Access Network (CRAN), or the access network device 110 may be a relay station, an access point, an in-vehicle device, A wearable device, a network side device in a future 5G network, or a network device in a future evolved Public Land Mobile Network (PLMN).
  • the access network device 110 may also be an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) or a Next Generation Radio Access Network (NG-RAN).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • NG-RAN Next Generation Radio Access Network
  • the wireless communication system 100 can also include a core network device 130 in communication with an access network device.
  • the core network device 130 may be an Evolved Packet Core (EPC) of the LTE network; or may be a 5G core network device (5G Core, 5GC), such as access and mobility management functions (Access and Mobility). Management Function (AMF) or Session Management Function (SMF).
  • EPC Evolved Packet Core
  • the core network device 130 may also be an Evolved Packet Core (EPC) device of the LTE network, for example, a session management function + a core network data gateway (Session Management Function+Core Packet Gateway, SMF+PGW- C) Equipment. It should be understood that SMF+PGW-C can simultaneously implement the functions that SMF and PGW-C can achieve.
  • the wireless communication system 100 can also include at least one terminal device 120 located within the coverage of the network device 110.
  • Terminal device 120 can be mobile or fixed.
  • the terminal device 120 may refer to an access terminal, a user equipment (User Equipment, UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, and a wireless communication.
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication.
  • the wireless communication system 100 may include multiple access network devices and coverage of each access network device. Other numbers of terminal devices may be included in the scope, which is not limited in this embodiment of the present application.
  • the wireless communication system 100 may further include a Mobile Management Entity (MME), a Unified Data Management (UDM), an Authentication Server Function (AUSF), and a User Plane Function (User).
  • MME Mobile Management Entity
  • UDM Unified Data Management
  • AUSF Authentication Server Function
  • User User Plane Function
  • Other network entities such as a Plane Function (UPF) and a Signaling Gateway (SGW), are not limited in this embodiment of the present application.
  • UPF Plane Function
  • SGW Signaling Gateway
  • FIG. 2 is a schematic flowchart of a method 200 for establishing a transmission path according to an embodiment of the present application.
  • the method 200 shown in FIG. 2 can be performed by a first core network device, which can be, for example, the core network device 130 of FIG.
  • the method 200 includes some or all of the following:
  • the first core network device receives the first request message.
  • the first request message is used to request the first core network device to be a transit node of a target transmission path based on a non-PDU session connection to be established.
  • the first core network device determines whether to act as a transport node for the target transmission path.
  • the first request message is received by the first core network device, where the first request message is used to request to establish a target transmission path based on the non-PDU session connection and request the first core network device to be in the target transmission path.
  • the target transmission path may be used to transmit downlink data of the terminal device, for example, to transmit data packets encapsulated as NAS PDUs to the terminal device.
  • the first core network device After the first core network device receives the first request message, it determines whether it is a transmission node of the target transmission path.
  • the first request message may be, for example, a registration request message, for requesting registration of the terminal device on the first core network device, and the core network device registered by the terminal device may form a transmission path, that is, the target
  • the transmission path is such that data can be transmitted to the terminal device through the registered core network devices.
  • the first core network device is used as the transmission node of the target transmission path, and is completed by the terminal device completing registration on the first core network device, where the terminal device completes registration on the first core network device. Indicates that the device of the first core network agrees to be the transmission node of the target transmission path.
  • the first core network device is any one of the following: an AMF device, an SMF device, a UPF device, a device that is configured with an SMF and a UPF, and a gateway that connects the external network element.
  • the first core network device determines whether it is a transit node of the target transmission path, including:
  • the first core network device determines a transmission node that is the target transmission path:
  • the target network slice to which the target transmission path is applied is a network slice signed by the terminal device, an external server to which the external server applied by the target transmission path is contracted, and an external service function applied to the target transmission path is the terminal The external service function of the device contract.
  • the target transmission path may be established for a specific network slice request, and then the network slice applied by the target transmission path is Specific network slices.
  • the specific network slice is a network slice signed by the terminal device, the target transmission path may be established. Therefore, after receiving the first request message, the first core network device verifies whether the target network slice is a network slice subscribed by the terminal device.
  • the target transmission path can also be established for a specific external server request, and the external server to which the target transmission path is applied is the specific external server.
  • the specific external server is an external server that is contracted by the terminal device
  • the target transmission path may be established. Therefore, after receiving the first request message, the first core network device verifies whether the external server is an external server that is subscribed by the terminal device.
  • the target transmission path may also be established for a specific external service function request, and the external service function applied by the target transmission path is the specific external service function.
  • the target transmission path may be established. Therefore, after receiving the first request message, the first core network device verifies whether the external service function is an external service function signed by the terminal device.
  • the first core network device determines that the target for the external server (external service function) can be established on the target network slice a transmission path and the first core network device can serve as a transmission node of the target transmission path; if the requested target network slice and/or an external server (external service function) is not allowed, then the first core network device It is determined that the target transmission path for the external server (external service function) cannot be established on the target network slice, and the first core network device is not used as the transmission node of the target transmission path.
  • the first core network device may obtain, from a UDM device or a network slice selection function (NSSF) device, information about a network slice subscribed by the terminal device, and information about an external server that is subscribed by the terminal device. Information about the external service function contracted with the terminal device.
  • NSF network slice selection function
  • the first core network may obtain information about the allowed network slice of the terminal device from the NSSF device, or obtain subscription information of the terminal device from the UDM device, where the subscription information includes information about the network slice subscribed by the terminal device.
  • the method further includes:
  • the first core network device selects a second core network device.
  • the first core network device sends a second request message to the second core network device.
  • the second request message is used to request the second core network device to be the transit node of the target transmission path to be established.
  • the second request message may be, for example, a registration request message, for requesting registration of the terminal device on the second core network device, and the core network device registered by the terminal device may form a transmission path, that is, the target transmission. A path so that data can be transmitted to the terminal device through the registered core network devices.
  • the second core network device is any one of the following: an AMF device, an SMF device, a UPF device, a device that is configured with an SMF and a UPF, and a gateway that connects the external network element.
  • the first core network device determines that the target transmission path can be established and the first core network device serves as the transmission node of the target transmission path
  • the next transmission node of the target transmission path may continue to be searched, for example, The second core network device is the next transmission node selected.
  • the first core network device sends second request information to the second core network device to request the second core network device to be the transit node of the target transmission path.
  • the target transmission path includes at least two transmission nodes of the first core network device and the second core network device.
  • the second core network device may also send a request message to other core network devices to request other core network devices as the transmission node of the target transmission path.
  • the target transmission path may also include other core network devices that are requested.
  • the transit node in the target transmission path may send its own information to the UDM device after completing the establishment of the transit node, so that the UDM device stores the target transmission path.
  • the information is the information of each transmission node in the target transmission path.
  • the first core network device selects the second core network device, and the first core network device selects the second core network device according to the first request message.
  • the first request message carries at least one of the following information: information of a target network slice to which the target transmission path is applied, data network name (DNN) information of the terminal device, and service of the terminal device.
  • Network identification information information of a target network slice to which the target transmission path is applied.
  • the first core network device may select the second information according to the received information of the target network slice carried in the first request message. Core network equipment. The second core network device selected by the first core network device should support the target network slice carried in the first request message.
  • the first core network device may select the second core network device according to the received DNN information carried in the first request message.
  • the second core network device selected by the first core network device should support communication with the external network indicated by the DNN information.
  • the first core network device may select the second core network device according to the received service network identifier information carried in the first request message.
  • the second core network device selected by the first core network device should support communication with the service network indicated by the service network identification information.
  • the first core network device selects the second core network device, and the first core network device selects according to the local configuration of the first core network device and/or the subscription information of the terminal device.
  • the second core network device selects the first core network device.
  • the subscription information of the terminal device includes at least one of the following information: information about a network slice subscribed by the terminal device, information of an external server that the terminal device subscribes to, and an external service function that is signed by the terminal device. information.
  • the local configuration of the first core network device includes information of a second core network device that can communicate with the first core network device.
  • the first core network device may The second core network device is selected according to the local configuration of the first core network device and/or the subscription information of the terminal device.
  • the local configuration of the first core network device includes information of a second core network device capable of communicating with the first core network device, and the first core network device may be from a core network device capable of communicating with the first core network device Selecting a second core network device for establishing the target transmission path, thereby transmitting a second request message to the selected second core network device.
  • the subscription information of the terminal device includes the network slice information that is signed by the terminal device
  • the subscription information of the terminal device includes the network slice information that is signed by the terminal device
  • only one of the network slices that are subscribed to the target network slice may be sliced, and then the first request information is not required to be carried.
  • the information of the target network slice, and the first core network device can obtain the network slice applied by the target transmission path that it requests to establish from the subscription information of the terminal device.
  • the subscription information of the terminal device includes information of an external server subscribed to by the terminal device and/or information about an external service function subscribed by the terminal device, for some terminal devices, the contracted external server and/or external service function There may be only one, then the first request information is not required to carry the information of the external server and/or the external service function, and the first core network device can obtain the target transmission requested by the first core network device from the subscription information of the terminal device.
  • the first core network device receives the first request message sent by the terminal device.
  • step 220 after receiving the downlink data transmitted through the target transmission path, the first core network device sends the downlink data to the terminal device.
  • the terminal device sends the first request message to the first core network device, and the first core network device agrees to establish the target transmission path and serves as a transmission node of the target transmission path, and sends the first to the second core network device.
  • the second core network device also agrees to be the transmission node of the target transmission path, if no other core network device is needed, the target transmission path is established, and the target transmission path includes the first core network device and the second Core network equipment.
  • the second core network device sends the downlink data to the first core network device in the target transmission path applied to the same network slice according to the device identifier of the terminal device and the network slice corresponding to the downlink data. And sent by the first core network device to the terminal device.
  • the first core network device receives the first request message sent by the third core network device.
  • the third core network device is any one of the following: an AMF device, an SMF device, a UPF device, a device that is configured with an SMF and a UPF, and a gateway that connects the external network element.
  • the third core network device sends the downlink data to the terminal device by using the third core network device.
  • the terminal device sends the first request message to the third core network device, and the third core network device agrees to establish the target transmission path and serves as a transmission node of the target transmission path, and sends the first to the first core network device.
  • a request message the first core network device also agrees to be the transport node of the target transmission path. If no other core network device is needed, the target transmission path is established, and the target transmission path includes the third core network device and the first core network device.
  • the first core network device sends the downlink data to the third core network device in the target transmission path applied to the same network slice according to the device identifier of the terminal device and the network slice corresponding to the downlink data. And sent by the third core network device to the terminal device.
  • the first core network device may further send a second request message to the second core network device, if the second core network
  • the device also agrees to be the transport node of the target transmission path, and the target transmission path includes the third core network device, the first core network device, and the second core network device.
  • the downlink data arrives, the downlink data is sequentially sent to the terminal device through the second network device, the first network device, and the third network device.
  • the method further includes: the first core network device acquiring information about the third core network device, and according to The information of the third core network device determines the third core network device.
  • the first core network device may obtain information about the third core network device from the UDM device; or the first core network device obtains information about the third core network device stored in the first core network device. .
  • the registration information of the terminal device may be sent to the UDM device, and after receiving the registration information of the terminal device sent by each transmission node on the target transmission path, the UDM receives the registration information of the terminal device. Saving the information is equivalent to recording the information of each transmission node in the target transmission path.
  • each core network device can obtain information of each transmission node in the target transmission path from the UDM, thereby receiving The downlink data can be addressed to the next core network device and sent to the next core network device.
  • the information of the third core network device to which the first request message is sent may be recorded, so that when the downlink data is received, it is required to The third core network device sends the downlink data.
  • the terminal device may request to establish different target transmission paths for different network slices.
  • the UDM device can save the target transmission path corresponding to each network slice.
  • the target transmission path 1 is applied to the network slice of the IoT service, including AMF1 and SMF1;
  • the target transmission path 2 is applied to the network slice of the Enhanced Mobile Broadband (eMBB) service, including AMF1 and SMF2;
  • the target transmission path 3 is applied.
  • Network slicing of the Ultra Reliable & Low Latency Communication (URLLC) service including AMF2 and SMF3.
  • URLLC Ultra Reliable & Low Latency Communication
  • the method further includes: the first core network device sends a response message for the first request message, where the response message is used to indicate whether the target transmission path is established.
  • the first core network device may respond to the terminal device or the third core network device, and the response message indicates that the target transmission path fails to be established;
  • the first core network device agrees to be the transmission node of the target transmission path, and after the target transmission path is established, the first network device responds to the first request message, where the response message indicates that the target transmission path is established;
  • the first core network device agrees to be the transmission node of the target transmission path, and sends a second request message to the second core network device, where the second core network device does not agree to be the transmission node of the target transmission path, And sending, to the first core network device, a response message indicating that the target transmission path establishment fails, and the first core network device is configured to send a response message indicating that the target transmission path establishment fails to the third core network device or the terminal device.
  • the second core network device When the second core network device agrees to be the transmission node of the target transmission path, it sends a response message indicating that the target transmission path is completed to the first core network device, and the first core network device is thus directed to the third core network device or terminal. The device sends a response message indicating that the target transmission path is established.
  • FIG. 1 A terminal device, an access network device, an AMF device, an SMF device, an SMF device, a UPF device, and a UDM device are shown in FIG.
  • the terminal device sends the first request message to the AMF device by using the access network device.
  • the first request message is used to request the AMF device to be a transit node of a target transmission path based on a non-PDU session connection to be established.
  • the first request message is, for example, a registration request, requesting registration of the terminal device on the first core network device.
  • the first request message may, for example, carry at least one of information of a target network slice applied by the target transmission path, DNN information of the terminal device, and service network identification information of the terminal device.
  • the AMF device determines whether it is a transmission node of the target transmission path.
  • the AMF device may determine, according to the first request message, whether the target network slice of the target transmission path request application is the terminal device.
  • the allowed network slice is the network slice subscribed by the terminal device. If the target network slice is a network slice subscribed by the terminal device, the first core network device determines a transmission node that can serve as the target transmission path.
  • the AMF device selects the SMF device.
  • the AMF device may select the SMF device according to the information carried by the first request message.
  • the AMF device may select an SMF device that supports the target network slice.
  • the SMF device selected by the AMF device needs to support the external network indicated by the DNN information.
  • the SMF device selected by the AMF device needs to support the service network indicated by the service network identifier information.
  • the AMF device may select the SMF according to the local configuration of the AMF device and/or the subscription information of the terminal device. device.
  • the network slice signed in the subscription information of the terminal device is the target network slice applied by the target transmission path.
  • the AMF device can acquire the target network slice according to the subscription information of the terminal device, and select an SMF device that supports the target network slice.
  • the AMF device sends a second request message to the SMF device.
  • the second request message is used to request the SMF device to be the transit node of the target transmission path to be established.
  • the second request message is, for example, a registration request, requesting registration of the terminal device on the second core network device.
  • the second request message may, for example, carry at least one of information of a target network slice applied by the target transmission path, DNN information of the terminal device, and service network identification information of the terminal device.
  • the SMF device determines whether it is a transmission node of the target transmission path.
  • the SMF device selects the UPF device.
  • the SMF device may select the UPF device according to the information carried in the first request message.
  • the SMF device may select a UPF device that supports the target network slice.
  • the UPF device selected by the SMF device needs to support an external network indicated by the DNN information.
  • the UPF device selected by the SMF device needs to support the service network indicated by the service network identifier information.
  • the second request message does not carry the information of the target network slice, the DNN information, and the service network identifier information
  • the SMF device may select the UPF according to the local configuration of the SMF device and/or the subscription information of the terminal device. device.
  • the network slice signed in the subscription information of the terminal device is the target network slice applied by the target transmission path.
  • the SMF device can acquire the target network slice according to the subscription information of the terminal device, and select a UPF device that supports the target network slice.
  • a response message indicating that the target transmission path establishment failure may be sent to the AMF device, and the AMF device transmits a response message indicating that the target transmission path establishment failure has been sent to the terminal device.
  • the SMF device sends a third request message to the UPF device.
  • the third request message is used to request the UPF device as the transit node of the target transmission path to be established.
  • the third request message is, for example, a registration request, requesting registration of the terminal device on the third core network device.
  • the third request message may, for example, carry at least one of information of a target network slice applied by the target transmission path, DNN information of the terminal device, and service network identification information of the terminal device.
  • the UPF device determines whether it is a transmission node of the target transmission path.
  • the UPF device determines a transmission node that is the target transmission path, the UPF device sends a response message to the SMF device.
  • the response message indicates that the target transmission path is established.
  • the SMF device after receiving the response message sent by the UPF device, the SMF device sends a response message to the AMF device.
  • the response message indicates that the target transmission path is established.
  • the AMF device after receiving the response message sent by the SMF device, the AMF device sends a response message to the terminal device.
  • the response message indicates that the target transmission path is established.
  • the registration information of the terminal device on each device is separately sent to the UDM device.
  • the UDM device After receiving the registration information reported by the AMF device, the SMF device, and the UPF device, the UDM device records the AMF device, the SMF device, and the UPF device in each transmission node, that is, the recording target transmission path, thereby completing the establishment of the target transmission path. .
  • the UDM may record a target transmission path for a different network slice's target transmission path, a different external server, or an external service function.
  • a response message indicating that the target transmission path establishment failure may be sent to the SMF device, and the SMF device sends an indication to the AMF device indicating that the target transmission path is established.
  • the AMF device sends a response message to the terminal device indicating that the target transmission path establishment failed.
  • the terminal device may establish another transmission path, for example, based on a transmission path of the PDU session connection.
  • the UPF device may obtain the target transmission applied to the target network slice from the UDM device according to the UE ID of the terminal device and the target network slice corresponding to the downlink data.
  • the path and the downlink data is sent to the SMF device in the target transmission path.
  • the SMF device acquires the information of the target transmission path from the UDM device, and sends the downlink data to the AMF device in the target transmission path.
  • the AMF device performs paging to the terminal device.
  • the terminal device responds to the paging, the AMF device encapsulates the downlink data into an ANS PDU and sends the downlink data to the terminal device through the access network device.
  • the terminal device sends a request message to the core network device to register on different core network devices.
  • the registered core network device serves as a transmission node of the target transmission path, so that in the absence of a PDU session connection, the terminal device can still perform data transmission through the target transmission path, that is, through the registered transmission nodes.
  • FIG. 4 is a schematic flowchart of a method 400 for establishing a transmission path according to an embodiment of the present application.
  • the method 400 shown in FIG. 4 can be performed by a terminal device, which can be, for example, the terminal device 120 of FIG.
  • the method 400 includes:
  • the terminal device sends a first request message to the first core network device.
  • the first request message is used to request the first core network device to be a transit node of a target transmission path based on a non-PDU session connection to be established.
  • the first request message may be sent to the first core network device, where the first request message is used to request to establish a target transmission path based on the non-PDU session connection. And requesting the first core network device as a transmission node of the target transmission path.
  • the first request message may be, for example, a registration request message, for requesting registration of the terminal device on the first core network device, and the core network device registered by the terminal device may form a transmission path, that is, the target The transmission path is such that data can be transmitted to the terminal device through the registered core network devices.
  • the first request message carries at least one of the following information: information of a target network slice to which the target transmission path is applied, data network name DNN information of the terminal device, and service network identification information of the terminal device.
  • This information can be used by the first core network device to determine whether to act as a transport node for the target transmission path.
  • the method further includes: receiving, by the terminal device, a response message sent by the first core network device, where the response message is used to indicate whether the first core network device is a transit node of the target transmission path.
  • the first core network device determines that the target transmission path can be established and the first core network device serves as the transmission node of the target transmission path, then the next transmission node of the target transmission path can continue to be searched, for example, as described in FIG. The second core network device, thereby completing the establishment of the target transmission path.
  • the terminal device may receive the downlink data that is sent by the first core network device and is transmitted through the target transmission path.
  • the terminal device sends a request message to the core network device to register on different core network devices.
  • the registered core network device serves as a transmission node of the target transmission path, so that in the absence of a PDU session connection, the terminal device can still perform data transmission through the target transmission path, that is, through the registered transmission nodes.
  • the process performed by the terminal device may refer to the foregoing description of the terminal device in FIG. 2 and FIG. 3, and details are not described herein for brevity.
  • the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be implemented in the present application.
  • the implementation of the examples constitutes any limitation.
  • FIG. 5 is a schematic block diagram of a core network device 500 in accordance with an embodiment of the present application.
  • the core network device 500 is a first core network device, and the first core network device includes a transceiver unit 510 and a processing unit 520, where:
  • the transceiver unit 510 is configured to receive a first request message, where the first request message is used to request the first core network device to be a transit node of a target transmission path based on a PDU session connection to be established;
  • the processing unit 520 is configured to determine whether it is a transmission node of the target transmission path.
  • the terminal device sends a request message to the core network device to register on different core network devices.
  • the registered core network device serves as a transmission node of the target transmission path, so that in the absence of a PDU session connection, the terminal device can still perform data transmission through the target transmission path, that is, through the registered transmission nodes.
  • the processing unit 520 is specifically configured to: if the target transmission path meets at least one of the following conditions, determine a transit node that is the target transmission path:
  • the target network slice to which the target transmission path is applied is a network slice signed by the terminal device, an external server to which the external transmission server applied by the target transmission path is contracted, and an external service applied by the target transmission path.
  • the function is an external service function signed by the terminal device.
  • the transceiver unit 510 is further configured to: obtain, from the unified data management UDM or the network slice selection function NSSF, information about a network slice subscribed by the terminal device, information and an external server that is subscribed by the terminal device. Information about the external service function signed by the terminal device.
  • the processing unit 520 is further configured to: select a second core network device; the transceiver unit 510 is further configured to: The second core network device sends a second request message, where the second request message is used to request the second core network device to be the transit node of the target transmission path to be established.
  • the processing unit 520 is specifically configured to: select, according to the first request message, the second core network device, where the first request message carries at least one of the following information: the target Information of a target network slice to which the transmission path is applied, data network name DNN information of the terminal device, and service network identification information of the terminal device.
  • the processing unit 520 is specifically configured to select the second core network device according to the local configuration of the first core network device and/or the subscription information of the terminal device.
  • the subscription information of the terminal device includes at least one of the following information: information of a network slice subscribed by the terminal device, information of an external server subscribed by the terminal device, and an external service function signed by the terminal device.
  • Information, the local configuration of the first core network device includes information of a second core network device capable of communicating with the first core network device.
  • the transceiver unit 510 is specifically configured to: receive the first request message sent by the terminal device.
  • the transceiver unit 510 is further configured to: after receiving downlink data transmitted by using the target transmission path, send the downlink data to the terminal device.
  • the transceiver unit 510 is specifically configured to: receive the first request message sent by the third core network device.
  • the transceiver unit 510 is further configured to: receive downlink data that is transmitted by using the target transmission path, and send the downlink data to the terminal device by using the third core network device.
  • the processing unit 520 is further configured to: acquire, by the transceiver unit 510, information of the third core network device from a UDM device; or acquire the foregoing stored in the first core network device. Information about the third core network device.
  • the transceiver unit 510 is further configured to: send a response message for the first request message, where the response message is used to indicate whether the target transmission path is established.
  • the third core network device is any one of the following: an access and mobility management function AMF device, a session management function SMF device, a user plane function UPF device, and a device that is combined with an SMF and a UPF. And a gateway that connects to external network elements.
  • the second core network device is any one of the following: an AMF device, an SMF device, a UPF device, a device that is configured with an SMF and a UPF, and a gateway that connects the external network element.
  • the first core network device is any one of the following: an AMF device, an SMF device, a UPF device, a device that is configured with an SMF and a UPF, and a gateway that connects the external network element.
  • the core network device 500 can perform the corresponding operations performed by the first core network device in the foregoing method 200, and details are not described herein for brevity.
  • FIG. 6 is a schematic block diagram of a terminal device 600 according to an embodiment of the present application. As shown in FIG. 6, the terminal device 600 includes a processing unit 610 and a transceiver unit 620, where:
  • the processing unit 610 is configured to generate a first request message, where the first request message is used to request the first core network device to be the transit node of the target transmission path based on the non-protocol data unit PDU session connection to be established.
  • the transceiver unit 620 is configured to send the first request message generated by the processing unit 610 to the first core network device.
  • the terminal device sends a request message to the core network device to register on different core network devices.
  • the registered core network device serves as a transmission node of the target transmission path, so that in the absence of a PDU session connection, the terminal device can still perform data transmission through the target transmission path, that is, through the registered transmission nodes.
  • the first request message carries at least one of the following information: information of a target network slice to which the target transmission path is applied, data network name DNN information of the terminal device, and service of the terminal device. Network identification information.
  • the transceiver unit 620 is further configured to: receive a response message sent by the first core network device, where the response message is used to indicate whether the target transmission path is established.
  • the transceiver unit 620 is further configured to: receive downlink data that is sent by the first core network device and that is transmitted through the target transmission path.
  • the first core network device is any one of the following: an access and mobility management function AMF device, a session management function SMF device, a user plane function UPF device, and a device that is equipped with an SMF and a UPF. And a gateway that connects to external network elements.
  • terminal device 600 can perform the corresponding operations performed by the terminal device in the foregoing method 400, and details are not described herein for brevity.
  • FIG. 7 is a schematic structural diagram of a communication device 700 according to an embodiment of the present application.
  • the communication device includes a processor 710, a transceiver 720, and a memory 730, wherein the processor 710, the transceiver 720, and the memory 730 communicate with each other through an internal connection path.
  • the memory 730 is configured to store instructions for executing the instructions stored by the memory 730 to control the transceiver 720 to receive signals or transmit signals.
  • the processor 710 can call the program code stored in the memory 730 to perform the corresponding operation of the first core network device in the method 200.
  • the processor 710 can call the program code stored in the memory 730 to perform the corresponding operation of the first core network device in the method 200.
  • the processor 710 can call the program code stored in the memory 730 to perform the corresponding operations performed by the terminal device in the method 400.
  • the processor 710 can call the program code stored in the memory 730 to perform the corresponding operations performed by the terminal device in the method 400.
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • 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 or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.
  • 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 may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • SDRAM Double Data Rate SDRAM
  • DDR SDRAM Double Data Rate SDRAM
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SLDRAM Synchronous Connection Dynamic Random Access Memory
  • DR RAM direct memory bus random access memory
  • FIG. 8 is a schematic structural diagram of a system chip according to an embodiment of the present application.
  • the system chip 800 of FIG. 8 includes an input interface 801, an output interface 802, at least one processor 803, and a memory 804.
  • the input interface 801, the output interface 802, the processor 803, and the memory 804 are interconnected by an internal connection path.
  • the processor 803 is configured to execute code in the memory 804.
  • the processor 1503 can implement a corresponding operation in the method 200 performed by the first core network device. For the sake of brevity, it will not be repeated here.
  • the processor 1503 can implement a corresponding operation performed by the terminal device in the method 400. For the sake of brevity, it will not be repeated here.
  • B corresponding to (corresponding to) A means that B is associated with A, and B can be determined according to A.
  • determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • 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, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one monitoring unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请公开了一种建立传输路径的方法和设备，包括：第一核心网设备接收第一请求消息，所述第一请求消息用于请求所述第一核心网设备作为待建立的基于非协议数据单元PDU会话连接的目标传输路径的传输节点；所述第一核心网设备确定是否作为所述目标传输路径的传输节点。因此，终端设备向核心网设备发送请求消息，以在不同核心网设备上进行注册。注册过的核心网设备作为该目标传输路径的传输节点，从而在不存在PDU会话连接的情况下，终端设备仍能够通过该目标传输路径即通过注册过的这些传输节点进行数据传输。

Description

建立传输路径的方法和设备 技术领域
本申请实施例涉及通信领域，并且更具体地，涉及建立传输路径的方法和设备。
背景技术
在未来的通信系统中，将会有大量的物联网(Internet of things，IoT)设备存在于网络中。当需要向这些IoT设备传输小数据时，可以通过建立PDU会话(PDU session)连接，从而将小数据封装为非接入层(Non Access Stratum，NAS)协议数据单元(Protocol Data Unit，PDU)进行传输。但是，当不存在PDU会话(Session)连接时，这些小数据如何传输就成为亟待解决的问题。
发明内容
本申请实施例提供了一种建立传输路径的方法和设备，能够在不建立PDU会话连接的情况下实现数据传输。
第一方面，提供了一种建立传输路径的方法，包括：第一核心网设备接收第一请求消息，所述第一请求消息用于请求所述第一核心网设备作为待建立的基于非协议数据单元PDU会话连接的目标传输路径的传输节点；所述第一核心网设备确定是否作为所述目标传输路径的传输节点。
因此，终端设备向核心网设备发送请求消息，以在不同核心网设备上进行注册。注册过的核心网设备作为该目标传输路径的传输节点，从而在不存在PDU会话连接的情况下，终端设备仍能够通过该目标传输路径即通过注册过的这些传输节点进行数据传输。
结合第一方面，在第一方面的一种可能的实现方式中，所述第一核心网设备确定是否作为所述目标传输路径的传输节点，包括：
若所述目标传输路径满足以下条件中的至少一个条件，则所述第一核心网设备确定作为所述目标传输路径的传输节点：
所述目标传输路径所应用的目标网络切片为终端设备签约的网络切片、所述目标传输路径所应用的外部服务器为所述终端设备签约的外部服务器、以及所述目标传输路径所应用的外部服务功能为所述终端设备签约的外部服务功能。
结合第一方面或上述任一种可能的实现方式，在第一方面的另一种可能的实现方式中，所述方法还包括：所述第一核心网设备从统一数据管理UDM或者网络片选择功能NSSF中，获取所述终端设备签约的网络切片的信息、所述终端设备签约的外部服务器的信息和所述终端设备签约的外部服务功能的信息。
结合第一方面或上述任一种可能的实现方式，在第一方面的另一种可能的实现方式中，若所述第一核心网设备确定作为所述目标传输路径的传输节点，所述方法还包括：所述第一核心网设备选择第二核心网设备；所述第一核心网设备向所述第二核心网设备发送第二请求消息，所述第二请求消息用于请求所述第二核心网设备作为待建立的所述目标传输路径的传输节点。
结合第一方面或上述任一种可能的实现方式，在第一方面的另一种可能的实现方式中，所述第一核心网设备选择第二核心网设备，包括：所述第一核心网设备根据所述第一请求消息，选择所述第二核心网设备，其中，所述第一请求消息携带以下信息中的至少一种：所述目标传输路径所应用的目标网络切片的信息、所述终端设备的数据网络名称DNN信息和所述终端设备的服务网络标识信息。
结合第一方面或上述任一种可能的实现方式，在第一方面的另一种可能的实现方式中，所述第一核心网设备选择第二核心网设备，包括：所述第一核心网设备根据所述第一核心网设备的本地配置和/或所述终端设备的签约信息，选择所述第二核心网设备。
其中，可选地，所述终端设备的签约信息包括以下信息中的至少一种：所述终端设备签约的网络切片的信息、所述终端设备签约的外部服务器的信息和所述终端设备签约的外部服务功能的信息，所述第一核心网设备的本地配置包括能够与所述第一核心网设备通信的第二核心网设备的信息。
结合第一方面或上述任一种可能的实现方式，在第一方面的另一种可能的实现方式中，所述第一核心网设备接收第一请求消息，包括：所述第一核心网设备接收终端设备发送的所述第一请求消息。
结合第一方面或上述任一种可能的实现方式，在第一方面的另一种可能的实现方式中，所述方法还包括：所述第一核心网设备接收到通过所述目标传输路径传输的下行数据后，向所述终端设备发送所述下行数据。
结合第一方面或上述任一种可能的实现方式，在第一方面的另一种可能的实现方式中，所述第一核心网设备接收第一请求消息，包括：所述第一核心网设备接收第三核心网设备发送的所述第一请求消息。
结合第一方面或上述任一种可能的实现方式，在第一方面的另一种可能的实现方式中，所述方法还包括：所述第一核心网设备接收到通过所述目标传输路径传输的下行数据后，通过所述第三核心网设备向所述终端设备发送所述下行数据。
结合第一方面或上述任一种可能的实现方式，在第一方面的另一种可能的实现方式中，所述第一核心网设备通过所述第三核心网设备向所述终端设备发送所述下行数据之前，所述方法还包括：所述第一核心网设备获取所述第三核心网设备的信息，并根据所述第三核心网设备的信息，确定所述第三核心网设备。
结合第一方面或上述任一种可能的实现方式，在第一方面的另一种可能的实现方式中，所述第一核心网设备获取所述第三核心网设备的信息，包括：所述第一核心网设备从UDM设备中获取所述第三核心网设备的信息；或者，所述第一核心网设备获取存储在所述第一核心网设备中的所述第三核心网设备的信息。
结合第一方面或上述任一种可能的实现方式，在第一方面的另一种可能的实现方式中，所述方法还包括：所述第一核心网设备发送针对所述第一请求消息的响应消息，所述响应消息用于指示所述目标传输路径是否建立完成。
结合第一方面或上述任一种可能的实现方式，在第一方面的另一种可能的实现方式中，所述第三核心网设备为以下设备中的任意一种：接入和移动性管理功能AMF设备、会话管理功能SMF设备、用户平面功能UPF设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
结合第一方面或上述任一种可能的实现方式，在第一方面的另一种可能的实现方式中，所述第二核心网设备为以下设备中的任意一种：AMF设备、SMF设备、UPF设备、合设有SMF和UPF的设备、和连接外部网元的网关。
结合第一方面或上述任一种可能的实现方式，在第一方面的另一种可能的实现方式中，所述第一核心网设备为以下设备中的任意一种：AMF设备、SMF设备、UPF设备、合设有SMF和UPF的设备、和连接外部网元的网关。
第二方面，提供了一种建立传输路径的方法，包括：终端设备向第一核心网设备发送第一请求消息，所述第一请求消息用于请求所述第一核心网设备作为待建立的基于非协议数据单元PDU会话连接的目标传输路径的传输节点。
因此，终端设备向核心网设备发送请求消息，以在不同核心网设备上进行注册。注册过的核心网设备作为该目标传输路径的传输节点，从而在不存在PDU会话连接的情况下，终端设备仍能够通过该目标传输路径即通过注册过的这些传输节点进行数据传输。
结合第二方面，在第二方面的一种可能的实现方式中，所述第一请求消息携带以下信息中的至少一种：所述目标传输路径所应用的目标网络切片的信息、所述终端设备的数据网络名称DNN信息和所述终端设备的服务网络标识信息。
结合第二方面或上述任一种可能的实现方式，在第二方面的另一种可能的实现方式中，所述方法还包括：所述终端设备接收所述第一核心网设备发送的响应消息，所述响应消息用于指示所述目标传输路径是否建立完成。
结合第二方面或上述任一种可能的实现方式，在第二方面的另一种可能的实现方式中，所述方法还包括：所述终端设备接收所述第一核心网设备发送的经过所述目标传输路径传输的下行数据。
结合第二方面或上述任一种可能的实现方式，在第二方面的另一种可能的实现方式中，所述第一核心网设备为以下设备中的任意一种：接入和移动性管理功能AMF设备、会话管理功能SMF设备、用户平面功能UPF设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
第三方面，提供了一种核心网设备，该核心网设备可以执行上述第一方面或第一方面的任意可选的实现方式中的核心网设备的操作。具体地，该核心网设备可以包括用于执行上述第一方面或第一方面的任意可能的实现方式中的第一核心网设备。
第四方面，提供了一种终端设备，该终端设备可以执行上述第二方面或第二方面的任意可选的实现方式中的终端设备的操作。具体地，该终端设备可以包括用于执行上述第二方面或第二方面的任意可能的实现方式中的终端设备。
第五方面，提供了一种核心网设备，该核心网设备包括：处理器、收发器和存储器。其中，该处理器、收发器和存储器之间通过内部连接通路互相通信。该存储器用于存储指令，该处理器用于执行该存储器存储的指令。当该处理器执行该存储器存储的指令时，该执行使得该核心网设备执行第一方面或第一方面的任意可能的实现方式中的方法，或者该执行使得该核心网设备实现第三方面提供的第一核心网设备。
第六方面，提供了一种终端设备，该终端设备包括：处理器、收发器和存储器。其中，该处理器、收发器和存储器之间通过内部连接通路互相通信。该存储器用于存储指令，该处理器用于执行该存储器存储的指令。当该处理器执行该存储器存储的指令时，该执行使得该终端设备执行第二方面或第二方面的任意可能的实现方式中的方法，或者该执行使得该终端设备实现第四方面提供的终端设备。
第七方面，提供了一种系统芯片，该系统芯片包括输入接口、输出接口、处理器和存储器，该处理器用于执行该存储器存储的指令，当该指令被执行时，该处理器可以实现前述第一方面或第一方面的任意可能的实现方式中的方法。
第八方面，提供了一种系统芯片，该系统芯片包括输入接口、输出接口、处理器和存储器，该处理器用于执行该存储器存储的指令，当该指令被执行时，该处理器可以实现前述第二方面或第二方面的任意可能的实现方式中的方法。
第九方面，提供了一种包括指令的计算机程序产品，当所述计算机程序产品在计算机上运行时，使得该计算机执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第十方面，提供了一种包括指令的计算机程序产品，当所述计算机程序产品在计算机上运行时，使得该计算机执行上述第二方面或第二方面的任意可能的实现方式中的方法。
附图说明
图1是本申请实施例应用的一种可能的无线通信系统的示意图。
图2是本申请实施例的建立传输路径的方法的示意性流程图。
图3是本申请实施例的建立传输路径的方法的流程交互图。
图4是本申请实施例的建立传输路径的方法的示意性流程图。
图5是本申请实施例的核心网设备的示意性框图。
图6是本申请实施例的终端设备的示意性框图。
图7是本申请实施例的通信设备的示意性结构图。
图8是本申请实施例的系统芯片的示意性结构图。
具体实施方式
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(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”)、通用移动通信系统(Universal Mobile Telecommunication System，简称为“UMTS”)、全球互联微波接入(Worldwide Interoperability for Microwave Access，简称为“WiMAX”)通信系统或未来的5G系统等。
图1示出了本申请实施例应用的无线通信系统100。该无线通信系统100可以包括接入网设备110。接入网设备110可以是与终端设备通信的设备。接入网设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备(例如UE)进行通信。可选地，该接入网设备110可以是GSM系统或CDMA系统中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional NodeB，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该接入网设备110可以为中继站、接入点、车载设备、可穿戴设备、未来5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。该接入网设备110还可以为演进的通用陆地无线接入网(Evolved Universal Terrestrial Radio Access Network，E-UTRAN)或者下一代无线接入网络(Next Generation Radio Access Network，NG-RAN)。
该无线通信系统100还可以包括与接入网设备进行通信的核心网设备130。可选地，该核心网设备130可以是LTE网络的分组核心演进(Evolved Packet Core，EPC)；也可以是5G核心网设备(5G Core，5GC)例如接入与移动性管理功能(Access and Mobility Management Function，AMF)或者会话管理功能(Session Management Function，SMF)。可选地，核心网络设备130也可以是LTE网络的分组核心演进(Evolved Packet Core，EPC)设备，例如，会话管理功能+核心网络的数据网关(Session Management Function+Core Packet Gateway，SMF+PGW-C)设备。应理解，SMF+PGW-C可以同时实现SMF和PGW-C所能实现的功能。
该无线通信系统100还可以包括位于网络设备110覆盖范围内的至少一个终端设备120。终端设备120可以是移动的或固定的。可选地，终端设备120可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、未来5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
图1示例性地示出了一个接入网设备、一个核心网设备和两个终端设备，可选地，该无线通信系统100可以包括多个接入网设备并且每个接入网设备的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。可选地，该无线通信系统100还可以包括移动管理实体(Mobile Management Entity，MME)、统一数据管理(Unified Data  Management，UDM)，认证服务器功能(Authentication Server Function，AUSF)、用户面功能(User Plane Function，UPF)、信令网关(Signaling Gateway，SGW)等其他网络实体，本申请实施例对此不作限定。应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
图2示出了本申请实施例的建立传输路径的方法200的示意性流程图。图2所示的方法200可以由第一核心网设备执行，该第一核心网设备例如可以为图1中的核心网设备130。如图2所示，该方法200包括以下部分或全部内容：
在210中，第一核心网设备接收第一请求消息。
其中，该第一请求消息用于请求该第一核心网设备作为待建立的基于非PDU会话连接的目标传输路径的传输节点。
在220中，该第一核心网设备确定是否作为该目标传输路径的传输节点。
具体地，第一核心网设备接收到的该第一请求消息，该第一请求消息用于请求建立基于非PDU会话连接的目标传输路径且请求该第一核心网设备作为该目标传输路径中的一个传输节点。该目标传输路径可以用于传输终端设备的下行数据例如向该终端设备传输被封装为NAS PDU的数据包。当该第一核心网设备接收到该第一请求消息后，确定是否作为该目标传输路径的传输节点。
该第一请求消息例如可以为注册请求消息(Registration Request)，用于请求在该第一核心网设备上对终端设备进行注册，该终端设备注册过的核心网设备可以组成一个传输路径即该目标传输路径，从而可以通过注册过的这些核心网设备向该终端设备传输数据。换句话说，该第一核心网设备作为该目标传输路径的传输节点，是通过终端设备在该第一核心网设备上完成注册来实现的，该终端设备在该第一核心网设备上完成注册表示该第一核心网该设备同意作为该目标传输路径的传输节点。
可选地，该第一核心网设备为以下设备中的任意一种：AMF设备、SMF设备、UPF设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
可选地，在220中，该第一核心网设备确定是否作为该目标传输路径的传输节点，包括：
若该目标传输路径满足以下条件中的至少一个条件，则该第一核心网设备确定作为该目标传输路径的传输节点：
该目标传输路径所应用的目标网络切片为终端设备签约的网络切片、该目标传输路径所应用的外部服务器为该终端设备签约的外部服务器、以及该目标传输路径所应用的外部服务功能为该终端设备签约的外部服务功能。
通过该第一请求消息请求建立基于非PDU会话连接的目标传输路径时，可以是针对某个特定的网络切片请求建立该目标传输路径，那么，该目标传输路径所应用的网络切片，即为该特定的网络切片。该特定的网络切片为该终端设备签约的网络切片时，该目标传输路径才可能建立。因此，该第一核心网设备接收到该第一请求消息后，会验证该目标网络切片是否为终端设备签约的网络切片。
当然，还可以针对某个特定的外部服务器请求建立该目标传输路径，这时，该目标传输路径所应用的外部服务器，即为该特定的外部服务器。该特定的外部服务器为该终端设备签约的外部服务器时，该目标传输路径才可能建立。因此，该第一核心网设备接收到该第一请求消息后，会验证该外部服务器是否为终端设备签约的外部服务器。
或者，还可以针对某个特定的外部服务功能请求建立该目标传输路径，这时，该目标传输路径所应用的外部服务功能，即为该特定的外部服务功能。该特定的外部服务功能为该终端设备签约的外部服务功能时，该目标传输路径才可能建立。因此，该第一核 心网设备接收到该第一请求消息后，会验证该外部服务功能是否为终端设备签约的外部服务功能。
如果所请求的该目标网络切片和/或外部服务器(外部服务功能)是允许的，那么该第一核心网设备确定可以在该目标网络切片上建立针对该外部服务器(外部服务功能)的该目标传输路径且该第一核心网设备可以作为该目标传输路径的一个传输节点；如果所请求的该目标网络切片和/或外部服务器(外部服务功能)是不允许的，那么该第一核心网设备确定不可以在该目标网络切片上建立针对该外部服务器(外部服务功能)的该目标传输路径，该第一核心网设备也不会作为该目标传输路径的传输节点。
可选地，该第一核心网设备可以从UDM设备或者网络片选择功能(Network Slice Selection Function，NSSF)设备中，获取该终端设备签约的网络切片的信息、该终端设备签约的外部服务器的信息和该终端设备签约的外部服务功能的信息。
即，该第一核心网可以从NSSF设备中获取该终端设备的允许的网络切片的信息，或者从UDM设备中获取该终端设备的签约信息，其中该签约信息包括终端设备签约的网络切片的信息、该终端设备签约的外部服务器的信息和该终端设备签约的外部服务功能的信息等。
可选地，在220中，若该第一核心网设备确定作为该目标传输路径的传输节点，则该方法还包括：
在230中，该第一核心网设备选择第二核心网设备。
在240中，该第一核心网设备向该第二核心网设备发送第二请求消息。
其中，该第二请求消息用于请求该第二核心网设备作为待建立的该目标传输路径的传输节点。
该第二请求消息例如可以为注册请求消息(Registration Request)，用于请求在该第二核心网设备上对终端设备进行注册，终端设备注册过的核心网设备可以组成一个传输路径即该目标传输路径，从而可以通过注册过的这些核心网设备向该终端设备传输数据。
可选地，该第二核心网设备为以下设备中的任意一种：AMF设备、SMF设备、UPF设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
具体地，当该第一核心网设备确定可以建立该目标传输路径且该第一核心网设备作为该目标传输路径的传输节点，那么还可以继续寻找该目标传输路径的下一个传输节点，例如这里的第二核心网设备即为被选择的下一个传输节点。第一核心网设备选择第二核心网设备后，向该第二核心网设备发送第二请求信息，以请求该第二核心网设备作为该目标传输路径的传输节点。
如果第二核心网设备也同意作为该目标传输路径的传输节点，那么该目标传输路径中至少包括第一核心网设备和第二核心网设备这两个传输节点。
进一步地，如果目标传输路径中还需要其他核心网设备时，该第二核心网设备还可以向其他核心网设备发送请求消息，以请求其他核心网设备作为该目标传输路径的传输节点，这时该目标传输路径还可能包括被请求的其他核心网设备。
可选地，目标传输路径中的传输节点比如该第一核心网设备和第二核心网设备，在完成传输节点的建立后，可以向UDM设备发送自己的信息，从而UDM设备存储该目标传输路径的信息即该目标传输路径中各传输节点的信息。
可选地，在230中，该第一核心网设备选择第二核心网设备，包括：该第一核心网设备根据该第一请求消息，选择该第二核心网设备。
其中，该第一请求消息携带以下信息中的至少一种：该目标传输路径所应用的目标网络切片的信息、该终端设备的数据网络名称(Data Network Name，DNN)信息和该终端设备的服务网络标识信息。
若该第一请求消息携带了该目标传输路径所应用的目标网络切片的信息，该第一核心网设备可以根据接收到的该第一请求消息中携带的该目标网络切片的信息，选择第二 核心网设备。该第一核心网设备所选择的该第二核心网设备应当支持该第一请求消息中携带的该目标网络切片。
若该第一请求消息携带了该终端设备的DNN信息，该第一核心网设备可以根据接收到的该第一请求消息中携带的该DNN信息，选择第二核心网设备。该第一核心网设备所选择的该第二核心网设备应当支持与该DNN信息指示的外部网络的通信。
若该第一请求消息携带了该终端设备的服务网络标识信息，该第一核心网设备可以根据接收到的该第一请求消息中携带的服务网络标识信息，选择第二核心网设备。该第一核心网设备所选择的该第二核心网设备应当支持与该服务网络标识信息指示的服务网络的通信。
可选地，在230中，该第一核心网设备选择第二核心网设备，包括：该第一核心网设备根据该第一核心网设备的本地配置和/或该终端设备的签约信息，选择该第二核心网设备。
其中，可选地，该终端设备的签约信息包括以下信息中的至少一种：该终端设备签约的网络切片的信息、该终端设备签约的外部服务器的信息和该终端设备签约的外部服务功能的信息。
其中，可选地，该第一核心网设备的本地配置包括能够与该第一核心网设备通信的第二核心网设备的信息。
若该第一请求消息不携带该目标传输路径所应用的目标网络切片的信息、该终端设备的数据网络名称DNN信息和该终端设备的服务网络标识信息等信息时，该第一核心网设备可以根据该第一核心网设备的本地配置和/或该终端设备的签约信息，选择该第二核心网设备。
该第一核心网设备的本地配置包括能够与该第一核心网设备通信的第二核心网设备的信息，该第一核心网设备可以从能够与该第一核心网设备通信的核心网设备中选择用于建立该目标传输路径的第二核心网设备，从而向所选择的第二核心网设备发送第二请求消息。
该终端设备的签约信息包括该终端设备签约的网络切片的信息时，对于某些终端设备，其签约的网络切片可能只有一个即该目标网络切片，那么此时无需该第一请求信息再携带该目标网络切片的信息，而第一核心网设备从终端设备的签约信息中就能够得到其请求建立的该目标传输路径所应用的网络切片。
同样，该终端设备的签约信息包括该终端设备签约的外部服务器的信息和/或该终端设备签约的外部服务功能的信息时，对于某些终端设备，其签约的外部服务器和/或外部服务功能可能只有一个，那么此时无需该第一请求信息再携带该外部服务器和/或外部服务功能的信息，而第一核心网设备从终端设备的签约信息中就能够得到其请求建立的该目标传输路径所应用的外部服务器和/或外部服务功能。
可选地，在210中，该第一核心网设备接收终端设备发送的该第一请求消息。
相应地，在220中，该第一核心网设备接收到通过该目标传输路径传输的下行数据后，向该终端设备发送该下行数据。
例如，终端设备向第一核心网设备发送了该第一请求消息，该第一核心网设备同意建立该目标传输路径且作为该目标传输路径的传输节点，并向第二核心网设备发送了第二请求消息，该第二核心网设备也同意作为该目标传输路径的传输节点后，若无需其他核心网设备，则该目标传输路径建立完成，该目标传输路径包括第一核心网设备和第二核心网设备。当下行数据到达时，该第二核心网设备根据终端设备的设备标识和该下行数据对应的网络切片，将该下行数据发送给应用于相同网络切片的目标传输路径中的该第一核心网设备，并由该第一核心网设备发送给终端设备。
可选地，在210中，该第一核心网设备接收第三核心网设备发送的该第一请求消息。
可选地，该第三核心网设备为以下设备中的任意一种：AMF设备、SMF设备、UPF 设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
相应地，在220中，该第一核心网设备接收到通过该目标传输路径传输的下行数据后，通过该第三核心网设备向该终端设备发送该下行数据。
例如，终端设备向第三核心网设备发送了该第一请求消息，该第三核心网设备同意建立该目标传输路径且作为该目标传输路径的传输节点，并向第一核心网设备发送了第一请求消息，该第一核心网设备也同意作为该目标传输路径的传输节点。若无需其他核心网设备，则该目标传输路径建立完成，该目标传输路径包括第三核心网设备和第一核心网设备。当下行数据到达时，该第一核心网设备根据终端设备的设备标识和该下行数据对应的网络切片，将该下行数据发送给应用于相同网络切片的目标传输路径中的该第三核心网设备，并由该第三核心网设备发送给终端设备。若该第一核心网设备同意作为该目标传输路径的传输节点后，仍需其他核心网设备，则第一核心网设备还可以向第二核心网设备发送第二请求消息，若第二核心网设备也同意作为该目标传输路径的传输节点，则该目标传输路径包括第三核心网设备、第一核心网设备和第二核心网设备。当下行数据到达时，该下行数据依次经过第二网络设备、第一网络设备和第三网络设备发送至该终端设备。
可选地，该第一核心网设备通过该第三核心网设备向该终端设备发送该下行数据之前，该方法还包括：该第一核心网设备获取该第三核心网设备的信息，并根据该第三核心网设备的信息，确定该第三核心网设备。
其中，该第一核心网设备可以从UDM设备中获取该第三核心网设备的信息；或者，该第一核心网设备获取存储在该第一核心网设备中的该第三核心网设备的信息。
例如，第一核网设备确定作为该目标传输路径的传输节点后，可以向该UDM设备发送终端设备的注册信息，UDM接收到目标传输路径上每个传输节点发送的终端设备的注册信息后，保存这些信息，相当于记录了该目标传输路径中各传输节点的信息，在进行数据传输时，每个核心网设备可以从该UDM中获取目标传输路径中各传输节点的信息，从而在接收到下行数据时可以寻址该下一个核心网设备并向下一个核心网设备发送该下行数据。
又例如，第一核心网设备确定作为该目标传输路径的传输节点后，可以记录向其发送第一请求消息的第三核心网设备的信息，从而在接收到下行数据时，就知道需要向第三核心网设备发送该下行数据。
应理解，终端设备针对不同的网络切片可以请求建立不同的目标传输路径。UDM设备可以保存每个网络切片对应的目标传输路径。例如目标传输路径1应用于IoT业务的网络切片，包括AMF1和SMF1；目标传输路径2应用于增强移动宽带(Enhance Mobile Broadband，eMBB)业务的网络切片，包括AMF1和SMF2；目标传输路径3应用于高可靠低时延通信(Ultra Reliable &Low Latency Communication，URLLC)业务的网络切片，包括AMF2和SMF3。
可选地，在220之后，该方法还包括：第一核心网设备发送针对该第一请求消息的响应消息，该响应消息用于指示该目标传输路径是否建立完成。
若第一核心网设备不同意作为该目标传输路径的传输节点，则该第一核心网设备可以向终端设备或第三核心网设备进行响应，该响应消息指示该目标传输路径建立失败；若该第一核心网设备同意作为该目标传输路径的传输节点，且至此目标传输路径建立完成，则该第一网设备针对该第一请求消息进行响应，该响应消息指示该目标传输路径建立完成；若该第一核心网设备同意作为该目标传输路径的传输节点，且向第二核心网设备发送了第二请求消息，那么该第二核心网设备不同意作为该目标传输路径的传输节点时，会向该第一核心网设备发送指示目标传输路径建立失败的响应消息，第一核心网设备从而向第三核心网设备或终端设备发送指示目标传输路径建立失败的响应消息。该第二核心网设备同意作为该目标传输路径的传输节点时，会向该第一核心网设备发送指示 目标传输路径建立完成的响应消息，第一核心网设备从而向第三核心网设备或终端设备发送指示目标传输路径建立完成的响应消息。
下面结合图3，举例描述本申请实施例的建立传输路径的方法。图3中示出了终端设备、接入网设备、AMF设备、SMF设备、SMF设备、UPF设备和UDM设备。
在301中，终端设备通过接入网设备向AMF设备发送该第一请求消息。
该第一请求消息用于请求该AMF设备作为待建立的基于非PDU会话连接的目标传输路径的传输节点。该第一请求消息例如为注册请求，请求在该第一核心网设备上进行终端设备的注册。
该第一请求消息例如可以携带该目标传输路径所应用的目标网络切片的信息、该终端设备的DNN信息和该终端设备的服务网络标识信息中的至少一种。
在302中，该AMF设备接收到该第一请求消息后，确定是否作为该目标传输路径的传输节点。
例如，该第一请求消息携带该目标传输路径所应用的目标网络切片的信息时，该AMF设备可以根据该第一请求消息，判断该目标传输路径请求应用的目标网络切片是否为该终端设备被允许的网络切片即该终端设备签约的网络切片，若该目标网络切片为该终端设备签约的网络切片，则第一核心网设备确定可以作为该目标传输路径的传输节点。
在303中，如果该AMF设备确定作为该目标传输路径的传输节点，则该AMF设备选择SMF设备。
其中，该AMF设备可以根据该第一请求消息携带的信息选择SMF设备。
例如，该第一请求消息携带该目标传输路径所应用的目标网络切片的信息时，该AMF设备可以选择支持该目标网络切片的SMF设备。
又例如，该第一请求消息携带该终端设备的DNN信息时，该AMF设备选择的SMF设备需要支持该DNN信息指示的外部网络。
又例如，该第一请求消息携带该终端设备的服务网络标识信息时，该AMF设备选择的SMF设备需要支持该服务网络标识信息指示的服务网络。
或者，该第一请求消息不携带该目标网络切片的信息、该DNN信息和该服务网络标识信息时，该AMF设备可以根据该AMF设备的本地配置和/或该终端设备的签约信息，选择SMF设备。
例如，该终端设备仅支持一种网络切片时，该终端设备的签约信息中所签约的网络切片即为该目标传输路径应用的目标网络切片。该AMF设备根据该终端设备的签约信息就能够获取该目标网络切片，并选择支持该目标网络切片的SMF设备。
在304中，AMF设备向SMF设备发送第二请求消息。
其中，该第二请求消息用于请求该SMF设备作为待建立的该目标传输路径的传输节点。该第二请求消息例如为注册请求，请求在该第二核心网设备上进行终端设备的注册。
该第二请求消息例如可以携带该目标传输路径所应用的目标网络切片的信息、该终端设备的DNN信息和该终端设备的服务网络标识信息中的至少一种。
在305中，SMF设备接收到该第二请求消息后，确定是否作为该目标传输路径的传输节点。
在306中，如果该SMF设备确定作为该目标传输路径的传输节点，则该SMF设备选择UPF设备。
其中，该SMF设备可以根据该第一请求消息携带的信息选择UPF设备。
例如，该第二请求消息携带该目标传输路径所应用的目标网络切片的信息时，该SMF设备可以选择支持该目标网络切片的UPF设备。
又例如，该第二请求消息携带该终端设备的DNN信息时，该SMF设备选择的UPF设备需要支持该DNN信息指示的外部网络。
又例如，该第二请求消息携带该终端设备的服务网络标识信息时，该SMF设备选择 的UPF设备需要支持该服务网络标识信息指示的服务网络。
或者，该第二请求消息不携带该目标网络切片的信息、该DNN信息和该服务网络标识信息，那么该SMF设备可以根据该SMF设备的本地配置和/或该终端设备的签约信息，选择UPF设备。
例如，该终端设备仅支持一种网络切片时，该终端设备的签约信息中所签约的网络切片即为该目标传输路径应用的目标网络切片。该SMF设备根据该终端设备的签约信息就能够获取该目标网络切片，并选择支持该目标网络切片的UPF设备。
当然，如果该SMF设备不同意作为该目标传输路径的传输节点，那么可以向AMF设备发送指示目标传输路径建立失败的响应消息，并且AMF设备向终端设备发送指示目标传输路径建立失败的响应消息。
在307中，SMF设备向UPF设备发送第三请求消息。
其中，该第三请求消息用于请求该UPF设备作为待建立的该目标传输路径的传输节点。该第三请求消息例如为注册请求，请求在该第三核心网设备上进行终端设备的注册。
该第三请求消息例如可以携带该目标传输路径所应用的目标网络切片的信息、该终端设备的DNN信息和该终端设备的服务网络标识信息中的至少一种。
在308中，UPF设备接收到该第二请求消息后，确定是否作为该目标传输路径的传输节点。
在309中，如果该UPF设备确定作为该目标传输路径的传输节点，则该UPF设备向该SMF设备发送响应消息。
其中，该响应消息指示该目标传输路径建立完成。
在310中，SMF设备接收到UPF设备发送的响应消息后，向AMF设备发送响应消息。
其中，该响应消息指示该目标传输路径建立完成。
在311中，AMF设备接收到SMF设备发送的响应消息后，向终端设备发送响应消息。
其中，该响应消息指示该目标传输路径建立完成。
在312中，AMF设备、SMF设备、UPF设备确定作为该目标传输路径的传输节点后，分别向UDM设备发送该终端设备在各设备上的注册信息。
在313中，UDM设备接收AMF设备、SMF设备、UPF设备上报的注册信息后，记录各传输节点即记录目标传输路径中的AMF设备、SMF设备、UPF设备，从而完成对该目标传输路径的建立。
可选地，该UDM可以记录针对不同网络切片的目标传输路径、不同外部服务器或外部服务功能的目标传输路径。
至此，该目标传输路径建立完成。
当然，在308中，如果该UPF设备不同意作为该目标传输路径的传输节点，那么可以向SMF设备发送指示目标传输路径建立失败的响应消息，并且该SMF设备向AMF设备发送指示目标传输路径建立失败的响应消息，AMF设备向终端设备发送指示目标传输路径建立失败的响应消息。那么终端设备接收到该响应消息后可以建立其他传输路径例如基于PDU会话连接的传输路径进行数据传输。
该目标传输路径建立完成后，当有下行数据到达UPF设备时，UPF设备可以根据终端设备的UE ID和该下行数据对应的目标网络切片，从UDM设备中获取应用于该目标网络切片的目标传输路径，并向该目标传输路径中的SMF设备发送该下行数据。该SMF设备接收到该下行数据后，从UDM设备中获取该目标传输路径的信息，并向该目标传输路径中的AMF设备发送该下行数据。该AMF设备接收到该下行数据后，向该终端设备进行寻呼，该终端设备响应该寻呼后，该AMF设备将该下行数据封装为ANS PDU并通过接入网设备发送给该终端设备。
因此，本申请实施例中，终端设备向核心网设备发送请求消息，以在不同核心网设备上进行注册。注册过的核心网设备作为该目标传输路径的传输节点，从而在不存在PDU会话连接的情况下，终端设备仍能够通过该目标传输路径即通过注册过的这些传输节点进行数据传输。
图4示出了本申请实施例的建立传输路径的方法400的示意性流程图。图4所示的方法400可以由终端设备执行，该终端设备例如可以为图1中的终端设备120。如图4所示，该方法400包括：
在410中，终端设备向第一核心网设备发送第一请求消息。
其中，该第一请求消息用于请求该第一核心网设备作为待建立的基于非PDU会话连接的目标传输路径的传输节点。
具体地，该终端设备需要建立基于非PDU会话连接的目标传输路径时，可以向第一核心网设备发送第一请求消息，该第一请求消息用于请求建立基于非PDU会话连接的目标传输路径且请求该第一核心网设备作为该目标传输路径的传输节点。该第一请求消息例如可以为注册请求消息(Registration Request)，用于请求在该第一核心网设备上对终端设备进行注册，该终端设备注册过的核心网设备可以组成一个传输路径即该目标传输路径，从而可以通过注册过的这些核心网设备向该终端设备传输数据。
可选地，该第一请求消息携带以下信息中的至少一种：该目标传输路径所应用的目标网络切片的信息、该终端设备的数据网络名称DNN信息和该终端设备的服务网络标识信息。
这些信息可以用于该第一核心网设备确定是否作为该目标传输路径的传输节点。
可选地，该方法还包括：该终端设备接收该第一核心网设备发送的响应消息，该响应消息用于指示该第一核心网设备是否作为该目标传输路径的传输节点。
当该第一核心网设备确定可以建立该目标传输路径且该第一核心网设备作为该目标传输路径的传输节点，那么还可以继续寻找该目标传输路径的下一个传输节点例如图2中所描述的第二核心网设备，从而完成该目标传输路径的建立。
可选地，该目标传输路径建立完成后，该终端设备可以接收该第一核心网设备发送的经过该目标传输路径传输的该下行数据。
因此，终端设备向核心网设备发送请求消息，以在不同核心网设备上进行注册。注册过的核心网设备作为该目标传输路径的传输节点，从而在不存在PDU会话连接的情况下，终端设备仍能够通过该目标传输路径即通过注册过的这些传输节点进行数据传输。
应理解，在方法400的该目标传输路径建立过程中，该终端设备执行的过程具体可以参考前述对图2和图3中的终端设备的描述，为了简洁，这里不再赘述。
还应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
上文中详细描述了根据本申请实施例的建立传输路径的方法，下面将结合图5至图8，描述根据本申请实施例的装置，方法实施例所描述的技术特征适用于以下装置实施例。
图5是根据本申请实施例的核心网设备500的示意性框图。如图5所示，该核心网设备500为第一核心网设备，该第一核心网设备包括收发单元510和处理单元520，其中：
收发单元510，用于接收第一请求消息，所述第一请求消息用于请求所述第一核心网设备作为待建立的基于PDU会话连接的目标传输路径的传输节点；
处理单元520，用于确定是否作为所述目标传输路径的传输节点。
因此，终端设备向核心网设备发送请求消息，以在不同核心网设备上进行注册。注册过的核心网设备作为该目标传输路径的传输节点，从而在不存在PDU会话连接的情况下，终端设备仍能够通过该目标传输路径即通过注册过的这些传输节点进行数据传输。
可选地，所述处理单元520具体用于：若所述目标传输路径满足以下条件中的至少 一个条件，则确定作为所述目标传输路径的传输节点：
所述目标传输路径所应用的目标网络切片为终端设备签约的网络切片、所述目标传输路径所应用的外部服务器为所述终端设备签约的外部服务器、以及所述目标传输路径所应用的外部服务功能为所述终端设备签约的外部服务功能。
可选地，所述收发单元510还用于：从统一数据管理UDM或者网络片选择功能NSSF中，获取所述终端设备签约的网络切片的信息、所述终端设备签约的外部服务器的信息和所述终端设备签约的外部服务功能的信息。
可选地，若所述第一核心网设备确定作为所述目标传输路径的传输节点，所述处理单元520还用于：选择第二核心网设备；所述收发单元510还用于：向所述第二核心网设备发送第二请求消息，所述第二请求消息用于请求所述第二核心网设备作为待建立的所述目标传输路径的传输节点。
可选地，所述处理单元520具体用于：根据所述第一请求消息，选择所述第二核心网设备，其中，所述第一请求消息携带以下信息中的至少一种：所述目标传输路径所应用的目标网络切片的信息、所述终端设备的数据网络名称DNN信息和所述终端设备的服务网络标识信息。
可选地，所述处理单元520具体用于：根据所述第一核心网设备的本地配置和/或所述终端设备的签约信息，选择所述第二核心网设备。
其中，所述终端设备的签约信息包括以下信息中的至少一种：所述终端设备签约的网络切片的信息、所述终端设备签约的外部服务器的信息和所述终端设备签约的外部服务功能的信息，所述第一核心网设备的本地配置包括能够与所述第一核心网设备通信的第二核心网设备的信息。
可选地，所述收发单元510具体用于：接收终端设备发送的所述第一请求消息。
可选地，所述收发单元510还用于：接收到通过所述目标传输路径传输的下行数据后，向所述终端设备发送所述下行数据。
可选地，所述收发单元510具体用于：接收第三核心网设备发送的所述第一请求消息。
可选地，所述收发单元510还用于：接收通过所述目标传输路径传输的下行数据，并通过所述第三核心网设备向所述终端设备发送所述下行数据。
可选地，所述处理单元520还用于：通过所述收发单元510从UDM设备中获取所述第三核心网设备的信息；或者，获取存储在所述第一核心网设备中的所述第三核心网设备的信息。
可选地，所述收发单元510还用于：发送针对所述第一请求消息的响应消息，所述响应消息用于指示所述目标传输路径是否建立完成。
可选地，所述第三核心网设备为以下设备中的任意一种：接入和移动性管理功能AMF设备、会话管理功能SMF设备、用户平面功能UPF设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
可选地，所述第二核心网设备为以下设备中的任意一种：AMF设备、SMF设备、UPF设备、合设有SMF和UPF的设备、和连接外部网元的网关。
可选地，所述第一核心网设备为以下设备中的任意一种：AMF设备、SMF设备、UPF设备、合设有SMF和UPF的设备、和连接外部网元的网关。
应理解，核心网设备500可以执行上述方法200中由第一核心网设备执行的相应操作，为了简洁，在此不再赘述。
图6是根据本申请实施例的终端设备600的示意性框图。如图6所示，该终端设备600包括处理单元610和收发单元620，其中：
处理单元610，用于生成第一请求消息，所述第一请求消息用于请求第一核心网设备作为待建立的基于非协议数据单元PDU会话连接的目标传输路径的传输节点。
收发单元620，用于向所述第一核心网设备发送所述处理单元610生成的所述第一请求消息。
因此，终端设备向核心网设备发送请求消息，以在不同核心网设备上进行注册。注册过的核心网设备作为该目标传输路径的传输节点，从而在不存在PDU会话连接的情况下，终端设备仍能够通过该目标传输路径即通过注册过的这些传输节点进行数据传输。
可选地，所述第一请求消息携带以下信息中的至少一种：所述目标传输路径所应用的目标网络切片的信息、所述终端设备的数据网络名称DNN信息和所述终端设备的服务网络标识信息。
可选地，所述收发单元620还用于：接收所述第一核心网设备发送的响应消息，所述响应消息用于指示所述目标传输路径是否建立完成。
可选地，所述收发单元620还用于：接收所述第一核心网设备发送的经过所述目标传输路径传输的下行数据。
可选地，所述第一核心网设备为以下设备中的任意一种：接入和移动性管理功能AMF设备、会话管理功能SMF设备、用户平面功能UPF设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
应理解，该终端设备600可以执行上述方法400中由终端设备执行的相应操作，为了简洁，在此不再赘述。
图7是根据本申请实施例的通信设备700的示意性结构图。如图7所示，该通信设备包括处理器710、收发器720和存储器730，其中，该处理器710、收发器720和存储器730之间通过内部连接通路互相通信。该存储器730用于存储指令，该处理器710用于执行该存储器730存储的指令，以控制该收发器720接收信号或发送信号。
可选地，该处理器710可以调用存储器730中存储的程序代码，执行方法200中由第一核心网设备的相应操作，为了简洁，在此不再赘述。
可选地，该处理器710可以调用存储器730中存储的程序代码，执行方法400中由终端设备执行的相应操作，为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(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)。应注意，本申请描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
图8是本申请实施例的系统芯片的一个示意性结构图。图8的系统芯片800包括输入接口801、输出接口802、至少一个处理器803、存储器804，所述输入接口801、输出接口802、所述处理器803以及存储器804之间通过内部连接通路互相连接。所述处理器803用于执行所述存储器804中的代码。
可选地，当所述代码被执行时，所述处理器1503可以实现方法200中由第一核心网设备执行的相应操作。为了简洁，这里不再赘述。
可选地，当所述代码被执行时，所述处理器1503可以实现方法400中由终端设备执行的相应操作。为了简洁，这里不再赘述。
应理解，在本发明实施例中，“与A相应(对应)的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，该单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个监测单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (40)

  1. 一种建立传输路径的方法，其特征在于，所述方法包括：
    第一核心网设备接收第一请求消息，所述第一请求消息用于请求所述第一核心网设备作为待建立的基于非协议数据单元PDU会话连接的目标传输路径的传输节点；
    所述第一核心网设备确定是否作为所述目标传输路径的传输节点。
  2. 根据权利要求1所述的方法，其特征在于，所述第一核心网设备确定是否作为所述目标传输路径的传输节点，包括：
    若所述目标传输路径满足以下条件中的至少一个条件，则所述第一核心网设备确定作为所述目标传输路径的传输节点：
    所述目标传输路径所应用的目标网络切片为终端设备签约的网络切片、所述目标传输路径所应用的外部服务器为所述终端设备签约的外部服务器、以及所述目标传输路径所应用的外部服务功能为所述终端设备签约的外部服务功能。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    所述第一核心网设备从统一数据管理UDM或者网络片选择功能NSSF中，获取所述终端设备签约的网络切片的信息、所述终端设备签约的外部服务器的信息和所述终端设备签约的外部服务功能的信息。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，若所述第一核心网设备确定作为所述目标传输路径的传输节点，所述方法还包括：
    所述第一核心网设备选择第二核心网设备；
    所述第一核心网设备向所述第二核心网设备发送第二请求消息，所述第二请求消息用于请求所述第二核心网设备作为待建立的所述目标传输路径的传输节点。
  5. 根据权利要求4所述的方法，其特征在于，所述第一核心网设备选择第二核心网设备，包括：
    所述第一核心网设备根据所述第一请求消息，选择所述第二核心网设备，其中，所述第一请求消息携带以下信息中的至少一种：所述目标传输路径所应用的目标网络切片的信息、所述终端设备的数据网络名称DNN信息和所述终端设备的服务网络标识信息。
  6. 根据权利要求4所述的方法，其特征在于，所述第一核心网设备选择第二核心网设备，包括：
    所述第一核心网设备根据所述第一核心网设备的本地配置和/或所述终端设备的签约信息，选择所述第二核心网设备，
    其中，所述终端设备的签约信息包括以下信息中的至少一种：所述终端设备签约的网络切片的信息、所述终端设备签约的外部服务器的信息和所述终端设备签约的外部服务功能的信息，所述第一核心网设备的本地配置包括能够与所述第一核心网设备通信的第二核心网设备的信息。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述第一核心网设备接收第一请求消息，包括：
    所述第一核心网设备接收终端设备发送的所述第一请求消息。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    所述第一核心网设备接收到通过所述目标传输路径传输的下行数据后，向所述终端设备发送所述下行数据。
  9. 根据权利要求1至6中任一项所述的方法，其特征在于，所述第一核心网设备接收第一请求消息，包括：
    所述第一核心网设备接收第三核心网设备发送的所述第一请求消息。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述第一核心网设备接收通过所述目标传输路径传输的下行数据，并通过所述第三核心网设备向所述终端设备发送所述下行数据。
  11. 根据权利要求10所述的方法，其特征在于，所述第一核心网设备通过所述第三核心网设备向所述终端设备发送所述下行数据之前，所述方法还包括：
    所述第一核心网设备从UDM设备中获取所述第三核心网设备的信息；或者，所述第一核心网设备获取存储在所述第一核心网设备中的所述第三核心网设备的信息。
  12. 根据权利要求1至11中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一核心网设备发送针对所述第一请求消息的响应消息，所述响应消息用于指示所述目标传输路径是否建立完成。
  13. 根据权利要求9至12中任一项所述的方法，其特征在于，所述第三核心网设备为以下设备中的任意一种：
    接入和移动性管理功能AMF设备、会话管理功能SMF设备、用户平面功能UPF设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
  14. 根据权利要求4至13中任一项所述的方法，其特征在于，所述第二核心网设备为以下设备中的任意一种：
    AMF设备、SMF设备、UPF设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
  15. 根据权利要求1至14中任一项所述的方法，其特征在于，所述第一核心网设备为以下设备中的任意一种：
    AMF设备、SMF设备、UPF设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
  16. 一种建立传输路径的方法，其特征在于，所述方法包括：
    终端设备向第一核心网设备发送第一请求消息，所述第一请求消息用于请求所述第一核心网设备作为待建立的基于非协议数据单元PDU会话连接的目标传输路径的传输节点。
  17. 根据权利要求16所述的方法，其特征在于，所述第一请求消息携带以下信息中的至少一种：
    所述目标传输路径所应用的目标网络切片的信息、所述终端设备的数据网络名称DNN信息和所述终端设备的服务网络标识信息。
  18. 根据权利要求16或17所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收所述第一核心网设备发送的响应消息，所述响应消息用于指示所述目标传输路径是否建立完成。
  19. 根据权利要求16至18中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收所述第一核心网设备发送的经过所述目标传输路径传输的下行数据。
  20. 根据权利要求16至19中任一项所述的方法，其特征在于，所述第一核心网设备为以下设备中的任意一种：
    接入和移动性管理功能AMF设备、会话管理功能SMF设备、用户平面功能UPF设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
  21. 一种核心网设备，其特征在于，所述核心网设备为第一核心网设备，所述第一核心网设备包括：
    收发单元，用于接收第一请求消息，所述第一请求消息用于请求所述第一核心网设备作为待建立的基于非协议数据单元PDU会话连接的目标传输路径的传输节点；
    处理单元，用于确定是否作为所述目标传输路径的传输节点。
  22. 根据权利要求21所述的核心网设备，其特征在于，所述处理单元具体用于：
    若所述目标传输路径满足以下条件中的至少一个条件，则确定作为所述目标传输路径的传输节点：
    所述目标传输路径所应用的目标网络切片为终端设备签约的网络切片、所述目标传 输路径所应用的外部服务器为所述终端设备签约的外部服务器、以及所述目标传输路径所应用的外部服务功能为所述终端设备签约的外部服务功能。
  23. 根据权利要求22所述的核心网设备，其特征在于，所述收发单元还用于：
    从统一数据管理UDM或者网络片选择功能NSSF中，获取所述终端设备签约的网络切片的信息、所述终端设备签约的外部服务器的信息和所述终端设备签约的外部服务功能的信息。
  24. 根据权利要求21至23中任一项所述的核心网设备，其特征在于，若所述第一核心网设备确定作为所述目标传输路径的传输节点，所述处理单元还用于：
    选择第二核心网设备；
    所述收发单元还用于：
    向所述第二核心网设备发送第二请求消息，所述第二请求消息用于请求所述第二核心网设备作为待建立的所述目标传输路径的传输节点。
  25. 根据权利要求24所述的核心网设备，其特征在于，所述处理单元具体用于：
    根据所述第一请求消息，选择所述第二核心网设备，其中，所述第一请求消息携带以下信息中的至少一种：所述目标传输路径所应用的目标网络切片的信息、所述终端设备的数据网络名称DNN信息和所述终端设备的服务网络标识信息。
  26. 根据权利要求24所述的核心网设备，其特征在于，所述处理单元具体用于：
    根据所述第一核心网设备的本地配置和/或所述终端设备的签约信息，选择所述第二核心网设备，
    其中，所述终端设备的签约信息包括以下信息中的至少一种：所述终端设备签约的网络切片的信息、所述终端设备签约的外部服务器的信息和所述终端设备签约的外部服务功能的信息，所述第一核心网设备的本地配置包括能够与所述第一核心网设备通信的第二核心网设备的信息。
  27. 根据权利要求21至26中任一项所述的核心网设备，其特征在于，所述收发单元具体用于：
    接收终端设备发送的所述第一请求消息。
  28. 根据权利要求27所述的核心网设备，其特征在于，所述收发单元还用于：
    接收到通过所述目标传输路径传输的下行数据后，向所述终端设备发送所述下行数据。
  29. 根据权利要求21至26中任一项所述的核心网设备，其特征在于，所述收发单元具体用于：
    接收第三核心网设备发送的所述第一请求消息。
  30. 根据权利要求29所述的核心网设备，其特征在于，所述收发单元还用于：
    接收通过所述目标传输路径传输的下行数据，并通过所述第三核心网设备向所述终端设备发送所述下行数据。
  31. 根据权利要求30所述的核心网设备，其特征在于，所述处理单元还用于：
    通过所述收发单元从UDM设备中获取所述第三核心网设备的信息；或者，获取存储在所述第一核心网设备中的所述第三核心网设备的信息。
  32. 根据权利要求21至31中任一项所述的核心网设备，其特征在于，所述收发单元还用于：
    发送针对所述第一请求消息的响应消息，所述响应消息用于指示所述目标传输路径是否建立完成。
  33. 根据权利要求29至32中任一项所述的核心网设备，其特征在于，所述第三核心网设备为以下设备中的任意一种：
    接入和移动性管理功能AMF设备、会话管理功能SMF设备、用户平面功能UPF设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
  34. 根据权利要求24至33中任一项所述的核心网设备，其特征在于，所述第二核心网设备为以下设备中的任意一种：
    AMF设备、SMF设备、UPF设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
  35. 根据权利要求21至34中任一项所述的核心网设备，其特征在于，所述第一核心网设备为以下设备中的任意一种：
    AMF设备、SMF设备、UPF设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
  36. 一种终端设备，其特征在于，所述终端设备包括：
    处理单元，用于生成第一请求消息，所述第一请求消息用于请求第一核心网设备作为待建立的基于非协议数据单元PDU会话连接的目标传输路径的传输节点；
    收发单元，用于向所述第一核心网设备发送所述处理单元生成的US噢书第一请求消息。
  37. 根据权利要求36所述的终端设备，其特征在于，所述第一请求消息携带以下信息中的至少一种：
    所述目标传输路径所应用的目标网络切片的信息、所述终端设备的数据网络名称DNN信息和所述终端设备的服务网络标识信息。
  38. 根据权利要求36或37所述的终端设备，其特征在于，所述收发单元还用于：
    接收所述第一核心网设备发送的响应消息，所述响应消息用于指示所述目标传输路径是否建立完成。
  39. 根据权利要求36至38中任一项所述的终端设备，其特征在于，所述收发单元还用于：
    接收所述第一核心网设备发送的经过所述目标传输路径传输的下行数据。
  40. 根据权利要求36至39中任一项所述的终端设备，其特征在于，所述第一核心网设备为以下设备中的任意一种：
    接入和移动性管理功能AMF设备、会话管理功能SMF设备、用户平面功能UPF设备、合设有SMF和UPF的设备、以及连接外部网元的网关。
PCT/CN2018/082922 2018-04-13 2018-04-13 建立传输路径的方法和设备 WO2019196078A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
EP18914216.9A EP3780743B1 (en) 2018-04-13 2018-04-13 Method and device for establishing transmission path
KR1020207031690A KR20200142531A (ko) 2018-04-13 2018-04-13 전송 경로를 구성하는 방법과 장치
AU2018418065A AU2018418065A1 (en) 2018-04-13 2018-04-13 Method and device for establishing transmission path
CN201880092308.XA CN111972005B (zh) 2018-04-13 2018-04-13 建立传输路径的方法和设备
PCT/CN2018/082922 WO2019196078A1 (zh) 2018-04-13 2018-04-13 建立传输路径的方法和设备
US17/034,797 US20210014766A1 (en) 2018-04-13 2020-09-28 Method and Device for Establishing Transmission Path

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/082922 WO2019196078A1 (zh) 2018-04-13 2018-04-13 建立传输路径的方法和设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/034,797 Continuation US20210014766A1 (en) 2018-04-13 2020-09-28 Method and Device for Establishing Transmission Path

Publications (1)

Publication Number Publication Date
WO2019196078A1 true WO2019196078A1 (zh) 2019-10-17

Family

ID=68163831

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/082922 WO2019196078A1 (zh) 2018-04-13 2018-04-13 建立传输路径的方法和设备

Country Status (6)

Country Link
US (1) US20210014766A1 (zh)
EP (1) EP3780743B1 (zh)
KR (1) KR20200142531A (zh)
CN (1) CN111972005B (zh)
AU (1) AU2018418065A1 (zh)
WO (1) WO2019196078A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113709904A (zh) * 2020-05-22 2021-11-26 华为技术有限公司 连接建立的方法、装置和系统

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112312418A (zh) * 2019-07-26 2021-02-02 华为技术有限公司 一种用户面数据的获取方法、装置及存储介质
US11700516B2 (en) 2021-05-27 2023-07-11 T-Mobile Innovations Llc Service modification in wireless communication networks
CN113434766B (zh) * 2021-06-30 2024-03-22 青岛海尔科技有限公司 订阅信息的推送方法和装置、存储介质及电子装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103415059A (zh) * 2013-08-26 2013-11-27 宇龙计算机通信科技(深圳)有限公司 终端和移动通信方法
CN104322082A (zh) * 2012-05-07 2015-01-28 三星电子株式会社 用于无连接消息传递的方法、机器可读存储介质和通信终端
CN107484224A (zh) * 2016-06-08 2017-12-15 中国移动通信有限公司研究院 一种数据传输方法及装置
WO2018059515A1 (en) * 2016-09-30 2018-04-05 Huawei Technologies Co., Ltd. Method and system for user plane path selection

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101867972B (zh) * 2010-06-29 2012-12-12 中国科学院计算技术研究所 无线链路控制层非确认模式下的数据传输方法
CN107396401A (zh) * 2016-05-17 2017-11-24 中兴通讯股份有限公司 数据发送方法及装置
KR102162808B1 (ko) * 2016-05-30 2020-10-07 후아웨이 테크놀러지 컴퍼니 리미티드 무선 통신 방법 및 장치
US10158565B2 (en) * 2016-08-26 2018-12-18 Cisco Technology, Inc. Network services across non-contiguous subnets of a label switched network separated by a non-label switched network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104322082A (zh) * 2012-05-07 2015-01-28 三星电子株式会社 用于无连接消息传递的方法、机器可读存储介质和通信终端
CN103415059A (zh) * 2013-08-26 2013-11-27 宇龙计算机通信科技(深圳)有限公司 终端和移动通信方法
CN107484224A (zh) * 2016-06-08 2017-12-15 中国移动通信有限公司研究院 一种数据传输方法及装置
WO2018059515A1 (en) * 2016-09-30 2018-04-05 Huawei Technologies Co., Ltd. Method and system for user plane path selection

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3780743A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113709904A (zh) * 2020-05-22 2021-11-26 华为技术有限公司 连接建立的方法、装置和系统
CN113709904B (zh) * 2020-05-22 2024-04-09 华为技术有限公司 连接建立的方法、装置和系统

Also Published As

Publication number Publication date
EP3780743B1 (en) 2022-03-30
AU2018418065A1 (en) 2020-11-26
US20210014766A1 (en) 2021-01-14
CN111972005B (zh) 2022-10-18
KR20200142531A (ko) 2020-12-22
EP3780743A1 (en) 2021-02-17
CN111972005A (zh) 2020-11-20
EP3780743A4 (en) 2021-04-21

Similar Documents

Publication Publication Date Title
KR101645106B1 (ko) 무선 통신 네트워크 내의 소규모 데이터 통신
WO2019075816A1 (zh) 用于传输数据的方法、终端设备和会话管理功能smf设备
WO2019196078A1 (zh) 建立传输路径的方法和设备
US11457331B2 (en) Positioning method and related device
WO2019157736A1 (zh) 寻呼的方法和设备
WO2019080070A1 (zh) 无线通信方法和设备
WO2020056611A1 (zh) 用于网络切片鉴权的方法和设备
WO2019148398A1 (zh) 寻呼方法和设备
JP2021158664A (ja) 間接通信用のエラー処理のための方法、装置、およびコンピュータプログラム製品
WO2019153272A1 (zh) 基于业务质量进行数据传输的方法和设备
WO2019136611A1 (zh) 小区切换的方法、接入网设备和终端设备
WO2019157635A1 (zh) 无线通信的方法、终端设备和网络设备
TW202025696A (zh) 一種控制數據傳輸方法、網路設備和儲存媒介
WO2019019150A1 (zh) 数据传输的方法、终端设备和网络设备
EP3975592B1 (en) Communication method and network device
WO2019113981A1 (zh) 保障切换的方法、终端设备和网络设备
WO2019090770A1 (zh) 切换过程中确定核心网类型的方法、终端设备、接入网设备和核心网设备
WO2021027660A1 (zh) 无线通信的方法和通信装置
WO2019136644A1 (zh) 无线通信方法和设备
AU2021417277A1 (en) Key identifier generation method, and related apparatus
WO2020019910A1 (zh) 一种车联网中的通信方法及终端设备、网络设备
WO2019136663A1 (zh) 多连接网络中的定位方法、终端设备和定位管理功能实体
WO2021022428A1 (zh) 无线通信的方法、终端设备和网络设备
WO2019196090A1 (zh) 通信方法、网络设备和终端设备
WO2019237359A1 (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: 18914216

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020552737

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207031690

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2018914216

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2018418065

Country of ref document: AU

Date of ref document: 20180413

Kind code of ref document: A