WO2023193786A1 - 数据传输方法、设备、装置及存储介质 - Google Patents

数据传输方法、设备、装置及存储介质 Download PDF

Info

Publication number
WO2023193786A1
WO2023193786A1 PCT/CN2023/086859 CN2023086859W WO2023193786A1 WO 2023193786 A1 WO2023193786 A1 WO 2023193786A1 CN 2023086859 W CN2023086859 W CN 2023086859W WO 2023193786 A1 WO2023193786 A1 WO 2023193786A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
user plane
plane functional
functional network
information
Prior art date
Application number
PCT/CN2023/086859
Other languages
English (en)
French (fr)
Inventor
程志密
王亚鹏
Original Assignee
大唐移动通信设备有限公司
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 大唐移动通信设备有限公司 filed Critical 大唐移动通信设备有限公司
Publication of WO2023193786A1 publication Critical patent/WO2023193786A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H04B7/1853—Satellite systems for providing telephony service to a mobile station, i.e. mobile satellite service
    • H04B7/18539—Arrangements for managing radio, resources, i.e. for establishing or releasing a connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/06—Airborne or Satellite Networks

Definitions

  • the present disclosure relates to the field of wireless communication technology, and in particular, to a data transmission method, equipment, device and storage medium.
  • the fifth generation mobile communication (5G) system serves a variety of scenarios and aims to provide ubiquitous mobile network access and high-speed data transmission.
  • satellite communications can achieve wide-area or even global coverage using high, medium and low-orbit satellites.
  • the 5G system combined with satellite communications technology can further achieve seamless global coverage.
  • Current solutions for 5G system integration of satellites include: using satellites as part of access network equipment (such as base stations) to provide access to terminals (also called user equipment, User Equipment, UE), or integrating some network functions (such as base stations, gateways) That is, the user plane function) is deployed on the satellite.
  • the control plane data transmission method for the data transmission of equipment terminals that send small data, if the control plane data transmission method is used to realize the data transmission, the data transmission needs to be realized with the help of control plane network elements deployed on the ground, which will increase the data transmission delay. ; If a dedicated user plane connection method is used to realize data transmission, that is, a user plane tunnel is established, then due to dynamic changes in the satellite network topology, the user plane function (UPF) deployed on the satellite needs to be maintained in real time according to the network topology changes. User plane tunnel information will cause a waste of user plane resources and is also a challenge to scarce on-board resources.
  • UPF user plane function
  • Embodiments of the present disclosure provide a data transmission method, equipment, device and storage medium to reduce Low data transmission latency and reduced use of user plane resources.
  • embodiments of the present disclosure provide a data transmission method applied to a first user plane functional network element, including:
  • the N4 session establishment request message carries first information; the first information is used to instruct the first user plane function network element to perform specified data through service operations. transmission;
  • the data matching the first information is sent to the next hop user plane functional network element through a service operation.
  • the first information includes one or more of the following:
  • the second user plane functional network element includes multiple user plane functional network elements connected to the first user plane functional network element in different time periods;
  • the information of the second user plane functional network element includes one or more of the following:
  • the identification information of the second user plane functional network element is the identification information of the second user plane functional network element
  • the ephemeris information of the satellite where the second user plane functional network element is located is located;
  • sending data matching the first information to the next-hop user plane functional network element through service operations includes:
  • the data matching the first information is sent to the next-hop user plane functional network element through an event notification service operation or a data transmission request service operation.
  • the method before sending the data matching the first information to the next-hop user plane functional network element through the event notification service operation, the method further includes:
  • the method before sending the data matching the first information to the next-hop user plane functional network element through the service operation, the method further includes:
  • the inter-satellite visibility time between the satellite and the satellite where the first user plane functional network element is located determines the next hop user plane functional network element.
  • the method further includes:
  • service operation information of user plane function network elements connected to the first user plane function network element in different time periods is obtained from the network storage function network element.
  • the method further includes:
  • N4 session establishment response message to the session management function network element, where the N4 session establishment response message carries N3 tunnel information of the N3 side user plane function network element.
  • the method further includes:
  • the downlink data After receiving the downlink data, the downlink data is encapsulated, and the encapsulated data is sent to the access network device.
  • the method further includes:
  • After receiving the uplink data After receiving the uplink data, send the uplink data to the data network; and/or,
  • the downlink data is sent to the next hop user plane functional network element through a service operation.
  • embodiments of the present disclosure also provide a data transmission method, applied to session management function network elements, including:
  • N4 session establishment request message to the first user plane functional network element, where the N4 session establishment request message carries first information; the first information is used to instruct the first user plane functional network element to specify through a service operation Transmission of data.
  • the first information includes one or more of the following:
  • the second user plane functional network element includes multiple user plane functional network elements connected to the first user plane functional network element in different time periods;
  • the information of the second user plane functional network element includes one or more of the following:
  • the identification information of the second user plane functional network element is the identification information of the second user plane functional network element
  • the ephemeris information of the satellite where the second user plane functional network element is located is located;
  • the determination is to transmit data through service operations, including:
  • the wireless access type of the terminal it is determined that the data transmission of the terminal is performed through a service operation.
  • the method further includes:
  • N4 session establishment response message sent by the N3 side user plane functional network element, where the N4 session establishment response message carries N3 tunnel information of the N3 side user plane functional network element.
  • embodiments of the present disclosure also provide a first user plane functional network element, including a memory, a transceiver, and a processor:
  • Memory used to store computer programs
  • transceiver used to send and receive data under the control of the processor
  • processor used to read the computer program in the memory and perform the following operations:
  • the N4 session establishment request message carries first information; the first information is used to instruct the first user plane function network element to perform specified data through service operations. transmission;
  • the data matching the first information is sent to the next hop user plane functional network element through a service operation.
  • the first information includes one or more of the following:
  • the second user plane functional network element includes multiple user plane functional network elements connected to the first user plane functional network element in different time periods;
  • the information of the second user plane functional network element includes one or more of the following:
  • the identification information of the second user plane functional network element is the identification information of the second user plane functional network element
  • the ephemeris information of the satellite where the second user plane functional network element is located is located;
  • sending data matching the first information to the next-hop user plane functional network element through service operations includes:
  • the first information will be related to The matching data is sent to the next hop user plane functional network element.
  • the operation before sending the data matching the first information to the next-hop user plane functional network element through the event notification service operation, the operation further includes:
  • the operation before sending the data matching the first information to the next-hop user plane functional network element through the service operation, the operation further includes:
  • the inter-satellite visibility time between the satellite and the satellite where the first user plane functional network element is located determines the next hop user plane functional network element.
  • the operation further includes:
  • service operation information of user plane function network elements connected to the first user plane function network element in different time periods is obtained from the network storage function network element.
  • the operation further includes:
  • N4 session establishment response message to the session management function network element, where the N4 session establishment response message carries N3 tunnel information of the N3 side user plane function network element.
  • the operation further includes:
  • the downlink data After receiving the downlink data, the downlink data is encapsulated, and the encapsulated data is sent to Access network equipment.
  • the operation further includes:
  • After receiving the uplink data After receiving the uplink data, send the uplink data to the data network; and/or,
  • the downlink data is sent to the next hop user plane functional network element through a service operation.
  • embodiments of the present disclosure also provide a session management function network element, including a memory, a transceiver, and a processor:
  • Memory used to store computer programs
  • transceiver used to send and receive data under the control of the processor
  • processor used to read the computer program in the memory and perform the following operations:
  • N4 session establishment request message to the first user plane functional network element, where the N4 session establishment request message carries first information; the first information is used to instruct the first user plane functional network element to specify through a service operation Transmission of data.
  • the first information includes one or more of the following:
  • the second user plane functional network element includes multiple user plane functional network elements connected to the first user plane functional network element in different time periods;
  • the information of the second user plane functional network element includes one or more of the following:
  • the identification information of the second user plane functional network element is the identification information of the second user plane functional network element
  • the ephemeris information of the satellite where the second user plane functional network element is located is located;
  • the determination is to transmit data through service operations, including:
  • the wireless access type of the terminal it is determined that the data transmission of the terminal is performed through a service operation.
  • the operation further includes:
  • N4 session establishment response message sent by the N3 side user plane functional network element, where the N4 session establishment response message carries N3 tunnel information of the N3 side user plane functional network element.
  • embodiments of the present disclosure also provide a data transmission device, applied to the first user plane functional network element, including:
  • the first receiving unit is configured to receive an N4 session establishment request message sent by the session management function network element.
  • the N4 session establishment request message carries first information; the first information is used to indicate the first user plane function network element. Yuan performs the transmission of specified data through service operations;
  • the first sending unit is configured to send data matching the first information to the next-hop user plane functional network element through service operations.
  • embodiments of the present disclosure also provide a data transmission device applied to a session management function network element, including:
  • a second determination unit used to determine data transmission through service operations
  • the second sending unit is configured to send an N4 session establishment request message to the first user plane function network element.
  • the N4 session establishment request message carries first information; the first information is used to indicate the first user plane function.
  • Network elements transmit specified data through service operations.
  • embodiments of the present disclosure further provide a computer-readable storage medium storing a computer program, the computer program being used to cause the computer to perform the data transmission described in the first aspect.
  • embodiments of the present disclosure further provide a communication device.
  • a computer program is stored in the communication device.
  • the computer program is used to cause the communication device to perform the steps of the data transmission method described in the first aspect, Or perform the steps of the data transmission method described in the second aspect above.
  • embodiments of the present disclosure further provide a processor-readable storage medium, wherein the processor
  • the readable storage medium stores a computer program, which is used to cause the processor to perform the steps of the data transmission method described in the first aspect as described above, or to perform the steps of the data transmission method described in the second aspect as described above.
  • embodiments of the present disclosure also provide a chip product, a computer program is stored in the chip product, and the computer program is used to cause the chip product to execute the steps of the data transmission method described in the first aspect, Or perform the steps of the data transmission method described in the second aspect above.
  • the session management function network element carries the first information in the N4 session establishment request message, instructing the first user plane function network element to perform specified data through service operations. transmission, so that data does not need to be transmitted to the ground, and data transmission can be achieved without establishing a dedicated user plane tunnel, which not only improves data transmission efficiency, but also saves user plane resources on the satellite.
  • Figure 1 is a schematic diagram of satellite access user services in a non-implemented service scenario provided by an embodiment of the present disclosure
  • Figure 2 is one of the flow diagrams of a data transmission method provided by an embodiment of the present disclosure
  • Figure 3 is a schematic flowchart of data transmission through event notification service operations provided by an embodiment of the present disclosure
  • Figure 4 is a schematic flowchart of event subscription through event subscription service operations provided by an embodiment of the present disclosure
  • Figure 5 is a schematic flowchart of data transmission through a data transmission request service operation provided by an embodiment of the present disclosure
  • Figure 6 is a second schematic flowchart of a data transmission method provided by an embodiment of the present disclosure.
  • Figure 7 is one of the implementation schematic diagrams of the data transmission method provided by the embodiment of the present disclosure.
  • Figure 8 is a second schematic diagram of the implementation of the data transmission method provided by the embodiment of the present disclosure.
  • Figure 9 is a third schematic diagram of the implementation of the data transmission method provided by the embodiment of the present disclosure.
  • Figure 10 is the fourth implementation schematic diagram of the data transmission method provided by the embodiment of the present disclosure.
  • Figure 11 is a fifth implementation schematic diagram of the data transmission method provided by the embodiment of the present disclosure.
  • Figure 12 is a schematic structural diagram of a first user plane functional network element provided by an embodiment of the present disclosure.
  • Figure 13 is a schematic structural diagram of a session management function network element provided by an embodiment of the present disclosure.
  • Figure 14 is one of the structural schematic diagrams of a data transmission device provided by an embodiment of the present disclosure.
  • Figure 15 is a second structural schematic diagram of a data transmission device provided by an embodiment of the present disclosure.
  • the term "and/or” describes the association relationship of associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone. these three situations.
  • the character "/” generally indicates that the related objects are in an "or” relationship.
  • the term “plurality” refers to two or more than two, and other quantifiers are similar to it.
  • FIG. 1 is a schematic diagram of satellite access user services in a scenario where services are not implemented according to an embodiment of the present disclosure.
  • core network control plane network elements are deployed on the ground, and UPF and mobile Edge computing (Mobile Edge Computing, MEC) platform is deployed on satellites.
  • MEC Mobile Edge Computing
  • the control plane is used to realize data transmission, it is necessary to use control plane network elements deployed on the ground, which will increase the data transmission delay; if a dedicated
  • the user plane connection method implements data transmission, that is, establishing a user plane tunnel. Due to the dynamic changes in the satellite network topology, UPF needs to maintain the user plane tunnel information in real time according to the network topology changes. This will cause a waste of user plane resources and impose a heavy burden on the scarce satellites. Resources are also a challenge.
  • each embodiment of the present disclosure provides a solution that supports service-based interfaces based on UPF and adopts a service-based approach to small data processing on the user plane of the satellite network. Forwarding, that is, when UPF receives a data message, it triggers the service operation of the peer UPF to send data, in which small data is used as a parameter of the service operation to realize the transmission of small data, thereby saving on-board resources and speeding up small data transmission. Forwarding of data.
  • Figure 2 is one of the flow diagrams of a data transmission method provided by an embodiment of the present disclosure. The method is applied to the first user plane functional network element. As shown in Figure 2, the method includes the following steps:
  • Step 200 Receive the N4 session establishment request message sent by the session management function network element.
  • the N4 session establishment request message carries first information; the first information is used to instruct the first user plane function network element to transmit specified data through service operations.
  • the first user plane functional network element may be any user plane functional network element on the data transmission path, and the user plane functional network element may be a UPF or other network element with similar user plane functions.
  • the session management function network element can be a session management function (Session Management Function, SMF) or other network elements with similar session management functions.
  • the session management function network element may send an N4 session establishment request message to the first user plane function network element when it is determined that data transmission is performed through a service operation.
  • the N4 session establishment request message carries the first information, and is passed through the first user plane function network element.
  • the information instructs the first user plane functional network element to transmit designated data through service operations.
  • the designated data is data in the first information that directly or indirectly indicates that it can be transmitted through service operations.
  • the first information may include one or more of the following:
  • the second user plane functional network element includes the first user plane Multiple user plane functional network elements connected to functional network elements in different time periods.
  • the session management function network element can carry the second user plane function in the N4 session establishment request message.
  • the information of the network element is used to inform the first user plane functional network element of the information of the corresponding second user plane functional network element.
  • the session Internet Protocol (IP) address can be an IP address indicating a certain session, and can include the session source IP address and the session destination IP address.
  • the session can be a protocol data unit (Protocol Data Unit, PDU) session, session management function
  • PDU Protocol Data Unit
  • the network element may carry the session IP address in the N4 session establishment request message to instruct the first user plane function network element to send the data to the next hop through service operations when receiving data matching the session IP address.
  • User plane functional network element may carry the session IP address in the N4 session establishment request message to instruct the first user plane function network element to send the data to the next hop through service operations when receiving data matching the session IP address.
  • the small data transmission indication can be used to instruct the first user plane functional network element to transmit small data through service operations.
  • the session management function network element determines to transmit small data through service operations
  • the session management function network element can The N4 session establishment request message carries a small data transmission indication, instructing the first user plane functional network element to send the small data to the next hop user plane functional network element through a service operation when receiving the small data.
  • the event notification subscription instruction can be used to instruct the first user plane functional network element to send the data to the next hop user plane functional network element through the event notification service operation when receiving the data that needs to be sent through the service operation, that is, to the next hop user plane functional network element.
  • the user plane function network element triggers event notification service operations to realize data transmission.
  • the first user plane functional network element can trigger the Nupf_EventExposure_Notify service operation to the opposite user plane functional network element based on the session source IP address, and use such data as a POST request.
  • the Nupf_EventExposure_Notify service operation can be triggered to the peer user plane functional network element based on the session destination IP address, and such data can be used as the content of the POST request. Payload body.
  • the information about the second user plane functional network element may include one or more of the following:
  • the session management function network element may carry the identification information of the second user plane function network element in the N4 session establishment request message to indicate the identification of the second user plane function network element.
  • the session management function network element may carry the identification information of the second user plane function network element in the N4 session establishment request message, and carry the first user plane function network element in which time period it is connected to which (or which ) Information about the second user plane functional network element.
  • the session management function network element may carry the identification information of the second user plane function network element in the N4 session establishment request message, but does not carry the time period in which each second user plane function network element communicates with the first user plane function network element. Information on establishing connections between user plane functional network elements.
  • the time-related information may include time period information.
  • the time-related information may be used to indicate in which time period each second user plane functional network element establishes a connection with the first user plane functional network element, so that the first user plane functional network element establishes a connection with the first user plane functional network element.
  • the user plane functional network element can determine the second user plane functional network element to which it is connected in different time periods.
  • the inter-satellite visibility time refers to the time the satellites are visible to each other (which can also be understood as a state where they can communicate). Since the user plane functional network element is located on the satellite, as the movement trajectory of the satellite changes, each user plane The connection relationship between functional network elements will change accordingly. When the time windows of the two satellites coincide (or the two satellites are visible to each other), a connection can be established between the user plane functional network elements on the two satellites. , therefore, the session management function network element can carry the above-mentioned inter-satellite visible time duration information in the N4 session establishment request message, which is used to indicate the situation of the satellite where each second user plane function network element of the first user plane function network element is located. For example, the first user plane functional network element can refer to the information on the inter-satellite visible time duration to select the next hop user plane functional network element during data transmission.
  • the ephemeris information can be used to indicate the ephemeris of the satellite where the second user plane function network element is located.
  • the session management function network element can carry the ephemeris information in the N4 session establishment request message, so that the first user plane function network element can carry out the ephemeris information according to the N4 session establishment request message.
  • Ephemeris information determines the star orbit data of the satellite where the second user plane functional network element is located.
  • the service operation information can be used to indicate information about service operations supported by the second user plane functional network element, such as the type of service operation, the application programming interface (Application Programming Interface, API) of the service operation, the uniform resource identifier (Uniform Resource Identifier) , URI), etc.
  • the application programming interface Application Programming Interface, API
  • the uniform resource identifier Uniform Resource Identifier
  • Step 201 Send data matching the first information to the next-hop user plane functional network element through service operations.
  • the first user plane function network element After the first user plane function network element receives the N4 session establishment request message sent by the session management function network element, it can obtain the first information from the N4 session establishment request message. According to the first information, the first user plane When the functional network element subsequently receives data that matches the first information, it can send the data to the next-hop user plane functional network element through service operations, thereby realizing data transmission through service operations.
  • the first user plane function network element receives the data containing the session IP address in the data information, it can send the data to the next hop user plane function through service operations. network element.
  • the first user plane functional network element receives small data (data with a small amount of data, such as tens to hundreds of bits of data), it can operate through the service Send small data to the next hop user plane functional network element.
  • small data data with a small amount of data, such as tens to hundreds of bits of data
  • the session management function network element carries the first information in the N4 session establishment request message, instructing the first user plane function network element to transmit the specified data through service operations, so that the data does not need to be transmitted.
  • data transmission can be achieved without establishing a dedicated user plane tunnel, which not only improves data transmission efficiency, but also saves user plane resources on the satellite.
  • data matching the first information is sent to the next-hop user plane functional network element through service operations, including:
  • Data matching the first information is sent to the next-hop user plane functional network element through an event notification service operation or a data transmission request service operation.
  • the first user plane functional network element can send the data to the next hop user plane functional network element through an event notification service operation or a data transmission request service operation, that is, Trigger the event notification service operation or the data transmission request service operation of the next-hop user plane functional network element to send data to the next-hop user plane functional network element.
  • the event notification service operation may refer to the Nupf_EventExposure_Notify service operation, and the Nupf_EventExposure_Notify service operation information may be as shown in Table 1 below.
  • Figure 3 is a schematic flow chart of data transmission through event notification service operations provided by an embodiment of the present disclosure. As shown in Figure 3, taking small data transmission between UPFs as an example, it mainly includes the following processes:
  • UPF sends a POST request based on the service operation information (eventNotificationUri) of the peer UPF provided by SMF during the session establishment process.
  • the payload body of the POST request contains the small data that the UPF wants to transmit to the peer UPF.
  • HTTP Hyper Text Transfer Protocol
  • Figure 4 is a schematic process diagram of event subscription through event subscription service operations provided by an embodiment of the present disclosure. As shown in Figure 4, taking event subscription between UPFs as an example, it mainly includes the following processes:
  • UPF sends a POST request to the peer UPF to create a subscription (.../ ⁇ sessionIdentity ⁇ /ee-subscriptions) in the message body.
  • the event trigger indication includes the source IP address or destination IP address.
  • the request may contain an expiration time suggested by the UPF, representing how long you wish to keep the subscription active, and how long the subscribed events should stop generating notifications.
  • the data transfer request service operation may refer to the Nupf_PDUSession_TransferData_Request service operation, and the Nupf_PDUSession_TransferData_Request service operation information may be as shown in Table 3 below.
  • Figure 5 is a schematic flowchart of data transmission through a data transmission request service operation provided by an embodiment of the present disclosure. As shown in Figure 5, taking small data transmission between UPFs as an example, it mainly includes the following processes:
  • the UPF sends a POST request based on the service operation information of the peer UPF.
  • the payload body of the POST request contains the small data that the UPF wants to transmit to the peer UPF.
  • the method before sending the data matching the first information to the next-hop user plane functional network element through the event notification service operation, the method further includes:
  • the first user plane functional network element when data is transmitted through an event notification service operation, can first trigger an event subscription service operation to the user plane functional network elements it is connected to in different time periods for subsequent data transmission. , the data can be sent to the next-hop user plane functional network element connected to the first user plane functional network element through the event notification service operation.
  • the first user plane functional network element when the first information does not contain an event notification subscription instruction, if the first user plane functional network element needs to perform data transmission through the event notification service operation, it can first transmit data to it in different time periods before performing data transmission.
  • the connected user plane functional network element triggers the event subscription service operation.
  • the first user plane functional network element can only send data to the user plane connected to the current time period in a certain time period.
  • the functional network element triggers the event subscription service operation, so the first user plane functional network element can trigger the event subscription service operation to the user plane functional network element connected to the corresponding time period multiple times and in different time periods.
  • the method further includes:
  • the next hop user plane functional network element needs to trigger the data
  • the transmission response service operation is used as a response so that the first user plane functional network element confirms that the data is successfully transmitted to the next hop user plane functional network element.
  • the method before sending the data matching the first information to the next-hop user plane functional network element through the service operation, the method further includes:
  • the operation information determines the next hop user plane Functional network element.
  • the first user plane functional network element Before the first user plane functional network element sends data matching the first information to the next hop user plane functional network element through a service operation, it needs to first determine the next hop user plane functional network element.
  • the first user plane functional network element can be configured according to the service operation information of each user plane functional network element it is connected to in the current time period, and the satellite where each user plane functional network element is connected to it in the current time period.
  • the inter-satellite visibility time between the satellites is used to determine the next hop user plane functional network element.
  • the first user plane functional network element can select to support event notification from each user plane functional network element it is connected to in the current time period based on the service operation information of each user plane functional network element it is connected to in the current time period.
  • the user plane functional network element for service operation or data transmission request service operation serves as the next hop user plane functional network element.
  • multiple user plane functional network elements that meet the conditions can be selected according to the service operation information, it can be determined which user plane functional network element among these user plane functional network elements that meet the conditions is located on the satellite that is the same as the first user plane If the inter-satellite visible time between the satellites where the functional network element is located is the longest, this user plane functional network element will be used as the next hop user plane functional network element.
  • the method further includes:
  • service operation information of user plane function network elements connected to the first user plane function network element in different time periods is obtained from the network storage function network element.
  • the first user plane functional network element can obtain it in different ways as needed.
  • the first user plane function network element can directly obtain it from the N4 session establishment request message. and save.
  • the first user plane function network element can also obtain the service operation information from the network based on the first information carried in the N4 session establishment request message. Obtain the service operation information from the storage function network element.
  • the network storage function network element can be a network storage function (Network Repository Function, NRF) or other network elements with similar network storage functions.
  • the method further includes:
  • the N4 session establishment response message carries the N3 tunnel information of the N3 side user plane function network element.
  • data transmission is performed between user plane functional network elements through service operations, and there is no need to establish a dedicated user plane tunnel. Therefore, the first user plane functional network element receives the message sent by the session management function network element. After the N4 session establishment request message, when the first user plane functional network element is the N3 side user plane functional network element, the N3 side user plane functional network element only needs to carry the N4 session establishment response message allocated for the session. N3 tunnel information is sufficient, and the N3 side user plane functional network element does not need to allocate N9 tunnel information for this session.
  • the first user plane functional network element is not an N3 side user plane functional network element
  • the first user plane functional network element does not need to carry tunnel information in the N4 session establishment response message.
  • the method further includes:
  • the downlink data After receiving the downlink data, the downlink data is encapsulated, and the encapsulated data is sent to the access network device.
  • the first user plane functional network element after receiving the uplink/downlink data, the first user plane functional network element can perform corresponding data decapsulation/encapsulation and data processing. transfer operations.
  • the first user plane function can decapsulate the uplink data to obtain the data, and then send the decapsulated data to the next-hop user plane functional network element through service operations (such as event notification service operations, data transmission request service operations, etc.) .
  • service operations such as event notification service operations, data transmission request service operations, etc.
  • the first user plane functional network element can encapsulate the downlink data, and then send the encapsulated data to the access network equipment, such as Radio Access Network equipment (Radio Access Network). , RAN).
  • the access network equipment such as Radio Access Network equipment (Radio Access Network). , RAN).
  • the method further includes:
  • After receiving the uplink data After receiving the uplink data, send the uplink data to the data network; and/or,
  • the downlink data is sent to the next hop user plane functional network element through service operations.
  • the first user plane functional network element is an anchor user plane functional network element (such as PDU Session Anchor, PSA)
  • the first user plane functional network element receives uplink/downlink data After that, the corresponding data decapsulation/encapsulation and data transmission operations can be performed.
  • anchor user plane functional network element such as PDU Session Anchor, PSA
  • the first user plane functional network element can directly send the data to the data network (Data Network, DN).
  • Data Network Data Network
  • the first user plane functional network element can send the downlink data to the next hop user plane functional network through service operations (such as event notification service operations, data transmission request service operations, etc.) Yuan.
  • service operations such as event notification service operations, data transmission request service operations, etc.
  • Figure 6 is a second schematic flowchart of a data transmission method provided by an embodiment of the present disclosure. The method is applied to the session management function network element. As shown in Figure 6, the method includes the following steps:
  • Step 600 Determine data transmission through service operation.
  • Step 601 Send an N4 session establishment request message to the first user plane functional network element.
  • the N4 session establishment request message carries first information; the first information is used to instruct the first user plane functional network element to transmit designated data through service operations. .
  • the session management function network element may be an SMF or other network element with similar session management functions.
  • the first user plane functional network element may be any user plane functional network element on the data transmission path, and the user plane functional network element may be a UPF or other network element with similar user plane functions.
  • the session management function network element may send an N4 session establishment request message to the first user plane function network element when it is determined that data transmission is performed through a service operation.
  • the N4 session establishment request message carries the first information, and is passed through the first user plane function network element.
  • the information instructs the first user plane functional network element to transmit designated data through service operations.
  • the designated data is data in the first information that directly or indirectly indicates that it can be transmitted through service operations.
  • the first information may include one or more of the following:
  • the second user plane functional network element includes multiple user plane functional network elements connected to the first user plane functional network element in different time periods.
  • the session management function network element can carry the second user plane function in the N4 session establishment request message.
  • the information of the network element is used to inform the first user plane functional network element of the information of the corresponding second user plane functional network element.
  • the session IP address can be an IP address indicating a certain session, and can include the session source IP address and the session destination IP address.
  • the session can be a PDU session.
  • the session management function network element can carry the session IP address in the N4 session establishment request message, using Instructing the first user plane functional network element to send the data to the next hop user plane functional network element through a service operation when receiving data matching the session IP address.
  • the small data transmission indication can be used to instruct the first user plane functional network element to transmit small data through service operations.
  • the session management function network element determines to transmit small data through service operations
  • the session management function network element can The N4 session establishment request message carries a small data transmission indication, instructing the first user plane functional network element to send the small data to the next hop user plane functional network element through a service operation when receiving the small data.
  • the event notification subscription instruction can be used to instruct the first user plane functional network element to send the data to the next hop user plane functional network element through the event notification service operation when receiving the data that needs to be sent through the service operation, that is, to the next hop user plane functional network element.
  • the user plane function network element triggers event notification service operations to realize data transmission.
  • the first user plane functional network element can trigger the Nupf_EventExposure_Notify service operation to the opposite user plane functional network element based on the session source IP address, and use such data as a POST request.
  • the Nupf_EventExposure_Notify service operation can be triggered to the peer user plane functional network element based on the session destination IP address, and such data can be used as the payload body of the POST request.
  • the information about the second user plane functional network element may include one or more of the following:
  • the session management function network element may carry the identification information of the second user plane function network element in the N4 session establishment request message to indicate the identification of the second user plane function network element.
  • the session management function network element may carry the identification information of the second user plane function network element in the N4 session establishment request message, and carry the first user plane function network element in which time period it is connected to which (or which ) Information about the second user plane functional network element.
  • the session management function network element may carry the identification information of the second user plane function network element in the N4 session establishment request message, but does not carry the time period in which each second user plane function network element communicates with the first user plane function network element. Information on establishing connections between user plane functional network elements.
  • the time-related information may include time period information.
  • the time-related information may be used to indicate in which time period each second user plane functional network element establishes a connection with the first user plane functional network element, so that the first user plane functional network element establishes a connection with the first user plane functional network element.
  • the user plane functional network element can determine the second user plane functional network element to which it is connected in different time periods.
  • the inter-satellite visibility time refers to the time the satellites are visible to each other (which can also be understood as a state where they can communicate). Since the user plane functional network element is located on the satellite, as the movement trajectory of the satellite changes, each user plane The connection relationship between functional network elements will change accordingly. When the time windows of the two satellites coincide (or the two satellites are visible to each other), a connection can be established between the user plane functional network elements on the two satellites. , therefore, the session management function network element can carry the above-mentioned inter-satellite visible time duration information in the N4 session establishment request message, which is used to indicate the situation of the satellite where each second user plane function network element of the first user plane function network element is located. For example, the first user plane functional network element can refer to the information on the inter-satellite visible time duration to select the next hop user plane functional network element during data transmission.
  • the ephemeris information can be used to indicate the ephemeris of the satellite where the second user plane function network element is located.
  • the session management function network element can carry the ephemeris information in the N4 session establishment request message, so that the first user plane function network element can carry out the ephemeris information according to the N4 session establishment request message.
  • Ephemeris information determines the star orbit data of the satellite where the second user plane functional network element is located.
  • the service operation information can be used to indicate information about the service operations supported by the second user plane functional network element, such as the type of service operation, the API URI of the service operation, etc.
  • the first user plane functional network element After receiving the N4 session establishment request message sent by the session management function network element, the first user plane functional network element can obtain the first information from the N4 session establishment request message. According to the first information, the first user plane functional network element When data matching the first information is subsequently received, the data can be sent to the next-hop user plane functional network element through service operations, thereby realizing data transmission through service operations.
  • the first user plane function network element receives the data containing the session IP address in the data information, it can send the data to the next hop user plane function through service operations. network element.
  • the first information contains a small data transmission indication
  • the first user plane functional network element when it receives the small data, it can send the small data to the next hop user plane functional network element through a service operation.
  • the data transmission method provided by the embodiment of the present disclosure uses the session management function network element to perform the N4 session
  • the establishment request message carries the first information, instructing the first user plane functional network element to transmit specified data through service operations, so that the data does not need to be transmitted to the ground, and data transmission can be achieved without establishing a dedicated user plane tunnel, which not only improves It improves data transmission efficiency and saves user plane resources on the satellite.
  • determine data transmission through service operations including:
  • the data transmission of the terminal is determined through the service operation.
  • the session management function network element can determine whether to perform data transmission of the terminal through service operations according to the radio access technology type (RAT Type) of the terminal.
  • RAT Type radio access technology type
  • the session management function network element obtains that the RAT Type of the terminal is Narrow Band Internet of Things (NB-IoT).
  • NB-IoT Narrow Band Internet of Things
  • the amount of data transmitted by the NB-IoT type terminal is small, and the data is sent infrequently, which can be applied to
  • the session management function network element can determine the data transmission of the terminal through service operations.
  • the N4 session establishment request message can be sent to these UPFs.
  • the first information may include the IP address of the PDU session of the terminal for indication.
  • the method further includes:
  • the N4 session establishment response message carries the N3 tunnel information of the N3 side user plane functional network element.
  • data transmission is performed between user plane functional network elements through service operations, and there is no need to establish a dedicated user plane tunnel. Therefore, the first user plane functional network element receives the message sent by the session management function network element. After the N4 session establishment request message, when the first user plane functional network element is the N3 side user plane functional network element, the N3 side user plane functional network element only needs to carry the N4 session establishment response message allocated for the session. N3 tunnel information is sufficient, and the N3 side user plane functional network element does not need to allocate N9 tunnel information for this session.
  • the N4 session establishment response message sent by the N3 side user plane function network element received by the session management function network element carries the N3 tunnel information of the N3 side user plane function network element, but not the N3 tunnel information of the N3 side user plane function network element. N9 tunnel information.
  • user plane functional network elements other than the N3 side user plane functional network element they may not carry tunnel information in the N4 session establishment response message sent to the session management functional network element.
  • Embodiment 1-3 Based on the subscription-notification method, data forwarding between user plane UPFs is implemented.
  • Embodiment 1 SMF replaces UPF subscription to implement data forwarding between user planes and UPFs.
  • Figure 7 is one of the implementation schematic diagrams of the data transmission method provided by the embodiment of the present disclosure. As shown in Figure 7, it mainly includes the following steps:
  • Step 1 The UE initiates a PDU session establishment request to the Access and Mobility Management Function (AMF).
  • AMF Access and Mobility Management Function
  • Step 2-3 AMF selects SMF to establish a session and triggers a create session management context request (Nsmf_PDUSession_CreateSMContextRequest) to SMF.
  • Nsmf_PDUSession_CreateSMContextRequest create session management context request
  • Step 4 If the session management is related to the User Permanent Identifier (Subscription Permanent Identifier, SUPI), Data Network Name (Data Network Name, DNN) and Single Network Slice Selection Assistance Information (S-NSSAI) If the subscription data is not available, SMF uses Nudm_SDM_Get(SUPI,Session Management Subscription data,DNN,S-NSSAI) to retrieve the session management subscription data, and uses Nudm_SDM_Subscribe(SUPI,Session Management Subscription data,DNN,S-NSSAI) to Unified Data Management (Unified Data Management, UDM) Subscribe to notifications about contract data changes.
  • SUPI User Permanent Identifier
  • DNN Data Network Name
  • S-NSSAI Single Network Slice Selection Assistance Information
  • Step 5 SMF sends a create session management context response (Nsmf_PDUSession_CreateSMContextResponse) to AMF.
  • Nsmf_PDUSession_CreateSMContextResponse create session management context response
  • Step 6 PDU session assisted authentication/authorization.
  • Step 7 If dynamic policy and charging control (PCC) is used for the PDU session, the SMF performs policy control function (PCF) selection. And execute the session management policy establishment process, establish a session management (SM) policy association with PCF, and obtain the default PCC policy of the PDU session.
  • PCF policy control function
  • Step 8 Based on the RAT Type of the UE obtained in Step 3, assuming that the RAT Type is NB-IoT, the SMF determines not to establish a dedicated user plane connection for the session, that is, data transmission is implemented through service operations. At the same time, the SMF performs UPF selection. , including other connected UPF information in different time periods obtained by the SMF based on the ephemeris information of the UPF, where the UPF information includes service operation information.
  • service operation information There are four ways to obtain service operation information: first, configure it in UPF, and then send it to SMF through the N4 association establishment process; second, configure on-board UPF on SMF through Operation Administration and Maintenance (OAM) Service operation information; third, when UPF registers with NRF, it carries service operation information, and then SMF obtains it from NRF when needed; fourth, when OAM registers UPF with NRF, it carries the service operations supported by UPF, and then SMF obtains it from NRF when needed.
  • OAM Operation Administration and Maintenance
  • Step 9 SMF can execute the session management policy modification process and provide PCF with relevant information about the policy control request trigger (Policy Control Request Trigger) whose conditions have been met.
  • Policy Control Request Trigger Policy Control Request Trigger
  • Step 10a The SMF sends an N4 session establishment request message to all selected UPFs.
  • the message carries the first information.
  • the first information includes the identification and service operations of other UPFs connected to the UPF in different time periods.
  • the first information includes the UPF Information such as identification and service operation information of other connected UPFs, ephemeris information of satellites where other UPFs are located, session IP addresses, small data transmission instructions, event notification subscription instructions, etc.; or the first information includes the identification and service operation information of other UPFs connected to the UPF. Service operation information, session IP address, small data transmission instructions, event notification subscription instructions and other information.
  • the event notification subscription indication can be expressed as:
  • the Nupf_EventExposure_Notify service operation can be triggered to the peer UPF based on the session source IP address, and such data can be used as the payload body of the POST request;
  • the Nupf_EventExposure_Notify service operation can be triggered based on the session destination IP address.
  • the peer UPF triggers the Nupf_EventExposure_Notify service operation and uses such data as the payload body of the POST request.
  • SMF does not need to send N4 sessions to other UPFs except the N3 side UPF. Modify the request message.
  • Step 10b All UPFs send N4 session establishment response messages to SMF.
  • the N3 side UPF only sends the N3 side tunnel information allocated for the session.
  • the N3 side UPF does not need to allocate the N9 side tunnel information; except for the N3 side UPF Other UPFs do not need to distribute tunnel information.
  • Each UPF saves the service operation information of the peer UPF in different periods, including API URI, so that when small data on the session is received, the service operation is triggered to send small data.
  • UPFs other than the N3 side UPF do not need to send the N4 session modification response message to the SMF.
  • Step 11 The SMF sends an N1N2 message transfer request (Namf_Communication_N1N2MessageTransfer) to the AMF.
  • Namf_Communication_N1N2MessageTransfer N1N2 message transfer request
  • Steps 12-14 AMF sends an N2 session request to establish an N3 connection and a Radio Resource Control (Radio Resource Control, RRC) connection.
  • RRC Radio Resource Control
  • Step 14b When the N3 side UPF receives the small data of the session, it decapsulates and obtains the data information, such as the session source IP address or the session destination IP address. Then select the appropriate next step based on the UPF and the API URI of the UPF corresponding service operation saved in step 10a, as well as based on the current neighbor connection relationship and the inter-satellite visible time duration of the satellite (such as selecting the inter-satellite visible time duration).
  • One-hop UPF or calculate the connected UPF at the current moment and the inter-satellite visible time duration based on the ephemeris information of the UPF saved in step 10a, select the appropriate next-hop UPF, and trigger corresponding service operations, such as events Notification service operation (Nupf_EventExposure_Notify) uses the data to be sent as the payload body of the POST request to send the received small data to the next hop UPF.
  • events Notification service operation uses the data to be sent as the payload body of the POST request to send the received small data to the next hop UPF.
  • UPFs on the path only need to extract small data, obtain data information (such as session source IP address or session destination IP address), select the appropriate next-hop UPF, and trigger corresponding service operations, such as event notification service operations (Nupf_EventExposure_Notify) , use the data to be sent as the payload body of the POST request to send the data to the next hop UPF.
  • PSA extracts small data and forwards it directly to DN.
  • Step 15 AMF sends an update session management context request (Nsmf_PDUSession_UpdateSMContextRequest) to SMF to establish an N3 connection.
  • Nsmf_PDUSession_UpdateSMContextRequest an update session management context request
  • Step 16 SMF initiates the N4 session modification process to UPF to establish the N3 connection and register the PDU session (if not registered).
  • Step 17a When the PSA receives the small data, it obtains the data information, such as the session source IP address or the destination IP address. Then, based on the UPF and the API URI of the UPF corresponding service operation saved in step 10a, as well as the current neighbor connection relationship and the inter-satellite visible time duration of the satellite (such as selecting the inter-satellite visible time duration), select the appropriate next step.
  • the data information such as the session source IP address or the destination IP address.
  • One-hop UPF or calculate the currently connected UPF and the inter-satellite visible time duration based on the ephemeris information of the UPF saved in step 10a, select the appropriate next-hop UPF, and trigger the corresponding service operation, such as Nupf_EventExposure_Notify
  • the service operation uses the data to be sent as the payload body of the POST request to send the received small data to the next hop UPF.
  • UPFs on the path only need to extract small data, obtain data information (such as session source IP address or destination IP address) and select the appropriate next-hop UPF, and trigger the corresponding service operation, such as the Nupf_EventExposure_Notify service operation, the data to be sent As the payload body of the POST request to send data to the next hop UPF.
  • the UPF on the N3 side extracts the small data, encapsulates it into a General Packet Radio Service Tunneling Protocol (GPRS Tunneling Protocol, GTP) message and sends it to the RAN.
  • GTP General Packet Radio Service Tunneling Protocol
  • Step 17 SMF sends an update session management context response (Nsmf_PDUSession_UpdateSMContextResponse) to AMF.
  • Nsmf_PDUSession_UpdateSMContextResponse an update session management context response
  • Step 18 If the PDU session establishment fails, SMF calls the session management context status notification (Nsmf_PDUSession_SMContextStatusNotify (Release)) to notify AMF.
  • Nsmf_PDUSession_SMContextStatusNotify (Release)
  • Step 19 SMF goes to UE via UPF: If the PDU session type is IPv6 or IPv4v6, SMF generates IPv6 routing notification (IPv6Address Configuration) and sends it to UE and UPF through N4.
  • IPv6Address Configuration IPv6Address Configuration
  • Step 20 SMF executes the session management policy modification process.
  • Step 21 If the PDU session establishment fails after step 4, the SMF should execute Nudm_SDM_Unsubscribe to implement the subscription.
  • the UPF executes step 14b or step 17a.
  • Embodiment 2 UPF actively subscribes to other UPFs to realize data forwarding between user plane UPFs.
  • Figure 8 is a second implementation schematic diagram of the data transmission method provided by an embodiment of the present disclosure. As shown in Figure 8, it mainly includes the following steps:
  • Step 1 The UE initiates a PDU session establishment request to the AMF.
  • Step 2-3 AMF selects SMF to establish a session and triggers a create session management context request (Nsmf_PDUSession_CreateSMContextRequest) to SMF.
  • Nsmf_PDUSession_CreateSMContextRequest create session management context request
  • Step 4 If the session management subscription data related to SUPI, DNN and S-NSSAI is not available, SMF uses Nudm_SDM_Get(SUPI,Session Management Subscription data,DNN,S-NSSAI) to retrieve the session management subscription data and uses Nudm_SDM_Subscribe(SUPI ,Session Management Subscription data,DNN,S-NSSAI) subscribes to UDM for notifications about changes in contract data.
  • Step 5 SMF sends a create session management context response (Nsmf_PDUSession_CreateSMContextResponse) to AMF.
  • Nsmf_PDUSession_CreateSMContextResponse create session management context response
  • Step 6 PDU session assisted authentication/authorization.
  • Step 7 If PCC is used for the PDU session, the SMF performs the policy control function PCF selection and performs the session management policy establishment process, establishes an SM policy association with the PCF, and obtains the default PCC policy for the PDU session.
  • Step 8 Based on the RAT Type of the UE obtained in Step 3, assuming that the RAT Type is NB-IoT, the SMF determines not to establish a dedicated user plane connection for the session, that is, data transmission is implemented through service operations. At the same time, the SMF performs UPF selection. , including other connected UPF information in different time periods obtained by the SMF based on the ephemeris information of the UPF, where the UPF information includes service operation information.
  • service operation information There are four ways to obtain service operation information: first, configure it in UPF and then send it to SMF through the N4 association establishment process; second, OAM configures the service operation information of on-board UPF on SMF; third, UPF registers with NRF When OAM registers UPF with NRF, it carries the service operation information supported by UPF, and then SMF obtains it from NRF when needed.
  • Step 9 SMF can execute the session management policy modification process and provide PCF with relevant information about the policy control request trigger (Policy Control Request Trigger) whose conditions have been met.
  • Policy Control Request Trigger Policy Control Request Trigger
  • Step 10a The SMF sends an N4 session establishment request message to all selected UPFs.
  • the message carries the first information.
  • the first information includes the identification and service operations of other UPFs connected to the UPF in different time periods.
  • the SMF does not need to send the N4 session modification request message to other UPFs except the N3 side UPF.
  • Step 10b All UPFs send N4 session establishment response messages to SMF.
  • the N3 side UPF only sends the N3 side tunnel information allocated for the session.
  • the N3 side UPF does not need to allocate the N9 side tunnel information; except for the N3 side UPF Other UPFs do not need to distribute tunnel information.
  • Each UPF saves the service operation information of the peer UPF in different periods, including API URI, so that when small data on the session is received, the service operation is triggered to send small data.
  • UPFs other than the N3 side UPF do not need to send the N4 session modification response message to the SMF.
  • Step 10c Based on the received service operation information, the UPF triggers the event subscription service operation to the connected peer UPF in different time periods for subsequent sending of data messages, that is, triggering the Nupf_EventExposure_Subscribe service operation.
  • Step 11 The SMF sends an N1N2 message transfer request (Namf_Communication_N1N2MessageTransfer) to the AMF.
  • Namf_Communication_N1N2MessageTransfer N1N2 message transfer request
  • Steps 12-14 AMF sends an N2 session request to establish an N3 connection and an RRC connection.
  • Step 14b When the N3 side UPF receives the small data of the session, it decapsulates and obtains the data information, such as the session source IP address or the session destination IP address. Then select the appropriate next step based on the UPF and the API URI of the UPF corresponding service operation saved in step 10a, as well as based on the current neighbor connection relationship and the inter-satellite visible time duration of the satellite (such as selecting the inter-satellite visible time duration).
  • One-hop UPF or calculate the currently connected UPF and the inter-satellite visible time duration based on the ephemeris information of the UPF saved in step 10a, select the appropriate next-hop UPF, and trigger the corresponding service operation, such as Nupf_EventExposure_Notify
  • the service operation uses the data to be sent as the payload body of the POST request to send the received small data to the next hop UPF.
  • UPFs on the path only need to extract small data, obtain data information (such as session source IP address or session destination IP address), select the appropriate next-hop UPF, and trigger corresponding service operations, such as The Nupf_EventExposure_Notify service operation uses the data to be sent as the payload body of the POST request to send the data to the next hop UPF.
  • PSA extracts small data and forwards it directly to DN.
  • Step 15 AMF sends an update session management context request (Nsmf_PDUSession_UpdateSMContextRequest) to SMF to establish an N3 connection.
  • Nsmf_PDUSession_UpdateSMContextRequest an update session management context request
  • Step 16 SMF initiates the N4 session modification process to UPF to establish the N3 connection and register the PDU session (if not registered).
  • Step 17a When the PSA receives the small data, it obtains the data information, such as the session source IP address or the destination IP address. Then, based on the UPF and the API URI of the UPF corresponding service operation saved in step 10a, as well as the current neighbor connection relationship and the inter-satellite visible time duration of the satellite (such as selecting the inter-satellite visible time duration), select the appropriate next step.
  • the data information such as the session source IP address or the destination IP address.
  • One-hop UPF or calculate the currently connected UPF and the inter-satellite visible time duration based on the ephemeris information of the UPF saved in step 10a, select the appropriate next-hop UPF, and trigger the corresponding service operation, such as Nupf_EventExposure_Notify
  • the service operation uses the data to be sent as the payload body of the POST request to send the received small data to the next hop UPF.
  • UPFs on the path only need to extract small data, obtain data information (such as session source IP address or destination IP address) and select the appropriate next-hop UPF, and trigger the corresponding service operation, such as the Nupf_EventExposure_Notify service operation, the data to be sent As the payload body of the POST request to send data to the next hop UPF.
  • the UPF on the N3 side extracts the small data, encapsulates it into a GTP message and sends it to the RAN.
  • Step 17 SMF sends an update session management context response (Nsmf_PDUSession_UpdateSMContextResponse) to AMF.
  • Nsmf_PDUSession_UpdateSMContextResponse an update session management context response
  • Step 18 If the PDU session establishment fails, SMF calls the session management context status notification (Nsmf_PDUSession_SMContextStatusNotify (Release)) to notify AMF.
  • Nsmf_PDUSession_SMContextStatusNotify (Release)
  • Step 19 SMF goes to UE via UPF: If the PDU session type is IPv6 or IPv4v6, SMF generates IPv6 routing notification (IPv6Address Configuration) and sends it to UE and UPF through N4.
  • IPv6Address Configuration IPv6Address Configuration
  • Step 20 SMF executes the session management policy modification process.
  • Step 21 If the PDU session establishment fails after step 4, the SMF should execute Nudm_SDM_Unsubscribe to implement the subscription.
  • the UPF executes step 14b or step 17a.
  • Embodiment 3 UPF requests other UPF information from NRF, and UPF actively subscribes to other UPFs to realize data forwarding between user plane UPFs.
  • Figure 9 is a third implementation schematic diagram of the data transmission method provided by the embodiment of the present disclosure. As shown in Figure 9, it mainly includes the following steps:
  • Step 1 The UE initiates a PDU session establishment request to the AMF.
  • Step 2-3 AMF selects SMF to establish a session and triggers a create session management context request (Nsmf_PDUSession_CreateSMContextRequest) to SMF.
  • Nsmf_PDUSession_CreateSMContextRequest create session management context request
  • Step 4 If the session management subscription data related to SUPI, DNN and S-NSSAI is not available, SMF uses Nudm_SDM_Get(SUPI,Session Management Subscription data,DNN,S-NSSAI) to retrieve the session management subscription data and uses Nudm_SDM_Subscribe(SUPI ,Session Management Subscription data,DNN,S-NSSAI) subscribes to UDM for notifications about changes in contract data.
  • Step 5 SMF sends a create session management context response (Nsmf_PDUSession_CreateSMContextResponse) to AMF.
  • Nsmf_PDUSession_CreateSMContextResponse create session management context response
  • Step 6 PDU session assisted authentication/authorization.
  • Step 7 If PCC is used for the PDU session, the SMF performs the policy control function PCF selection and performs the session management policy establishment process, establishes an SM policy association with the PCF, and obtains the default PCC policy for the PDU session.
  • Step 8 Based on the RAT Type of the UE obtained in Step 3, assuming that the RAT Type is NB-IoT, the SMF determines not to establish a dedicated user plane connection for the session, that is, data transmission is implemented through service operations. At the same time, the SMF performs UPF selection. , including other connected UPF information in different time periods obtained by the SMF based on the ephemeris information of the UPF, where the UPF information includes service operation information (if any is saved).
  • Step 9 SMF can execute the session management policy modification process and provide PCF with relevant information about the policy control request trigger (Policy Control Request Trigger) whose conditions have been met.
  • Policy Control Request Trigger Policy Control Request Trigger
  • Step 10a SMF sends an N4 session establishment request message to all selected UPFs.
  • the message carries the first information.
  • the first information includes the UPF's time in different time periods.
  • SMF has UPF service operation information, it is also carried in this step. At this time, the SMF does not need to send the N4 session modification request message to other UPFs except the N3 side UPF.
  • Step 10b All UPFs send N4 session establishment response messages to SMF.
  • the N3 side UPF only sends the N3 side tunnel information allocated for the session.
  • the N3 side UPF does not need to allocate the N9 side tunnel information; except for the N3 side UPF Other UPFs do not need to distribute tunnel information.
  • Each UPF saves the service operation information of the peer UPF in different periods, including API URI, so that when small data on the session is received, the service operation is triggered to send small data.
  • UPFs other than the N3 side UPF do not need to send the N4 session modification response message to the SMF.
  • Step 10c If the UPF does not receive all the service operation information of the peer UPF in different time periods, it needs to obtain it from the NRF (UPF discovery) and save it. Based on the received service operation information, UPF triggers the event subscription service operation to the connected peer UPF in different time periods for subsequent sending of data messages, that is, triggering the Nupf_EventExposure_Subscribe service operation.
  • NRF UPF discovery
  • Step 11 The SMF sends an N1N2 message transfer request (Namf_Communication_N1N2MessageTransfer) to the AMF.
  • Namf_Communication_N1N2MessageTransfer N1N2 message transfer request
  • Steps 12-14 AMF sends an N2 session request to establish an N3 connection and an RRC connection.
  • Step 14b When the N3 side UPF receives the small data of the session, it decapsulates and obtains the data information, such as the session source IP address or the session destination IP address. Then select the appropriate next step based on the UPF and the API URI of the UPF corresponding service operation saved in step 10a, as well as based on the current neighbor connection relationship and the inter-satellite visible time duration of the satellite (such as selecting the inter-satellite visible time duration).
  • One-hop UPF or calculate the currently connected UPF and the inter-satellite visible time duration based on the ephemeris information of the UPF saved in step 10a, select the appropriate next-hop UPF, and trigger the corresponding service operation, such as Nupf_EventExposure_Notify
  • the service operation uses the data to be sent as the payload body of the POST request to send the received small data to the next hop UPF.
  • UPFs only need to extract small data, obtain data information (such as session source IP address or session destination IP address) and select the appropriate next-hop UPF, and trigger the corresponding service operation, such as the Nupf_EventExposure_Notify service operation, and use the data to be sent as The payload body of the POST request to send data to the next hop UPF.
  • PSA extracts small data and forwards it directly to DN.
  • Step 15 AMF sends an update session management context request (Nsmf_PDUSession_UpdateSMContextRequest) to SMF to establish an N3 connection.
  • Nsmf_PDUSession_UpdateSMContextRequest an update session management context request
  • Step 16 SMF initiates the N4 session modification process to UPF to establish the N3 connection and register the PDU session (if not registered).
  • Step 17a When the PSA receives the small data, it obtains the data information, such as the session source IP address or the destination IP address. Then, based on the UPF and the API URI of the UPF corresponding service operation saved in step 10a, as well as the current neighbor connection relationship and the inter-satellite visible time duration of the satellite (such as selecting the inter-satellite visible time duration), select the appropriate next step.
  • the data information such as the session source IP address or the destination IP address.
  • One-hop UPF or calculate the currently connected UPF and the inter-satellite visible time duration based on the ephemeris information of the UPF saved in step 10a, select the appropriate next-hop UPF, and trigger the corresponding service operation, such as Nupf_EventExposure_Notify
  • the service operation uses the data to be sent as the payload body of the POST request to send the received small data to the next hop UPF.
  • UPFs on the path only need to extract small data, obtain data information (such as session source IP address or destination IP address) and select the appropriate next-hop UPF, and trigger the corresponding service operation, such as the Nupf_EventExposure_Notify service operation, the data to be sent As the payload body of the POST request to send data to the next hop UPF.
  • the UPF on the N3 side extracts the small data, encapsulates it into a GTP message and sends it to the RAN.
  • Step 17 SMF sends an update session management context response (Nsmf_PDUSession_UpdateSMContextResponse) to AMF.
  • Nsmf_PDUSession_UpdateSMContextResponse an update session management context response
  • Step 18 If the PDU session establishment fails, SMF calls the session management context status notification (Nsmf_PDUSession_SMContextStatusNotify (Release)) to notify AMF.
  • Nsmf_PDUSession_SMContextStatusNotify (Release)
  • Step 19 SMF goes to UE via UPF: If the PDU session type is IPv6 or IPv4v6, SMF generates IPv6 routing notification (IPv6Address Configuration) and sends it to UE and UPF through N4.
  • IPv6Address Configuration IPv6Address Configuration
  • Step 20 SMF executes the session management policy modification process.
  • Step 21 If the PDU session establishment fails after step 4, the SMF should execute Nudm_SDM_Unsubscribe to implement the subscription.
  • the UPF executes step 14b or step 17a.
  • Embodiment 4-5 Based on the request-response method, data forwarding between user plane UPFs is implemented.
  • Embodiment 4 When the SMF obtains UPF-related information (including service operation information) through NRF, or the SMF has configured UPF-related information (including service operation information), data forwarding between user plane UPFs is implemented.
  • Figure 10 is a fourth implementation schematic diagram of the data transmission method provided by the embodiment of the present disclosure. As shown in Figure 10, it mainly includes the following steps:
  • Step 1 The UE initiates a PDU session establishment request to the AMF.
  • Step 2-3 AMF selects SMF to establish a session and triggers a create session management context request (Nsmf_PDUSession_CreateSMContextRequest) to SMF.
  • Nsmf_PDUSession_CreateSMContextRequest create session management context request
  • Step 4 If the session management subscription data related to SUPI, DNN and S-NSSAI is not available, SMF uses Nudm_SDM_Get(SUPI,Session Management Subscription data,DNN,S-NSSAI) to retrieve the session management subscription data and uses Nudm_SDM_Subscribe(SUPI ,Session Management Subscription data,DNN,S-NSSAI) subscribes to UDM for notifications about changes in contract data.
  • Step 5 SMF sends a create session management context response (Nsmf_PDUSession_CreateSMContextResponse) to AMF.
  • Nsmf_PDUSession_CreateSMContextResponse create session management context response
  • Step 6 PDU session assisted authentication/authorization.
  • Step 7 If PCC is used for the PDU session, the SMF performs the policy control function PCF selection and performs the session management policy establishment process, establishes an SM policy association with the PCF, and obtains the default PCC policy for the PDU session.
  • Step 8 Based on the RAT Type of the UE obtained in Step 3, assuming that the RAT Type is NB-IoT, the SMF determines not to establish a dedicated user plane connection for the session, that is, data transmission is implemented through service operations. At the same time, the SMF performs UPF selection. , including other connected UPF information in different time periods obtained by the SMF based on the ephemeris information of the UPF, where the UPF information includes service operation information.
  • service operation information There are four ways to obtain service operation information: first, configure it in UPF, and then use N4 The association establishment process is sent to SMF; second, OAM configures the service operation information of on-board UPF on SMF; third, UPF carries the service operation information when registering with NRF, and then SMF obtains it from NRF when needed; fourth, OAM registers UPF with NRF It carries the service operations supported by UPF, and then SMF obtains them from NRF when needed.
  • Step 9 SMF can execute the session management policy modification process and provide PCF with relevant information about the policy control request trigger (Policy Control Request Trigger) whose conditions have been met.
  • Policy Control Request Trigger Policy Control Request Trigger
  • Step 10a The SMF sends an N4 session establishment request message to all selected UPFs.
  • the message carries the first information.
  • the first information includes the identification and service operations of other UPFs connected to the UPF in different time periods.
  • the SMF does not need to send the N4 session modification request message to other UPFs except the N3 side UPF.
  • Step 10b All UPFs send N4 session establishment response messages to SMF.
  • the N3 side UPF only sends the N3 side tunnel information allocated for the session.
  • the N3 side UPF does not need to allocate the N9 side tunnel information; except for the N3 side UPF Other UPFs do not need to distribute tunnel information.
  • Each UPF saves the service operation information of the peer UPF in different periods, including API URI, so that when small data on the session is received, the service operation is triggered to send small data.
  • UPFs other than the N3 side UPF do not need to send the N4 session modification response message to the SMF.
  • Step 11 The SMF sends an N1N2 message transfer request (Namf_Communication_N1N2MessageTransfer) to the AMF.
  • Namf_Communication_N1N2MessageTransfer N1N2 message transfer request
  • Steps 12-14 AMF sends an N2 session request to establish an N3 connection and an RRC connection.
  • Step 14b When the N3 side UPF receives the small data of the session, it decapsulates and obtains the data information, such as the session source IP address or the session destination IP address. Then select the appropriate next step based on the UPF and the API URI of the UPF corresponding service operation saved in step 10a, as well as based on the current neighbor connection relationship and the inter-satellite visible time duration of the satellite (such as selecting the inter-satellite visible time duration).
  • a jump UPF or calculate the currently connected UPF and the inter-satellite visibility time of the satellite based on the ephemeris information of the UPF saved in step 10a, select the appropriate next-hop UPF, and trigger the corresponding service operation, such as a data transmission request (Nupf_PDUSession_TransferData Request) service operation uses the data to be sent as the payload body of the POST request to send the received small data to the next hop UPF.
  • a data transmission request such as a data transmission request (Nupf_PDUSession_TransferData Request) service operation uses the data to be sent as the payload body of the POST request to send the received small data to the next hop UPF.
  • UPFs on the path only need to extract small data, obtain data information (such as session source IP address or session destination IP address), select the appropriate next-hop UPF, and trigger corresponding service operations, such as data transfer request (Nupf_PDUSession_TransferData Request) Service operation, use the data to be sent as the payload body of the POST request to send the data to the next hop UPF.
  • PSA extracts small data and forwards it directly to DN.
  • all UPFs must trigger the data transfer response (Nupf_PDUSession_TransferData Response) service operation to respond.
  • Step 15 AMF sends an update session management context request (Nsmf_PDUSession_UpdateSMContextRequest) to SMF to establish an N3 connection.
  • Nsmf_PDUSession_UpdateSMContextRequest an update session management context request
  • Step 16 SMF initiates the N4 session modification process to UPF to establish the N3 connection and register the PDU session (if not registered).
  • Step 17a When the PSA receives the small data, it obtains the data information, such as the session source IP address or the destination IP address. Then, based on the UPF and the API URI of the UPF corresponding service operation saved in step 10a, as well as the current neighbor connection relationship and the inter-satellite visible time duration of the satellite (such as selecting the inter-satellite visible time duration), select the appropriate next step.
  • the data information such as the session source IP address or the destination IP address.
  • One-hop UPF or calculate the connected UPF at the current moment and the inter-satellite visible time duration based on the ephemeris information of the UPF saved in step 10a, select the appropriate next-hop UPF, and trigger the corresponding service operation, such as data
  • the transfer request (Nupf_PDUSession_TransferData Request) service operation uses the data to be sent as the payload body of the POST request to send the received small data to the next hop UPF.
  • UPFs on the path only need to extract small data, obtain data information (such as session source IP address or destination IP address), select the appropriate next-hop UPF, and trigger corresponding service operations, such as the data transfer request (Nupf_PDUSession_TransferData Request) service Operation, use the data to be sent as the payload body of the POST request to send the data to the next hop UPF.
  • the UPF on the N3 side extracts the small data, encapsulates it into a GTP message and sends it to the RAN.
  • the data transfer response (Nupf_PDUSession_TransferData Response) service operation must be triggered to respond.
  • Step 17 SMF sends an update session management context response (Nsmf_PDUSession_UpdateSMContextResponse) to AMF.
  • Nsmf_PDUSession_UpdateSMContextResponse an update session management context response
  • Step 18 If the PDU session establishment fails, SMF calls the session management context status notification (Nsmf_PDUSession_SMContextStatusNotify (Release)) to notify AMF.
  • Nsmf_PDUSession_SMContextStatusNotify (Release)
  • Step 19 SMF goes to UE via UPF: If the PDU session type is IPv6 or IPv4v6, SMF generates IPv6 routing notification (IPv6Address Configuration) and sends it to UE and UPF through N4.
  • IPv6Address Configuration IPv6Address Configuration
  • Step 20 SMF executes the session management policy modification process.
  • Step 21 If the PDU session establishment fails after step 4, the SMF should execute Nudm_SDM_Unsubscribe to implement the subscription.
  • the UPF executes step 14b or step 17a.
  • Embodiment 5 UPF obtains UPF-related information (including service operation information) through NRF to implement data forwarding between user plane UPFs.
  • Figure 11 is a fifth implementation schematic diagram of the data transmission method provided by the embodiment of the present disclosure. As shown in Figure 11, it mainly includes the following steps:
  • Step 1 The UE initiates a PDU session establishment request to the AMF.
  • Step 2-3 AMF selects SMF to establish a session and triggers a create session management context request (Nsmf_PDUSession_CreateSMContextRequest) to SMF.
  • Nsmf_PDUSession_CreateSMContextRequest create session management context request
  • Step 4 If the session management subscription data related to SUPI, DNN and S-NSSAI is not available, SMF uses Nudm_SDM_Get(SUPI,Session Management Subscription data,DNN,S-NSSAI) to retrieve the session management subscription data and uses Nudm_SDM_Subscribe(SUPI ,Session Management Subscription data,DNN,S-NSSAI) subscribes to UDM for notifications about changes in contract data.
  • Step 5 SMF sends a create session management context response (Nsmf_PDUSession_CreateSMContextResponse) to AMF.
  • Nsmf_PDUSession_CreateSMContextResponse create session management context response
  • Step 6 PDU session assisted authentication/authorization.
  • Step 7 If PCC is used for the PDU session, the SMF performs the policy control function PCF selection and performs the session management policy establishment process, establishes an SM policy association with the PCF, and obtains the default PCC policy for the PDU session.
  • Step 8 Based on the RAT Type of the UE obtained in Step 3, assuming that the RAT Type is NB-IoT, the SMF determines not to establish a dedicated user plane connection for the session, that is, data transmission is implemented through service operations. At the same time, the SMF performs UPF selection. , including other connected UPF information in different time periods obtained by the SMF based on the ephemeris information of the UPF, where the UPF information includes service operation information (if any is saved).
  • Step 9 SMF can execute the session management policy modification process and provide PCF with relevant information about the policy control request trigger (Policy Control Request Trigger) whose conditions have been met.
  • Policy Control Request Trigger Policy Control Request Trigger
  • Step 10a The SMF sends an N4 session establishment request message to all selected UPFs.
  • the message carries the first information.
  • the first information includes the identifiers of other UPFs connected to the UPF in different time periods, and other UPFs.
  • Step 10b All UPFs send N4 session establishment response messages to SMF.
  • the N3 side UPF only sends the N3 side tunnel information allocated for the session.
  • the N3 side UPF does not need to allocate the N9 side tunnel information; except for the N3 side UPF Other UPFs do not need to distribute tunnel information.
  • Each UPF saves the service operation information of the peer UPF in different periods, including API URI, so that when small data on the session is received, the service operation is triggered to send small data.
  • UPFs other than the N3 side UPF do not need to send the N4 session modification response message to the SMF.
  • Step 10c If the UPF does not receive all the service operation information of the peer UPF in different time periods, it needs to obtain it from the NRF (UPF discovery) and save it.
  • NRF UPF discovery
  • Step 11 SMF sends N1N2 message transmission request to AMF (Namf_Communication_N1N2MessageTransfer).
  • Steps 12-14 AMF sends an N2 session request to establish an N3 connection and an RRC connection.
  • Step 14b When the N3 side UPF receives the small data of the session, it decapsulates and obtains the data information, such as the session source IP address or the session destination IP address. Then select the appropriate next step based on the UPF and the API URI of the UPF corresponding service operation saved in step 10a, as well as based on the current neighbor connection relationship and the inter-satellite visible time duration of the satellite (such as selecting the inter-satellite visible time duration).
  • One-hop UPF or calculate the connected UPF at the current moment and the inter-satellite visible time duration based on the ephemeris information of the UPF saved in step 10a, select the appropriate next-hop UPF, and trigger the corresponding service operation, such as data
  • the transfer request (Nupf_PDUSession_TransferData Request) service operation uses the data to be sent as the payload body of the POST request to send the received small data to the next hop UPF.
  • UPFs on the path only need to extract small data, obtain data information (such as session source IP address or session destination IP address), select the appropriate next-hop UPF, and trigger corresponding service operations, such as data transfer request (Nupf_PDUSession_TransferData Request) Service operation, use the data to be sent as the payload body of the POST request to send the data to the next hop UPF.
  • PSA extracts small data and forwards it directly to DN.
  • all UPFs must trigger the data transfer response (Nupf_PDUSession_TransferData Response) service operation to respond.
  • Step 15 AMF sends an update session management context request (Nsmf_PDUSession_UpdateSMContextRequest) to SMF to establish an N3 connection.
  • Nsmf_PDUSession_UpdateSMContextRequest an update session management context request
  • Step 16 SMF initiates the N4 session modification process to UPF to establish the N3 connection and register the PDU session (if not registered).
  • Step 17a When the PSA receives the small data, it obtains the data information, such as the session source IP address or the destination IP address. Then, based on the UPF and the API URI of the UPF corresponding service operation saved in step 10a, as well as the current neighbor connection relationship and the inter-satellite visible time duration of the satellite (such as selecting the inter-satellite visible time duration), select the appropriate next step.
  • the data information such as the session source IP address or the destination IP address.
  • One-hop UPF or calculate the connected UPF at the current moment and the inter-satellite visible time duration based on the ephemeris information of the UPF saved in step 10a, select the appropriate next-hop UPF, and trigger the corresponding service operation, such as data Transfer request (Nupf_PDUSession_TransferData Request) service operation, the data to be sent is The payload body of the POST request to send the received small data to the next hop UPF.
  • Nupf_PDUSession_TransferData Request data Transfer request
  • UPFs on the path only need to extract small data, obtain data information (such as session source IP address or destination IP address), select the appropriate next-hop UPF, and trigger corresponding service operations, such as the data transfer request (Nupf_PDUSession_TransferData Request) service Operation, use the data to be sent as the payload body of the POST request to send the data to the next hop UPF.
  • the UPF on the N3 side extracts the small data, encapsulates it into a GTP message and sends it to the RAN.
  • all UPFs must trigger the data transfer response (Nupf_PDUSession_TransferData Response) service operation to respond.
  • Step 17 SMF sends an update session management context response (Nsmf_PDUSession_UpdateSMContextResponse) to AMF.
  • Nsmf_PDUSession_UpdateSMContextResponse an update session management context response
  • Step 18 If the PDU session establishment fails, SMF calls the session management context status notification (Nsmf_PDUSession_SMContextStatusNotify (Release)) to notify AMF.
  • Nsmf_PDUSession_SMContextStatusNotify (Release)
  • Step 19 SMF goes to UE via UPF: If the PDU session type is IPv6 or IPv4v6, SMF generates IPv6 routing notification (IPv6Address Configuration) and sends it to UE and UPF through N4.
  • IPv6Address Configuration IPv6Address Configuration
  • Step 20 SMF executes the session management policy modification process.
  • Step 21 If the PDU session establishment fails after step 4, the SMF should execute Nudm_SDM_Unsubscribe to implement the subscription.
  • the UPF executes step 14b or step 17a.
  • Figure 12 is a schematic structural diagram of a first user plane functional network element provided by an embodiment of the present disclosure.
  • the first user plane functional network element includes a memory 1220, a transceiver 1210 and a processor 1200; wherein, the processor 1200 and memory 1220 may also be physically separated.
  • the memory 1220 is used to store computer programs; the transceiver 1210 is used to send and receive data under the control of the processor 1200.
  • the transceiver 1210 is used to receive and transmit data under the control of the processor 1200.
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1200 and various circuits of the memory represented by memory 1220 are linked together.
  • the bus architecture can also link together various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all well known in the art and therefore will not be described further in this disclosure.
  • the bus interface provides the interface.
  • the transceiver 1210 may be a plurality of elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical cables, and other transmission media.
  • the processor 1200 is responsible for managing the bus architecture and general processing, and the memory 1220 can store data used by the processor 1200 when performing operations.
  • the processor 1200 may be a central processing unit (CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field-Programmable Gate Array, FPGA) or a complex programmable logic device (Complex Programmable Logic Device (CPLD), the processor can also adopt a multi-core architecture.
  • CPU central processing unit
  • ASIC Application Specific Integrated Circuit
  • FPGA field programmable gate array
  • CPLD Complex Programmable Logic Device
  • the processor 1200 is configured to execute any of the methods provided by the embodiments of the present disclosure according to the obtained executable instructions by calling the computer program stored in the memory 1220, for example: receiving the N4 session establishment request message sent by the session management function network element, N4
  • the session establishment request message carries the first information; the first information is used to instruct the first user plane functional network element to transmit specified data through a service operation; and the data matching the first information is sent to the next hop user through the service operation. functional network elements.
  • the first information includes one or more of the following:
  • the second user plane functional network element includes multiple user plane functional network elements connected to the first user plane functional network element in different time periods;
  • the information of the second user plane functional network element includes one or more of the following:
  • the identification information of the second user plane functional network element is the identification information of the second user plane functional network element
  • Ephemeris information of the satellite where the second user plane functional network element is located
  • data matching the first information is sent to the next-hop user plane functional network element through service operations, including:
  • Data matching the first information is sent to the next-hop user plane functional network element through an event notification service operation or a data transmission request service operation.
  • the method before sending the data matching the first information to the next-hop user plane functional network element through the event notification service operation, the method further includes:
  • the method before sending the data matching the first information to the next-hop user plane functional network element through the service operation, the method further includes:
  • the inter-satellite visibility time between satellites where the user plane functional network element is located determines the next hop user plane functional network element.
  • the method further includes:
  • service operation information of user plane function network elements connected to the first user plane function network element in different time periods is obtained from the network storage function network element.
  • the method further includes:
  • the N4 session establishment response message carries the N3 tunnel information of the N3 side user plane function network element.
  • the method further includes:
  • the downlink data After receiving the downlink data, the downlink data is encapsulated, and the encapsulated data is sent to the access network device.
  • the method further includes:
  • After receiving the uplink data After receiving the uplink data, send the uplink data to the data network; and/or,
  • the downlink data is sent to the next hop user plane functional network element through service operations.
  • Figure 13 is a schematic structural diagram of a session management function network element provided by an embodiment of the present disclosure.
  • the session management function network element includes a memory 1320, a transceiver 1310 and a processor 1300; wherein, the processor 1300 and the memory 1320 They can also be physically separated.
  • the memory 1320 is used to store computer programs; the transceiver 1310 is used to send and receive data under the control of the processor 1300.
  • the transceiver 1310 is used to receive and transmit data under the control of the processor 1300.
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1300 and various circuits of the memory represented by memory 1320 are linked together. Bus architectures can also integrate circuits such as peripherals, voltage regulators, and power management Various other circuits, etc., are linked together, which are well known in the art, and therefore will not be further described in this disclosure.
  • the bus interface provides the interface.
  • the transceiver 1310 may be a plurality of elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical cables, and other transmission media.
  • the processor 1300 is responsible for managing the bus architecture and general processing, and the memory 1320 can store data used by the processor 1300 when performing operations.
  • the processor 1300 can be a CPU, ASIC, FPGA or CPLD, and the processor can also adopt a multi-core architecture.
  • the processor 1300 is configured to execute any of the methods provided by the embodiments of the present disclosure according to the obtained executable instructions by calling the computer program stored in the memory 1320, for example: determining to perform data transmission through a service operation;
  • the N4 session establishment request message is sent by the network element, and the N4 session establishment request message carries the first information; the first information is used to instruct the first user plane functional network element to transmit designated data through service operations.
  • the first information includes one or more of the following:
  • the second user plane functional network element includes multiple user plane functional network elements connected to the first user plane functional network element in different time periods;
  • the information of the second user plane functional network element includes one or more of the following:
  • the identification information of the second user plane functional network element is the identification information of the second user plane functional network element
  • Ephemeris information of the satellite where the second user plane functional network element is located
  • determine data transmission through service operations including:
  • the data transmission of the terminal is determined through the service operation.
  • the method further includes:
  • the N4 session establishment response message carries the N3 tunnel information of the N3 side user plane functional network element.
  • first user plane functional network element and session management functional network element provided by the embodiments of the present disclosure can implement all the method steps implemented by the above method embodiments, and can achieve the same technical effect.
  • the parts and beneficial effects in this embodiment that are the same as those in the method embodiment will not be described in detail.
  • Figure 14 is one of the structural schematic diagrams of a data transmission device provided by an embodiment of the present disclosure.
  • the device is applied to the first user plane functional network element.
  • the device includes:
  • the first receiving unit 1400 is configured to receive the N4 session establishment request message sent by the session management function network element.
  • the N4 session establishment request message carries the first information; the first information is used to instruct the first user plane function network element to perform service operations. Specify the transmission of data;
  • the first sending unit 1410 is configured to send data matching the first information to the next-hop user plane functional network element through service operations.
  • the first information includes one or more of the following:
  • the second user plane functional network element includes multiple user plane functional network elements connected to the first user plane functional network element in different time periods;
  • the information of the second user plane functional network element includes one or more of the following:
  • the identification information of the second user plane functional network element is the identification information of the second user plane functional network element
  • Ephemeris information of the satellite where the second user plane functional network element is located
  • data matching the first information is sent to the next-hop user plane functional network element through service operations, including:
  • Data matching the first information is sent to the next-hop user plane functional network element through an event notification service operation or a data transmission request service operation.
  • the device also includes:
  • a subscription unit configured to subscribe to user plane functional network elements connected to the first user plane functional network element in different time periods according to the service operation information of the user plane functional network elements connected to the first user plane functional network element in different time periods. Trigger event subscription service operation.
  • the device also includes:
  • the first determining unit is configured to operate according to the service operation information of the user plane functional network element connected to the first user plane functional network element in the current time period, and the user plane function connected to the first user plane functional network element in the current time period.
  • the inter-satellite visibility time between the satellite where the network element is located and the satellite where the first user plane functional network element is located determines the next hop user plane functional network element.
  • the device also includes an acquisition unit for:
  • service operation information of user plane function network elements connected to the first user plane function network element in different time periods is obtained from the network storage function network element.
  • the first sending unit 1410 is also used to:
  • the N4 session establishment response message carries the N3 tunnel information of the N3 side user plane function network element.
  • the first sending unit 1410 is also used to:
  • the first sending unit 1410 is also used to:
  • After receiving the uplink data After receiving the uplink data, send the uplink data to the data network; and/or,
  • the downlink data is sent to the next hop user plane functional network element through service operations.
  • Figure 15 is a second structural schematic diagram of a data transmission device provided by an embodiment of the present disclosure.
  • the device is applied to a session management function network element.
  • the device includes:
  • the second determination unit 1500 is used to determine data transmission through service operations
  • the second sending unit 1510 is configured to send an N4 session establishment request message to the first user plane functional network element.
  • the N4 session establishment request message carries the first information; the first information is used to instruct the first user plane functional network element to operate through the service. Transfer specified data.
  • the first information includes one or more of the following:
  • the second user plane functional network element includes multiple user plane functional network elements connected to the first user plane functional network element in different time periods;
  • the information of the second user plane functional network element includes one or more of the following:
  • the identification information of the second user plane functional network element is the identification information of the second user plane functional network element
  • Ephemeris information of the satellite where the second user plane functional network element is located
  • determine data transmission through service operations including:
  • the data transmission of the terminal is determined through the service operation.
  • the device when the first user plane functional network element is an N3 side user plane functional network element, the device further includes:
  • the second receiving unit is configured to receive an N4 session establishment response message sent by the N3 side user plane functional network element.
  • the N4 session establishment response message carries the N3 tunnel information of the N3 side user plane functional network element.
  • each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above integrated units can be implemented in the form of hardware or software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a processor-readable storage medium.
  • the technical solution of the present disclosure is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to cause a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in various embodiments of the present disclosure.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .
  • embodiments of the present disclosure also provide a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program.
  • the computer program is used to cause the computer to execute the data transmission method provided by the above embodiments.
  • the computer-readable storage medium can be any available media or data that can be accessed by a computer Storage devices, including but not limited to magnetic memory (such as floppy disk, hard disk, tape, magneto-optical disk (MO), etc.), optical memory (such as CD, DVD, BD, HVD, etc.), and semiconductor memory (such as ROM, EPROM, EEPROM, Non-volatile memory (NAND FLASH), solid state drive (SSD)), etc.
  • magnetic memory such as floppy disk, hard disk, tape, magneto-optical disk (MO), etc.
  • optical memory such as CD, DVD, BD, HVD, etc.
  • semiconductor memory such as ROM, EPROM, EEPROM, Non-volatile memory (NAND FLASH), solid state drive (SSD)
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • GPRS general packet Wireless service
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD LTE time division duplex
  • UMTS Universal mobile telecommunication system
  • WiMAX microwave access
  • 5G New Radio, NR 5G New Radio
  • EPS Evolved Packet System
  • 5GS 5G system
  • EPS Evolved Packet System
  • 5GS 5G system
  • the terminal involved in the embodiments of the present disclosure may be a device that provides voice and/or data connectivity to users, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem, etc.
  • the name of the terminal may be different.
  • the terminal may be called User Equipment (UE).
  • UE User Equipment
  • Wireless terminal equipment can communicate with one or more core networks (Core Network, CN) via a Radio Access Network (RAN).
  • RAN Radio Access Network
  • the wireless terminal equipment can be a mobile terminal equipment, such as a mobile phone (also known as a "cellular phone").
  • Wireless terminal equipment may also be called a system, a subscriber unit (subscriber unit), Subscriber station, mobile station, mobile, remote station, access point, remote terminal, access terminal ), user terminal equipment (user terminal), user agent (user agent), and user device (user device) are not limited in the embodiments of the present disclosure.
  • embodiments of the present disclosure may be provided as methods, systems, or computer program products. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) embodying computer-usable program code therein.
  • a computer-usable storage media including, but not limited to, magnetic disk storage, optical storage, and the like
  • processor-executable instructions may also be stored in a processor-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the generation of instructions stored in the processor-readable memory includes the manufacture of the instruction means product, the instruction device implements the function specified in one process or multiple processes in the flow chart and/or one block or multiple blocks in the block diagram.
  • processor-executable instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby causing the computer or other programmable device to
  • the instructions that are executed provide steps for implementing the functions specified in a process or processes of the flowchart diagrams and/or a block or blocks of the block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • General Physics & Mathematics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例提供一种数据传输方法、设备、装置及存储介质，其中应用于第一用户面功能网元，该方法包括：接收会话管理功能网元发送的N4会话建立请求消息，所述N4会话建立请求消息中携带第一信息；所述第一信息用于指示所述第一用户面功能网元通过服务操作进行指定数据的传输；通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元。通过会话管理功能网元在N4会话建立请求消息中携带第一信息，指示第一用户面功能网元通过服务操作进行指定数据的传输，使得数据不需要传输至地面，且无需建立专用的用户面隧道即可实现数据传输，不仅提高了数据传输效率，而且能够节省星上的用户面资源。

Description

数据传输方法、设备、装置及存储介质
相关申请的交叉引用
本申请要求于2022年04月07日提交的申请号为202210363826.9，发明名称为“数据传输方法、设备、装置及存储介质”的中国专利申请的优先权，其通过引用方式全部并入本文。
技术领域
本公开涉及无线通信技术领域，尤其涉及一种数据传输方法、设备、装置及存储介质。
背景技术
第五代移动通信(5th Generation Mobile Communication，5G)系统服务于多种场景，旨在提供无处不在的移动网络接入和高速的数据传输。相比地面移动通信网络，卫星通信利用高、中、低轨卫星可实现广域甚至全球覆盖，5G系统结合卫星通信技术，可以进一步实现全球无缝覆盖。目前5G系统融合卫星的方案包括：将卫星作为接入网设备(如基站)的一部分为终端(也称用户设备，User Equipment，UE)提供接入、或将部分网络功能(例如基站、网关(即用户面功能))部署在卫星上。
现有技术中，对于发送小数据的设备终端的数据传输，如果采用控制面数据传输方式实现数据传输，则需要借助地面上部署的控制面网元实现数据传输，这样就会增加数据传输时延；若采用建立专用的用户面连接方式实现数据传输，即建立用户面隧道，则由于卫星网络拓扑动态变化，部署在卫星上的用户面功能(User Plane Function，UPF)需根据网络拓扑变化实时维护用户面隧道信息，这样就会造成用户面资源的浪费，对稀缺的星上资源也是一种挑战。
发明内容
本公开实施例提供一种数据传输方法、设备、装置及存储介质，用以降 低数据传输时延，并减少用户面资源的使用。
第一方面，本公开实施例提供一种数据传输方法，应用于第一用户面功能网元，包括：
接收会话管理功能网元发送的N4会话建立请求消息，所述N4会话建立请求消息中携带第一信息；所述第一信息用于指示所述第一用户面功能网元通过服务操作进行指定数据的传输；
通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元。
可选地，所述第一信息包括以下一项或多项：
第二用户面功能网元的信息；所述第二用户面功能网元包括所述第一用户面功能网元在不同时间段所连接的多个用户面功能网元；
会话IP地址；
小数据传输指示；
事件通知订阅指示。
可选地，所述第二用户面功能网元的信息包括以下一项或多项：
所述第二用户面功能网元的标识信息；
所述第二用户面功能网元与所述第一用户面功能网元之间建立连接的时间相关信息；
所述第二用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长；
所述第二用户面功能网元所在卫星的星历信息；
所述第二用户面功能网元的服务操作信息。
可选地，所述通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元，包括：
通过事件通知服务操作或数据传输请求服务操作，将与所述第一信息相匹配的数据发送给下一跳用户面功能网元。
可选地，在通过事件通知服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元之前，所述方法还包括：
根据所述第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息，向所述第一用户面功能网元在不同时间段所连接的用户面功能网元触发事件订阅服务操作。
可选地，所述通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元之前，所述方法还包括：
根据所述第一用户面功能网元在当前时间段所连接的用户面功能网元的服务操作信息，以及所述第一用户面功能网元在当前时间段所连接的用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长，确定下一跳用户面功能网元。
可选地，所述接收会话管理功能网元发送的N4会话建立请求消息之后，所述方法还包括：
从所述N4会话建立请求消息中获取所述第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息；或者，
根据所述N4会话建立请求消息，从网络存储功能网元中获取所述第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息。
可选地，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述接收会话管理功能网元发送的N4会话建立请求消息之后，所述方法还包括：
向所述会话管理功能网元发送N4会话建立响应消息，所述N4会话建立响应消息中携带所述N3侧用户面功能网元的N3隧道信息。
可选地，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述方法还包括：
在接收上行数据后，对所述上行数据进行解封装，通过服务操作将解封装后得到的数据发送给下一跳用户面功能网元；和/或，
在接收下行数据后，对所述下行数据进行封装，将封装后的数据发送给接入网设备。
可选地，在所述第一用户面功能网元为锚点用户面功能网元的情况下，所述方法还包括：
在接收上行数据后，将所述上行数据发送给数据网络；和/或，
在接收下行数据后，通过服务操作将所述下行数据发送给下一跳用户面功能网元。
第二方面，本公开实施例还提供一种数据传输方法，应用于会话管理功能网元，包括：
确定通过服务操作进行数据传输；
向第一用户面功能网元发送N4会话建立请求消息，所述N4会话建立请求消息中携带第一信息；所述第一信息用于指示所述第一用户面功能网元通过服务操作进行指定数据的传输。
可选地，所述第一信息包括以下一项或多项：
第二用户面功能网元的信息；所述第二用户面功能网元包括所述第一用户面功能网元在不同时间段所连接的多个用户面功能网元；
会话IP地址；
小数据传输指示；
事件通知订阅指示。
可选地，所述第二用户面功能网元的信息包括以下一项或多项：
所述第二用户面功能网元的标识信息；
所述第二用户面功能网元与所述第一用户面功能网元之间建立连接的时间相关信息；
所述第二用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长；
所述第二用户面功能网元所在卫星的星历信息；
所述第二用户面功能网元的服务操作信息。
可选地，所述确定通过服务操作进行数据传输，包括：
根据终端的无线接入类型，确定通过服务操作进行所述终端的数据传输。
可选地，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述向第一用户面功能网元发送N4会话建立请求消息之后，所述方法还包括：
接收所述N3侧用户面功能网元发送的N4会话建立响应消息，所述N4会话建立响应消息中携带所述N3侧用户面功能网元的N3隧道信息。
第三方面，本公开实施例还提供一种第一用户面功能网元，包括存储器，收发机，处理器：
存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
接收会话管理功能网元发送的N4会话建立请求消息，所述N4会话建立请求消息中携带第一信息；所述第一信息用于指示所述第一用户面功能网元通过服务操作进行指定数据的传输；
通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元。
可选地，所述第一信息包括以下一项或多项：
第二用户面功能网元的信息；所述第二用户面功能网元包括所述第一用户面功能网元在不同时间段所连接的多个用户面功能网元；
会话IP地址；
小数据传输指示；
事件通知订阅指示。
可选地，所述第二用户面功能网元的信息包括以下一项或多项：
所述第二用户面功能网元的标识信息；
所述第二用户面功能网元与所述第一用户面功能网元之间建立连接的时间相关信息；
所述第二用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长；
所述第二用户面功能网元所在卫星的星历信息；
所述第二用户面功能网元的服务操作信息。
可选地，所述通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元，包括：
通过事件通知服务操作或数据传输请求服务操作，将与所述第一信息相 匹配的数据发送给下一跳用户面功能网元。
可选地，在通过事件通知服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元之前，所述操作还包括：
根据所述第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息，向所述第一用户面功能网元在不同时间段所连接的用户面功能网元触发事件订阅服务操作。
可选地，所述通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元之前，所述操作还包括：
根据所述第一用户面功能网元在当前时间段所连接的用户面功能网元的服务操作信息，以及所述第一用户面功能网元在当前时间段所连接的用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长，确定下一跳用户面功能网元。
可选地，所述接收会话管理功能网元发送的N4会话建立请求消息之后，所述操作还包括：
从所述N4会话建立请求消息中获取所述第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息；或者，
根据所述N4会话建立请求消息，从网络存储功能网元中获取所述第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息。
可选地，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述接收会话管理功能网元发送的N4会话建立请求消息之后，所述操作还包括：
向所述会话管理功能网元发送N4会话建立响应消息，所述N4会话建立响应消息中携带所述N3侧用户面功能网元的N3隧道信息。
可选地，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述操作还包括：
在接收上行数据后，对所述上行数据进行解封装，通过服务操作将解封装后得到的数据发送给下一跳用户面功能网元；和/或，
在接收下行数据后，对所述下行数据进行封装，将封装后的数据发送给 接入网设备。
可选地，在所述第一用户面功能网元为锚点用户面功能网元的情况下，所述操作还包括：
在接收上行数据后，将所述上行数据发送给数据网络；和/或，
在接收下行数据后，通过服务操作将所述下行数据发送给下一跳用户面功能网元。
第四方面，本公开实施例还提供一种会话管理功能网元，包括存储器，收发机，处理器：
存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
确定通过服务操作进行数据传输；
向第一用户面功能网元发送N4会话建立请求消息，所述N4会话建立请求消息中携带第一信息；所述第一信息用于指示所述第一用户面功能网元通过服务操作进行指定数据的传输。
可选地，所述第一信息包括以下一项或多项：
第二用户面功能网元的信息；所述第二用户面功能网元包括所述第一用户面功能网元在不同时间段所连接的多个用户面功能网元；
会话IP地址；
小数据传输指示；
事件通知订阅指示。
可选地，所述第二用户面功能网元的信息包括以下一项或多项：
所述第二用户面功能网元的标识信息；
所述第二用户面功能网元与所述第一用户面功能网元之间建立连接的时间相关信息；
所述第二用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长；
所述第二用户面功能网元所在卫星的星历信息；
所述第二用户面功能网元的服务操作信息。
可选地，所述确定通过服务操作进行数据传输，包括：
根据终端的无线接入类型，确定通过服务操作进行所述终端的数据传输。
可选地，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述向第一用户面功能网元发送N4会话建立请求消息之后，所述操作还包括：
接收所述N3侧用户面功能网元发送的N4会话建立响应消息，所述N4会话建立响应消息中携带所述N3侧用户面功能网元的N3隧道信息。
第五方面，本公开实施例还提供一种数据传输装置，应用于第一用户面功能网元，包括：
第一接收单元，用于接收会话管理功能网元发送的N4会话建立请求消息，所述N4会话建立请求消息中携带第一信息；所述第一信息用于指示所述第一用户面功能网元通过服务操作进行指定数据的传输；
第一发送单元，用于通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元。
第六方面，本公开实施例还提供一种数据传输装置，应用于会话管理功能网元，包括：
第二确定单元，用于确定通过服务操作进行数据传输；
第二发送单元，用于向第一用户面功能网元发送N4会话建立请求消息，所述N4会话建立请求消息中携带第一信息；所述第一信息用于指示所述第一用户面功能网元通过服务操作进行指定数据的传输。
第七方面，本公开实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序用于使计算机执行如上所述第一方面所述的数据传输方法的步骤，或执行如上所述第二方面所述的数据传输方法的步骤。
第八方面，本公开实施例还提供一种通信设备，所述通信设备中存储有计算机程序，所述计算机程序用于使通信设备执行如上所述第一方面所述的数据传输方法的步骤，或执行如上所述第二方面所述的数据传输方法的步骤。
第九方面，本公开实施例还提供一种处理器可读存储介质，所述处理器 可读存储介质存储有计算机程序，所述计算机程序用于使处理器执行如上所述第一方面所述的数据传输方法的步骤，或执行如上所述第二方面所述的数据传输方法的步骤。
第十方面，本公开实施例还提供一种芯片产品，所述芯片产品中存储有计算机程序，所述计算机程序用于使芯片产品执行如上所述第一方面所述的数据传输方法的步骤，或执行如上所述第二方面所述的数据传输方法的步骤。
本公开实施例提供的数据传输方法、设备、装置及存储介质，通过会话管理功能网元在N4会话建立请求消息中携带第一信息，指示第一用户面功能网元通过服务操作进行指定数据的传输，使得数据不需要传输至地面，且无需建立专用的用户面隧道即可实现数据传输，不仅提高了数据传输效率，而且能够节省星上的用户面资源。
附图说明
为了更清楚地说明本公开实施例或相关技术中的技术方案，下面将对实施例或相关技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本公开实施例提供的业务不落地场景下的卫星接入用户业务示意图；
图2是本公开实施例提供的数据传输方法的流程示意图之一；
图3是本公开实施例提供的通过事件通知服务操作进行数据传输的流程示意图；
图4是本公开实施例提供的通过事件订阅服务操作进行事件订阅的流程示意图；
图5是本公开实施例提供的通过数据传输请求服务操作进行数据传输的流程示意图；
图6是本公开实施例提供的数据传输方法的流程示意图之二；
图7是本公开实施例提供的数据传输方法的实施示意图之一；
图8是本公开实施例提供的数据传输方法的实施示意图之二；
图9是本公开实施例提供的数据传输方法的实施示意图之三；
图10是本公开实施例提供的数据传输方法的实施示意图之四；
图11是本公开实施例提供的数据传输方法的实施示意图之五；
图12是本公开实施例提供的第一用户面功能网元的结构示意图；
图13是本公开实施例提供的会话管理功能网元的结构示意图；
图14是本公开实施例提供的数据传输装置的结构示意图之一；
图15是本公开实施例提供的数据传输装置的结构示意图之二。
具体实施方式
本公开实施例中术语“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本公开实施例中术语“多个”是指两个或两个以上，其它量词与之类似。
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本公开一部分实施例，并不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
图1为本公开实施例提供的业务不落地场景下的卫星接入用户业务示意图，如图1所示，在卫星网络业务不落地场景中，核心网控制面网元部署在地面，UPF和移动边缘计算(Mobile Edge Computing，MEC)平台部署在卫星上。在此场景下，对于小数据设备终端的数据传输，如果采用控制面的方式实现数据传输，则需要借助地面上部署的控制面网元，这样就会增加数据传输时延；若采用建立专用的用户面连接方式实现数据传输，即建立用户面隧道，则由于卫星网络拓扑动态变化，UPF需根据网络拓扑变化实时维护用户面隧道信息，这样就会造成用户面资源的浪费，对稀缺的星上资源也是一种挑战。
基于小数据终端具备不频繁发报文特性和星上资源稀缺的特性，本公开各实施例提供一种解决方案，基于UPF支持服务化接口，在卫星网络的用户面采用服务化方式进行小数据的转发，也就是当UPF接收到数据报文时，触发对端UPF的服务操作以发送数据，其中将小数据作为该服务操作的参数，实现小数据的传输，从而节省星上资源并加快小数据的转发。
需要说明的是，本公开各实施例虽然以小数据传输为例进行说明，但这仅是示例性的，并非限制性的，本领域技术人员所熟知的现有的或者将来的能够通过服务操作实现传输的数据类型都可以应用本公开各实施例所提供的技术方案，对此不做限定。
图2为本公开实施例提供的数据传输方法的流程示意图之一，该方法应用于第一用户面功能网元，如图2所示，该方法包括如下步骤：
步骤200、接收会话管理功能网元发送的N4会话建立请求消息，N4会话建立请求消息中携带第一信息；第一信息用于指示第一用户面功能网元通过服务操作进行指定数据的传输。
具体地，第一用户面功能网元可以是数据传输路径上的任意用户面功能网元，用户面功能网元可以是UPF或其他具有类似用户面功能的网元。会话管理功能网元可以是会话管理功能(Session Management Function，SMF)或其他具有类似会话管理功能的网元。
为了提高卫星网络的数据传输效率并节省用户面资源，本公开实施例中，提出在卫星网络的用户面采用服务化方式进行数据转发，也就是当用户面功能网元接收到数据报文时，触发对端用户面功能网元的服务操作以发送数据。
具体地，会话管理功能网元可以在确定通过服务操作进行数据传输的情况下，向第一用户面功能网元发送N4会话建立请求消息，N4会话建立请求消息中携带第一信息，通过第一信息指示第一用户面功能网元通过服务操作进行指定数据的传输。所述指定数据为第一信息中直接或间接指示可以通过服务操作进行传输的数据。
可选地，第一信息可以包括以下一项或多项：
(1)第二用户面功能网元的信息；第二用户面功能网元包括第一用户面 功能网元在不同时间段所连接的多个用户面功能网元。
由于卫星网络拓扑动态变化，第一用户面功能网元在不同时间段所连接的用户面功能网元会有所变化，会话管理功能网元可以在N4会话建立请求消息中携带第二用户面功能网元的信息，以告知第一用户面功能网元其所对应的第二用户面功能网元的信息。
(2)会话IP地址。
会话互联网协议(Internet Protocol，IP)地址可以是指示某个会话的IP地址，可以包括会话源IP地址和会话目的IP地址，会话可以是协议数据单元(Protocol Data Unit，PDU)会话，会话管理功能网元可以在N4会话建立请求消息中携带会话IP地址，用于指示第一用户面功能网元在接收到与该会话IP地址相匹配的数据时，通过服务操作将该数据发送给下一跳用户面功能网元。
(3)小数据传输指示。
该小数据传输指示可用于指示第一用户面功能网元通过服务操作进行小数据的传输，比如会话管理功能网元在确定通过服务操作进行小数据的传输的情况下，会话管理功能网元可以在N4会话建立请求消息中携带小数据传输指示，指示第一用户面功能网元在接收到小数据时，通过服务操作将该小数据发送给下一跳用户面功能网元。
(4)事件通知订阅指示。
该事件通知订阅指示可用于指示第一用户面功能网元在接收到需要通过服务操作发送的数据时，通过事件通知服务操作将数据发送给下一跳用户面功能网元，也即向下一跳用户面功能网元触发事件通知服务操作以实现数据传输。
例如，第一用户面功能网元接收到该事件通知订阅指示后，对于上行数据，可以基于会话源IP地址向对端用户面功能网元触发Nupf_EventExposure_Notify服务操作，并将此类数据作为POST请求的有效载荷体；对于下行数据，可以基于会话目的IP地址向对端用户面功能网元触发Nupf_EventExposure_Notify服务操作，并将此类数据作为POST请求的有 效载荷体。
可选地，上述第二用户面功能网元的信息可以包括以下一项或多项：
(1)第二用户面功能网元的标识信息。
可选地，会话管理功能网元可以在N4会话建立请求消息中携带第二用户面功能网元的标识信息，用于指示第二用户面功能网元的标识。
一种实施方式中，会话管理功能网元可以在N4会话建立请求消息中携带第二用户面功能网元的标识信息，并携带第一用户面功能网元是在哪个时间段连接哪个(或哪些)第二用户面功能网元的信息。
一种实施方式中，会话管理功能网元可以在N4会话建立请求消息中携带第二用户面功能网元的标识信息，但不携带各个第二用户面功能网元分别在哪个时间段与第一用户面功能网元之间建立连接的信息。
(2)第二用户面功能网元与第一用户面功能网元之间建立连接的时间相关信息。
该时间相关信息可以包括时间段信息，例如，该时间相关信息可用于指示各个第二用户面功能网元分别是在哪个时间段与第一用户面功能网元之间建立连接的，从而第一用户面功能网元可以确定其在不同时间段所连接的第二用户面功能网元。
(3)第二用户面功能网元所在卫星与第一用户面功能网元所在卫星之间的星间可见时间时长。
星间可见时间时长指的是卫星之间处于彼此可见状态(也可以理解为可以通信的状态)的时间时长，由于用户面功能网元位于卫星上，随着卫星的运动轨迹变化，各个用户面功能网元之间的连接关系会随之变化，在两个卫星的时间窗口重合(或者说两个卫星彼此可见)的情况下，这两个卫星上的用户面功能网元之间可以建立连接，因此会话管理功能网元可以在N4会话建立请求消息中携带上述星间可见时间时长的信息，用于指示第一用户面功能网元各个第二用户面功能网元所在卫星的情况。比如，第一用户面功能网元可以参考该星间可见时间时长的信息，来选择数据传输时的下一跳用户面功能网元。
(4)第二用户面功能网元所在卫星的星历信息。
该星历信息可用于指示第二用户面功能网元所在卫星的星历，会话管理功能网元可以在N4会话建立请求消息中携带该星历信息，从而第一用户面功能网元可以根据该星历信息，确定第二用户面功能网元所在卫星的星体轨道数据。
(5)第二用户面功能网元的服务操作信息。
该服务操作信息可用于指示第二用户面功能网元所支持的服务操作的信息，比如服务操作的类型，服务操作的应用程序编程接口(Application Programming Interface，API)统一资源标志符(Uniform Resource Identifier，URI)等。
步骤201、通过服务操作将与第一信息相匹配的数据发送给下一跳用户面功能网元。
具体地，第一用户面功能网元接收到会话管理功能网元发送的N4会话建立请求消息后，可以从N4会话建立请求消息中获取到第一信息，根据该第一信息，第一用户面功能网元在后续接收到与该第一信息相匹配的数据时，便可以通过服务操作将这些数据发送给下一跳用户面功能网元，从而通过服务操作实现数据传输。
例如，第一信息中包含会话IP地址，则第一用户面功能网元在接收到数据信息中包含该会话IP地址的数据时，便可以通过服务操作将这些数据发送给下一跳用户面功能网元。
例如，第一信息中包含小数据传输指示，则第一用户面功能网元在接收到小数据(数据量较小的数据，比如几十至几百比特的数据)时，便可以通过服务操作将小数据发送给下一跳用户面功能网元。
本公开实施例提供的数据传输方法，通过会话管理功能网元在N4会话建立请求消息中携带第一信息，指示第一用户面功能网元通过服务操作进行指定数据的传输，使得数据不需要传输至地面，且无需建立专用的用户面隧道即可实现数据传输，不仅提高了数据传输效率，而且能够节省星上的用户面资源。
可选地，通过服务操作将与第一信息相匹配的数据发送给下一跳用户面功能网元，包括：
通过事件通知服务操作或数据传输请求服务操作，将与第一信息相匹配的数据发送给下一跳用户面功能网元。
具体地，第一用户面功能网元在接收到与第一信息相匹配的数据后，可以通过事件通知服务操作或数据传输请求服务操作，将数据发送给下一跳用户面功能网元，即触发下一跳用户面功能网元的事件通知服务操作或数据传输请求服务操作，以向下一跳用户面功能网元发送数据。
可选地，事件通知服务操作可以是指Nupf_EventExposure_Notify服务操作，Nupf_EventExposure_Notify服务操作信息可以如下表1所示。
图3为本公开实施例提供的通过事件通知服务操作进行数据传输的流程示意图，如图3所示，以UPF之间进行小数据传输为例，其主要包括如下流程：
1、UPF基于SMF在会话建立过程中提供的对端UPF的服务操作信息(eventNotificationUri)发送POST请求，POST请求的有效载荷体包含该UPF要传输给对端UPF的小数据。
2a、成功后，对端UPF以“204无内容(No Content)”进行响应。
2b、在失败或重定向时，返回相应的超文本传输协议(Hyper Text Transfer Protocol，HTTP)状态代码，比如4xx/5xx或3xx响应。
表1 Nupf_EventExposure_Notify服务操作信息
Nupf_EventExposure_Notify服务操作所对应的事件订阅服务操作Nupf_EventExposure_Subscribe的信息如下表2所示。
表2 Nupf_EventExposure_Subscribe服务操作信息
图4为本公开实施例提供的通过事件订阅服务操作进行事件订阅的流程示意图，如图4所示，以UPF之间进行事件订阅为例，其主要包括如下流程：
1、UPF向对端UPF发送一个POST请求，以创建消息体中的订阅(.../{sessionIdentity}/ee-subscriptions)，事件触发指示包括源IP地址或者目的IP地址。该请求可能包含一个由该UPF建议的到期时间，代表希望保持订阅活动的时间，以及被订阅事件停止生成通知的时间。
2a、一旦成功，对端UPF将以“201已创建(Created)”进行响应，消息主体包含所创建的订阅的标识。
2b、在失败时，返回“404未找到(Not Found)”或“403禁止(Forbidden)”响应。
可选地，数据传输请求服务操作可以是指Nupf_PDUSession_TransferDat a_Request服务操作，Nupf_PDUSession_TransferData_Request服务操作信息可以如下表3所示。
表3 Nupf_PDUSession_TransferData_Request服务操作信息
图5为本公开实施例提供的通过数据传输请求服务操作进行数据传输的流程示意图，如图5所示，以UPF之间进行小数据传输为例，其主要包括如下流程：
1、UPF基于对端UPF的服务操作信息发送POST请求，POST请求的有效载荷体包含该UPF要传输给对端UPF的小数据。
2a、成功后，对端UPF以“204无内容(No Content)”进行响应。
2b、在失败或重定向时，返回相应的HTTP状态代码，比如4xx/5xx或3xx响应。
可选地，在通过事件通知服务操作将与第一信息相匹配的数据发送给下一跳用户面功能网元之前，该方法还包括：
根据第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息，向第一用户面功能网元在不同时间段所连接的用户面功能网元触发事件订阅服务操作。
具体地，通过事件通知服务操作进行数据传输的情况下，第一用户面功能网元可以先向其在不同时间段所连接的用户面功能网元触发事件订阅服务操作，以便后续进行数据传输时，可以通过事件通知服务操作将数据发送给第一用户面功能网元所连接的下一跳用户面功能网元。
例如，在第一信息中没有包含事件通知订阅指示的情况下，第一用户面功能网元若需要通过事件通知服务操作进行数据传输，则可以在进行数据传输之前，先向其在不同时间段所连接的用户面功能网元触发事件订阅服务操作。
可选地，由于第一用户面功能网元在不同时间段所连接的用户面功能网元不同，在某个时间段内第一用户面功能网元只能向当前时间段所连接的用户面功能网元触发事件订阅服务操作，所以第一用户面功能网元可以分多次、在不同的时间段里，向相应时间段所连接的用户面功能网元触发事件订阅服务操作。
可选地，在通过数据传输请求服务操作将与第一信息相匹配的数据发送给下一跳用户面功能网元之后，该方法还包括：
接收下一跳用户面功能网元发送的数据传输响应。
具体地，通过数据传输请求服务操作进行数据传输的情况下，第一用户面功能网元在将数据发送给下一跳用户面功能网元之后，该下一跳用户面功能网元需要触发数据传输响应服务操作作为响应，以便第一用户面功能网元确认数据成功传输至下一跳用户面功能网元。
可选地，通过服务操作将与第一信息相匹配的数据发送给下一跳用户面功能网元之前，该方法还包括：
根据第一用户面功能网元在当前时间段所连接的用户面功能网元的服务 操作信息，以及第一用户面功能网元在当前时间段所连接的用户面功能网元所在卫星与第一用户面功能网元所在卫星之间的星间可见时间时长，确定下一跳用户面功能网元。
具体地，第一用户面功能网元在通过服务操作将与第一信息相匹配的数据发送给下一跳用户面功能网元之前，需要先确定下一跳用户面功能网元。
可选地，第一用户面功能网元可以根据其在当前时间段所连接的各个用户面功能网元的服务操作信息，以及其在当前时间段所连接的各个用户面功能网元所在卫星与其所在卫星之间的星间可见时间时长，来确定下一跳用户面功能网元。
例如，第一用户面功能网元可以根据其在当前时间段所连接的各个用户面功能网元的服务操作信息，从其当前时间段所连接的各个用户面功能网元中，选择支持事件通知服务操作或者数据传输请求服务操作的用户面功能网元，作为下一跳用户面功能网元。
可选地，若根据服务操作信息可以选出多个满足条件的用户面功能网元，则可以判断这些满足条件的用户面功能网元中，哪个用户面功能网元所在卫星与第一用户面功能网元所在卫星之间的星间可见时间时长最长，则将这个用户面功能网元作为下一跳用户面功能网元。
可选地，接收会话管理功能网元发送的N4会话建立请求消息之后，该方法还包括：
从N4会话建立请求消息中获取第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息；或者，
根据N4会话建立请求消息，从网络存储功能网元中获取第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息。
具体地，对于第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息，第一用户面功能网元可以根据需要通过不同的方式进行获取。
可选地，若会话管理功能网元在N4会话建立请求消息中携带有该服务操作信息，则第一用户面功能网元可以直接从N4会话建立请求消息中获取 并保存。
可选地，若会话管理功能网元在N4会话建立请求消息中没有携带有该服务操作信息，则第一用户面功能网元也可以根据N4会话建立请求消息中携带的第一信息，从网络存储功能网元中获取该服务操作信息。其中，网络存储功能网元可以是网络存储功能(Network Repository Function，NRF)或其他具有类似网络存储功能的网元。
可选地，在第一用户面功能网元为N3侧用户面功能网元的情况下，接收会话管理功能网元发送的N4会话建立请求消息之后，该方法还包括：
向会话管理功能网元发送N4会话建立响应消息，N4会话建立响应消息中携带N3侧用户面功能网元的N3隧道信息。
具体地，本公开实施例中，用户面功能网元之间通过服务操作进行数据传输，可以不需要建立专用的用户面隧道，因此第一用户面功能网元接收到会话管理功能网元发送的N4会话建立请求消息后，在第一用户面功能网元为N3侧用户面功能网元的情况下，该N3侧用户面功能网元在N4会话建立响应消息中只需携带为该会话分配的N3隧道信息即可，该N3侧用户面功能网元无需为该会话分配N9隧道信息。
在第一用户面功能网元不为N3侧用户面功能网元的情况下，第一用户面功能网元在N4会话建立响应消息中可以不携带隧道信息。
可选地，在第一用户面功能网元为N3侧用户面功能网元的情况下，该方法还包括：
在接收上行数据后，对上行数据进行解封装，通过服务操作将解封装后得到的数据发送给下一跳用户面功能网元；和/或，
在接收下行数据后，对下行数据进行封装，将封装后的数据发送给接入网设备。
具体地，在第一用户面功能网元为N3侧用户面功能网元的情况下，该第一用户面功能网元接收到上/下行数据后，可进行相应的数据解封装/封装和数据传输操作。
可选地，对于接收到的上行数据(比如上行数据包)，该第一用户面功能 网元可以对该上行数据进行解封装获取其中的数据，然后通过服务操作(比如事件通知服务操作、数据传输请求服务操作等)将解封装后得到的数据发送给下一跳用户面功能网元。
可选地，对于接收到的下行数据，该第一用户面功能网元可以对该下行数据进行封装，然后将封装后的数据发送给接入网设备，比如无线接入网设备(Radio Access Network，RAN)。
可选地，在第一用户面功能网元为锚点用户面功能网元的情况下，该方法还包括：
在接收上行数据后，将上行数据发送给数据网络；和/或，
在接收下行数据后，通过服务操作将下行数据发送给下一跳用户面功能网元。
具体地，在第一用户面功能网元为锚点用户面功能网元(比如PDU会话锚点(PDU Session Anchor，PSA)的情况下，该第一用户面功能网元接收到上/下行数据后，可进行相应的数据解封装/封装和数据传输操作。
可选地，对于接收到的上行数据，该第一用户面功能网元可以直接将该数据发送给数据网络(Data Network，DN)。
可选地，对于接收到的下行数据，该第一用户面功能网元可以将该下行数据通过服务操作(比如事件通知服务操作、数据传输请求服务操作等)发送给下一跳用户面功能网元。
图6为本公开实施例提供的数据传输方法的流程示意图之二，该方法应用于会话管理功能网元，如图6所示，该方法包括如下步骤：
步骤600、确定通过服务操作进行数据传输。
步骤601、向第一用户面功能网元发送N4会话建立请求消息，N4会话建立请求消息中携带第一信息；第一信息用于指示第一用户面功能网元通过服务操作进行指定数据的传输。
具体地，会话管理功能网元可以是SMF或其他具有类似会话管理功能的网元。第一用户面功能网元可以是数据传输路径上的任意用户面功能网元，用户面功能网元可以是UPF或其他具有类似用户面功能的网元。
为了提高卫星网络的数据传输效率并节省用户面资源，本公开实施例中，提出在卫星网络的用户面采用服务化方式进行数据转发，也就是当用户面功能网元接收到数据报文时，触发对端用户面功能网元的服务操作以发送数据。
具体地，会话管理功能网元可以在确定通过服务操作进行数据传输的情况下，向第一用户面功能网元发送N4会话建立请求消息，N4会话建立请求消息中携带第一信息，通过第一信息指示第一用户面功能网元通过服务操作进行指定数据的传输。所述指定数据为第一信息中直接或间接指示可以通过服务操作进行传输的数据。
可选地，第一信息可以包括以下一项或多项：
(1)第二用户面功能网元的信息；第二用户面功能网元包括第一用户面功能网元在不同时间段所连接的多个用户面功能网元。
由于卫星网络拓扑动态变化，第一用户面功能网元在不同时间段所连接的用户面功能网元会有所变化，会话管理功能网元可以在N4会话建立请求消息中携带第二用户面功能网元的信息，以告知第一用户面功能网元其所对应的第二用户面功能网元的信息。
(2)会话IP地址。
会话IP地址可以是指示某个会话的IP地址，可以包括会话源IP地址和会话目的IP地址，会话可以是PDU会话，会话管理功能网元可以在N4会话建立请求消息中携带会话IP地址，用于指示第一用户面功能网元在接收到与该会话IP地址相匹配的数据时，通过服务操作将该数据发送给下一跳用户面功能网元。
(3)小数据传输指示。
该小数据传输指示可用于指示第一用户面功能网元通过服务操作进行小数据的传输，比如会话管理功能网元在确定通过服务操作进行小数据的传输的情况下，会话管理功能网元可以在N4会话建立请求消息中携带小数据传输指示，指示第一用户面功能网元在接收到小数据时，通过服务操作将该小数据发送给下一跳用户面功能网元。
(4)事件通知订阅指示。
该事件通知订阅指示可用于指示第一用户面功能网元在接收到需要通过服务操作发送的数据时，通过事件通知服务操作将数据发送给下一跳用户面功能网元，也即向下一跳用户面功能网元触发事件通知服务操作以实现数据传输。
例如，第一用户面功能网元接收到该事件通知订阅指示后，对于上行数据，可以基于会话源IP地址向对端用户面功能网元触发Nupf_EventExposure_Notify服务操作，并将此类数据作为POST请求的有效载荷体；对于下行数据，可以基于会话目的IP地址向对端用户面功能网元触发Nupf_EventExposure_Notify服务操作，并将此类数据作为POST请求的有效载荷体。
可选地，上述第二用户面功能网元的信息可以包括以下一项或多项：
(1)第二用户面功能网元的标识信息。
可选地，会话管理功能网元可以在N4会话建立请求消息中携带第二用户面功能网元的标识信息，用于指示第二用户面功能网元的标识。
一种实施方式中，会话管理功能网元可以在N4会话建立请求消息中携带第二用户面功能网元的标识信息，并携带第一用户面功能网元是在哪个时间段连接哪个(或哪些)第二用户面功能网元的信息。
一种实施方式中，会话管理功能网元可以在N4会话建立请求消息中携带第二用户面功能网元的标识信息，但不携带各个第二用户面功能网元分别在哪个时间段与第一用户面功能网元之间建立连接的信息。
(2)第二用户面功能网元与第一用户面功能网元之间建立连接的时间相关信息。
该时间相关信息可以包括时间段信息，例如，该时间相关信息可用于指示各个第二用户面功能网元分别是在哪个时间段与第一用户面功能网元之间建立连接的，从而第一用户面功能网元可以确定其在不同时间段所连接的第二用户面功能网元。
(3)第二用户面功能网元所在卫星与第一用户面功能网元所在卫星之间的星间可见时间时长。
星间可见时间时长指的是卫星之间处于彼此可见状态(也可以理解为可以通信的状态)的时间时长，由于用户面功能网元位于卫星上，随着卫星的运动轨迹变化，各个用户面功能网元之间的连接关系会随之变化，在两个卫星的时间窗口重合(或者说两个卫星彼此可见)的情况下，这两个卫星上的用户面功能网元之间可以建立连接，因此会话管理功能网元可以在N4会话建立请求消息中携带上述星间可见时间时长的信息，用于指示第一用户面功能网元各个第二用户面功能网元所在卫星的情况。比如，第一用户面功能网元可以参考该星间可见时间时长的信息，来选择数据传输时的下一跳用户面功能网元。
(4)第二用户面功能网元所在卫星的星历信息。
该星历信息可用于指示第二用户面功能网元所在卫星的星历，会话管理功能网元可以在N4会话建立请求消息中携带该星历信息，从而第一用户面功能网元可以根据该星历信息，确定第二用户面功能网元所在卫星的星体轨道数据。
(5)第二用户面功能网元的服务操作信息。
该服务操作信息可用于指示第二用户面功能网元所支持的服务操作的信息，比如服务操作的类型，服务操作的API URI等。
第一用户面功能网元接收到会话管理功能网元发送的N4会话建立请求消息后，可以从N4会话建立请求消息中获取到第一信息，根据该第一信息，第一用户面功能网元在后续接收到与该第一信息相匹配的数据时，便可以通过服务操作将这些数据发送给下一跳用户面功能网元，从而通过服务操作实现数据传输。
例如，第一信息中包含会话IP地址，则第一用户面功能网元在接收到数据信息中包含该会话IP地址的数据时，便可以通过服务操作将这些数据发送给下一跳用户面功能网元。
例如，第一信息中包含小数据传输指示，则第一用户面功能网元在接收到小数据时，便可以通过服务操作将小数据发送给下一跳用户面功能网元。
本公开实施例提供的数据传输方法，通过会话管理功能网元在N4会话 建立请求消息中携带第一信息，指示第一用户面功能网元通过服务操作进行指定数据的传输，使得数据不需要传输至地面，且无需建立专用的用户面隧道即可实现数据传输，不仅提高了数据传输效率，而且能够节省星上的用户面资源。
可选地，确定通过服务操作进行数据传输，包括：
根据终端的无线接入类型，确定通过服务操作进行终端的数据传输。
具体地，一种实施方式中，会话管理功能网元可以根据终端的无线接入类型(Radio Access Technology Type，RAT Type)，来确定是否通过服务操作进行该终端的数据传输。
例如，会话管理功能网元获取到终端的RAT Type为窄带物联网(Narrow Band Internet of Things，NB-IoT)，NB-IoT类型的终端传输的数据量小，且数据发送不频繁，可适用于通过服务操作进行数据传输的场景，则会话管理功能网元可以确定通过服务操作进行终端的数据传输，在后续选择该终端的PDU会话的UPF后，可以向这些UPF发送N4会话建立请求消息，消息中携带第一信息，用于指示这些UPF通过服务操作进行该终端的数据传输。例如，第一信息中可以包含该终端的PDU会话的IP地址进行指示。
可选地，在第一用户面功能网元为N3侧用户面功能网元的情况下，向第一用户面功能网元发送N4会话建立请求消息之后，该方法还包括：
接收N3侧用户面功能网元发送的N4会话建立响应消息，N4会话建立响应消息中携带N3侧用户面功能网元的N3隧道信息。
具体地，本公开实施例中，用户面功能网元之间通过服务操作进行数据传输，可以不需要建立专用的用户面隧道，因此第一用户面功能网元接收到会话管理功能网元发送的N4会话建立请求消息后，在第一用户面功能网元为N3侧用户面功能网元的情况下，该N3侧用户面功能网元在N4会话建立响应消息中只需携带为该会话分配的N3隧道信息即可，该N3侧用户面功能网元无需为该会话分配N9隧道信息。
相应地，会话管理功能网元接收到该N3侧用户面功能网元发送的N4会话建立响应消息中携带的是该N3侧用户面功能网元的N3隧道信息，而没有 N9隧道信息。对于除N3侧用户面功能网元以外的其他用户面功能网元，它们可以在向会话管理功能网元发送的N4会话建立响应消息中不携带隧道信息。
本公开各实施例提供的方法是基于同一申请构思的，因此各方法的实施可以相互参见，重复之处不再赘述。
以下通过具体应用场景的实施例对本公开各上述实施例提供的方法进行举例说明。
实施例1-3：基于订阅-通知方式，实现用户面UPF之间的数据转发。
实施例1：SMF代替UPF订阅，实现用户面UPF之间的数据转发。
图7为本公开实施例提供的数据传输方法的实施示意图之一，如图7所示，其主要包括如下步骤：
步骤1、UE向接入和移动性管理功能(Access and Mobility Management Function，AMF)发起PDU会话建立请求。
步骤2-3、AMF选择SMF以建立会话，并向SMF触发创建会话管理上下文请求(Nsmf_PDUSession_CreateSMContextRequest)。
步骤4、如果与用户永久标识符(Subscription Permanent Identifier，SUPI)、数据网络名称(Data Network Name，DNN)和单一网络切片选择协助信息(Single Network Slice Selection Assistance Information，S-NSSAI)相关的会话管理签约数据不可用，则SMF使用Nudm_SDM_Get(SUPI,Session Management Subscription data,DNN,S-NSSAI)检索会话管理签约数据，并使用Nudm_SDM_Subscribe(SUPI,Session Management Subscription data,DNN,S-NSSAI)向统一数据管理(Unified Data Management,UDM)订阅关于签约数据改变的通知。
步骤5、SMF向AMF发送创建会话管理上下文响应(Nsmf_PDUSession_CreateSMContextResponse)。
步骤6、PDU会话辅助认证/授权。
步骤7、如果为PDU会话使用动态策略和计费控制(Policy and Charging Control,PCC)，则SMF执行策略控制功能(Policy Control Function,PCF)选择， 并执行会话管理策略建立过程，与PCF建立一个会话管理(Session Management，SM)策略关联，并获得PDU会话的缺省PCC策略。
步骤8、基于步骤3中获取的UE的RAT Type，假设RAT Type为NB-IoT，则SMF确定不为该会话建立专用的用户面连接，即通过服务操作实现数据传输，同时，SMF执行UPF选择，包括SMF根据星历信息获得的该UPF不同时间段内的相连的其它UPF信息，其中UPF信息包括服务操作信息。关于服务操作信息的获取可以通过四种方式：一是在UPF配置，而后通过N4关联建立过程发送给SMF的；二是操作维护管理(Operation Administration and Maintenance，OAM)在SMF上配置星上UPF的服务操作信息；三是UPF向NRF注册时携带服务操作信息，而后SMF需要时从NRF获取；四是OAM向NRF注册UPF时携带UPF支持的服务操作，而后SMF需要时从NRF获取。
步骤9、SMF可执行会话管理策略修改过程，向PCF提供条件已满足的策略控制请求触发器(Policy Control Request Trigger)的相关信息。
步骤10a、SMF向选择的所有UPF发送N4会话建立请求消息，消息中携带第一信息，以任意一个UPF为例，第一信息包括该UPF在不同时间段内相连的其它UPF的标识和服务操作信息、其他UPF所在卫星与该UPF所在卫星的星间可见时间时长、其他UPF所在卫星的星历信息、会话IP地址、小数据传输指示、事件通知订阅指示等信息；或者第一信息包括该UPF相连的其它UPF的标识和服务操作信息、其他UPF所在卫星的星历信息、会话IP地址、小数据传输指示、事件通知订阅指示等信息；或者第一信息包括该UPF相连的其它UPF的标识和服务操作信息、会话IP地址、小数据传输指示、事件通知订阅指示等信息。
其中，事件通知订阅指示可以表示为对于上行数据可以基于会话源IP地址向对端UPF触发Nupf_EventExposure_Notify服务操作，并将此类数据作为POST请求的有效载荷体；对于下行数据可以基于会话目的IP地址向对端UPF触发Nupf_EventExposure_Notify服务操作，并将此类数据作为POST请求的有效载荷体。此时，SMF不需要向除N3侧UPF外的其它UPF发送N4会话 修改请求消息。
步骤10b、所有UPF向SMF发送N4会话建立响应消息，此时N3侧UPF只发送为该会话分配的N3侧的隧道信息，N3侧UPF不需要分配N9侧的隧道信息；除N3侧UPF以外的其它UPF不需要分配隧道信息。各UPF保存不同时段对端UPF的服务操作信息，包括API URI，以供收到该会话上的小数据时触发服务操作来发送小数据。此时，除N3侧UPF外的其它UPF不需要向SMF发送N4会话修改响应消息。
步骤11、SMF向AMF发送N1N2消息传输请求(Namf_Communication_N1N2MessageTransfer)。
步骤12-14、AMF发送N2会话请求以建立N3连接和无线资源控制(Radio Resource Control，RRC)连接。
步骤14b、当N3侧UPF接收该会话的小数据时，解封装获取数据信息，比如会话源IP地址或者会话目的IP地址。而后再依据步骤10a中保存的UPF和UPF对应服务操作的API URI，以及依据当前的邻居连接关系和卫星的星间可见时间时长(比如选择星间可见时间时长长的)，选择出合适的下一跳UPF；或者依据步骤10a中保存的UPF的星历信息计算出当前时刻相连的UPF以及卫星的星间可见时间时长，选择出合适的下一跳UPF，并触发对应的服务操作，比如事件通知服务操作(Nupf_EventExposure_Notify)，将要发送的数据作为POST请求的有效载荷体，以发送接收到的小数据到下一跳UPF。路径上其它UPF只需提取出小数据、获取数据信息(比如会话源IP地址或者会话目的IP地址)和选择合适的下一跳UPF，并触发对应的服务操作，比如事件通知服务操作(Nupf_EventExposure_Notify)，将要发送的数据作为POST请求的有效载荷体以发送数据到下一跳UPF。PSA提取出小数据，直接转发到DN中。
步骤15、AMF向SMF发送更新会话管理上下文请求(Nsmf_PDUSession_UpdateSMContextRequest)，以建立N3连接。
步骤16、SMF向UPF发起N4会话修改流程以建立N3连接，并为该PDU会话注册(若未注册)。
步骤17a、PSA接收到小数据时，获取数据信息，比如会话源IP地址或者目的IP地址。而后再基于步骤10a中保存的UPF和UPF对应服务操作的API URI，以及依据当前的邻居连接关系和卫星的星间可见时间时长(比如选择星间可见时间时长长的)，选择出合适的下一跳UPF；或者依据步骤10a中保存的UPF的星历信息计算出当前时刻相连的UPF以及卫星的星间可见时间时长，选择出合适的下一跳UPF，并触发对应的服务操作，比如Nupf_EventExposure_Notify服务操作，将要发送的数据作为POST请求的有效载荷体，以发送接收到的小数据到下一跳UPF。路径上其它UPF只需提取出小数据、获取数据信息(比如会话源IP地址或者目的IP地址)和选择合适的下一跳UPF，并触发对应的服务操作，比如Nupf_EventExposure_Notify服务操作，将要发送的数据作为POST请求的有效载荷体以发送数据到下一跳UPF。N3侧UPF提取出小数据，进行封装，封装成通用无线分组业务隧道协议(GPRS Tunneling Protocol,GTP)报文并发送到RAN。
步骤17、SMF向AMF发送更新会话管理上下文响应(Nsmf_PDUSession_UpdateSMContextResponse)。
步骤18、如果PDU会话建立失败，则SMF调用会话管理上下文状态通知(Nsmf_PDUSession_SMContextStatusNotify(Release))，通知AMF。
步骤19、SMF经过UPF到UE：如果PDU会话类型为IPv6或IPv4v6，SMF生成IPv6路由通知(IPv6Address Configuration)，并通过N4发给UE和UPF。
步骤20、SMF执行会话管理策略修改过程。
步骤21、如果在步骤4之后PDU会话建立失败，则SMF应执行Nudm_SDM_Unsubscribe实现去订阅。
后续，UPF再接收到小数据的数据报文时，执行步骤14b或者步骤17a。
实施例2：UPF主动向其它UPF订阅，实现用户面UPF之间的数据转发。
图8为本公开实施例提供的数据传输方法的实施示意图之二，如图8所示，其主要包括如下步骤：
步骤1、UE向AMF发起PDU会话建立请求。
步骤2-3、AMF选择SMF以建立会话，并向SMF触发创建会话管理上下文请求(Nsmf_PDUSession_CreateSMContextRequest)。
步骤4、如果与SUPI、DNN和S-NSSAI相关的会话管理签约数据不可用，则SMF使用Nudm_SDM_Get(SUPI,Session Management Subscription data,DNN,S-NSSAI)检索会话管理签约数据，并使用Nudm_SDM_Subscribe(SUPI,Session Management Subscription data,DNN,S-NSSAI)向UDM订阅关于签约数据改变的通知。
步骤5、SMF向AMF发送创建会话管理上下文响应(Nsmf_PDUSession_CreateSMContextResponse)。
步骤6、PDU会话辅助认证/授权。
步骤7、如果为PDU会话使用PCC，则SMF执行策略控制功能PCF选择，并执行会话管理策略建立过程，与PCF建立一个SM策略关联，并获得PDU会话的缺省PCC策略。
步骤8、基于步骤3中获取的UE的RAT Type，假设RAT Type为NB-IoT，则SMF确定不为该会话建立专用的用户面连接，即通过服务操作实现数据传输，同时，SMF执行UPF选择，包括SMF根据星历信息获得的该UPF不同时间段内的相连的其它UPF信息，其中UPF信息包括服务操作信息。关于服务操作信息的获取可以通过四种方式：一是在UPF配置，而后通过N4关联建立过程发送给SMF的；二是OAM在SMF上配置星上UPF的服务操作信息；三是UPF向NRF注册时携带服务操作信息，而后SMF需要时从NRF获取；四是OAM向NRF注册UPF时携带UPF支持的服务操作，而后SMF需要时从NRF获取。
步骤9、SMF可执行会话管理策略修改过程，向PCF提供条件已满足的策略控制请求触发器(Policy Control Request Trigger)的相关信息。
步骤10a、SMF向选择的所有UPF发送N4会话建立请求消息，消息中携带第一信息，以任意一个UPF为例，第一信息包括该UPF在不同时间段内相连的其它UPF的标识和服务操作信息、其他UPF所在卫星与该UPF所在 卫星的星间可见时间时长、其他UPF所在卫星的星历信息、会话IP地址、小数据传输指示等信息；或者第一信息包括该UPF相连的其它UPF的标识和服务操作信息、其他UPF所在卫星的星历信息、会话IP地址、小数据传输指示等信息；或者第一信息包括该UPF相连的其它UPF的标识和服务操作信息、会话IP地址、小数据传输指示等信息。此时，SMF不需要向除N3侧UPF外的其它UPF发送N4会话修改请求消息。
步骤10b、所有UPF向SMF发送N4会话建立响应消息，此时N3侧UPF只发送为该会话分配的N3侧的隧道信息，N3侧UPF不需要分配N9侧的隧道信息；除N3侧UPF以外的其它UPF不需要分配隧道信息。各UPF保存不同时段对端UPF的服务操作信息，包括API URI，以供收到该会话上的小数据时触发服务操作来发送小数据。此时，除N3侧UPF外的其它UPF不需要向SMF发送N4会话修改响应消息。
步骤10c、UPF根据收到的服务操作信息，在不同时间段向其所连接的对端UPF触发事件订阅服务操作以供后续发送数据报文，即触发Nupf_EventExposure_Subscribe服务操作。
步骤11、SMF向AMF发送N1N2消息传输请求(Namf_Communication_N1N2MessageTransfer)。
步骤12-14、AMF发送N2会话请求以建立N3连接和RRC连接。
步骤14b、当N3侧UPF接收该会话的小数据时，解封装获取数据信息，比如会话源IP地址或者会话目的IP地址。而后再依据步骤10a中保存的UPF和UPF对应服务操作的API URI，以及依据当前的邻居连接关系和卫星的星间可见时间时长(比如选择星间可见时间时长长的)，选择出合适的下一跳UPF；或者依据步骤10a中保存的UPF的星历信息计算出当前时刻相连的UPF以及卫星的星间可见时间时长，选择出合适的下一跳UPF，并触发对应的服务操作，比如Nupf_EventExposure_Notify服务操作，将要发送的数据作为POST请求的有效载荷体，以发送接收到的小数据到下一跳UPF。路径上其它UPF只需提取出小数据、获取数据信息(比如会话源IP地址或者会话目的IP地址)和选择合适的下一跳UPF，并触发对应的服务操作，比如 Nupf_EventExposure_Notify服务操作，将要发送的数据作为POST请求的有效载荷体以发送数据到下一跳UPF。PSA提取出小数据，直接转发到DN中。
步骤15、AMF向SMF发送更新会话管理上下文请求(Nsmf_PDUSession_UpdateSMContextRequest)，以建立N3连接。
步骤16、SMF向UPF发起N4会话修改流程以建立N3连接，并为该PDU会话注册(若未注册)。
步骤17a、PSA接收到小数据时，获取数据信息，比如会话源IP地址或者目的IP地址。而后再基于步骤10a中保存的UPF和UPF对应服务操作的API URI，以及依据当前的邻居连接关系和卫星的星间可见时间时长(比如选择星间可见时间时长长的)，选择出合适的下一跳UPF；或者依据步骤10a中保存的UPF的星历信息计算出当前时刻相连的UPF以及卫星的星间可见时间时长，选择出合适的下一跳UPF，并触发对应的服务操作，比如Nupf_EventExposure_Notify服务操作，将要发送的数据作为POST请求的有效载荷体，以发送接收到的小数据到下一跳UPF。路径上其它UPF只需提取出小数据、获取数据信息(比如会话源IP地址或者目的IP地址)和选择合适的下一跳UPF，并触发对应的服务操作，比如Nupf_EventExposure_Notify服务操作，将要发送的数据作为POST请求的有效载荷体以发送数据到下一跳UPF。N3侧UPF提取出小数据，进行封装，封装成GTP报文并发送到RAN。
步骤17、SMF向AMF发送更新会话管理上下文响应(Nsmf_PDUSession_UpdateSMContextResponse)。
步骤18、如果PDU会话建立失败，则SMF调用会话管理上下文状态通知(Nsmf_PDUSession_SMContextStatusNotify(Release))，通知AMF。
步骤19、SMF经过UPF到UE：如果PDU会话类型为IPv6或IPv4v6，SMF生成IPv6路由通知(IPv6Address Configuration)，并通过N4发给UE和UPF。
步骤20、SMF执行会话管理策略修改过程。
步骤21、如果在步骤4之后PDU会话建立失败，则SMF应执行Nudm_SDM_Unsubscribe实现去订阅。
后续，UPF再接收到小数据的数据报文时，执行步骤14b或者步骤17a。
实施例3：UPF向NRF请求其它UPF信息，并且UPF主动向其它UPF订阅，实现用户面UPF之间的数据转发。
图9为本公开实施例提供的数据传输方法的实施示意图之三，如图9所示，其主要包括如下步骤：
步骤1、UE向AMF发起PDU会话建立请求。
步骤2-3、AMF选择SMF以建立会话，并向SMF触发创建会话管理上下文请求(Nsmf_PDUSession_CreateSMContextRequest)。
步骤4、如果与SUPI、DNN和S-NSSAI相关的会话管理签约数据不可用，则SMF使用Nudm_SDM_Get(SUPI,Session Management Subscription data,DNN,S-NSSAI)检索会话管理签约数据，并使用Nudm_SDM_Subscribe(SUPI,Session Management Subscription data,DNN,S-NSSAI)向UDM订阅关于签约数据改变的通知。
步骤5、SMF向AMF发送创建会话管理上下文响应(Nsmf_PDUSession_CreateSMContextResponse)。
步骤6、PDU会话辅助认证/授权。
步骤7、如果为PDU会话使用PCC，则SMF执行策略控制功能PCF选择，并执行会话管理策略建立过程，与PCF建立一个SM策略关联，并获得PDU会话的缺省PCC策略。
步骤8、基于步骤3中获取的UE的RAT Type，假设RAT Type为NB-IoT，则SMF确定不为该会话建立专用的用户面连接，即通过服务操作实现数据传输，同时，SMF执行UPF选择，包括SMF根据星历信息获得的该UPF不同时间段内的相连的其它UPF信息，其中UPF信息包括服务操作信息(若保存的有)。
步骤9、SMF可执行会话管理策略修改过程，向PCF提供条件已满足的策略控制请求触发器(Policy Control Request Trigger)的相关信息。
步骤10a、SMF向选择的所有UPF发送N4会话建立请求消息，消息中携带第一信息，以任意一个UPF为例，第一信息包括该UPF在不同时间段内 相连的其它UPF的标识、其他UPF所在卫星与该UPF所在卫星的星间可见时间时长、其他UPF所在卫星的星历信息、会话IP地址、小数据传输指示等信息；或者第一信息包括该UPF相连的其它UPF的标识、其他UPF所在卫星的星历信息、会话IP地址、小数据传输指示等信息；或者第一信息包括该UPF相连的其它UPF的标识、会话IP地址、小数据传输指示等信息。如果SMF有UPF的服务操作信息，此步骤中也携带。此时，SMF不需要向除N3侧UPF外的其它UPF发送N4会话修改请求消息。
步骤10b、所有UPF向SMF发送N4会话建立响应消息，此时N3侧UPF只发送为该会话分配的N3侧的隧道信息，N3侧UPF不需要分配N9侧的隧道信息；除N3侧UPF以外的其它UPF不需要分配隧道信息。各UPF保存不同时段对端UPF的服务操作信息，包括API URI，以供收到该会话上的小数据时触发服务操作来发送小数据。此时，除N3侧UPF外的其它UPF不需要向SMF发送N4会话修改响应消息。
步骤10c、若UPF没有收到所有不同时段对端UPF的服务操作信息，需要从NRF获取(UPF发现)，并保存。UPF根据收到的服务操作信息，在不同时间段向其所连接的对端UPF触发事件订阅服务操作以供后续发送数据报文，即触发Nupf_EventExposure_Subscribe服务操作。
步骤11、SMF向AMF发送N1N2消息传输请求(Namf_Communication_N1N2MessageTransfer)。
步骤12-14、AMF发送N2会话请求以建立N3连接和RRC连接。
步骤14b、当N3侧UPF接收该会话的小数据时，解封装获取数据信息，比如会话源IP地址或者会话目的IP地址。而后再依据步骤10a中保存的UPF和UPF对应服务操作的API URI，以及依据当前的邻居连接关系和卫星的星间可见时间时长(比如选择星间可见时间时长长的)，选择出合适的下一跳UPF；或者依据步骤10a中保存的UPF的星历信息计算出当前时刻相连的UPF以及卫星的星间可见时间时长，选择出合适的下一跳UPF，并触发对应的服务操作，比如Nupf_EventExposure_Notify服务操作，将要发送的数据作为POST请求的有效载荷体，以发送接收到的小数据到下一跳UPF。路径上 其它UPF只需提取出小数据、获取数据信息(比如会话源IP地址或者会话目的IP地址)和选择合适的下一跳UPF，并触发对应的服务操作，比如Nupf_EventExposure_Notify服务操作，将要发送的数据作为POST请求的有效载荷体以发送数据到下一跳UPF。PSA提取出小数据，直接转发到DN中。
步骤15、AMF向SMF发送更新会话管理上下文请求(Nsmf_PDUSession_UpdateSMContextRequest)，以建立N3连接。
步骤16、SMF向UPF发起N4会话修改流程以建立N3连接，并为该PDU会话注册(若未注册)。
步骤17a、PSA接收到小数据时，获取数据信息，比如会话源IP地址或者目的IP地址。而后再基于步骤10a中保存的UPF和UPF对应服务操作的API URI，以及依据当前的邻居连接关系和卫星的星间可见时间时长(比如选择星间可见时间时长长的)，选择出合适的下一跳UPF；或者依据步骤10a中保存的UPF的星历信息计算出当前时刻相连的UPF以及卫星的星间可见时间时长，选择出合适的下一跳UPF，并触发对应的服务操作，比如Nupf_EventExposure_Notify服务操作，将要发送的数据作为POST请求的有效载荷体，以发送接收到的小数据到下一跳UPF。路径上其它UPF只需提取出小数据、获取数据信息(比如会话源IP地址或者目的IP地址)和选择合适的下一跳UPF，并触发对应的服务操作，比如Nupf_EventExposure_Notify服务操作，将要发送的数据作为POST请求的有效载荷体以发送数据到下一跳UPF。N3侧UPF提取出小数据，进行封装，封装成GTP报文并发送到RAN。
步骤17、SMF向AMF发送更新会话管理上下文响应(Nsmf_PDUSession_UpdateSMContextResponse)。
步骤18、如果PDU会话建立失败，则SMF调用会话管理上下文状态通知(Nsmf_PDUSession_SMContextStatusNotify(Release))，通知AMF。
步骤19、SMF经过UPF到UE：如果PDU会话类型为IPv6或IPv4v6，SMF生成IPv6路由通知(IPv6Address Configuration)，并通过N4发给UE和UPF。
步骤20、SMF执行会话管理策略修改过程。
步骤21、如果在步骤4之后PDU会话建立失败，则SMF应执行Nudm_SDM_Unsubscribe实现去订阅。
后续，UPF再接收到小数据的数据报文时，执行步骤14b或者步骤17a。
实施例4-5：基于请求-响应方式，实现用户面UPF之间的数据转发。
实施例4：SMF通过NRF获取UPF相关信息(包括服务操作信息)，或SMF已配置UPF相关信息(包括服务操作信息)时，实现用户面UPF之间的数据转发。
图10为本公开实施例提供的数据传输方法的实施示意图之四，如图10所示，其主要包括如下步骤：
步骤1、UE向AMF发起PDU会话建立请求。
步骤2-3、AMF选择SMF以建立会话，并向SMF触发创建会话管理上下文请求(Nsmf_PDUSession_CreateSMContextRequest)。
步骤4、如果与SUPI、DNN和S-NSSAI相关的会话管理签约数据不可用，则SMF使用Nudm_SDM_Get(SUPI,Session Management Subscription data,DNN,S-NSSAI)检索会话管理签约数据，并使用Nudm_SDM_Subscribe(SUPI,Session Management Subscription data,DNN,S-NSSAI)向UDM订阅关于签约数据改变的通知。
步骤5、SMF向AMF发送创建会话管理上下文响应(Nsmf_PDUSession_CreateSMContextResponse)。
步骤6、PDU会话辅助认证/授权。
步骤7、如果为PDU会话使用PCC，则SMF执行策略控制功能PCF选择，并执行会话管理策略建立过程，与PCF建立一个SM策略关联，并获得PDU会话的缺省PCC策略。
步骤8、基于步骤3中获取的UE的RAT Type，假设RAT Type为NB-IoT，则SMF确定不为该会话建立专用的用户面连接，即通过服务操作实现数据传输，同时，SMF执行UPF选择，包括SMF根据星历信息获得的该UPF不同时间段内的相连的其它UPF信息，其中UPF信息包括服务操作信息。关于服务操作信息的获取可以通过四种方式：一是在UPF配置，而后通过N4 关联建立过程发送给SMF的；二是OAM在SMF上配置星上UPF的服务操作信息；三是UPF向NRF注册时携带服务操作信息，而后SMF需要时从NRF获取；四是OAM向NRF注册UPF时携带UPF支持的服务操作，而后SMF需要时从NRF获取。
步骤9、SMF可执行会话管理策略修改过程，向PCF提供条件已满足的策略控制请求触发器(Policy Control Request Trigger)的相关信息。
步骤10a、SMF向选择的所有UPF发送N4会话建立请求消息，消息中携带第一信息，以任意一个UPF为例，第一信息包括该UPF在不同时间段内相连的其它UPF的标识和服务操作信息、其他UPF所在卫星与该UPF所在卫星的星间可见时间时长、其他UPF所在卫星的星历信息、会话IP地址、小数据传输指示等信息；或者第一信息包括该UPF相连的其它UPF的标识和服务操作信息、其他UPF所在卫星的星历信息、会话IP地址、小数据传输指示等信息；或者第一信息包括该UPF相连的其它UPF的标识和服务操作信息、会话IP地址、小数据传输指示等信息。此时，SMF不需要向除N3侧UPF外的其它UPF发送N4会话修改请求消息。
步骤10b、所有UPF向SMF发送N4会话建立响应消息，此时N3侧UPF只发送为该会话分配的N3侧的隧道信息，N3侧UPF不需要分配N9侧的隧道信息；除N3侧UPF以外的其它UPF不需要分配隧道信息。各UPF保存不同时段对端UPF的服务操作信息，包括API URI，以供收到该会话上的小数据时触发服务操作来发送小数据。此时，除N3侧UPF外的其它UPF不需要向SMF发送N4会话修改响应消息。
步骤11、SMF向AMF发送N1N2消息传输请求(Namf_Communication_N1N2MessageTransfer)。
步骤12-14、AMF发送N2会话请求以建立N3连接和RRC连接。
步骤14b、当N3侧UPF接收该会话的小数据时，解封装获取数据信息，比如会话源IP地址或者会话目的IP地址。而后再依据步骤10a中保存的UPF和UPF对应服务操作的API URI，以及依据当前的邻居连接关系和卫星的星间可见时间时长(比如选择星间可见时间时长长的)，选择出合适的下一跳 UPF；或者依据步骤10a中保存的UPF的星历信息计算出当前时刻相连的UPF以及卫星的星间可见时间时长，选择出合适的下一跳UPF，并触发对应的服务操作，比如数据传输请求(Nupf_PDUSession_TransferData Request)服务操作，将要发送的数据作为POST请求的有效载荷体，以发送接收到的小数据到下一跳UPF。路径上其它UPF只需提取出小数据、获取数据信息(比如会话源IP地址或者会话目的IP地址)和选择合适的下一跳UPF，并触发对应的服务操作，比如数据传输请求(Nupf_PDUSession_TransferData Request)服务操作，将要发送的数据作为POST请求的有效载荷体以发送数据到下一跳UPF。PSA提取出小数据，直接转发到DN中。同时，所有UPF接收到对端UPF的请求后，要触发数据传输响应(Nupf_PDUSession_TransferData Response)服务操作进行响应。
步骤15、AMF向SMF发送更新会话管理上下文请求(Nsmf_PDUSession_UpdateSMContextRequest)，以建立N3连接。
步骤16、SMF向UPF发起N4会话修改流程以建立N3连接，并为该PDU会话注册(若未注册)。
步骤17a、PSA接收到小数据时，获取数据信息，比如会话源IP地址或者目的IP地址。而后再基于步骤10a中保存的UPF和UPF对应服务操作的API URI，以及依据当前的邻居连接关系和卫星的星间可见时间时长(比如选择星间可见时间时长长的)，选择出合适的下一跳UPF；或者依据步骤10a中保存的UPF的星历信息计算出当前时刻相连的UPF以及卫星的星间可见时间时长，选择出合适的下一跳UPF，并触发对应的服务操作，比如数据传输请求(Nupf_PDUSession_TransferData Request)服务操作，将要发送的数据作为POST请求的有效载荷体，以发送接收到的小数据到下一跳UPF。路径上其它UPF只需提取出小数据、获取数据信息(比如会话源IP地址或者目的IP地址)和选择合适的下一跳UPF，并触发对应的服务操作，比如数据传输请求(Nupf_PDUSession_TransferData Request)服务操作，将要发送的数据作为POST请求的有效载荷体以发送数据到下一跳UPF。N3侧UPF提取出小数据，进行封装，封装成GTP报文并发送到RAN。同时，所有UPF接收到 对端UPF的请求后，要触发数据传输响应(Nupf_PDUSession_TransferData Response)服务操作进行响应。
步骤17、SMF向AMF发送更新会话管理上下文响应(Nsmf_PDUSession_UpdateSMContextResponse)。
步骤18、如果PDU会话建立失败，则SMF调用会话管理上下文状态通知(Nsmf_PDUSession_SMContextStatusNotify(Release))，通知AMF。
步骤19、SMF经过UPF到UE：如果PDU会话类型为IPv6或IPv4v6，SMF生成IPv6路由通知(IPv6Address Configuration)，并通过N4发给UE和UPF。
步骤20、SMF执行会话管理策略修改过程。
步骤21、如果在步骤4之后PDU会话建立失败，则SMF应执行Nudm_SDM_Unsubscribe实现去订阅。
后续，UPF再接收到小数据的数据报文时，执行步骤14b或者步骤17a。
实施例5：UPF通过NRF获取UPF相关信息(包括服务操作信息)，实现用户面UPF之间的数据转发。
图11为本公开实施例提供的数据传输方法的实施示意图之五，如图11所示，其主要包括如下步骤：
步骤1、UE向AMF发起PDU会话建立请求。
步骤2-3、AMF选择SMF以建立会话，并向SMF触发创建会话管理上下文请求(Nsmf_PDUSession_CreateSMContextRequest)。
步骤4、如果与SUPI、DNN和S-NSSAI相关的会话管理签约数据不可用，则SMF使用Nudm_SDM_Get(SUPI,Session Management Subscription data,DNN,S-NSSAI)检索会话管理签约数据，并使用Nudm_SDM_Subscribe(SUPI,Session Management Subscription data,DNN,S-NSSAI)向UDM订阅关于签约数据改变的通知。
步骤5、SMF向AMF发送创建会话管理上下文响应(Nsmf_PDUSession_CreateSMContextResponse)。
步骤6、PDU会话辅助认证/授权。
步骤7、如果为PDU会话使用PCC，则SMF执行策略控制功能PCF选择，并执行会话管理策略建立过程，与PCF建立一个SM策略关联，并获得PDU会话的缺省PCC策略。
步骤8、基于步骤3中获取的UE的RAT Type，假设RAT Type为NB-IoT，则SMF确定不为该会话建立专用的用户面连接，即通过服务操作实现数据传输，同时，SMF执行UPF选择，包括SMF根据星历信息获得的该UPF不同时间段内的相连的其它UPF信息，其中UPF信息包括服务操作信息(若保存的有)。
步骤9、SMF可执行会话管理策略修改过程，向PCF提供条件已满足的策略控制请求触发器(Policy Control Request Trigger)的相关信息。
步骤10a、SMF向选择的所有UPF发送N4会话建立请求消息，消息中携带第一信息，以任意一个UPF为例，第一信息包括该UPF在不同时间段内相连的其它UPF的标识、其他UPF所在卫星与该UPF所在卫星的星间可见时间时长、其他UPF所在卫星的星历信息、会话IP地址、小数据传输指示等信息；或者第一信息包括该UPF相连的其它UPF的标识、其他UPF所在卫星的星历信息、会话IP地址、小数据传输指示等信息；或者第一信息包括该UPF相连的其它UPF的标识、会话IP地址、小数据传输指示等信息。如果SMF有UPF的服务操作信息，此步骤中也携带。此时，SMF不需要向除N3侧UPF外的其它UPF发送N4会话修改请求消息。
步骤10b、所有UPF向SMF发送N4会话建立响应消息，此时N3侧UPF只发送为该会话分配的N3侧的隧道信息，N3侧UPF不需要分配N9侧的隧道信息；除N3侧UPF以外的其它UPF不需要分配隧道信息。各UPF保存不同时段对端UPF的服务操作信息，包括API URI，以供收到该会话上的小数据时触发服务操作来发送小数据。此时，除N3侧UPF外的其它UPF不需要向SMF发送N4会话修改响应消息。
步骤10c、若UPF没有收到所有不同时段对端UPF的服务操作信息，需要从NRF获取(UPF发现)，并保存。
步骤11、SMF向AMF发送N1N2消息传输请求 (Namf_Communication_N1N2MessageTransfer)。
步骤12-14、AMF发送N2会话请求以建立N3连接和RRC连接。
步骤14b、当N3侧UPF接收该会话的小数据时，解封装获取数据信息，比如会话源IP地址或者会话目的IP地址。而后再依据步骤10a中保存的UPF和UPF对应服务操作的API URI，以及依据当前的邻居连接关系和卫星的星间可见时间时长(比如选择星间可见时间时长长的)，选择出合适的下一跳UPF；或者依据步骤10a中保存的UPF的星历信息计算出当前时刻相连的UPF以及卫星的星间可见时间时长，选择出合适的下一跳UPF，并触发对应的服务操作，比如数据传输请求(Nupf_PDUSession_TransferData Request)服务操作，将要发送的数据作为POST请求的有效载荷体，以发送接收到的小数据到下一跳UPF。路径上其它UPF只需提取出小数据、获取数据信息(比如会话源IP地址或者会话目的IP地址)和选择合适的下一跳UPF，并触发对应的服务操作，比如数据传输请求(Nupf_PDUSession_TransferData Request)服务操作，将要发送的数据作为POST请求的有效载荷体以发送数据到下一跳UPF。PSA提取出小数据，直接转发到DN中。同时，所有UPF接收到对端UPF的请求后，要触发数据传输响应(Nupf_PDUSession_TransferData Response)服务操作进行响应。
步骤15、AMF向SMF发送更新会话管理上下文请求(Nsmf_PDUSession_UpdateSMContextRequest)，以建立N3连接。
步骤16、SMF向UPF发起N4会话修改流程以建立N3连接，并为该PDU会话注册(若未注册)。
步骤17a、PSA接收到小数据时，获取数据信息，比如会话源IP地址或者目的IP地址。而后再基于步骤10a中保存的UPF和UPF对应服务操作的API URI，以及依据当前的邻居连接关系和卫星的星间可见时间时长(比如选择星间可见时间时长长的)，选择出合适的下一跳UPF；或者依据步骤10a中保存的UPF的星历信息计算出当前时刻相连的UPF以及卫星的星间可见时间时长，选择出合适的下一跳UPF，并触发对应的服务操作，比如数据传输请求(Nupf_PDUSession_TransferData Request)服务操作，将要发送的数据作 为POST请求的有效载荷体，以发送接收到的小数据到下一跳UPF。路径上其它UPF只需提取出小数据、获取数据信息(比如会话源IP地址或者目的IP地址)和选择合适的下一跳UPF，并触发对应的服务操作，比如数据传输请求(Nupf_PDUSession_TransferData Request)服务操作，将要发送的数据作为POST请求的有效载荷体以发送数据到下一跳UPF。N3侧UPF提取出小数据，进行封装，封装成GTP报文并发送到RAN。同时，所有UPF接收到对端UPF的请求后，要触发数据传输响应(Nupf_PDUSession_TransferData Response)服务操作进行响应。
步骤17、SMF向AMF发送更新会话管理上下文响应(Nsmf_PDUSession_UpdateSMContextResponse)。
步骤18、如果PDU会话建立失败，则SMF调用会话管理上下文状态通知(Nsmf_PDUSession_SMContextStatusNotify(Release))，通知AMF。
步骤19、SMF经过UPF到UE：如果PDU会话类型为IPv6或IPv4v6，SMF生成IPv6路由通知(IPv6Address Configuration)，并通过N4发给UE和UPF。
步骤20、SMF执行会话管理策略修改过程。
步骤21、如果在步骤4之后PDU会话建立失败，则SMF应执行Nudm_SDM_Unsubscribe实现去订阅。
后续，UPF再接收到小数据的数据报文时，执行步骤14b或者步骤17a。
本公开实施例提供的数据传输方法，相比现有技术有如下优点：
(1)节省用户面资源：不需要建立专用隧道，和维护隧道信息。
(2)减少用户面功能网元的处理复杂度：用户面功能网元不需要对报文进行解封装和封装。
(3)降低数据的传输时延：用户面功能网元不需要对报文进行解封装和封装减少了对数据的处理时延；另外，不需要将数据传输到地面，可以大大减少数据的传输时延。
本公开各实施例提供的方法和装置是基于同一申请构思的，由于方法和装置解决问题的原理相似，因此装置和方法的实施可以相互参见，重复之处 不再赘述。
图12为本公开实施例提供的第一用户面功能网元的结构示意图，如图12所示，该第一用户面功能网元包括存储器1220，收发机1210和处理器1200；其中，处理器1200与存储器1220也可以物理上分开布置。
存储器1220，用于存储计算机程序；收发机1210，用于在处理器1200的控制下收发数据。
具体地，收发机1210用于在处理器1200的控制下接收和发送数据。
其中，在图12中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1200代表的一个或多个处理器和存储器1220代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本公开不再对其进行进一步描述。总线接口提供接口。收发机1210可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元，这些传输介质包括无线信道、有线信道、光缆等传输介质。
处理器1200负责管理总线架构和通常的处理，存储器1220可以存储处理器1200在执行操作时所使用的数据。
处理器1200可以是中央处理器(Central Processing Unit,CPU)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field－Programmable Gate Array，FPGA)或复杂可编程逻辑器件(Complex Programmable Logic Device，CPLD)，处理器也可以采用多核架构。
处理器1200通过调用存储器1220存储的计算机程序，用于按照获得的可执行指令执行本公开实施例提供的任一所述方法，例如：接收会话管理功能网元发送的N4会话建立请求消息，N4会话建立请求消息中携带第一信息；第一信息用于指示第一用户面功能网元通过服务操作进行指定数据的传输；通过服务操作将与第一信息相匹配的数据发送给下一跳用户面功能网元。
可选地，第一信息包括以下一项或多项：
第二用户面功能网元的信息；第二用户面功能网元包括第一用户面功能网元在不同时间段所连接的多个用户面功能网元；
会话IP地址；
小数据传输指示；
事件通知订阅指示。
可选地，第二用户面功能网元的信息包括以下一项或多项：
第二用户面功能网元的标识信息；
第二用户面功能网元与第一用户面功能网元之间建立连接的时间相关信息；
第二用户面功能网元所在卫星与第一用户面功能网元所在卫星之间的星间可见时间时长；
第二用户面功能网元所在卫星的星历信息；
第二用户面功能网元的服务操作信息。
可选地，通过服务操作将与第一信息相匹配的数据发送给下一跳用户面功能网元，包括：
通过事件通知服务操作或数据传输请求服务操作，将与第一信息相匹配的数据发送给下一跳用户面功能网元。
可选地，在通过事件通知服务操作将与第一信息相匹配的数据发送给下一跳用户面功能网元之前，该方法还包括：
根据第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息，向第一用户面功能网元在不同时间段所连接的用户面功能网元触发事件订阅服务操作。
可选地，通过服务操作将与第一信息相匹配的数据发送给下一跳用户面功能网元之前，该方法还包括：
根据第一用户面功能网元在当前时间段所连接的用户面功能网元的服务操作信息，以及第一用户面功能网元在当前时间段所连接的用户面功能网元所在卫星与第一用户面功能网元所在卫星之间的星间可见时间时长，确定下一跳用户面功能网元。
可选地，接收会话管理功能网元发送的N4会话建立请求消息之后，该方法还包括：
从N4会话建立请求消息中获取第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息；或者，
根据N4会话建立请求消息，从网络存储功能网元中获取第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息。
可选地，在第一用户面功能网元为N3侧用户面功能网元的情况下，接收会话管理功能网元发送的N4会话建立请求消息之后，该方法还包括：
向会话管理功能网元发送N4会话建立响应消息，N4会话建立响应消息中携带N3侧用户面功能网元的N3隧道信息。
可选地，在第一用户面功能网元为N3侧用户面功能网元的情况下，该方法还包括：
在接收上行数据后，对上行数据进行解封装，通过服务操作将解封装后得到的数据发送给下一跳用户面功能网元；和/或，
在接收下行数据后，对下行数据进行封装，将封装后的数据发送给接入网设备。
可选地，在第一用户面功能网元为锚点用户面功能网元的情况下，该方法还包括：
在接收上行数据后，将上行数据发送给数据网络；和/或，
在接收下行数据后，通过服务操作将下行数据发送给下一跳用户面功能网元。
图13为本公开实施例提供的会话管理功能网元的结构示意图，如图13所示，该会话管理功能网元包括存储器1320，收发机1310和处理器1300；其中，处理器1300与存储器1320也可以物理上分开布置。
存储器1320，用于存储计算机程序；收发机1310，用于在处理器1300的控制下收发数据。
具体地，收发机1310用于在处理器1300的控制下接收和发送数据。
其中，在图13中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1300代表的一个或多个处理器和存储器1320代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路 等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本公开不再对其进行进一步描述。总线接口提供接口。收发机1310可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元，这些传输介质包括无线信道、有线信道、光缆等传输介质。
处理器1300负责管理总线架构和通常的处理，存储器1320可以存储处理器1300在执行操作时所使用的数据。
处理器1300可以是CPU、ASIC、FPGA或CPLD，处理器也可以采用多核架构。
处理器1300通过调用存储器1320存储的计算机程序，用于按照获得的可执行指令执行本公开实施例提供的任一所述方法，例如：确定通过服务操作进行数据传输；向第一用户面功能网元发送N4会话建立请求消息，N4会话建立请求消息中携带第一信息；第一信息用于指示第一用户面功能网元通过服务操作进行指定数据的传输。
可选地，第一信息包括以下一项或多项：
第二用户面功能网元的信息；第二用户面功能网元包括第一用户面功能网元在不同时间段所连接的多个用户面功能网元；
会话IP地址；
小数据传输指示；
事件通知订阅指示。
可选地，第二用户面功能网元的信息包括以下一项或多项：
第二用户面功能网元的标识信息；
第二用户面功能网元与第一用户面功能网元之间建立连接的时间相关信息；
第二用户面功能网元所在卫星与第一用户面功能网元所在卫星之间的星间可见时间时长；
第二用户面功能网元所在卫星的星历信息；
第二用户面功能网元的服务操作信息。
可选地，确定通过服务操作进行数据传输，包括：
根据终端的无线接入类型，确定通过服务操作进行终端的数据传输。
可选地，在第一用户面功能网元为N3侧用户面功能网元的情况下，向第一用户面功能网元发送N4会话建立请求消息之后，该方法还包括：
接收N3侧用户面功能网元发送的N4会话建立响应消息，N4会话建立响应消息中携带N3侧用户面功能网元的N3隧道信息。
在此需要说明的是，本公开实施例提供的上述第一用户面功能网元和会话管理功能网元，能够实现上述方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
图14为本公开实施例提供的数据传输装置的结构示意图之一，该装置应用于第一用户面功能网元，如图14所示，该装置包括：
第一接收单元1400，用于接收会话管理功能网元发送的N4会话建立请求消息，N4会话建立请求消息中携带第一信息；第一信息用于指示第一用户面功能网元通过服务操作进行指定数据的传输；
第一发送单元1410，用于通过服务操作将与第一信息相匹配的数据发送给下一跳用户面功能网元。
可选地，第一信息包括以下一项或多项：
第二用户面功能网元的信息；第二用户面功能网元包括第一用户面功能网元在不同时间段所连接的多个用户面功能网元；
会话IP地址；
小数据传输指示；
事件通知订阅指示。
可选地，第二用户面功能网元的信息包括以下一项或多项：
第二用户面功能网元的标识信息；
第二用户面功能网元与第一用户面功能网元之间建立连接的时间相关信息；
第二用户面功能网元所在卫星与第一用户面功能网元所在卫星之间的星间可见时间时长；
第二用户面功能网元所在卫星的星历信息；
第二用户面功能网元的服务操作信息。
可选地，通过服务操作将与第一信息相匹配的数据发送给下一跳用户面功能网元，包括：
通过事件通知服务操作或数据传输请求服务操作，将与第一信息相匹配的数据发送给下一跳用户面功能网元。
可选地，该装置还包括：
订阅单元，用于根据第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息，向第一用户面功能网元在不同时间段所连接的用户面功能网元触发事件订阅服务操作。
可选地，该装置还包括：
第一确定单元，用于根据第一用户面功能网元在当前时间段所连接的用户面功能网元的服务操作信息，以及第一用户面功能网元在当前时间段所连接的用户面功能网元所在卫星与第一用户面功能网元所在卫星之间的星间可见时间时长，确定下一跳用户面功能网元。
可选地，该装置还包括获取单元，用于：
从N4会话建立请求消息中获取第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息；或者，
根据N4会话建立请求消息，从网络存储功能网元中获取第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息。
可选地，第一发送单元1410，还用于：
向会话管理功能网元发送N4会话建立响应消息，N4会话建立响应消息中携带N3侧用户面功能网元的N3隧道信息。
可选地，在第一用户面功能网元为N3侧用户面功能网元的情况下，第一发送单元1410，还用于：
在接收上行数据后，对上行数据进行解封装，通过服务操作将解封装后得到的数据发送给下一跳用户面功能网元；和/或，
在接收下行数据后，对下行数据进行封装，将封装后的数据发送给接入 网设备。
可选地，在第一用户面功能网元为锚点用户面功能网元的情况下，第一发送单元1410，还用于：
在接收上行数据后，将上行数据发送给数据网络；和/或，
在接收下行数据后，通过服务操作将下行数据发送给下一跳用户面功能网元。
图15为本公开实施例提供的数据传输装置的结构示意图之二，该装置应用于会话管理功能网元，如图15所示，该装置包括：
第二确定单元1500，用于确定通过服务操作进行数据传输；
第二发送单元1510，用于向第一用户面功能网元发送N4会话建立请求消息，N4会话建立请求消息中携带第一信息；第一信息用于指示第一用户面功能网元通过服务操作进行指定数据的传输。
可选地，第一信息包括以下一项或多项：
第二用户面功能网元的信息；第二用户面功能网元包括第一用户面功能网元在不同时间段所连接的多个用户面功能网元；
会话IP地址；
小数据传输指示；
事件通知订阅指示。
可选地，第二用户面功能网元的信息包括以下一项或多项：
第二用户面功能网元的标识信息；
第二用户面功能网元与第一用户面功能网元之间建立连接的时间相关信息；
第二用户面功能网元所在卫星与第一用户面功能网元所在卫星之间的星间可见时间时长；
第二用户面功能网元所在卫星的星历信息；
第二用户面功能网元的服务操作信息。
可选地，确定通过服务操作进行数据传输，包括：
根据终端的无线接入类型，确定通过服务操作进行终端的数据传输。
可选地，在第一用户面功能网元为N3侧用户面功能网元的情况下，该装置还包括：
第二接收单元，用于接收N3侧用户面功能网元发送的N4会话建立响应消息，N4会话建立响应消息中携带N3侧用户面功能网元的N3隧道信息。
需要说明的是，本公开实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个处理器可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
在此需要说明的是，本公开实施例提供的上述装置，能够实现上述方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
另一方面，本公开实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序用于使计算机执行上述各实施例提供的数据传输方法。
在此需要说明的是，本公开实施例提供的计算机可读存储介质，能够实现上述方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
所述计算机可读存储介质可以是计算机能够存取的任何可用介质或数据 存储设备，包括但不限于磁性存储器(例如软盘、硬盘、磁带、磁光盘(MO)等)、光学存储器(例如CD、DVD、BD、HVD等)、以及半导体存储器(例如ROM、EPROM、EEPROM、非易失性存储器(NAND FLASH)、固态硬盘(SSD))等。
本公开实施例提供的技术方案可以适用于多种系统，尤其是5G系统。例如适用的系统可以是全球移动通讯(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)系统、高级长期演进(long term evolution advanced，LTE-A)系统、通用移动系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)系统、5G新空口(New Radio,NR)系统等。这多种系统中均包括终端设备和网络设备。系统中还可以包括核心网部分，例如演进的分组系统(Evloved Packet System,EPS)、5G系统(5GS)等。
本公开实施例涉及的终端，可以是指向用户提供语音和/或数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备等。在不同的系统中，终端的名称可能也不相同，例如在5G系统中，终端可以称为用户设备(User Equipment，UE)。无线终端设备可以经无线接入网(Radio Access Network,RAN)与一个或多个核心网(Core Network,CN)进行通信，无线终端设备可以是移动终端设备，如移动电话(或称为“蜂窝”电话)和具有移动终端设备的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(Personal Communication Service，PCS)电话、无绳电话、会话发起协议(Session Initiated Protocol，SIP)话机、无线本地环路(Wireless Local Loop，WLL)站、个人数字助理(Personal Digital Assistant，PDA)等设备。无线终端设备也可以称为系统、订户单元(subscriber unit)、 订户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点(access point)、远程终端设备(remote terminal)、接入终端设备(access terminal)、用户终端设备(user terminal)、用户代理(user agent)、用户装置(user device)，本公开实施例中并不限定。
本领域内的技术人员应明白，本公开的实施例可提供为方法、系统、或计算机程序产品。因此，本公开可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本公开可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本公开是参照根据本公开实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机可执行指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机可执行指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些处理器可执行指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的处理器可读存储器中，使得存储在该处理器可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些处理器可执行指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本公开进行各种改动和变型而不脱离本公开的精神和范围。这样，倘若本公开的这些修改和变型属于本公开权利要求及其等同技术的范围之内，则本公开也意图包含这些改动和变型在内。

Claims (46)

  1. 一种数据传输方法，其特征在于，应用于第一用户面功能网元，包括：
    接收会话管理功能网元发送的N4会话建立请求消息，所述N4会话建立请求消息中携带第一信息；所述第一信息用于指示所述第一用户面功能网元通过服务操作进行指定数据的传输；
    通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元。
  2. 根据权利要求1所述的数据传输方法，其特征在于，所述第一信息包括以下一项或多项：
    第二用户面功能网元的信息；所述第二用户面功能网元包括所述第一用户面功能网元在不同时间段所连接的多个用户面功能网元；
    会话IP地址；
    小数据传输指示；
    事件通知订阅指示。
  3. 根据权利要求2所述的数据传输方法，其特征在于，所述第二用户面功能网元的信息包括以下一项或多项：
    所述第二用户面功能网元的标识信息；
    所述第二用户面功能网元与所述第一用户面功能网元之间建立连接的时间相关信息；
    所述第二用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长；
    所述第二用户面功能网元所在卫星的星历信息；
    所述第二用户面功能网元的服务操作信息。
  4. 根据权利要求1所述的数据传输方法，其特征在于，所述通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元，包括：
    通过事件通知服务操作或数据传输请求服务操作，将与所述第一信息相匹配的数据发送给下一跳用户面功能网元。
  5. 根据权利要求4所述的数据传输方法，其特征在于，在通过事件通知 服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元之前，所述方法还包括：
    根据所述第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息，向所述第一用户面功能网元在不同时间段所连接的用户面功能网元触发事件订阅服务操作。
  6. 根据权利要求1所述的数据传输方法，其特征在于，所述通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元之前，所述方法还包括：
    根据所述第一用户面功能网元在当前时间段所连接的用户面功能网元的服务操作信息，以及所述第一用户面功能网元在当前时间段所连接的用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长，确定下一跳用户面功能网元。
  7. 根据权利要求1至6任一项所述的数据传输方法，其特征在于，所述接收会话管理功能网元发送的N4会话建立请求消息之后，所述方法还包括：
    从所述N4会话建立请求消息中获取所述第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息；或者，
    根据所述N4会话建立请求消息，从网络存储功能网元中获取所述第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息。
  8. 根据权利要求1所述的数据传输方法，其特征在于，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述接收会话管理功能网元发送的N4会话建立请求消息之后，所述方法还包括：
    向所述会话管理功能网元发送N4会话建立响应消息，所述N4会话建立响应消息中携带所述N3侧用户面功能网元的N3隧道信息。
  9. 根据权利要求1所述的数据传输方法，其特征在于，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述方法还包括：
    在接收上行数据后，对所述上行数据进行解封装，通过服务操作将解封装后得到的数据发送给下一跳用户面功能网元；和/或，
    在接收下行数据后，对所述下行数据进行封装，将封装后的数据发送给 接入网设备。
  10. 根据权利要求1所述的数据传输方法，其特征在于，在所述第一用户面功能网元为锚点用户面功能网元的情况下，所述方法还包括：
    在接收上行数据后，将所述上行数据发送给数据网络；和/或，
    在接收下行数据后，通过服务操作将所述下行数据发送给下一跳用户面功能网元。
  11. 一种数据传输方法，其特征在于，应用于会话管理功能网元，包括：
    确定通过服务操作进行数据传输；
    向第一用户面功能网元发送N4会话建立请求消息，所述N4会话建立请求消息中携带第一信息；所述第一信息用于指示所述第一用户面功能网元通过服务操作进行指定数据的传输。
  12. 根据权利要求11所述的数据传输方法，其特征在于，所述第一信息包括以下一项或多项：
    第二用户面功能网元的信息；所述第二用户面功能网元包括所述第一用户面功能网元在不同时间段所连接的多个用户面功能网元；
    会话IP地址；
    小数据传输指示；
    事件通知订阅指示。
  13. 根据权利要求12所述的数据传输方法，其特征在于，所述第二用户面功能网元的信息包括以下一项或多项：
    所述第二用户面功能网元的标识信息；
    所述第二用户面功能网元与所述第一用户面功能网元之间建立连接的时间相关信息；
    所述第二用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长；
    所述第二用户面功能网元所在卫星的星历信息；
    所述第二用户面功能网元的服务操作信息。
  14. 根据权利要求11所述的数据传输方法，其特征在于，所述确定通过 服务操作进行数据传输，包括：
    根据终端的无线接入类型，确定通过服务操作进行所述终端的数据传输。
  15. 根据权利要求11所述的数据传输方法，其特征在于，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述向第一用户面功能网元发送N4会话建立请求消息之后，所述方法还包括：
    接收所述N3侧用户面功能网元发送的N4会话建立响应消息，所述N4会话建立响应消息中携带所述N3侧用户面功能网元的N3隧道信息。
  16. 一种第一用户面功能网元，其特征在于，包括存储器，收发机，处理器：
    存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
    接收会话管理功能网元发送的N4会话建立请求消息，所述N4会话建立请求消息中携带第一信息；所述第一信息用于指示所述第一用户面功能网元通过服务操作进行指定数据的传输；
    通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元。
  17. 根据权利要求16所述的第一用户面功能网元，其特征在于，所述第一信息包括以下一项或多项：
    第二用户面功能网元的信息；所述第二用户面功能网元包括所述第一用户面功能网元在不同时间段所连接的多个用户面功能网元；
    会话IP地址；
    小数据传输指示；
    事件通知订阅指示。
  18. 根据权利要求17所述的第一用户面功能网元，其特征在于，所述第二用户面功能网元的信息包括以下一项或多项：
    所述第二用户面功能网元的标识信息；
    所述第二用户面功能网元与所述第一用户面功能网元之间建立连接的时间相关信息；
    所述第二用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长；
    所述第二用户面功能网元所在卫星的星历信息；
    所述第二用户面功能网元的服务操作信息。
  19. 根据权利要求16所述的第一用户面功能网元，其特征在于，所述通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元，包括：
    通过事件通知服务操作或数据传输请求服务操作，将与所述第一信息相匹配的数据发送给下一跳用户面功能网元。
  20. 根据权利要求19所述的第一用户面功能网元，其特征在于，在通过事件通知服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元之前，所述操作还包括：
    根据所述第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息，向所述第一用户面功能网元在不同时间段所连接的用户面功能网元触发事件订阅服务操作。
  21. 根据权利要求16所述的第一用户面功能网元，其特征在于，所述通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元之前，所述操作还包括：
    根据所述第一用户面功能网元在当前时间段所连接的用户面功能网元的服务操作信息，以及所述第一用户面功能网元在当前时间段所连接的用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长，确定下一跳用户面功能网元。
  22. 根据权利要求16至21任一项所述的第一用户面功能网元，其特征在于，所述接收会话管理功能网元发送的N4会话建立请求消息之后，所述操作还包括：
    从所述N4会话建立请求消息中获取所述第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息；或者，
    根据所述N4会话建立请求消息，从网络存储功能网元中获取所述第一 用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息。
  23. 根据权利要求16所述的第一用户面功能网元，其特征在于，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述接收会话管理功能网元发送的N4会话建立请求消息之后，所述操作还包括：
    向所述会话管理功能网元发送N4会话建立响应消息，所述N4会话建立响应消息中携带所述N3侧用户面功能网元的N3隧道信息。
  24. 根据权利要求16所述的第一用户面功能网元，其特征在于，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述操作还包括：
    在接收上行数据后，对所述上行数据进行解封装，通过服务操作将解封装后得到的数据发送给下一跳用户面功能网元；和/或，
    在接收下行数据后，对所述下行数据进行封装，将封装后的数据发送给接入网设备。
  25. 根据权利要求16所述的第一用户面功能网元，其特征在于，在所述第一用户面功能网元为锚点用户面功能网元的情况下，所述操作还包括：
    在接收上行数据后，将所述上行数据发送给数据网络；和/或，
    在接收下行数据后，通过服务操作将所述下行数据发送给下一跳用户面功能网元。
  26. 一种会话管理功能网元，其特征在于，包括存储器，收发机，处理器：
    存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
    确定通过服务操作进行数据传输；
    向第一用户面功能网元发送N4会话建立请求消息，所述N4会话建立请求消息中携带第一信息；所述第一信息用于指示所述第一用户面功能网元通过服务操作进行指定数据的传输。
  27. 根据权利要求26所述的会话管理功能网元，其特征在于，所述第一信息包括以下一项或多项：
    第二用户面功能网元的信息；所述第二用户面功能网元包括所述第一用 户面功能网元在不同时间段所连接的多个用户面功能网元；
    会话IP地址；
    小数据传输指示；
    事件通知订阅指示。
  28. 根据权利要求27所述的会话管理功能网元，其特征在于，所述第二用户面功能网元的信息包括以下一项或多项：
    所述第二用户面功能网元的标识信息；
    所述第二用户面功能网元与所述第一用户面功能网元之间建立连接的时间相关信息；
    所述第二用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长；
    所述第二用户面功能网元所在卫星的星历信息；
    所述第二用户面功能网元的服务操作信息。
  29. 根据权利要求26所述的会话管理功能网元，其特征在于，所述确定通过服务操作进行数据传输，包括：
    根据终端的无线接入类型，确定通过服务操作进行所述终端的数据传输。
  30. 根据权利要求26所述的会话管理功能网元，其特征在于，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述向第一用户面功能网元发送N4会话建立请求消息之后，所述操作还包括：
    接收所述N3侧用户面功能网元发送的N4会话建立响应消息，所述N4会话建立响应消息中携带所述N3侧用户面功能网元的N3隧道信息。
  31. 一种数据传输装置，其特征在于，应用于第一用户面功能网元，包括：
    第一接收单元，用于接收会话管理功能网元发送的N4会话建立请求消息，所述N4会话建立请求消息中携带第一信息；所述第一信息用于指示所述第一用户面功能网元通过服务操作进行指定数据的传输；
    第一发送单元，用于通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元。
  32. 根据权利要求31所述的数据传输装置，其特征在于，所述第一信息包括以下一项或多项：
    第二用户面功能网元的信息；所述第二用户面功能网元包括所述第一用户面功能网元在不同时间段所连接的多个用户面功能网元；
    会话IP地址；
    小数据传输指示；
    事件通知订阅指示。
  33. 根据权利要求32所述的数据传输装置，其特征在于，所述第二用户面功能网元的信息包括以下一项或多项：
    所述第二用户面功能网元的标识信息；
    所述第二用户面功能网元与所述第一用户面功能网元之间建立连接的时间相关信息；
    所述第二用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长；
    所述第二用户面功能网元所在卫星的星历信息；
    所述第二用户面功能网元的服务操作信息。
  34. 根据权利要求31所述的数据传输装置，其特征在于，所述通过服务操作将与所述第一信息相匹配的数据发送给下一跳用户面功能网元，包括：
    通过事件通知服务操作或数据传输请求服务操作，将与所述第一信息相匹配的数据发送给下一跳用户面功能网元。
  35. 根据权利要求34所述的数据传输装置，其特征在于，所述装置还包括：
    订阅单元，用于根据所述第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息，向所述第一用户面功能网元在不同时间段所连接的用户面功能网元触发事件订阅服务操作。
  36. 根据权利要求31所述的数据传输装置，其特征在于，所述装置还包括：
    第一确定单元，用于根据所述第一用户面功能网元在当前时间段所连接 的用户面功能网元的服务操作信息，以及所述第一用户面功能网元在当前时间段所连接的用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长，确定下一跳用户面功能网元。
  37. 根据权利要求31至36任一项所述的数据传输装置，其特征在于，所述装置还包括获取单元，用于：
    从所述N4会话建立请求消息中获取所述第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息；或者，
    根据所述N4会话建立请求消息，从网络存储功能网元中获取所述第一用户面功能网元在不同时间段所连接的用户面功能网元的服务操作信息。
  38. 根据权利要求31所述的数据传输装置，其特征在于，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述第一发送单元还用于：
    向所述会话管理功能网元发送N4会话建立响应消息，所述N4会话建立响应消息中携带所述N3侧用户面功能网元的N3隧道信息。
  39. 根据权利要求31所述的数据传输装置，其特征在于，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述第一发送单元还用于：
    在接收上行数据后，对所述上行数据进行解封装，通过服务操作将解封装后得到的数据发送给下一跳用户面功能网元；和/或，
    在接收下行数据后，对所述下行数据进行封装，将封装后的数据发送给接入网设备。
  40. 根据权利要求31所述的数据传输装置，其特征在于，在所述第一用户面功能网元为锚点用户面功能网元的情况下，所述第一发送单元还用于：
    在接收上行数据后，将所述上行数据发送给数据网络；和/或，
    在接收下行数据后，通过服务操作将所述下行数据发送给下一跳用户面功能网元。
  41. 一种数据传输装置，其特征在于，应用于会话管理功能网元，包括：
    第二确定单元，用于确定通过服务操作进行数据传输；
    第二发送单元，用于向第一用户面功能网元发送N4会话建立请求消息，所述N4会话建立请求消息中携带第一信息；所述第一信息用于指示所述第 一用户面功能网元通过服务操作进行指定数据的传输。
  42. 根据权利要求41所述的数据传输装置，其特征在于，所述第一信息包括以下一项或多项：
    第二用户面功能网元的信息；所述第二用户面功能网元包括所述第一用户面功能网元在不同时间段所连接的多个用户面功能网元；
    会话IP地址；
    小数据传输指示；
    事件通知订阅指示。
  43. 根据权利要求42所述的数据传输装置，其特征在于，所述第二用户面功能网元的信息包括以下一项或多项：
    所述第二用户面功能网元的标识信息；
    所述第二用户面功能网元与所述第一用户面功能网元之间建立连接的时间相关信息；
    所述第二用户面功能网元所在卫星与所述第一用户面功能网元所在卫星之间的星间可见时间时长；
    所述第二用户面功能网元所在卫星的星历信息；
    所述第二用户面功能网元的服务操作信息。
  44. 根据权利要求41所述的数据传输装置，其特征在于，所述确定通过服务操作进行数据传输，包括：
    根据终端的无线接入类型，确定通过服务操作进行所述终端的数据传输。
  45. 根据权利要求41所述的数据传输装置，其特征在于，在所述第一用户面功能网元为N3侧用户面功能网元的情况下，所述装置还包括：
    第二接收单元，用于接收所述N3侧用户面功能网元发送的N4会话建立响应消息，所述N4会话建立响应消息中携带所述N3侧用户面功能网元的N3隧道信息。
  46. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序，所述计算机程序用于使计算机执行权利要求1至10任一项所述的方法，或执行权利要求11至15任一项所述的方法。
PCT/CN2023/086859 2022-04-07 2023-04-07 数据传输方法、设备、装置及存储介质 WO2023193786A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210363826.9A CN116939883A (zh) 2022-04-07 2022-04-07 数据传输方法、设备、装置及存储介质
CN202210363826.9 2022-04-07

Publications (1)

Publication Number Publication Date
WO2023193786A1 true WO2023193786A1 (zh) 2023-10-12

Family

ID=88244123

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/086859 WO2023193786A1 (zh) 2022-04-07 2023-04-07 数据传输方法、设备、装置及存储介质

Country Status (2)

Country Link
CN (1) CN116939883A (zh)
WO (1) WO2023193786A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111917806A (zh) * 2019-05-07 2020-11-10 华为技术有限公司 通信方法及装置
CN112312510A (zh) * 2019-07-30 2021-02-02 华为技术有限公司 一种数据转发方法、装置及系统
US20210266797A1 (en) * 2018-11-14 2021-08-26 Huawei Technologies Co., Ltd. Method and apparatus for controlling disorder of downlink data
CN114189270A (zh) * 2021-10-25 2022-03-15 西安空间无线电技术研究所 一种部署UPF的星载gNB基站及其数据处理方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210266797A1 (en) * 2018-11-14 2021-08-26 Huawei Technologies Co., Ltd. Method and apparatus for controlling disorder of downlink data
CN111917806A (zh) * 2019-05-07 2020-11-10 华为技术有限公司 通信方法及装置
CN112312510A (zh) * 2019-07-30 2021-02-02 华为技术有限公司 一种数据转发方法、装置及系统
CN114189270A (zh) * 2021-10-25 2022-03-15 西安空间无线电技术研究所 一种部署UPF的星载gNB基站及其数据处理方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
THALES: "NG-RAN architecture options for NTN", 3GPP DRAFT; R3-185406 RAN ARCHITECTURE OPTIONS FOR NTN, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Chengdu/China; 20181008 - 20181012, 28 September 2018 (2018-09-28), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051528698 *

Also Published As

Publication number Publication date
CN116939883A (zh) 2023-10-24

Similar Documents

Publication Publication Date Title
JP7189316B2 (ja) セッション管理方法、端末装置とネットワーク装置
US12063595B2 (en) Network node selection method and apparatus
US20210022063A1 (en) Data transmission method and apparatus
US20220330361A1 (en) Method for establishing connection and obtaining relay service code and communications apparatus
US20210219364A1 (en) Resource establishing method, and device
KR20200125673A (ko) 통신 방법 및 통신 장치
US20220408162A1 (en) Multicast service transmission method and apparatus
WO2021031010A1 (zh) 通信方法、终端设备和网络设备
US11399307B2 (en) Service authorization method, terminal device and network device
US20230254922A1 (en) Multipath transmission method and communication apparatus
WO2019196788A1 (zh) 通信方法和通信装置
WO2023087965A1 (zh) 一种通信方法及装置
KR20220125209A (ko) 서비스 품질 파라미터(QoS) 구성 방법 및 관련 장치
US20230388756A1 (en) Communication method and apparatus for multicast/broadcast service
WO2023000884A1 (zh) 多播会话处理方法、网络功能实体、装置及存储介质
WO2021062727A1 (zh) 一种重定向方法及装置、终端设备、网络设备
WO2022170798A1 (zh) 确定策略的方法和通信装置
WO2021088007A1 (zh) 无线通信的方法、终端设备和网络设备
WO2023125168A1 (zh) 通信方法和装置
US20230018378A1 (en) Parameter configuration method, apparatus and system, device and storage medium
WO2023193786A1 (zh) 数据传输方法、设备、装置及存储介质
CN114902790A (zh) 一种传输模式切换方法、电子设备及存储介质
EP4195513A1 (en) Data compression method and apparatus, and storage medium
WO2024017069A1 (zh) 定位方法、装置及存储介质
WO2021203249A1 (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: 23784349

Country of ref document: EP

Kind code of ref document: A1