WO2023116102A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2023116102A1
WO2023116102A1 PCT/CN2022/121649 CN2022121649W WO2023116102A1 WO 2023116102 A1 WO2023116102 A1 WO 2023116102A1 CN 2022121649 W CN2022121649 W CN 2022121649W WO 2023116102 A1 WO2023116102 A1 WO 2023116102A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
message
user plane
network element
terminal
Prior art date
Application number
PCT/CN2022/121649
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 WO2023116102A1 publication Critical patent/WO2023116102A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • 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

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a communication method and device.
  • the 3GPP standard group formulated the fifth generation (5th generation, 5G) network architecture at the end of 2016.
  • the architecture supports wireless technologies defined by the 3GPP standard group (such as long term evolution (LTE), 5G radio access network (RAN), etc.), fixed network and other access methods to access the core network.
  • LTE long term evolution
  • RAN radio access network
  • a terminal device When a terminal device communicates, it can usually access the network through an interface provided by a transmission control protocol/internet protocol (transmission control protocol/internet protocol, TCP/IP) protocol stack.
  • TCP/IP transmission control protocol/internet protocol
  • the application in the terminal calls the interface provided by the protocol stack (such as the TCP/IP protocol stack in Figure 1), and then the protocol stack and the device on the network side (such as deployed on the user plane function (user plane) function, UPF) remote device, not marked in Figure 1) exchange messages.
  • the message of the protocol stack on the terminal device can be sent through the wireless module (user equipment (user equipment, UE) in FIG. 1 ), and the message can also be received through the wireless module.
  • the message sent by the terminal can be sent to the network side device through the UPF, and can also receive the message from the network side device through the UPF. That is to say, when the terminal communicates with the network side, it needs to be implemented by carrying a protocol stack on the terminal, but the deployment of the protocol stack mechanism is complicated.
  • the present application provides a communication method and device to reduce communication complexity.
  • the present application provides a communication method, which can be executed by a user plane network element, such as UPF, or by a terminal, such as UE, vehicle-mounted equipment, etc., or by other user plane network elements , the present application does not specifically limit it here, and only uses the interaction between the terminal and the user plane network element as an example for illustration. Executable as follows:
  • the terminal determines the application message, the application message includes the application data and the application address of the receiving end of the application message, and does not include the source address of the application message; the terminal sends the application message to the user plane network element.
  • the user plane network element receives the application message from the terminal, the application message includes the application data and the application address of the receiving end of the application message; the application message is carried in the session or flow; the user plane network element determines the application message according to the session configuration information The source address of the message; the session configuration information is used to indicate the provision of connection services for the terminal; the user plane network element determines the destination address of the application message according to the application address; the user plane network element sends the first message to the receiving end, and the first message Including application data, the source address of the application message, and the destination address of the application message.
  • the terminal when the terminal communicates with other devices, there is no need to deploy a protocol stack for transmitting application packets in the terminal, and the terminal can directly send the application packets to the user plane network element through the wireless communication protocol, so that there is no need to connect the terminal to the wireless access Connections above the transport layer are established between devices, and the user plane network element can establish a communication connection with other devices above the transport layer of the application message through the session configuration information and the application address of the receiving end of the application message.
  • This method can reduce the When the terminal transmits the message of the application program, it needs to build the complexity of the protocol stack above the transport layer.
  • the user plane network element may determine the session source address according to the session configuration information; the user plane network element may use the session source address as the source address of the application packet.
  • the terminal deploys a protocol stack for transmitting application packets, it needs to carry the source address and destination address of the application packet when sending the packet, such as the source IP address and destination IP address of the application packet.
  • the terminal does not deploy a protocol stack for transmitting application packets.
  • the user plane network element can determine the address of the application packet according to the session configuration information. Source address, in this way the complexity of device processing can be reduced.
  • the user plane network element can send a connection creation request, and the creation request includes the application address; the creation request is used to request the destination address corresponding to the application address; the user plane network element receives the response information of the connection creation request, and responds The information includes a destination address corresponding to the application address. It should be noted that the user plane network element determines the destination address corresponding to the application address of the application packet through the connection creation request, rather than directly carrying the destination address through the application packet. Therefore, this application can provide a terminal device that does not deploy the application packet In the case of the protocol stack for message transmission, the solution for obtaining the destination address of the application message.
  • the user plane network element when it receives the application packet from the terminal, there are many ways to implement it. For example, it can receive the forwarded packet from the radio access network device, forward the packet
  • the forwarded message includes the application message sent by the terminal to the wireless access network device. Reliability of application message transmission can be ensured by forwarding the message through the wireless access network device.
  • the forwarded message may also include the serial number of the application message; the user plane network element may also feed back the received serial number of the application message to the access network device. It should be noted that, in actual application, due to the different conditions of the communication environment (such as: the presence of channel interference and noise), the application message may not be received, so the application message includes the serial number of the application message, which can be Determine which packets are successfully received and which packets are not successfully received.
  • the session configuration information may include, but is not limited to, message protocol information; the message protocol information is: message protocol information for transmitting application messages, and/or, message protocol types corresponding to application messages, etc., the present application Not specifically limited.
  • the message protocol information may be hyper text transfer protocol (hyper text transfer protocol, HTTP).
  • the source address may be an address allocated to the terminal by a user plane network element.
  • the present application provides a communication method, which can be executed by a user plane network element, such as UPF, or by a terminal.
  • a user plane network element such as UPF
  • UPF user plane network element
  • the terminal determines the indication information, and the indication information indicates the destination address of the receiving end of the application message; the terminal sends the indication information to the user plane network element; the terminal determines the application message, and the application message includes application data, and does not include the source address and Destination address, the terminal sends the application packet to the user plane network element.
  • the user plane network element receives the indication information from the terminal; the user plane network element receives the application message from the terminal; the user plane network element determines the destination address of the application message according to the indication information; the user plane network element determines the destination address of the application message according to the session configuration information
  • the source address of the application message; the session configuration information is used to indicate the provision of connection services for the terminal; the user plane network element sends the first message to the receiving end, the first message includes application data, the source address of the application message, and the application message destination address.
  • the terminal when the terminal communicates with other devices, the terminal can directly send the application message to the user plane network element through the wireless communication protocol, and the user plane network element can establish the connection of the application message with other devices through session configuration information and instruction information. Communication connection, through this method, the user plane network element can also obtain connection information without being able to perceive application-related information.
  • the indication information may be sent by the terminal to the user plane network element through a protocol layer between the terminal and the user plane network element.
  • the protocol layer can be a Ctrl layer.
  • the application does not limit the name of the Ctrl layer and the position in the protocol stack.
  • the terminal can also support protocol stacks such as the TCP/IP network layer and the transport layer.
  • the Ctrl layer can be located in the wireless protocol stack, Arbitrary positions of the TCP/IP network layer, transport layer, and application layer.
  • the Ctrl layer is used for information exchange between UE and UPF as an example.
  • the Ctrl layer can be used between devices in the network Information interaction is performed, and the network device can modify its content when passing the Ctrl layer.
  • the UPF can send the Ctrl layer information to the equipment in the DN, and the UPF can also modify the content before sending it.
  • This method does not affect the functions of other existing protocol layers. , the present application does not specifically limit it here.
  • the indication information is sent through the protocol layer, and the indication information indicates the address of the receiving end of the application message.
  • the user plane network element can also obtain the connection information when it cannot perceive the application-related information.
  • the user plane network element can determine the source address of the session carried by the application message according to the session configuration information; the user plane network element uses the source address of the session carried by the application message as the source address of the application message .
  • the user plane network element can determine the source address of the application message according to the session configuration information, which can reduce the processing complexity of the device .
  • the indication information may be specifically used to indicate: determine the destination address of the receiving end according to the connection identifier carried in the application message; the terminal may send the application message to the user plane network element, and the application message includes the first The connection identifier, the connection corresponding to the first connection identifier is used to bear the application message, correspondingly, the user plane network element can receive the application message from the terminal, and the application message includes the first connection identifier; the user plane network element according to the application message The first connection identifier included in , determines the destination address of the application message.
  • connection identifier may be a connection identifier determined by the terminal itself, or it may be a connection identifier obtained by other methods.
  • the user plane network element can determine the destination address of the receiving end of the application message according to the connection identifier. This method can Improve communication efficiency and reduce the complexity of device processing.
  • the user plane network element may send connection identification information to the terminal, where the connection identification information includes one or more connection identifications, and each connection identification is used to identify the connection created by the user plane network element; the first connection The identifier is selected by the terminal from one or more connection identifiers.
  • the user plane network element can receive the connection identifier information of the user plane network element.
  • connection identifier of the application message is allocated by the user plane network element. After the user plane network element allocates the connection identifier, the terminal carries the selected connection identifier when sending the application data, and the user plane network element can determine the connection information. , which can improve data processing efficiency.
  • the user plane network element when the user plane network element can receive the application packet from the terminal, there are many ways to implement it. For example, it can receive the forwarded packet from the wireless access network device, forward the packet The message is sent by the terminal to the wireless access network device, and the forwarded message includes the application message. Reliability of application message transmission can be ensured by forwarding the message through the wireless access network device.
  • the forwarded message may also include the serial number of the application message; the user plane network element may also feed back the received serial number of the application message to the access network device. It should be noted that, in actual application, due to the different conditions of the communication environment (such as: the presence of channel interference and noise), the application message may not be received, so the application message includes the serial number of the application message, which can be Determine which packets are successfully received and which packets are not successfully received.
  • the indication information may include, but is not limited to: quality of service (quality of service, QoS) requirement information corresponding to the terminal, message protocol information for transmitting the application message, message protocol type corresponding to the application message, and the like.
  • the message protocol information may be an HTTP protocol.
  • the embodiment of the present application provides a communication device.
  • the communication device can be a user plane network element (such as the user plane network element in the first aspect, or the user plane network element in the second aspect) or set in the user plane network element.
  • the chip inside the network element may also be a terminal (such as the terminal in the first aspect, the terminal in the second aspect) or a chip arranged inside the terminal.
  • the communication device has the function of realizing any one of the first aspect to the second aspect above, for example, the communication device includes a module or unit corresponding to the steps involved in any aspect of the first aspect to the second aspect above or Means, the function or unit or means may be implemented by software, or by hardware, or by executing corresponding software by hardware.
  • the communication device includes a processing unit and a transceiver unit, wherein the transceiver unit can be used to send and receive signals to realize communication between the communication device and other devices, for example, the transceiver unit is used to receive signals from Configuration information of the terminal device; the processing unit can be used to perform some internal operations of the communication device.
  • the transceiver unit may be called an input-output unit, a communication unit, etc., and the transceiver unit may be a transceiver; the processing unit may be a processor.
  • the transceiver unit may be an input-output interface, an input-output circuit, or an input-output pin, etc., and may also be called an interface, a communication interface, or an interface circuit;
  • the processing unit may be a processor, a processing circuit, or a logic circuit.
  • the communication device includes a processor, and may also include a transceiver, the transceiver is used to send and receive signals, and the processor executes program instructions to complete the first aspect to the second aspect above.
  • the communication device may also include one or more memories, the memories are used to be coupled with the processor, and the memories may store the necessary computer programs to realize the functions involved in any one of the first aspect to the second aspect above or instructions.
  • the processor may execute the computer program or instruction stored in the memory, and when the computer program or instruction is executed, the communication device may implement any of the possible designs or implementations of the first aspect to the second aspect above. method.
  • the communication device includes a processor, and the processor can be used to be coupled with the memory.
  • the memory may store necessary computer programs or instructions for realizing the functions involved in any one of the first to second aspects above.
  • the processor may execute the computer program or instruction stored in the memory, and when the computer program or instruction is executed, the communication device may implement any of the possible designs or implementations of the first aspect to the second aspect above. method.
  • the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit, and execute any possible design or method in the implementation.
  • the processor can be implemented by hardware or by software.
  • the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor
  • the processor may be a general-purpose processor implemented by reading software codes stored in memory.
  • there may be one or more processors, and one or more memories.
  • the memory can be integrated with the processor, or the memory can be separated from the processor.
  • the memory and the processor can be integrated on the same chip, or they can be respectively arranged on different chips.
  • the embodiment of the present application does not limit the type of the memory and the arrangement of the memory and the processor.
  • an embodiment of the present application provides a communication system, and the communication system includes the user plane network element and the terminal in the first aspect to the second aspect.
  • the present application provides a system-on-a-chip, which includes a processor and may further include a memory, configured to implement the method described in any possible design of the first aspect to the second aspect above.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • the present application also provides a computer-readable storage medium, in which computer-readable instructions are stored, and when the computer-readable instructions are run on a computer, the computer executes the first-to-second A method in either of two possible designs.
  • the present application provides a computer program product including instructions, which, when run on a computer, cause the computer to execute the methods of the above-mentioned embodiments from the first aspect to the second aspect.
  • FIG. 1 shows a schematic diagram of a terminal device deploying a protocol stack
  • FIG. 2 shows a schematic diagram of a mobile communication network architecture provided by an embodiment of the present application
  • FIG. 3A shows a schematic structural diagram of a protocol stack
  • FIG. 3B shows a schematic structural diagram of another protocol stack
  • FIG. 4 shows a schematic diagram of a communication connection process
  • FIG. 5 shows a schematic flowchart of a communication method provided by an embodiment of the present application
  • FIG. 6 shows a schematic flowchart of a communication method provided by the implementation of the present application.
  • FIG. 7 shows a schematic flowchart of a communication method provided by the implementation of the present application.
  • FIG. 8 shows a schematic flowchart of a communication method provided by the implementation of the present application.
  • FIG. 9 shows a schematic flowchart of a communication method provided by the implementation of the present application.
  • FIG. 10 shows a schematic flowchart of a communication method provided by the implementation of the present application.
  • FIG. 11A shows a schematic flowchart of a communication method provided by the implementation of the present application.
  • FIG. 11B shows a schematic flowchart of a communication method provided by the implementation of the present application.
  • Fig. 12 shows a schematic flowchart of a communication method provided by the implementation of the present application.
  • FIG. 13 shows a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 14 shows a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 15 shows a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 2 exemplarily shows a schematic diagram of a mobile communication network architecture, which includes terminal equipment, access network equipment, access and mobility management functions, session management functions, user plane functions, policy control functions, and network slice selection functions, network slice-specific authentication and authorization functions, network warehouse functions, network data analysis functions, unified data management functions, unified data storage functions, authentication service functions, network capability exposure functions, terminal wireless capability management functions, binding support functions, Application functions, and the data network (data network, DN) connected to the operator's network.
  • the terminal device can access the wireless network through the access node at the current location.
  • the terminal equipment can send service data to the data network through the access network equipment and user plane functions, and receive service data from the data network.
  • the access and mobility management function is mainly used for the attachment of terminal equipment in the mobile network, mobility management, tracking area update process, etc.
  • the access and mobility management function can be the access and mobility management function (access and mobility management function, AMF).
  • AMF access and mobility management function
  • the access and mobility management function It may still be AMF, or may have another name, which is not limited by the present application.
  • the session management function is mainly used for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet protocol addresses to terminal devices, selecting user plane functions that provide message forwarding functions, and so on.
  • the session management function may be a session management function (session management function, SMF), and in a future communication system (such as a 6G communication system), the session management function may still be an SMF, or may have other names, This application is not limiting.
  • the user plane function is mainly used to process user packets, such as forwarding and charging.
  • the user plane function may be UPF
  • a future communication system such as a 6G communication system
  • the user plane function may still be UPF, or may have other names, which are not limited in this application.
  • Policy control function including policy control function, charging policy control function, QoS control, etc.
  • the policy control function may be a policy control function (policy control function, PCF), and in a future communication system (such as a 6G communication system), the policy control function may still be a PCF, or may have other names, This application is not limiting.
  • the network slice selection function is mainly used to select the appropriate network slice for the service of the terminal device.
  • the network slice selection function can be a network slice selection function (network slice selection function, NSSF).
  • NSSF network slice selection function
  • the network slice selection function can still be NSSF, or it can also be There are other names, which are not limited by this application.
  • the network slice-specific authentication and authorization function (network slice-specific authentication and authorization function, NSSAAF) is mainly used for the verification and authorization of terminal devices accessing specific network slices.
  • the network warehouse function is mainly used to provide registration and discovery of network functions or services provided by network functions.
  • the network repository function may be a network repository function (network repository function, NRF).
  • NRF network repository function
  • the network repository function may still be NRF, or may have other names, This application is not limiting.
  • the network data analysis function can collect data from various network functions, such as policy control functions, session management functions, user plane functions, access management functions, and application functions (through the network capability exposure function), and perform analysis and prediction.
  • the network data analysis function can be a network data analysis function (network data analytics function, NWDAF).
  • NWDAF network data analytics function
  • the network data analysis function can still be NWDAF, or it can also be There are other names, which are not limited by this application.
  • the unified data management function is mainly used to manage the contract information of terminal equipment.
  • the unified data management function may be a unified data management (unified data management, UDM) function.
  • UDM unified data management
  • the unified data management function may still be a UDM function, or it may also be There are other names, which are not limited by this application.
  • the unified data storage function is mainly used to store structured data information, including contract information, policy information, and network data or business data defined in a standard format.
  • the unified data storage function may be a unified data repository (UDR) function, and in a future communication system (such as a 6G communication system), the unified data storage function may still be a UDR function, or may also be There are other names, which are not limited by this application.
  • the authentication service function is mainly used for security authentication of terminal equipment.
  • the authentication service function may be an authentication server function (authentication server function, AUSF), and in a future communication system (such as a 6G communication system), the authentication service function may still be AUSF, or may have other names , this application is not limited.
  • the network capability exposure function can expose some functions of the network to applications in a controlled manner.
  • the network capability exposure function may be NEF.
  • the network capability exposure function may still be NEF, or may have another name, which is not limited in this application.
  • the terminal wireless capability management function is used to store and manage the wireless capabilities of terminal devices in the network.
  • the terminal radio capability management function can be the terminal radio capability management function (UE radio capability management function, UCMF).
  • UE radio capability management function UE radio capability management function
  • the terminal radio capability management function can still be UCMF , or may have other names, which are not limited in this application.
  • the binding support function is used to maintain the correspondence between the protocol (internet protocol, IP) addresses and service functions interconnected between user networks.
  • the binding support function may be a binding support function (binding support function, BSF).
  • BSF binding support function
  • the binding support function may still be a BSF, or may also have Other titles are not limited in this application.
  • the application function can provide service data of various applications to the control plane function of the operator's communication network, or obtain network data information and control information from the control plane function of the communication network.
  • the application function may be an application function (Application Function, AF).
  • AF Application Function
  • the application function may still be AF, or may have other names. This application does not limited.
  • the data network is mainly used to provide data transmission services for terminal devices.
  • the data network can be a private network, such as a local area network, or a public data network (PDN), such as the Internet (Internet), or a private network deployed by operators, such as a configured IP multimedia network subsystem (IP multimedia core network subsystem, IMS) service.
  • PDN public data network
  • IMS IP multimedia core network subsystem
  • the functions in this embodiment of the application may also be referred to as network elements, network functions or functional entities, devices, etc.
  • the access and mobility management functions may also be referred to as access and mobility management network elements, or access and mobility management network functions, or access and mobility management functional entities, etc.
  • the names of the functions are not limited in this application, and those skilled in the art can replace the names of the above functions with other names to perform the same function, which all belong to the protection scope of the present application.
  • the protocol stack can include a link layer, a network layer, a transport layer, and an application layer.
  • Figure 3A also includes Physical layer, but usually the physical layer is not included in the layering of the protocol stack.
  • the application layer can realize the following functions:
  • Support HTTP Provide request and transmission of global wide area network (world wide web, Web) documents.
  • Support domain name resolution convert the URL (uniform resource locator, URL) into a 32-bit network address.
  • the transport layer can realize the following functions:
  • TCP transmission control protocol
  • services include delivery of application layer messages to destinations and flow control (that is, sender and receiver rate matching); Packets are divided into short packets to provide congestion control and suppress source sending rate.
  • UDP Support User Datagram Protocol
  • IP layer can realize the following functions:
  • Support IP Define the various fields in the datagram and how the end systems and routers act on these fields.
  • the link layer can realize the following functions:
  • the data of the network layer is transmitted to the next node through the link layer, and then the data is handed over to the network layer from the link layer at the next node.
  • Link layer protocols include, for example, point to point protocol (PPP), and can provide reliable delivery, but are different from TCP reliable delivery.
  • PPP point to point protocol
  • the physical layer can provide protocols and transmission media for bit stream transmission, and different transmission media have different physical layer protocols.
  • Figure 3B shows a schematic diagram of another protocol stack
  • the access network (access network, AN) layer is the wireless protocol stack between the UE and the access network RAN (this application does not limit and explain)
  • Ctrl/RT is optional
  • the protocol layer provides control (control, Ctrl) (name used in this application, not limited) and/or reliable transport (reliable transport, RT) (name used in this application, not limited) between UE and UPF
  • the protocol layer is the application layer between the UE and the DN side equipment.
  • the RAN can optionally provide an RT layer between itself and the UPF to provide reliable transmission.
  • UPF can optionally provide the RT protocol layer with RAN, and optionally provide the Ctrl/RT layer with UE; UPF provides network-side connection services on the network side, such as TCP/RT in Figure 3B.
  • UDP user datagrm protocol, user datagram protocol
  • this application does not limit the network type, connection type and specific protocol used in the DN).
  • UPF When UPF receives an application or Ctrl-level message from UE, it creates a connection in DN to provide data sending and receiving services for UE; data and Ctrl-level messages between UPF and UE can be optionally realized through RT protocol layer Reliable transmission (including two optional methods: RT protocol layer is used between UE and UPF; reliable transmission is realized between RAN and UE through the air interface mechanism, reliable transmission is realized between RAN and UPF through RT, and then the connection between UE and UPF is realized. between reliable transmission).
  • RT protocol layer is used between UE and UPF
  • reliable transmission is realized between RAN and UE through the air interface mechanism, reliable transmission is realized between RAN and UPF through RT, and then the connection between UE and UPF is realized. between reliable transmission).
  • the terminal does not deploy the TCP/IP protocol stack, the terminal can directly transmit application messages or application data with the UPF, and the UPF can deploy the TCP/UDP protocol stack to establish a communication connection with the data network for transmission data.
  • the process shown in Figure 4 can be referred to, and the application of the terminal calls the TCP/IP protocol stack
  • the request of the interface, the layer to which TCP/IP belongs returns the interface identifier to the application, and the UE establishes a TCP connection with the network device by means of its own wireless module (uses the TCP connection between RAN and UPF to transmit application data), and receives the network device The returned connection status (whether a connection can be established).
  • the application in the UE can transmit data to the network device through the wireless module based on the established TCP connection. How much data was not successfully received, etc.).
  • each terminal needs to deploy the TCP or IP protocol stack, etc., that is, the terminal must support the transmission of the TCP or IP protocol, but the TCP Or the deployment of the IP protocol stack brings processing overhead to the terminal device, requiring the terminal device to provide a processing capability supporting the TCP or IP protocol.
  • this application provides a communication method to improve the processing efficiency when the terminal transmits the application data of the application to the network device and reduce the impact on the terminal.
  • the processing power requirements of the device to transmit application data are a few bits of data that can be used to transmit application data.
  • the method can be executed through the interaction of a terminal, a user plane network element, and a receiving end, where the receiving end may be a network device, a core network device, and a data center, etc.
  • the present application is not specifically limited here.
  • the communication between the terminal and the receiving end is realized by means of user plane network elements.
  • the terminal does not need to deploy TCP or IP protocol stacks, etc., and only needs to use wireless communication protocols to send application messages or application data to the receiving end.
  • the network element on the user plane can act as a client to establish a TCP or IP communication connection with the receiving end.
  • the network element on the user plane can act as a server and directly send application messages or application data to the terminal through the wireless communication protocol. Specifically, you can refer to the following steps to execute:
  • Step 501 the terminal determines the application message, the application message includes application data and the application address of the receiving end of the application message, and does not include the source address of the application message.
  • Application messages can be carried in sessions or streams, that is, application messages can be transmitted through sessions or streams. Usually, sessions include multiple streams. The streams can be QoS streams or other data streams. This application does not describe them here. Specific limits.
  • Step 502 the terminal sends an application packet to a user plane network element.
  • the user plane network element can receive the application message from the terminal.
  • Step 503 The user plane network element determines the source address of the application packet according to the session configuration information; the session configuration information is used to indicate to provide connection services for the terminal.
  • the session configuration information may be the information configured by the user plane network element, or the information from the session management network element, or the information from the core network equipment, or the information received by the user plane network element from the terminal
  • the application message is analyzed and determined.
  • This application does not specifically limit the source of the session configuration information here.
  • This method can make the acquisition method of the session configuration information more flexible and real-time adjustable. Since the user plane network element is equivalent to replacing the terminal device to communicate with the receiving end, the user plane network element must not only know the address of the receiving end but also determine the address of the replacing terminal device during communication, so as to establish a TCP or IP connection with the receiving end , so the source address of the application packet can be determined according to the session configuration information.
  • the user plane network element may determine the session source address according to the session configuration information; the user plane network element may use the session source address as the source address of the application packet.
  • the user plane network element determines the session or flow that bears the application message. Determine the source address of the session according to the session or flow carrying the application packet and session configuration information. And use the source address of the session as the source address of the application message.
  • the session configuration information includes the source address information of PDU session 1. If the application message is carried by PDU session 1 or the QoS flow under session 1, then the The source address of PDU session 1 is used as the source address of the application message.
  • the session configuration information may directly configure the source address information of the QoS flow subordinate to a certain PDU session, so it may also be directly based on the source address information of the QoS flow as the source address of the application message.
  • the present application is not specifically limited here.
  • the user plane network element can also assign a source address to the terminal without knowing the actual address of the terminal device.
  • terminal 1 corresponds to address 1
  • sending data to address 1 means sending data to terminal 1. Therefore, in actual application, the address of the terminal device can be set according to the performance of the user plane network element or the actual service requirements. It can be the address of the user plane network element, the actual address of the terminal device, or the user plane network element as The address assigned by the terminal device may also be address information composed of the address of the user plane network element and the actual address of the terminal device, etc., which are not specifically limited in this application.
  • a terminal when a terminal deploys a protocol stack for transmitting application packets, it needs to carry the source address and destination address of the application packet when sending the packet, such as the source IP address and destination IP address of the application packet.
  • the terminal when the terminal does not deploy the protocol stack for transmitting application packets, and the terminal device does not transmit the source address of the application packet to the user plane network element, the user plane network element can determine the source of the application packet according to the session configuration information The address, in this way, can reduce the processing complexity of the application data of the application transmitted by the terminal device.
  • the session configuration information may also include packet protocol information; the packet protocol information is: packet protocol information for transmitting application packets, and/or a packet protocol type corresponding to the application packets.
  • the message protocol information may be the HTTP protocol, etc., which is not specifically limited in this application.
  • Step 504 The user plane network element determines the destination address of the application packet according to the application address. Since the application packet carries the application address of the receiving end of the application packet, not the IP address, the user plane network element can determine the destination address of the application packet according to the application address. For example, the application address of the application packet is application address 1, and the user The corresponding relationship between the application address and the destination address of the application message may be stored in the network element on the plane. For example, if the application address 1 corresponds to the destination address 3, then the network element on the user plane may use the destination address 3 as the address of the receiving end of the application message.
  • the user plane network element may send a connection creation request, and the creation request includes an application address; the creation request is used to request a destination address corresponding to the application address; the user plane network element receives the response information of the connection creation request, The response information may include a destination address corresponding to the application address.
  • the user plane network element determines the destination address corresponding to the application address of the application packet through the connection creation request, rather than directly carrying the destination address through the application packet. Therefore, in this application, the terminal device can In the case of the transmission protocol stack of the document, the application message is sent to the UPF through a session or flow based on the wireless communication protocol, and the UPF can also obtain the destination address of the application message.
  • Step 505 the user plane network element sends a first packet to the receiving end, the first packet includes application data, a source address of the application packet, and a destination address of the application packet.
  • the user plane network element After the user plane network element determines the source address and destination address of the application message, it packs the application data with the application data to form the first message and transmits it to the receiving end.
  • the terminal communicates with the receiving end, there is no need to deploy the transmission protocol stack of the application message in the terminal.
  • the terminal sends the message to the user plane network element, it does not need to carry connection information based on the application message transmission protocol, such as source address or destination address.
  • the user plane network element can establish a communication connection with the receiving end for transmitting application messages, such as a TCP connection or an IP connection, through the session configuration information and the application address of the receiving end of the application message. This method can reduce UE transmission reference The complexity of data processing from packets to network-side devices.
  • the user plane network element and the terminal can directly transmit the application message based on the session or flow of the wireless communication protocol, without requiring the terminal to have a TCP or IP protocol stack to construct and communicate with the network side equipment.
  • the TCP or IP connection between the two devices is used to transmit the application message, and the application message can be sent between the network side device and the receiving end (such as the server corresponding to the application program) through the TCP or IP protocol stack.
  • the application message can also be transmitted using the HTTP protocol or the FTP protocol. In this way, the present application can support the terminal device to transmit the application message without deploying the protocol stack for transmitting the application message, which can simplify the process of transmitting the application message.
  • the session configuration information can also include the service type (connection service or addressing service, etc.) that the user plane network element can provide, the packet protocol or service type (IPv4/IPv6/ICN, MEC, etc.) that the receiving end can support, etc.,
  • This application is not specifically limited, and can be flexibly selected according to the user's service requirements and the equipment capabilities of the user plane network elements.
  • UPF User Plane Function
  • an external device that is, sends data during a communication connection
  • a UE there is an address server (such as a DNS server) in the external device, and there is also a device as a server or a receiving end.
  • the server or receiving end device can be deployed in the DN.
  • the receiving end device Deploy on DN as an example for illustration.
  • the application layer on the terminal side using the HTTP protocol as an example, the application on the terminal side sends packets directly through the wireless protocol layer, instead of transmitting application packets at the protocol layer such as Ctrl.
  • the data sent between UE and UPF is realized by means of RAN, and the data between RAN and UPF is guaranteed by reliable transmission GTP-U, which will not be explained here, but can be understood by referring to the description below, which can be executed as follows:
  • Step 0 The UPF determines session configuration information, which includes connection information required by the session or flow sent by the terminal device.
  • the source of the session configuration information is the same as the above-mentioned session configuration information, which may be configured or from other devices, but may also be default information (for example, the default application layer of the session/flow is the HTTP protocol), DNN/S-NSSAI ( For example, the network corresponding to DNN/S-NSSAI uses a specific application layer and/or network protocol), etc., and the connection information is determined according to the above information, which is not specifically limited in this application.
  • Step 1 The UE sends the first application message to the UPF, which is a message that complies with a certain application layer protocol (such as HTTP) and can contain relevant information defined by the application layer protocol (for example, the HTTP message contains URL information) .
  • the UE may send through a non-ip (non-IP) type session, or through a new type of session. If it is a new type of session, the session type is a session that supports the connection service provided by the network. It is assumed that the first application message is sent through a session, but it may also be sent through a stream in actual application, and this application does not specifically limit it here, and only uses a session as an example here.
  • Step 2 UPF determines to provide connection service for UE. For example, the UPF determines to provide the connection service according to the information in step 0, or the UPF determines to provide the connection service according to the session type, DNN/S-NSSAI, etc.
  • the UPF can determine the connection information required to provide the connection service according to the information in step 0, and analyze the first application message from step 1 to determine the type of application layer protocol, application layer address (that is, application address) information, etc.
  • Step 3 The UPF may determine the address information of the UE, and then request the address of the receiving end (for example, send a request to the DN), which is used to request the address of the receiving end corresponding to the first application message (for example, an IPv4 address).
  • the receiving end may be understood as a server or a receiving end device. The following refers to the receiving end and can be understood by referring to this.
  • Step 4 The UPF receives the address response from the receiving end of the DN, and obtains the address of the receiving end corresponding to the first application packet.
  • steps 3 and 4 do not need to be performed.
  • Step 5 UPF starts the application client and creates a TCP/IP connection with the receiving device.
  • Step 6 Create a TCP/IP connection corresponding to the application message between the UPF and the receiving end device.
  • the UPF can use its own address (such as an IPv4 address) to create a TCP/IP connection with the receiving end device, or use the address of the UE Create (the address assigned to the UE by the UPF or the control plane network element during the session creation process) and the TCP/IP connection with the receiving end device.
  • Step 7 UPF sends the first application packet received in step 1 to the receiving end device through the created TCP/IP connection, and then receives the application response from the receiving end device through the TCP/IP connection, and the application response is the receiving end device A response packet of the device to the received first application packet.
  • the UPF may not perform step 6, but directly execute the sending application to the receiving end device request, and then the UPF receives a response from the receiving device.
  • Step 8 The UPF sends an application response to the UE.
  • UPF directly obtains the content requested by UE through ICN definition or internal communication, and does not need to perform steps 3-7 (for ICN network, UPF is based on ICN request The name of the content, read or request the corresponding content, instead of having to create a connection; for scenarios such as UPF and application co-deployment, UPF can directly obtain relevant content on the co-deployed application according to the identification and other information in the application layer request, It is not necessary to obtain information through connection); or the UPF requests to obtain the content requested by the UE according to the application layer address requested by the UE (the UPF and the application can be accessed through the application layer address, and the above-mentioned ICN and co-deployment methods can be regarded as a specific one implementation), or for protocol types that do not need to be displayed to create a connection (such as UDP, when the UE needs to send a message, it can directly send the message
  • the UPF, external equipment, and UE are used as examples to illustrate, where the data sent between the UE and the UPF is realized by means of the RAN, and the RAN and the The data between UPFs is guaranteed by reliable transmission GTP-U, which will not be explained here, but can be understood by referring to the description below.
  • the external device includes the application client.
  • Figure 7 takes the external device deployed in the DN as an example to illustrate, and the executable as follows:
  • Step 0 UPF determines session configuration information, which is the same as Step 0 in FIG. 6 above and will not be repeated here.
  • Step 1 UPF determines to start the application server according to the session configuration information in step 0, and optionally creates a listening interface corresponding to the terminal/session/flow/application. Similar to the description corresponding to Figure 6, when the external device wants to send a message to the UPF, it does not need to display the connection creation process, but directly sends the request. Correspondingly, the UPF only needs to wait for the message to be received instead of completing it first. In order to describe the connection handshake process uniformly, in this application, waiting for receiving an application request is also regarded as creating a monitoring interface.
  • the UPF After the UPF creates a listening interface for the session, it can wait to receive the request message. When creating the listening interface, it can use the address of the UPF, or use the address corresponding to the terminal to create (the UPF or the network element of the control plane allocates for the terminal during the session creation process). address).
  • Step 2 The UPF reports the address information corresponding to the application to the address server.
  • the address server may be a control plane network element, or may be a device in the DN, and the DN is taken as an example in FIG. 7 for illustration.
  • the address information corresponding to the application includes the application address information and the address used by the listening interface created in step 1.
  • the application address can be obtained in step 0 or configured on the UPF (for example, DNN/S-NSSAI corresponds to a certain address).
  • Step 3 When the application client with the external device is ready to initiate an application request, it may optionally query the address server for the address of the terminal corresponding to the application address (that is, the address used when the UPF creates the listening interface in step 1). When the application client of the external device already has address information, or the application is accessible between the ICN network or the client and the UPF, the application client of the external device does not need to perform this step.
  • Step 4 When a connection needs to be established, the application client of the external device initiates a connection establishment request with the UPF according to the address information obtained in step 3.
  • Step 5 The UPF may report a session or flow creation request to a control plane network element (such as an SMF), thereby triggering a process of creating a flow at the control plane. It is also possible to create the stream before step 2. Optionally, when the UPF creates a listening interface in step 2, or detects connection creation in step 4, or receives an application request in step 6, this step may also be performed after step 2 or 6.
  • a control plane network element such as an SMF
  • Step 6 The application client of the external device sends an application request to the UPF.
  • the application client of the external device can send an application request through the connection created in step 4, or send an application request to the address obtained in step 3; or when the application can be directly accessed between the ICN network or the application client of the external device and the UPF, Send application requests directly.
  • Step 7 The UPF sends the application request through the session corresponding to the application/interface.
  • Step 8 The UPF receives the application response from the UE.
  • Step 9 The UPF directly sends the application response to the application client of the external device.
  • the terminal does not need to deploy a protocol stack for application message transmission, and the UPF provides the TCP or IP connection between the terminal and the external device, which can reduce the equipment overhead of the terminal and reduce the complexity of terminal processing.
  • the user plane network element can analyze the software application of the terminal device or obtain the connection information through session configuration information.
  • the software application of the terminal device It is a private application, and if the user plane network element cannot perceive application-related information, it cannot obtain connection information. Therefore, it can be executed with reference to the communication method provided in FIG. 8 , which can be illustrated through the interaction between the terminal, the user plane network element, and the receiving end. Executable as follows:
  • Step 801 the terminal determines indication information, and the indication information indicates the destination address of the receiving end of the application message.
  • the indication information may be sent by the terminal to the user plane network element through a protocol layer between the terminal and the user plane network element.
  • the protocol layer can be a Ctrl layer.
  • the application does not limit the name of the Ctrl layer and the position in the protocol stack.
  • the terminal can also support protocol stacks such as the TCP/IP network layer and the transport layer.
  • the Ctrl layer can be located in the wireless protocol stack, Arbitrary positions of the TCP/IP network layer, transport layer, and application layer.
  • the Ctrl layer is used for information exchange between UE and UPF as an example.
  • the Ctrl layer can be used between devices in the network Information interaction is performed, and the network device can modify its content when passing the Ctrl layer.
  • the UPF can send the Ctrl layer information to the equipment in the DN, and the UPF can also modify the content before sending it.
  • This method does not affect the functions of other existing protocol layers. , the present application does not specifically limit it here.
  • the indication information is sent through the protocol layer, and the indication information indicates the address of the receiving end of the application message.
  • the user plane network element can also obtain the connection information when it cannot perceive the application-related information.
  • Step 802 the terminal sends indication information to the user plane network element; correspondingly, the user plane network element receives the indication information.
  • Step 803 the terminal determines the application packet, the application packet includes application data, and does not include the source address and destination address of the application packet.
  • Step 804 the terminal sends the application packet to the user plane network element.
  • the user plane network element receives the application message.
  • the terminal can send the application message through the wireless communication protocol, and the terminal can also support the TCP/IP protocol stack, which is not specifically limited in this application.
  • Step 805 The user plane network element determines the destination address of the application message according to the indication information.
  • Step 806 The user plane network element determines the source address of the application packet according to the session configuration information; the session configuration information is used to indicate to provide connection services for the terminal. Reference may be made to the description at step 503 above, and the present application does not repeat it here.
  • Step 807 The user plane network element sends a first message to the receiving end, the first message includes application data, a source address of the application message, and a destination address of the application message.
  • the above indication information further includes: at least one of QoS requirement information corresponding to the terminal device, protocol information for transmitting application packets, and protocol type corresponding to the application packets.
  • the message protocol information may be HTTP. It should be noted that the indication information includes the QoS requirement information corresponding to the terminal equipment, the protocol information for transmitting application packets, and the protocol type corresponding to the application packets, so that the user plane network elements can clarify the connection information and improve data processing efficiency.
  • the user plane network element when the terminal communicates with other devices, the user plane network element can establish a communication connection of application packets with other devices through the session configuration information and indication information. In addition, in this way, the user plane network element cannot perceive the private application of the terminal In the case of relevant information, the destination address of the receiving end of the application packet can also be obtained through the indication information, which can reduce the occurrence of relying on the application address of the application packet to determine the destination address of the receiving end.
  • the indication information is specifically used to indicate: determine the destination address of the receiving end according to the connection identification carried in the application message; the terminal sends the application message to the user plane network element, and the application message includes the first connection identification , the connection corresponding to the first connection identifier is used to bear the application packet, correspondingly, the user plane network element receives the application packet from the terminal, and the application packet includes the first connection identifier; the user plane network element receives the application packet according to the The first connection identifier determines the destination address of the application message.
  • the connection identifier may be a connection identifier determined by the terminal itself, or it may be a connection identifier obtained by other methods.
  • the user plane network element can determine the destination address of the receiving end of the application message according to the connection identifier. This method can improve communication efficiency. Reduce the complexity of device handling.
  • the user plane network element sends connection identification information to the terminal, the connection identification information includes one or more connection identifications, and each connection identification is used to identify the connection created by the user plane network element; the first connection identification It is selected by the terminal from one or more connection identifiers, and correspondingly, the user plane network element receives the connection identifier information from the terminal.
  • the connection identifier of the application message is allocated by the user plane network element. After the user plane network element allocates the connection identifier, the terminal carries the selected connection identifier when sending the application data, and the user plane network element can determine the connection information. Data processing efficiency can be improved.
  • Figure 9 shows the flow of user plane network elements determining connection information based on indication information, where the UE may include an application, a Ctrl processing module, and a wireless sending module, where the data sent between the UE and the UPF is implemented by means of the RAN, and the RAN and the UPF
  • the data in between is guaranteed by reliable sending of GTP-U, which will not be explained here, but can be understood by referring to the description below, which can be executed as follows:
  • Step 1 During session (or flow) creation (or modification), the control plane network element (SMF) instructs UPF to provide connection service (or support Ctrl protocol) through session creation (or modification) information. Or the UPF determines that it needs to provide the connection service (or support the Ctrl protocol) for the user according to the session type, DNN/S-NSSAI and other information, then the UPF determines that the connection service can be provided.
  • SMF control plane network element
  • Step 2 The UE's application requests to create an interface.
  • the existing TCP/IP protocol stack interface can be used to request the creation of the interface, which is not limited in this application.
  • Step 3 The Ctrl processing module creates an interface for the application and returns the interface identifier.
  • Step 4 When the UE acts as an application client, it requests to establish a connection.
  • the UE is used as an example for illustration. If the UE is used as a server, it requests to monitor messages, which is not specifically described in this embodiment.
  • Step 5 The Ctrl processing module sends instruction information through the Ctrl layer, such as sending a control command and requesting to create a connection. This step can also be executed together when the terminal sends an application message (that is, advance steps 9 and 10 to step 4 and then execute, and merge steps 5, 11, and merge steps 8, 13).
  • the instruction information can include application layer address, server address, and information related to the sending protocol (such as protocol type, port number, etc.), which is used to provide the information required by UPF to provide connection services; it can also include the corresponding QoS requirements of the application (such as bandwidth , message period/burst traffic and other information), whether to support reliable transmission, etc., for UPF and wireless networks, and optionally including DN networks to provide requested QoS guarantees.
  • the traditional TCP/IP protocol stack interface is used between the application and the Ctrl processing module, and then the Ctrl processing module encapsulates the TCP/IP protocol stack interface and related parameters called by the application in the Ctrl layer, similar to the TCP/IP protocol stack interface implemented on UPF.
  • IP protocol stack, and the protocol stack service invoked by the application is implemented on UPF. This application does not limit how to implement the Ctrl module and the information format of the Ctrl layer.
  • Step 6 The UPF determines the address of the receiving end of the application message according to the indication information provided by the Ctrl layer.
  • the UPF records the correspondence between connections and sessions on the network side, and users subsequently forward packets between connections and sessions.
  • the UPF assigns a connection identifier to the session, and the identifier corresponds to the connection.
  • the identifier is used to indicate the corresponding connection.
  • Step 7 The UPF completes the connection creation process with the receiver device.
  • Step 8 The UPF feeds back the connection status through the Ctrl layer or executes the results indicated by the Ctrl. Optionally feedback the connection ID assigned in step 6.
  • Step 9 The Ctrl processing module feeds back the interface creation result to the application according to the result of step 8.
  • Step 10 When the application needs to send data, send the data through the Ctrl processing module.
  • the application can use the interface of the traditional TCP/IP protocol stack to send data, and the Ctrl module is adapted based on the processing logic of the interface.
  • Step 11 The Ctrl processing module forwards the data from the application, and may include the connection identifier fed back in step 8 when sending.
  • Step 12 The UPF sends the application data to the receiving end device through the application message or the connection corresponding to the connection identifier.
  • Step 13 The receiver can feed back the execution result to the UPF.
  • Step 14 the UPF sends the execution result of step 13 to the session corresponding to the connection through the Ctrl layer, and when the UPF receives the downlink message from the receiving end device, sends the received message to the terminal through the session corresponding to the connection text, where the execution result of step 13 can be sent together with the downlink message.
  • the connection identifier can optionally be carried at the Ctrl layer.
  • Step 15 The Ctrl processing module feeds back the execution result of step 11 to the application.
  • This step can be to determine the execution result based on the information fed back in step 13 (for example, for an application that requires reliable sending, the Ctrl processing module can determine whether the message is sent successfully based on the information fed back in step 13), or after executing step 11 or 12 Feedback the execution result (for example, for applications that do not require reliable sending, as long as the message is sent out, the sending is considered successful).
  • UPF enables users to provide connection services, reliable transmission, QoS guarantee, etc., and obtains relevant information required to provide the above services by receiving configuration.
  • This embodiment provides a specific enabling process For the process of obtaining related configurations, refer to Figure 10, and perform as follows:
  • steps 1, 2, and 3 are optional. When performing relevant configurations on UPF, part or all of steps 1, 2, and 3 can be executed, so that SMF obtains subsequent configurations from a single step or multiple steps to UPF related information.
  • Step 1 In the session creation request sent by the UE, optionally instruct the network to provide connection services (for example, use a special session type, or use the displayed indication information, or the network corresponding to the indicated DNN/S-NSSAI and other information needs to provide connection service, etc.), optionally indicating connection-related information (session configuration information), and optionally indicating the use of reliable sending and/or Ctrl protocol layers, etc. (the way of indicating is similar to indicating that connection services are provided).
  • connection services for example, use a special session type, or use the displayed indication information, or the network corresponding to the indicated DNN/S-NSSAI and other information needs to provide connection service, etc.
  • connection-related information session configuration information
  • Step 2 The AF updates the subscription data in the UDM, or the AF provides to the PCF (it can be sent by the AF to a network element such as the NEF, and then sent to the PCF, or the AF directly sends to the PCF) part or all of the information described in step 1.
  • Step 3 The SMF obtains part or all of the information described in Step 1 from the PCF or UDM. It is also possible not to perform step 2, but the AF provides the information to the SMF (the AF sends it directly to the SMF, or the AF sends it to a network element such as the NEF, and then sends it to the SMF).
  • Step 4 SMF provides connection information to UPF through N4 session creation (or modification) request.
  • Step 5 During session creation or stream creation, or when updating URSP information, SMF provides some or all of the information described in step 1 to the terminal (for example, through steps 2 and 3, AF updates application-related information, and then passes The URSP is sent to the UE to update the configuration on the UE), which is used for the terminal to execute the relevant processes in Figure 5-9 based on the configuration information, or to provide relevant information to the network through step 1 in Figure 6 when creating a session later.
  • SMF provides some or all of the information described in step 1 to the terminal (for example, through steps 2 and 3, AF updates application-related information, and then passes The URSP is sent to the UE to update the configuration on the UE), which is used for the terminal to execute the relevant processes in Figure 5-9 based on the configuration information, or to provide relevant information to the network through step 1 in Figure 6 when creating a session later.
  • Step 6 Execute the process shown in Figure 6, Figure 7 or Figure 9 above, or create a connection according to the connection information in Step 4.
  • the data sent between the UE and the UPF in Figures 5 to 10 above is realized by means of the RAN.
  • the user plane network element can receive the forwarded message from the radio access network device (RAN), and the forwarded message is sent by the terminal to the wireless access network.
  • the forwarded packets include application packets.
  • the data between RAN and UPF is guaranteed by reliable transmission of GTP-U. Next, how to ensure the reliable transmission of data is introduced in detail.
  • the application packets carried in the session between user plane network elements and terminal equipment are forwarded by RAN.
  • the user plane network element receives the forwarded message from the RAN, and the forwarded message includes: an application message and a serial number of the application message sent; the user plane network element feeds back the serial number of the received application message to the RAN.
  • the forwarded message includes: an application message and a serial number of the application message sent; the user plane network element feeds back the serial number of the received application message to the RAN.
  • it can be divided into two modes: RAN transparent transmission and forwarding.
  • RAN forwarding please refer to Figure 11A for illustration. Take the upstream data flow as an example to illustrate, and the specific implementation is as follows:
  • Step 1 The UE sends the uplink message, and the reliable transmission is guaranteed through the air interface mechanism between the UE and the RAN.
  • Step 2 When the RAN sends a message to the UPF, the GTP-U packet header contains the sequence number of the message to be sent.
  • the number of the sequence number can be flow granularity (that is, each flow is independently numbered sequentially), or GTP -U tunnel granularity (that is, the independent sequence number of each GTP-U tunnel, which can be considered to be equivalent to the session granularity sequence number).
  • GTP-U is carried on a reliable transmission protocol (such as TCP, QUIC, etc.
  • the prior art is carried on UDP), and based on this, reliable transmission at the device granularity between RAN and UPF can also be realized.
  • Step 3 The UPF feeds back the sequence number of the received message to the RAN, or feeds back the sequence number of the message not received within the timeout when the message is not received within the timeout.
  • Step 4 When packet loss occurs in step 2, the RAN determines the packet loss and the sequence number of the packet loss according to the feedback in step 3, and retransmits.
  • Step 1 Before the UE sends the upstream flow (for example, during or after the flow is created, or during the connection establishment process, etc.), the UPF provides (that is, the UPF distribution identifier) the sending identifier corresponding to the session to the UE, and the identifier can be used at the Ctrl layer
  • the connection ID can also be an independent ID for reliable sending. This identifier can be used to subsequently identify a reliably sent stream (or it can be understood that the subsequent sequence number is at the granularity of sending identification). It may also be that the UE assigns the sending identifier, for example, the UE sends it to the UPF, or the UE sends the message together with the message when it starts to send the message.
  • Step 2 The UE sends an uplink message, which contains the message sequence number of the QoS session sending identifier granularity, and the sequence number can be in an independent protocol layer (this application uses the RT protocol layer as an example for illustration, but does not limit the specific protocol layer name), or in the Ctrl layer, or in other packet headers. If there is a sending ID, the message can also contain the sending ID.
  • the sending ID is not limited to be at the same protocol layer as the message serial number. For example, the sending serial number uses the connection ID of the Ctrl layer, while the serial number is placed in the RT protocol. In the layer, there is no limitation here.
  • Step 3 The UPF feeds back the sequence number of the received packet to the UE, or feeds back the sequence number of the lost packet when the packet is not received within a timeout.
  • the fed back message sequence number can be sent together with the downlink message.
  • Step 4 When packet loss occurs in step 2, the terminal determines the packet loss and the sequence number of the packet loss according to the feedback in step 3, and retransmits.
  • Figure 12 illustrate how to send and retransmit packets between UPF and RAN.
  • RAN sends a packet to UPF, and the corresponding UPF sends an acknowledgment of the received packet to RAN.
  • GTP-U Take reliable sending as an example:
  • a mechanism for packet retransmission control can be introduced into the GTP-U packet header.
  • the ACK sequence number is introduced into the GTP-U packet header to realize packet receipt confirmation and reuse
  • the sequence number in the GTP-U packet header is used as the sequence number of the sent message; if selective retransmission is supported, the S-ACK sequence number can be introduced, and S-ACK and ACK are used together to confirm the receipt of a message with a sequence number in a range
  • S-ACK represents the start sequence number of the interval
  • ACK represents the last sequence number of the interval; if selective retransmission is not supported, the retransmission of the window mechanism can be realized through the sequence number and ACK (not described in detail here).
  • the receiving end of the confirmation message contains the ACK sequence number in the received message
  • the S-ACK sequence number is not included, then the messages before the ACK sequence number have been received, and the cache can be deleted ( As shown in Figure 12 above, when RAN receives packets 1 and 2, it returns ACK as sequence number 2); if the sequence number of S-ACK is included, the frame between S-ACK and ACK can be deleted (as shown in the figure above, RAN receives message 4 , 5, the returned S-ACK is 4, and the ACK is 5), and if there are serial numbers that have not been confirmed after timeout (such as message 3 in the above figure), retransmit the messages corresponding to these serial numbers.
  • This application can support retransmission control at a larger granularity, for example, the related numbers can be uniformly numbered at the device granularity, so as to realize the retransmission control at the device granularity.
  • the ACK can be sent together with the data message, and when no data message is sent, the ACK information can be sent through a separate message. At this time, the sequence number in the message sending the ACK also needs to be incremented, but When the peer end receives this kind of ACK message, it does not send an ACK response separately to avoid sending ACKs in a loop.
  • each device may include a corresponding hardware structure and/or software module for performing each function.
  • the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.
  • FIG. 13 shows a possible exemplary block diagram of a communication device involved in the embodiment of the present application.
  • the communication device may include: a processing unit 1301 and a transceiver unit 1302 .
  • the processing unit 1301 is used to control and manage the actions of the communication device.
  • the transceiver unit 1302 is used to support communication between the communication device and other devices.
  • the transceiver unit 1302 may include a receiving unit and/or a sending unit, configured to perform receiving and sending operations respectively.
  • the communication device may further include a storage unit, configured to store program codes and/or data of the communication device.
  • the transceiver unit may be called an input-output unit, a communication unit, etc., and the transceiver unit may be a transceiver; the processing unit may be a processor.
  • the communication device is a module (such as a chip) in a communication device
  • the transceiver unit may be an input-output interface, an input-output circuit, or an input-output pin, etc., and may also be called an interface, a communication interface, or an interface circuit;
  • the processing unit may be a processor, a processing circuit, or a logic circuit.
  • the device may be the above-mentioned terminal, user plane network element, and the like.
  • the transceiver unit 1302 can be used to receive an application packet from a terminal, the application packet includes application data and the application address of the receiving end of the application packet; the application packet is carried in a session or flow; the processing unit 1301 can be used to Determine the source address of the application message according to the session configuration information; the session configuration information is used to indicate the provision of connection services for the terminal; determine the destination address of the application message according to the application address; the transceiver unit 1302 can also be used to send the first message to the receiving end, The first packet includes application data, a source address of the application packet, and a destination address of the application packet.
  • the processing unit 1301 may be configured to determine the source address of the session according to the session configuration information; and use the source address of the session as the source address of the application packet.
  • the transceiver unit 1302 can be used to send a connection creation request, the creation request includes the application address; the creation request is used to request the destination address corresponding to the application address; and receive the response information of the connection creation request, the response information includes the application address the corresponding destination address.
  • the transceiver unit 1302 may be configured to receive a forwarded message from the wireless access network device, the forwarded message is sent by the terminal to the wireless access network device, and the forwarded message includes an application message.
  • the forwarded message further includes a serial number of the application message; the transceiver unit 1302 may be configured to feed back the received serial number of the application message to the access network device.
  • the session configuration information includes packet protocol information; the packet protocol information is: packet protocol information for transmitting an application packet, and/or, a packet protocol type corresponding to the application packet.
  • the message protocol information is HTTP.
  • the source address is an address allocated to the terminal by a user plane network element.
  • the processing unit 1301 can be used to determine the application message, the application message includes the application data and the application address of the receiving end of the application message, and does not include the source address of the application message; the transceiver unit 1302 can be used to send the user The plane NE sends application packets.
  • the transceiver unit 1302 may be configured to receive indication information from the terminal, the indication information indicating the destination address of the receiving end of the application message; receive the application message from the terminal, the application message includes application data; the processing unit 1301 may be Determine the destination address of the application message according to the indication information; determine the source address of the application message according to the session configuration information; the session configuration information is used to indicate that the terminal is provided with a connection service; the transceiver unit 1302 can also be used to send the first message to the receiving end , the first packet includes application data, a source address of the application packet, and a destination address of the application packet.
  • the indication information is sent by the terminal to the user plane network element through a protocol layer between the terminal and the user plane network element.
  • the processing unit 1301 may be configured to determine the source address of the session carried by the application packet according to the session configuration information; and use the source address of the session carried by the application packet as the source address of the application packet.
  • the indication information is specifically used to indicate: determine the destination address of the receiving end according to the connection identifier carried in the application message; the transceiver unit 1302 is used to receive the application message from the terminal, and the application message includes the first The connection identifier, the connection corresponding to the first connection identifier is used to carry the application message; the processing unit 1301 is configured to determine the destination address of the application message according to the first connection identifier included in the application message.
  • the transceiver unit 1302 is configured to send connection identification information to the terminal, where the connection identification information includes one or more connection identifications, and each connection identification is used to identify a connection created by a user plane network element; the first connection The ID is selected by the terminal from one or more connection IDs.
  • the transceiver unit 1302 may be configured to receive a forwarded message from the wireless access network device, the forwarded message is sent by the terminal to the wireless access network device, and the forwarded message includes an application message.
  • the forwarded message further includes a serial number of the application message; the transceiver unit 1302 may be configured to feed back the received serial number of the application message to the access network device.
  • the indication information includes: QoS requirement information corresponding to the terminal, message protocol information for transmitting the application message, and message protocol type corresponding to the application message.
  • the message protocol information is HTTP.
  • the processing unit 1301 can be used to determine the indication information, and the indication information indicates the destination address of the receiving end of the application message; the transceiver unit 1302 can be used to send the indication information to the user plane network element; the processing unit 1301 can be used to determine the application message The application message includes application data, and does not include the source address and destination address of the application message; the transceiver unit 1302 can be used to send the application message to the user plane network element, and the application message includes application data, and does not include the application message source and destination addresses.
  • the indication information is sent by the terminal to the user plane network element through a protocol layer between the terminal and the user plane network element.
  • the indication information is specifically used to indicate: the user plane network element determines the destination address of the receiving end according to the connection identifier carried in the application message; the transceiver unit 1302 is used to send the application message to the user plane network element,
  • the application packet includes a first connection identifier, and the connection corresponding to the first connection identifier is used to bear the application packet.
  • the transceiver unit 1302 is configured to receive connection identification information from a user plane network element, where the connection identification information includes one or more connection identifications, and each connection identification is used to identify a connection created by a user plane network element ;
  • the first connection identifier is selected by the terminal from one or more connection identifiers.
  • the communication device 1400 may be a chip or a chip system.
  • the system-on-a-chip may be composed of chips, or may include chips and other discrete devices.
  • the communication device 1400 may include at least one processor 1410, and the communication device 1400 may further include at least one memory 1420 for storing computer programs, program instructions and/or data.
  • the memory 1420 is coupled to the processor 1410 .
  • the coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1410 may operate in cooperation with the memory 1420 .
  • Processor 1410 may execute computer programs stored in memory 1420 .
  • the at least one memory 1420 may also be integrated with the processor 1410 .
  • the communication device 1400 may or may not include the transceiver 1430 , which is indicated by a dashed box in the figure, and the communication device 1400 may perform information exchange with other devices through the transceiver 1430 .
  • the transceiver 1430 may be a circuit, a bus, a transceiver or any other device that can be used for information exchange.
  • the communication apparatus 1400 may be applied to the aforementioned terminal equipment, or may be the aforementioned user plane network element.
  • the memory 1420 stores necessary computer programs, program instructions and/or data for implementing functions of the user plane network element in any of the foregoing embodiments.
  • the processor 1410 may execute the computer program stored in the memory 1420 to complete the method in any of the foregoing embodiments.
  • a specific connection medium among the transceiver 1430, the processor 1410, and the memory 1420 is not limited.
  • the memory 1420, the processor 1410, and the transceiver 1430 are connected through a bus.
  • the bus is represented by a thick line in FIG. 14, and the connection mode between other components is only for schematic illustration. It is not limited.
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 14 , but it does not mean that there is only one bus or one type of bus.
  • the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or Execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application.
  • a general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the methods disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.
  • the memory may be a non-volatile memory, such as a hard disk (hard disk drive, HDD) or a solid-state drive (solid-state drive, SSD), etc., and may also be a volatile memory (volatile memory), such as Random-access memory (RAM).
  • the memory may also be, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • the memory in the embodiments of the present application may also be a circuit or any other device capable of implementing a storage function, for storing computer programs, program instructions and/or data.
  • the embodiment of the present application also provides another communication device 1500, including: an interface circuit 1510 and a logic circuit 1520; the interface circuit 1510 can be understood as an input and output interface, and can be used to implement The schematic transceiver unit or the same operation steps as the transceiver shown in FIG. 14 will not be repeated in this application.
  • the logic circuit 1520 can be used to run the code instructions to execute the method in any of the above-mentioned embodiments, and can be understood as the processing unit in FIG. 13 or the processor in FIG. 14, which can realize the same function as the processing unit or processor, This application will not go into details here.
  • the embodiments of the present application further provide a readable storage medium, the readable storage medium stores instructions, and when the instructions are executed, the communication method in any of the above embodiments is executed.
  • the readable storage medium may include various mediums capable of storing program codes such as U disk, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk.
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising the instruction device, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

Landscapes

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

Abstract

本申请提供一种通信方法及装置，用户面网元接收来自终端的应用报文，应用报文包括应用数据和应用报文的接收端的应用地址；应用报文承载于会话或流中；用户面网元根据会话配置信息确定应用报文的源地址；会话配置信息用于指示为终端提供连接服务；用户面网元根据应用地址确定应用报文的目的地址；用户面网元发送第一报文至接收端，第一报文包括应用数据、应用报文的源地址以及应用报文的目的地址。本申请终端与其他设备通信时，无需在终端中部署应用报文传输的协议栈，终端将报文发送至用户面网元时，无需携带连接信息，通过用户面网元中的会话配置信息以及应用报文的接收端的应用地址即可与其他设备建立通信连接，该方式降低了数据处理的复杂度。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2021年12月24日提交中国专利局、申请号为202111599951.1、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
为了应对无线宽带技术的挑战，保持第三代合作伙伴计划(3rd generation partnership project，3GPP)网络的领先优势，3GPP标准组在2016年底制定了第五代(5th generation，5G)网络架构。该架构支持3GPP标准组定义的无线技术(如长期演进(long term evolution，LTE)，5G无线接入网(radio access network，RAN)等)，固定网络等接入方式接入核心网络。
终端设备在通信时，通常可通过传输控制协议/网络协议(transmission control protocol/internet protocol，TCP/IP)协议栈提供的接口访问网络。当终端设备为无线网络终端时，终端中的应用调用协议栈(例如图1中的TCP/IP协议栈)提供的接口，进而协议栈和网络侧的设备(例如部署在用户面功能(user plane function，UPF)远端的设备，图1中未标示)交互报文。终端设备上的协议栈的报文，可通过无线模块(图1中的用户设备(user equipment，UE))发送，也可通过无线模块接收报文。终端发送的报文可通过UPF向网络侧设备发送，也可通过UPF接收来自网络侧设备的报文。也即终端与网络侧通信时，均需要通过终端搭载协议栈来实现，但是协议栈机制部署复杂。
发明内容
本申请提供一种通信方法及装置，以降低通信复杂度。
第一方面，本申请提供一种通信方法，该方法可通过用户面网元，如UPF来执行，也可通过终端，如UE、车载设备等来执行，还可通过其他用户面网元来执行，本申请在此不具体限定，在此仅以终端与用户面网元的交互为例来说明。可执行如下：
终端确定应用报文，应用报文包括应用数据和应用报文的接收端的应用地址，且不包括应用报文的源地址；终端向用户面网元发送应用报文。相应地用户面网元接收来自终端的应用报文，应用报文包括应用数据和应用报文的接收端的应用地址；应用报文承载于会话或流中；用户面网元根据会话配置信息确定应用报文的源地址；会话配置信息用于指示为终端提供连接服务；用户面网元根据应用地址确定应用报文的目的地址；用户面网元发送第一报文至接收端，第一报文包括应用数据、应用报文的源地址以及应用报文的目的地址。
本申请中，终端与其他设备通信时，无需在终端中部署应用报文传输的协议栈，终端可将应用报文直接通过无线通信协议发送至用户面网元，从而无需在终端至无线接入设备 之间建立传输层以上层的连接，用户面网元通过会话配置信息以及应用报文的接收端的应用地址即可与其他设备建立应用报文的传输层以上层的通信连接，该方式可降低终端进行应用程序的报文传输时需要构建传输层以上层的协议栈的复杂度。
在一种可选的方式中，用户面网元可根据会话配置信息确定会话的源地址；用户面网元可将会话的源地址作为应用报文的源地址。需要说明的是，终端部署应用报文传输的协议栈的情况下，在发送报文时需要携带应用报文的源地址和目的地址，比如应用报文的源IP地址和目的IP地址等，但本申请中，终端未部署应用报文传输的协议栈，在终端设备在未向用户面网元传输应用报文的源地址的情况下，用户面网元可根据会话配置信息确定应用报文的源地址，通过该方式可以降低设备处理复杂度。
在一种可选的方式中，用户面网元可发送连接创建请求，创建请求包括应用地址；创建请求用于请求应用地址对应的目的地址；用户面网元接收连接创建请求的响应信息，响应信息包括应用地址对应的目的地址。需要说明的是，用户面网元通过连接创建请求确定应用报文的应用地址对应的目的地址，而非直接通过应用报文携带目的地址，从而，本申请可提供一种终端设备不部署应用报文传输的协议栈的情况下，获取应用报文的目的地址的方案。
在一种可选的方式中，用户面网元接收来自终端的应用报文时，可以有很多种实现方式，示例性的，比如可以是接收无线接入网设备的转发报文，转发报文为终端发送给无线接入网设备的，转发报文包括应用报文。通过无线接入网设备转发报文可以保证应用报文传输的可靠性。
在一种可选的方式中，转发报文还可以包括应用报文的序列号；用户面网元还可以向接入网设备反馈接收到的应用报文的序列号。需要说明的是，在实际应用时，由于通信环境的状况不同(如：信道干扰、噪声的存在)，应用报文可能不会被接收，因此应用报文中包括应用报文的序列号，可以确定知晓哪些报文被成功接收，哪些报文未被成功接收。
示例性的，会话配置信息可以但不限于包括报文协议信息；报文协议信息为：传输应用报文的报文协议信息，和/或，应用报文对应的报文协议类型等，本申请不做具体限定。其中，报文协议信息可为超文本传输协议(hyper text transfer protocol，HTTP)。
在一种可选的方式中，源地址可以为用户面网元为终端分配的地址。
第二方面，本申请提供一种通信方法，该方法可通过用户面网元，如UPF来执行，也可通过终端来执行，本申请在此不具体限定，在此仅以终端与用户面网元的交互为例来说明。可执行如下：
终端确定指示信息，指示信息指示应用报文的接收端的目的地址；终端发送指示信息至用户面网元；终端确定应用报文，应用报文包括应用数据，且不包括应用报文的源地址和目的地址，终端发送应用报文至用户面网元。相应地，用户面网元接收来自终端的指示信息；用户面网元接收来自终端的应用报文；用户面网元根据指示信息确定应用报文的目的地址；用户面网元根据会话配置信息确定应用报文的源地址；会话配置信息用于指示为终端提供连接服务；用户面网元发送第一报文至接收端，第一报文包括应用数据、应用报文的源地址以及应用报文的目的地址。
本申请中，终端与其他设备通信时，终端可将应用报文直接通过无线通信协议发送至用户面网元，用户面网元通过会话配置信息以及指示信息即可与其他设备建立应用报文的通信连接，通过该方式用户面网元在无法感知应用相关信息的情况下，也可以获得连接信 息。
在一种可选的方式中，指示信息可以是终端通过与用户面网元之间的协议层发送给用户面网元的。该协议层可以为Ctrl层，本申请不限定Ctrl层的名称、以及在协议栈的位置等，例如终端也可以支持TCP/IP网络层和传输层等协议栈，Ctrl层可以位于无线协议栈、TCP/IP网络层、传输层、以及应用层等的任意位置，本实施例中，以Ctrl层用于UE和UPF之间进行信息交互为例进行说明，Ctrl层可以用于网络中设备之间进行信息交互，并且网络设备在传递Ctrl层时可以对其内容进行修改。例如UE向UPF发送Ctrl信息(也即指示信息)后，UPF可以向DN中的设备发送Ctrl层信息，并且UPF在发送之前还可以对内容进行修改，该方式不影响其他已有协议层的功能，本申请在此不具体限定，通过协议层发送指示信息，通过指示信息指示应用报文的接收端的地址，用户面网元在无法感知应用相关信息的情况下，也可以获得连接信息。
在一种可选的方式中，用户面网元可根据会话配置信息确定应用报文承载的会话的源地址；用户面网元将应用报文承载的会话的源地址作为应用报文的源地址。本申请中，在终端设备未向用户面网元传输应用报文的源地址的情况下，用户面网元可根据会话配置信息确定应用报文的源地址，通过该方式可以降低设备处理复杂度。
在一种可选的方式中，指示信息可具体用于指示：根据应用报文中携带的连接标识确定接收端的目的地址；终端可向用户面网元发送应用报文，应用报文包括第一连接标识，第一连接标识对应的连接用于承载应用报文，相应地，用户面网元可接收来自终端的应用报文，应用报文包括第一连接标识；用户面网元根据应用报文中包括的第一连接标识，确定应用报文的目的地址。
本申请中，该连接标识可能是终端自行确定的连接标识，也可能是通过其他方式获取的连接标识，用户面网元根据该连接标识可以确定应用报文的接收端的目的地址，通过该方式可以提高通信效率，降低设备处理的复杂度。
在一种可选的方式中，用户面网元可向终端发送连接标识信息，连接标识信息包括一个或多个连接标识，各连接标识分别用于标识用户面网元创建的连接；第一连接标识是终端从一个或多个连接标识中选择的，相应地，用户面网元可接收用户面网元的连接标识信息。
本申请中，应用报文的连接标识是用户面网元分配的，用户面网元分配连接标识后，终端在发应用数据时，携带上选择的连接标识，用户面网元即可确定连接信息，可提高数据处理效率。
在一种可选的方式中，用户面网元可接收来自终端的应用报文时，可以有很多种实现方式，示例性的，比如可以是接收无线接入网设备的转发报文，转发报文为终端发送给无线接入网设备的，转发报文包括应用报文。通过无线接入网设备转发报文可以保证应用报文传输的可靠性。
在一种可选的方式中，转发报文还可以包括应用报文的序列号；用户面网元还可以向接入网设备反馈接收到的应用报文的序列号。需要说明的是，在实际应用时，由于通信环境的状况不同(如：信道干扰、噪声的存在)，应用报文可能不会被接收，因此应用报文中包括应用报文的序列号，可以确定知晓哪些报文被成功接收，哪些报文未被成功接收。
示例性的，指示信息可以但不限于包括：终端对应的服务质量(quality of service，QoS)需求信息、传输应用报文的报文协议信息、应用报文对应的报文协议类型等。
在一种可选的方式中，报文协议信息可以为HTTP协议。
第三方面，本申请实施例提供一种通信装置，所述通信装置可以为用户面网元(比如第一方面中的用户面网元、第二方面中的用户面网元)或者设置在用户面网元内部的芯片，还可以为终端(比如第一方面中的终端、第二方面中的终端)或者设置在终端内部的芯片。所述通信装置具备实现上述第一方面至第二方面中任一方面的功能，比如，所述通信装置包括执行上述第一方面至第二方面中任一方面涉及步骤所对应的模块或单元或手段(means)，所述功能或单元或手段可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述通信装置包括处理单元、收发单元，其中，收发单元可以用于收发信号，以实现该通信装置和其它装置之间的通信，比如，收发单元用于接收来自终端设备的配置信息；处理单元可以用于执行该通信装置的一些内部操作。所述收发单元可以称为输入输出单元、通信单元等，所述收发单元可以是收发器；所述处理单元可以是处理器。当通信装置是通信设备中的模块(如，芯片)时，所述收发单元可以是输入输出接口、输入输出电路或输入输出管脚等，也可以称为接口、通信接口或接口电路等；所述处理单元可以是处理器、处理电路或逻辑电路等。
在又一种可能的设计中，所述通信装置包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器执行程序指令，以完成上述第一方面至第二方面中任意可能的设计或实现方式中的方法。其中，所述通信装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合，所述存储器可以保存实现上述第一方面至第二方面中任一方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第一方面至第二方面任意可能的设计或实现方式中的方法。
在又一种可能的设计中，所述通信装置包括处理器，处理器可以用于与存储器耦合。所述存储器可以保存实现上述第一方面至第二方面中任一方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第一方面至第二方面任意可能的设计或实现方式中的方法。
在又一种可能的设计中，所述通信装置包括处理器和接口电路，其中，处理器用于通过所述接口电路与其它装置通信，并执行上述第一方面至第二方面任意可能的设计或实现方式中的方法。
可以理解地，上述第三方面中，处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。此外，以上处理器可以为一个或多个，存储器可以为一个或多个。存储器可以与处理器集成在一起，或者存储器与处理器分离设置。在具体实现过程中，存储器可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
第四方面，本申请实施例提供一种通信系统，该通信系统包括上述第一方面到第二方面中的用户面网元以及终端。
第五方面，本申请提供了一种芯片系统，该芯片系统包括处理器，还可以包括存储器， 用于实现上述第一方面到第二方面中任一种可能的设计中所述的方法。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第六方面，本申请还提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机可读指令，当计算机可读指令在计算机上运行时，以使得计算机执行如第一方面到第二方面中任一种可能的设计中的方法。
第七方面，本申请提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面到第二方面的各实施例的方法。
上述第三方面至第七方面可以达到的技术效果，请参照上述第一方面中或第二方面中相应可能设计方案可以达到的技术效果说明，本申请这里不再重复赘述。
附图说明
图1示出了一种终端设备部署协议栈的架构示意图；
图2示出了本申请实施例提供的一种移动通信网络架构的示意图；
图3A示出了一种协议栈的结构示意图；
图3B示出了另一种协议栈的结构示意图；
图4示出了一种通信连接流程的示意图；
图5示出了本申请实施例提供的一种通信方法的流程示意图；
图6示出了本申请实施提供的一种通信方法的流程示意图；
图7示出了本申请实施提供的一种通信方法的流程示意图；
图8示出了本申请实施提供的一种通信方法的流程示意图；
图9示出了本申请实施提供的一种通信方法的流程示意图；
图10示出了本申请实施提供的一种通信方法的流程示意图；
图11A示出了本申请实施提供的一种通信方法的流程示意图；
图11B示出了本申请实施提供的一种通信方法的流程示意图；
图12示出了本申请实施提供的一种通信方法的流程示意图；
图13示出了本申请实施例提供的通信装置的结构示意图；
图14示出了本申请实施例提供的通信装置的结构示意图；
图15示出了本申请实施例提供的通信装置的结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。因此装置与方法的实施可以相互参见，重复之处不再赘述。
图2示例性示出一种移动通信网络架构的示意图，该网络架构中包括终端设备、接入网设备、接入和移动管理功能、会话管理功能、用户面功能、策略控制功能、网络切片选择功能、网络切片特定身份验证和授权功能、网络仓库功能、网络数据分析功能、统一数据管理功能、统一数据存储功能、认证服务功能、网络能力开放功能、终端无线能力管理功能、绑定支撑功能、应用功能，以及连接运营商网络的数据网络(data network，DN)。 终端设备可通过当前位置的接入节点来接入无线网络。终端设备可通过接入网设备、用户面功能向数据网络发送业务数据，以及从数据网络接收业务数据。
接入和移动管理功能，主要用于移动网络中的终端设备的附着、移动性管理、跟踪区更新流程等。在5G通信系统中，接入和移动管理功能可以是接入与移动性管理功能(access and mobility management function，AMF)，在未来的通信系统(如6G通信系统)中，接入和移动管理功能可以仍是AMF，或者也可以具有其它名称，本申请并不限定。
会话管理功能，主要用于移动网络中的会话管理，如会话建立、修改、释放。具体功能如为终端设备分配互联网协议地址、选择提供报文转发功能的用户面功能等。在5G通信系统中，会话管理功能可以是会话管理功能(session management function，SMF)，在未来的通信系统(如6G通信系统)中，会话管理功能可以仍是SMF，或者也可以具有其它名称，本申请并不限定。
用户面功能，主要用于对用户报文进行处理，如转发和计费等。在5G通信系统中，用户面功能可以是UPF，在未来的通信系统(如6G通信系统)中，用户面功能可以仍是UPF，或者也可以具有其它名称，本申请并不限定。
策略控制功能，包含策略控制功能、计费策略控制功能、QoS控制等。在5G通信系统中，策略控制功能可以是策略控制功能(policy control function，PCF)，在未来的通信系统(如6G通信系统)中，策略控制功能可以仍是PCF，或者也可以具有其它名称，本申请并不限定。
网络切片选择功能，主要用于为终端设备的业务选择合适的网络切片。在5G通信系统中，网络切片选择功能可以是网络切片选择功能(network slice selection function，NSSF)，在未来的通信系统(如6G通信系统)中，网络切片选择功能可以仍是NSSF，或者也可以具有其它名称，本申请并不限定。
网络切片特定身份验证和授权功能(network slice-specific authentication and authorization function，NSSAAF)主要用于针对终端设备接入特定网络切片的验证和授权。
网络仓库功能，主要用于提供网络功能或网络功能所提供服务的注册和发现。在5G通信系统中，网络仓库功能可以是网络仓库功能(network repository function，NRF)，在未来的通信系统(如6G通信系统)中，网络仓库功能可以仍是NRF，或者也可以具有其它名称，本申请并不限定。
网络数据分析功能，可以从各个网络功能，例如策略控制功能、会话管理功能、用户面功能、接入管理功能、应用功能(通过网络能力开放功能)收集数据，并进行分析和预测。在5G通信系统中，网络数据分析功能可以是网络数据分析功能(network data analytics function，NWDAF)，在未来的通信系统(如6G通信系统)中，网络数据分析功能可以仍是NWDAF，或者也可以具有其它名称，本申请并不限定。
统一数据管理功能，主要用于管理终端设备的签约信息。在5G通信系统中，统一数据管理功能可以是统一数据管理(unified data management，UDM)功能，在未来的通信系统(如6G通信系统)中，统一数据管理功能可以仍是UDM功能，或者也可以具有其它名称，本申请并不限定。
统一数据存储功能，主要用于存储结构化的数据信息，其中包括签约信息、策略信息，以及有标准格式定义的网络数据或业务数据。在5G通信系统中，统一数据存储功能可以是统一数据存储(unified data repository，UDR)功能，在未来的通信系统(如6G通信系 统)中，统一数据存储功能可以仍是UDR功能，或者也可以具有其它名称，本申请并不限定。
认证服务功能，主要用于对终端设备进行安全认证。在5G通信系统中，认证服务功能可以是认证服务端功能(authentication server function，AUSF)，在未来的通信系统(如6G通信系统)中，认证服务功能可以仍是AUSF，或者也可以具有其它名称，本申请并不限定。
网络能力开放功能，可以将网络的部分功能有控制地暴露给应用。在5G通信系统中，网络能力开放功能可以是NEF，在未来的通信系统(如6G通信系统)中，网络能力开放功能可以仍是NEF，或者也可以具有其它名称，本申请并不限定。
终端无线能力管理功能，用于存储和管理网络内终端设备的无线能力。在5G通信系统中，终端无线能力管理功能可以是终端无线能力管理功能(UE radio capability management function，UCMF)，在未来的通信系统(如6G通信系统)中，终端无线能力管理功能可以仍是UCMF，或者也可以具有其它名称，本申请并不限定。
绑定支撑功能，用于维护用户网络之间互连的协议(internet protocol，IP)地址和服务功能的对应关系。在5G通信系统中，绑定支撑功能可以是绑定支撑功能(binding support function，BSF)，在未来的通信系统(如6G通信系统)中，绑定支撑功能可以仍是BSF，或者也可以具有其它名称，本申请并不限定。
应用功能，可以向运营商的通信网络的控制面功能提供各类应用的服务数据，或者从通信网络的控制面功能获得网络的数据信息和控制信息。在5G通信系统中，应用功能可以是应用功能(application function，AF)，在未来的通信系统(如6G通信系统)中，应用功能可以仍是AF，或者也可以具有其它名称，本申请并不限定。
数据网络，主要用于为终端设备提供数据传输服务。数据网络可以是私有网络，如局域网，也可以是公用数据网(public data network，PDN)，如因特网(Internet)，还可以是运营商合并部署的专有网络，如配置的IP多媒体网络子系统(IP multimedia core network subsystem，IMS)服务。
需要说明的是，本申请实施例中功能还可以称为网元、网络功能或功能实体、设备等，例如，接入和移动管理功能还可以称为接入和移动管理网元、或接入和移动管理网络功能、或接入和移动管理功能实体等。各个功能的名称在本申请中不做限定，本领域技术人员可以将上述功能的名称更换为其它名称而执行相同的功能，均属于本申请保护的范围。
如背景技术所示，终端设备在与网络设备通信时，通常需要部署协议栈，通常协议栈可包括链路层、网络层、传输层和应用层，以图3A为例，图3A中还包括物理层，但是通常物理层不包含在协议栈的分层中，其中，应用层，可实现如下功能：
1.支持HTTP：提供全球广域网(world wide web，Web)文档的请求和传送。
2.支持文件传输协议(file transfer protocol，FTP)协议：提供两个端系统之间的文件传输。
3.支持域名解析(domain name server，DNS)：将网址(统一资源定位系统(uniform resource locator，URL))转换为32比特网络地址。
传输层，可实现如下功能：
1.支持传输控制协议(transmission control protocol，TCP)：向应用程序提供面向连接 的服务，服务包括应用层报文向目的地的传递和流量控制(即发送方和接收方速率匹配)；将长报文划分为短报文，提供拥塞控制，抑制源发送速率。
2.支持用户数据包协议(user datagram protocol，UDP)：向应用程序提供无连接的服务，没有可靠性、流量控制和拥塞控制。
网络层(IP层)，可实现如下功能：
1.支持IP：定义数据报中各个字段以及端系统和路由器如何作用于这些字段。
2.支持多种路由选择协议：使数据报根据路由从源传输到目的地。
链路层，可实现如下功能：
1.将网络层的数据通过链路层传输到下一结点，在下一节点再从链路层将数据交给网络层。
2.链路层协议包括例如点到点传输协议(point to point protocol，PPP)，并且可提供可靠交付，但与TCP可靠交付不同。
物理层，可提供协议和传输介质供比特流传输，不同传输媒介具有不同的物理层协议。
图3B示出另一种协议栈的示意图，接入网(access network，AN)层为UE和接入网RAN之间的无线协议栈(本申请不作限制和说明)，Ctrl/RT为可选的协议层，提供UE和UPF之间的控制(control，Ctrl)(本申请采用的名称，不作限定)和/或可靠传输(reliable transport，RT)(本申请采用的名称，不作限定)，Application协议层为UE和DN侧设备之间的应用层。RAN可选提供其和UPF之间的RT层，用于提供可靠传输。UPF在无线网络侧，可选提供和RAN之间的RT协议层，以及可选提供和UE之间的Ctrl/RT层；UPF在网络侧提供网络侧的连接服务，例如图3B中的TCP/UDP(user datagrm protocol，用户数据报协议)(本申请不限制DN中网络类型、连接类型以及使用的具体协议)。UPF在接收到来自UE的应用或者Ctrl层消息时，创建DN中的连接，用于为UE提供数据发送和接收服务；UPF和UE之间的数据以及Ctrl层消息，可选通过RT协议层实现可靠传输(包括两种可选方式：UE和UPF之间使用RT协议层；以及RAN和UE之间通过空口机制实现可靠传输，RAN和UPF之间通过RT实现可靠传输，进而实现UE到UPF之间的可靠传输)。在图3B示出的协议栈示意图中，终端未部署TCP/IP的协议栈，终端可以直接与UPF传输应用报文或应用数据，UPF可部署TCP/UDP的协议栈与数据网络建立通信连接传输数据。
在采用图1所示的系统架构以及图3A所示的协议栈分层时，终端设备与网络设备建立通信连接时，可参照图4所示的流程，终端的应用发送调用TCP/IP协议栈的接口的请求，TCP/IP所属的层返回接口标识给应用，UE借助自身的无线模块与网络设备建立TCP连接(借助与RAN和UPF之间的TCP连接进行应用数据的传输)，接收网络设备返回的连接状态(是否可以建立连接)。若网络设备支持与终端建立TCP连接，UE中的应用可通过无线模块基于建立的TCP连接传输数据至网络设备，网络设备接收数据后反馈数据的接收情况(是否成功接收，多少数据被成功接收，多少数据未被成功接收等)。
由于终端与网络设备之间的应用数据的传输通常需要借助TCP协议栈来实现，因此在各个终端中均需部署TCP或IP协议栈等，也即终端必须支持TCP或IP协议的传输，但是TCP或IP协议栈的部署为终端设备带来了处理开销，要求终端设备需要提供支持TCP或IP协议的处理能力。
考虑到应用数据传输时，终端需要部署TCP或IP协议栈复杂度较高，基于此，本申 请提供一种通信方法，以提高终端传输应用的应用数据到网络设备时的处理效率，降低对终端设备传输应用数据的处理能力要求。
参阅图5为本申请实施例提供的一种通信方法的流程，该方法可通过终端、用户面网元以及接收端的交互来执行，其中接收端可能为网络设备、核心网设备以及数据中心等，本申请在此不具体限定。本申请中，终端与接收端之间的通信是借助用户面网元实现的，终端无需部署TCP或IP协议栈等仅需采用无线通信协议向接收端发送应用报文或应用数据就可以，用户面网元可充当客户端的角色与接收端创建TCP或IP通信连接，接收端向终端发送数据时，用户面网元可充当服务端的角色直接通过无线通信协议向终端发送应用报文或应用数据。具体可参照如下步骤来执行：
步骤501：终端确定应用报文，应用报文包括应用数据和应用报文的接收端的应用地址，且不包括应用报文的源地址。应用报文可承载于会话或流中，也即应用报文可通过会话或流传输，通常会话是包括多个流的，该流可以为QoS流也可能为其他数据流，本申请在此不具体限定。
步骤502：终端向用户面网元发送应用报文。相应地，用户面网元可接收来自终端的应用报文。
步骤503：用户面网元根据会话配置信息确定应用报文的源地址；会话配置信息用于指示为终端提供连接服务。
需要说明的是，会话配置信息可以是用户面网元配置的信息，也可以为来自会话管理网元的信息，还可能是来自核心网设备的信息，还可能是用户面网元接收到来自终端设备的应用报文后，对应用报文进行解析确定的，本申请在此不具体限定会话配置信息的来源，通过该方式可以使得会话配置信息的获取方式更加灵活，且可实时调整。由于用户面网元相当于替代终端设备与接收端进行通信，用户面网元既要知晓接收端的地址也要确定通信时替代终端设备的地址，才可创建与接收端之间的TCP或IP连接，因此可根据会话配置信息确定应用报文的源地址。
在一种可选的方式中，用户面网元可根据会话配置信息确定会话的源地址；用户面网元可将会话的源地址作为应用报文的源地址。用户面网元接收到应用报文后，确定承载应用报文的会话或流。根据承载应用报文的会话或流以及会话配置信息确定会话的源地址。并将会话的源地址作为应用报文的源地址，例如，会话配置信息包括PDU会话1的源地址信息，若应用报文是通过PDU会话1或会话1下属的QoS流承载的，那么可将PDU会话1的源地址作为应用报文的源地址。当然实际应用时，会话配置信息可能直接配置某个PDU会话下属的QoS流的源地址信息，那么也可直接基于QoS流的源地址信息作为应用报文的源地址。本申请在此不具体限定。
但是，在实际应用时，用户面网元也可为终端分配源地址，而无需知晓终端设备的实际地址，例如：终端1对应地址1，向地址1发送数据也即向终端1发送数据。因此，终端设备的地址在实际应用时，可根据用户面网元的性能或实际业务需求进行设置，可以为用户面网元的地址也可以为终端设备的实际地址还可以为用户面网元为终端设备分配的地址，还可能是用户面网元的地址和终端设备的实际地址共同组成的地址信息等，本申请在此不具体限定。现有技术中，终端部署应用报文传输的协议栈的情况下，在发送报文时需要携带应用报文的源地址和目的地址，比如应用报文的源IP地址和目的IP地址等，但 本申请中，终端未部署应用报文传输的协议栈时，终端设备未向用户面网元传输应用报文的源地址的情况下，用户面网元可根据会话配置信息确定应用报文的源地址，通过该方式可以降低终端设备传输应用的应用数据的处理复杂度。
需要说明的是，会话配置信息还可包括报文协议信息；报文协议信息为：传输应用报文的报文协议信息，和/或，应用报文对应的报文协议类型。报文协议信息可以为HTTP协议等，本申请在此不具体限定。
步骤504：用户面网元根据应用地址确定应用报文的目的地址。由于应用报文携带的是应用报文接收端的应用地址，非IP地址，因此用户面网元可根据应用地址确定应用报文的目的地址，例如，应用报文的应用地址为应用地址1，用户面网元中可能存储有应用地址与应用报文的目的地址的对应关系，如，应用地址1对应目的地址3，那么用户面网元可将目的地址3作为应用报文的接收端的地址。
在一种可选的实施方式中，用户面网元可发送连接创建请求，创建请求包括应用地址；创建请求用于请求应用地址对应的目的地址；用户面网元接收连接创建请求的响应信息，响应信息可包括应用地址对应的目的地址。需要说明的是，用户面网元通过连接创建请求确定应用报文的应用地址对应的目的地址，而非直接通过应用报文携带目的地址，从而，本申请中，终端设备可在不部署应用报文的传输协议栈的情况下，将应用报文通过基于无线通信协议的会话或流发送到UPF，UPF也可以获取到应用报文的目的地址。
步骤505：用户面网元发送第一报文至接收端，第一报文包括应用数据、应用报文的源地址以及应用报文的目的地址。
用户面网元在确定应用报文的源地址和目的地址后与应用数据进行打包构成第一报文传输到接收端。终端与接收端通信时，无需在终端中部署应用报文的传输协议栈，终端将报文发送至用户面网元时，无需携带基于应用报文传输协议的连接信息，比如源地址或目的地址信息等，用户面网元通过会话配置信息以及应用报文的接收端的应用地址即可与接收端建立用于传输应用报文的通信连接，比如TCP连接或IP连接，该方式可降低UE传输引用报文到网络侧设备的数据处理复杂度。
需要说明的是，本申请实施例中，用户面网元和终端之间可以直接基于无线通信协议的会话或流来传输应用报文，而无需终端具备TCP或IP协议栈来构造与网络侧设备之间的TCP连接或IP连接来传输应用报文，网络侧设备和接收端(比如应用程序对应的服务器)之间可以通过TCP或IP协议栈来发送应用报文。网络侧设备和接收端之间除了通过TCP或IP协议栈来传输应用报文之外，还可以采用HTTP协议或FTP协议等传输应用报文。这样，本申请可以支持终端设备在不部署应用报文传输的协议栈的情况下，进行应用报文的传输，可以简化应用报文传输的过程。
此外，会话配置信息还可包括用户面网元可提供的服务类型(连接服务或寻址服务等)、接收端可支持的报文协议或服务类型(IPv4/IPv6/ICN、MEC等)等，本申请在不具体限定，可根据用户的业务需求以及用户面网元的设备能力灵活选择。
用户面网元在充当客户端的角色(也即在通信连接时发送数据)时，以UPF、外部设备、UE为例来说明。本申请的实施例中，外部设备存在一个地址服务器(例如DNS服务器)，还存在一个作为服务端或者接收端的设备，该服务端或接收端的设备可部署在DN中，图6中以接收端的设备部署在DN为例来说明。以终端侧应用层使用HTTP协议为例，终端侧的应用直接通过无线协议层发送报文，不用在Ctrl等协议层传输应用报文。下文涉及 到DN可参照此处理解。其中UE与UPF之间发送的数据是借助RAN实现的，RAN与UPF之间的数据通过可靠传输GTP-U保证的，在此不展开说明，可参照下文的描述来理解，可执行如下：
步骤0：UPF确定会话配置信息，该会话配置信息包括终端设备发送的会话或流所需的连接信息。该会话配置信息与上述的会话配置信息的来源相同，可以是配置的或来自其他设备的，但也可能是默认的信息(例如会话/流默认应用层为HTTP协议)、DNN/S-NSSAI(例如DNN/S-NSSAI对应的网络中使用的是特定的应用层和/或网络协议)等，根据上述信息确定连接信息等，本申请在此不具体限定。
步骤1：UE发送第一应用报文至UPF，该报文为遵照某种应用层协议的报文(例如HTTP)，可包含应用层协议定义的相关信息(例如HTTP报文中包含URL信息)。其中UE可通过non-ip(非IP)类型的会话发送，或者是通过新的类型的会话发送，如果是新的会话类型，该会话类型为支持网络提供连接服务的会话。假定该第一应用报文是通过会话发送的，但是在实际应用时也可通过流发送，本申请在此不具体限定，在此仅以会话为例。
步骤2：UPF确定为UE提供连接服务。例如UPF根据步骤0中的信息确定提供连接服务，或者UPF根据会话类型、DNN/S-NSSAI等确定提供连接服务。UPF可以根据步骤0中的信息确定提供连接服务所需的连接信息，以及解析来自步骤1的第一应用报文，确定应用层协议的类型、应用层地址(也即应用地址)信息等。
步骤3：UPF可以确定UE的地址信息，进而请求接收端的地址(例如向DN发送请求)，用于请求获得第一应用报文对应的接收端的地址(例如IPv4地址)。其中，接收端可理解为服务端或者接收端的设备。下文涉及到接收端可参照此处理解。
步骤4：UPF接收来自DN的接收端的地址应答，获得第一应用报文对应的接收端的地址。
如果UPF本地记录有第一应用报文对应的接收端的地址，则不需要执行步骤3、4。
步骤5：UPF启动应用客户端，创建和接收端设备的TCP/IP连接。
步骤6：UPF和接收端设备之间创建与应用报文对应的TCP/IP连接，UPF可以使用自身的地址(例如IPv4地址)创建和接收端设备的TCP/IP连接，也可以使用UE的地址创建(会话创建过程中由UPF或控制面网元为UE分配的地址)和接收端设备的TCP/IP连接。
步骤7：UPF通过创建的TCP/IP连接，向接收端设备发送步骤1中接收到的第一应用报文，之后通过该TCP/IP连接接收来自接收端设备的应用应答，应用应答为接收端设备针对接收到的第一应用报文的应答报文。
或者对于不需要重新创建连接的协议类型(例如UDP)，或者说UPF和接收端设备之间的可靠性传输连接一直存在，UPF也可以不执行步骤6，而是直接执行向接收端设备发送应用请求，之后UPF接收接收端设备的应答。
步骤8：UPF向UE发送应用应答。
需要说明的是，对于ICN网络、UPF和应用服务共部署等场景，UPF直接通过ICN定义或内部通信获得UE请求的内容，可以不执行步骤3-7(对于ICN网络，UPF基于ICN请求中的内容的名称，读取或请求相应的内容，而不是必须创建连接；对于UPF和应用共部署等场景，UPF可以直接根据应用层请求中的标识等信息，在共部署的应用上获得相关内容，不需要通过连接来获取信息)；或者UPF根据UE请求的应用层地址，请求获得UE 请求的内容(UPF和应用之间可通过应用层地址访问，上述ICN和共部署方式可视为具体的一种实现方式)，或者对于不需要显示创建连接的协议类型(例如UDP，当UE需要发送报文时，直接向对端的地址和端口发送报文即可，而不用像TCP一样预先完成连接的握手过程)，不需要执行步骤6创建连接的过程，而直接向接收端设备发送请求，进而接收来自接收端设备的应答。类似的UPF获取UE请求的内容的过程，本申请中也视为连接服务。
用户面网元在充当服务端的角色(也即在通信连接时接收数据)时，以UPF、外部设备以及UE为例来说明，其中UE与UPF之间发送的数据是借助RAN实现的，RAN与UPF之间的数据通过可靠传输GTP-U保证，在此不展开说明，可参照下文的描述来理解，外部设备包括应用客户端，图7以外部设备部署在DN中为例进行说明，可执行如下：
步骤0：UPF确定会话配置信息，同上述图6中的步骤0在此不赘述。
步骤1：UPF根据步骤0的会话配置信息确定启动应用服务端，可选的创建终端/会话/流/应用对应的监听接口。和图6对应的描述类似的，外部设备要向UPF发送报文时，不需要显示的连接创建过程，而是直接发送请求，相应的，UPF只需要等待接收报文即可，而不用先完成连接的握手过程，为了统一描述，本申请中将等待接收应用请求也视为创建监听接口。
UPF为会话创建监听接口后，可等待接收请求报文，其中创建监听接口时，可以使用UPF的地址，或者使用终端对应的地址创建(会话创建过程中由UPF或控制面网元为终端分配的地址)。
步骤2：UPF向地址服务器上报应用对应的地址信息。其中，地址服务器可以是控制面网元，也可以是DN中的设备，图7中以DN为例来说明。应用对应的地址信息包括应用地址信息和步骤1中创建的监听接口使用的地址，其中应用地址可以是步骤0中获得的，也可以是配置在UPF上的(例如DNN/S-NSSAI对应某个地址)。
步骤3：当有外部设备的应用客户端准备发起应用请求时，可选的向地址服务器查询应用地址对应的终端的地址(即步骤1中UPF创建监听接口时使用的地址)。当外部设备的应用客户端已经有地址信息时，或者对于ICN网络或客户端与UPF之间可访问应用时，外部设备的应用客户端不需要执行该步骤。
步骤4：在需要创建连接时，外部设备的应用客户端根据步骤3获得的地址信息发起和UPF之间的连接创建请求。
步骤5：UPF可向控制面网元(例如SMF)上报会话或流创建请求，进而触发控制面创建流的流程。也可以是在步骤2之前创建流。可选的，当UPF在步骤2创建了监听接口，或者在步骤4监测到连接创建，或者在步骤6接收到应用请求时，该步骤也可以在步骤2或者6后执行。
步骤6：外部设备的应用客户端向UPF发送应用请求。外部设备的应用客户端可通过步骤4创建的连接发送应用请求，或者向步骤3获得的地址发送应用请求；或者对于ICN网络或外部设备的应用客户端与UPF之间可直接访问应用时，可直接发送应用请求。
步骤7：UPF通过应用/接口对应的会话发送应用请求。
步骤8：UPF接收来自UE的应用应答。
步骤9：UPF直接发送应用应答至外部设备的应用客户端。
本申请，终端无需部署应用报文传输的协议栈，通过UPF提供终端与外部设备的TCP或IP连接，可降低终端的设备开销，降低终端处理的复杂度。
采用图6或图7中的方案创建UE与接收端之间的通信连接时，用户面网元可解析终端设备的软件应用或通过会话配置信息，获得连接信息，但是，若终端设备的软件应用为私有应用，用户面网元无法感知应用相关信息的情况下，则无法获得连接信息。因此可参阅图8提供的通信方法来执行，可通过终端、用户面网元以及接收端的交互来说明。可执行如下：
步骤801：终端确定指示信息，指示信息指示应用报文的接收端的目的地址。
需要说明的是，指示信息可以是终端通过与用户面网元之间的协议层发送给用户面网元的。该协议层可以为Ctrl层，本申请不限定Ctrl层的名称、以及在协议栈的位置等，例如终端也可以支持TCP/IP网络层和传输层等协议栈，Ctrl层可以位于无线协议栈、TCP/IP网络层、传输层、以及应用层等的任意位置，本实施例中，以Ctrl层用于UE和UPF之间进行信息交互为例进行说明，Ctrl层可以用于网络中设备之间进行信息交互，并且网络设备在传递Ctrl层时可以对其内容进行修改。例如UE向UPF发送Ctrl信息(也即指示信息)后，UPF可以向DN中的设备发送Ctrl层信息，并且UPF在发送之前还可以对内容进行修改，该方式不影响其他已有协议层的功能，本申请在此不具体限定，通过协议层发送指示信息，通过指示信息指示应用报文的接收端的地址，用户面网元在无法感知应用相关信息的情况下，也可以获得连接信息。
步骤802：终端发送指示信息至用户面网元；相应地，用户面网元接收指示信息。
步骤803：终端确定应用报文，应用报文包括应用数据，且不包括应用报文的源地址和目的地址。
步骤804：终端发送应用报文至用户面网元。相应地，用户面网元接收应用报文。
需要说明的是，终端可通过无线通信协议发送应用报文，该终端也可支持TCP/IP的协议栈，本申请在此不具体限定。
步骤805：用户面网元根据指示信息确定应用报文的目的地址。
步骤806：用户面网元根据会话配置信息确定应用报文的源地址；会话配置信息用于指示为终端提供连接服务。可参照上述步骤503处的描述，本申请在此不赘述。
步骤807：用户面网元发送第一报文至接收端，第一报文包括应用数据、应用报文的源地址以及应用报文的目的地址。
上述的指示信息还包括：终端设备对应的QoS需求信息、传输应用报文的协议信息、应用报文对应的协议类型中的至少一个。该报文协议信息可以为HTTP。需要说明的是，指示信息中包括的终端设备对应的QoS需求信息、传输应用报文的协议信息、应用报文对应的协议类型，以便用户面网元可以更加明确连接信息，提高数据处理效率。
本申请中，终端与其他设备通信时，用户面网元通过会话配置信息以及指示信息即可与其他设备建立应用报文的通信连接，此外，通过该方式用户面网元在无法感知终端私有应用相关信息的情况下，也可以通过指示信息获得应用报文的接收端的目的地址，可以减少依赖应用报文的应用地址确定接收端的目的地址的情况出现。
在一种可选的方式中，指示信息具体用于指示：根据应用报文中携带的连接标识确定接收端的目的地址；终端向用户面网元发送应用报文，应用报文包括第一连接标识，第一 连接标识对应的连接用于承载应用报文，相应地，用户面网元接收来自终端的应用报文，应用报文包括第一连接标识；用户面网元根据应用报文中包括的第一连接标识，确定应用报文的目的地址。该连接标识可能是终端自行确定的连接标识，也可能是通过其他方式获取的连接标识，用户面网元根据该连接标识可以确定应用报文的接收端的目的地址，通过该方式可以提高通信效率，降低设备处理的复杂度。
在一种可选的方式中，用户面网元向终端发送连接标识信息，连接标识信息包括一个或多个连接标识，各连接标识分别用于标识用户面网元创建的连接；第一连接标识是终端从一个或多个连接标识中选择的，相应地，用户面网元接收来自终端的连接标识信息。该方式中应用报文的连接标识是用户面网元分配的，用户面网元分配连接标识后，终端在发应用数据时，携带上选择的连接标识，用户面网元即可确定连接信息，可提高数据处理效率。
图9示出用户面网元基于指示信息确定连接信息的流程，其中，UE可包括应用、Ctrl处理模块以及无线发送模块，其中UE与UPF之间发送的数据是借助RAN实现的，RAN与UPF之间的数据通过可靠发送GTP-U保证，在此不展开说明，可参照下文的描述来理解，可执行如下：
步骤1：在会话(或流)创建(或修改)过程中，控制面网元(SMF)通过会话创建(或修改)信息指示UPF提供连接服务(或支持Ctrl协议)。或者UPF根据会话类型、DNN/S-NSSAI等信息确定需要为用户提供连接服务(或支持Ctrl协议)，那么UPF确定可提供连接服务。
步骤2：UE的应用请求创建接口。可使用现有TCP/IP协议栈接口请求创建接口，本申请在此不限定。
步骤3：Ctrl处理模块为应用创建接口，并返回接口标识。
步骤4：UE作为应用客户端时，请求创建连接。图9中以UE作为客户端为例来说明，如果UE作为服务端，则请求监听报文，本实施例不具体描述。
步骤5：Ctrl处理模块通过Ctrl层发送指示信息，例如发送控制指令，请求创建连接，该步骤也可以在终端发送应用报文时一起执行(即将步骤9、10提前到步骤4后执行，合并步骤5、11，以及合并步骤8、13)。指示信息中可包含应用层地址、服务端地址、发送协议相关信息(例如协议类型、端口号等)，用于提供UPF提供连接服务所需的信息；还可以包含应用对应的QoS需求(例如带宽、报文周期/突发流量等信息)、是否支持可靠发送等，用于UPF及无线网络、可选的包括DN网络提供请求的QoS保障。
作为一种实现方式，应用和Ctrl处理模块间使用传统TCP/IP协议栈接口，之后Ctrl处理模块在Ctrl层中封装应用调用的TCP/IP协议栈接口和相关参数，类似于UPF上实现TCP/IP协议栈，而应用调用的协议栈服务是在UPF上实现的。本申请不限定具体如何实现Ctrl模块以及Ctrl层的信息格式。
步骤6：UPF根据Ctrl层提供的指示信息，确定应用报文的接收端的地址。
UPF记录网络侧连接和会话的对应关系，用户后续在连接和会话间转发报文。可选的，UPF为会话分配连接标识，该标识和连接对应，后续会话和UPF之间交互报文时，通过该标识指示对应的连接。
步骤7：UPF完成与接收端设备的连接创建过程。
步骤8：UPF通过Ctrl层反馈连接状态或执行Ctrl指示的结果。可选的反馈步骤6分 配的连接标识。
步骤9：Ctrl处理模块根据步骤8的结果，向应用反馈接口创建结果。
步骤10：当应用需要发送数据时，通过Ctrl处理模块发送数据。
作为一种实现方式，应用可以使用传统TCP/IP协议栈的接口发送数据，Ctrl模块基于接口的处理逻辑进行适配。
步骤11：Ctrl处理模块转发来自应用的数据，在发送时，可以包括步骤8反馈的连接标识。
步骤12：UPF通过应用报文或连接标识对应的连接向接收端设备发送应用数据。
步骤13：接收端可向UPF反馈执行结果。
步骤14：可选的，UPF通过Ctrl层向连接对应的会话发送步骤13的执行结果，以及当UPF接收到来自接收端设备的下行报文时，通过连接对应的会话向终端发送接收到的报文，其中步骤13的执行结果可以随同下行报文一起发送。在执行该过程时，可选的在Ctrl层携带连接标识。
步骤15：Ctrl处理模块向应用反馈步骤11的执行结果。该步骤可以是根据步骤13反馈的信息确定执行结果(例如对于有可靠发送需求的应用，Ctrl处理模块根据步骤13反馈的信息确定报文是否发送成功)，也可以是在执行步骤11或12后反馈执行结果(例如对于没有可靠发送需求的应用，只要将报文发送出去即认为发送成功)。
在上述的示例中均提及UPF使能为用户提供连接服务、可靠发送、QoS保障等，以及通过接收配置的方式获得提供上述服务时所需的相关信息，本实施例提供具体的使能过程和相关配置获得的过程，可参阅图10，执行如下：
下述步骤1、2、3为可选执行，当对UPF进行相关配置时，可执行步骤1、2、3的部分或全部，使得SMF从其中的单个步骤或多个步骤获得后续配置到UPF的相关信息。
步骤1：在UE发送的会话创建请求中，可选指示网络提供连接服务(例如使用特殊的会话类型，或者使用显示的指示信息，或者指示的DNN/S-NSSAI等信息对应的网络需要提供连接服务等)，可选指示连接相关的信息(会话配置信息)，可选指示使用可靠发送和/或Ctrl协议层等(指示的方式类似于指示提供连接服务)。
步骤2：AF更新UDM中的签约数据，或者AF向PCF提供(可以是AF发送到NEF等网元，再发送到PCF，或者AF直接向PCF发送)步骤1中所述的部分或全部信息。
步骤3：SMF从PCF或UDM获得步骤1中所述的部分或全部信息。也可以不执行步骤2，而是由AF向SMF提供所述信息(AF直接向SMF发送，或者AF发送给NEF等网元，再发送到SMF)。
步骤4：SMF通过N4会话创建(或修改)请求，向UPF提供连接信息。
步骤5：SMF在会话创建或流创建过程中，或者更新URSP信息时，向终端提供步骤1中所述的部分或全部信息(例如通过步骤2、3，由AF更新应用相关的信息，之后通过URSP发送给UE，更新UE上的配置)，用于终端基于配置信息执行图5-图9的相关流程，或者后续在创建会话时，通过图6的步骤1向网络提供相关信息。
步骤6：执行上述图6、图7或图9的流程，或者根据步骤4中的连接信息创建连接。
上述图5-图10中UE与UPF之间发送的数据是借助RAN实现的，用户面网元可接收 无线接入网设备(RAN)的转发报文，转发报文为终端发送给无线接入网设备的，转发报文包括应用报文。RAN与UPF之间的数据通过可靠发送GTP-U保证的，接下来具体介绍如何保证数据的可靠发送，用户面网元与终端设备的会话中携带的应用报文通过RAN转发，对于上行报文，用户面网元接收来自RAN的转发报文，转发报文包括：应用报文、发送应用报文的序列号；用户面网元向RAN反馈接收到的应用报文的序列号。在实际执行时，可分为RAN透传和转发两种方式，在采用RAN转发时，可参阅图11A来说明，以上行数据流为例来说明，具体可执行如下：
步骤1：UE发送上行报文，UE和RAN之间通过空口机制保障可靠发送。
步骤2：RAN向UPF发送报文时，在GTP-U包头中包含报文发送报文的序列号，序列号的编号可以是流粒度的(即每条流独立的按序编号)，或者GTP-U隧道粒度的(即每个GTP-U隧道独立的按序编号，可以认为等同于会话粒度的序列号)。也可以是GTP-U承载在可靠发送协议上(例如TCP、QUIC等。现有技术是承载在UDP上)，基于此也可以实现RAN和UPF之间设备粒度的可靠发送。
步骤3：UPF向RAN反馈接收到的报文的序列号，或者在超时未接收到报文时，反馈超时未接收到的报文序列号。
步骤4：在步骤2发生丢包时，RAN根据步骤3的反馈确定发生丢包及丢包的序号，并进行重传。
在采用RAN透传时，可参阅图11B来说明，可以上行数据流为例来说明，具体可执行如下：
步骤1：在UE发送上行流之前(例如在流创建过程中或流创建后，或者建立连接过程中等)，UPF向UE提供(即UPF分配标识)会话对应的发送标识，该标识可以Ctrl层的连接标识，也可以是用于可靠发送独立的标识。该标识可用于后续标识可靠发送的流(或者可以理解为后续的序列号是发送标识粒度的)。也可以是UE分配发送标识，例如由UE发送给UPF，或者UE在开始发送报文时随同报文一起发送。
步骤2：UE发送上行报文，报文中包含QoS会话发送标识粒度的报文序列编号，该序列编号可以是在独立的协议层(本申请以RT协议层为例进行说明，但不限定具体的协议层名称)，也可以是在Ctrl层，或者是其他包头中。如果有发送标识，那么报文中还可以包含该发送标识，发送标识不限定是和报文序列号在同一协议层，例如：发送序列号使用Ctrl层的连接标识，而序列号放在RT协议层中，这里不做限定。
步骤3：UPF向UE反馈接收到的报文序列号，或者在超时未接收到报文时反馈丢包序列号。反馈的报文序列号可以随同下行报文一起发送。
步骤4：在步骤2发生丢包时，终端根据步骤3的反馈确定发生丢包及丢包的序号，并进行重传。
此外，可参阅图12来说明UPF和RAN之间的报文如何发送和丢包重传，以RAN向UPF发送报文，相应的UPF向RAN发送对接收到的报文的确认，GTP-U实现可靠发送为例：
GTP-U包头中可以引入用于包的重传控制的机制，例如以会话粒度的控制为例，图12中在GTP-U包头中引入ACK序列号，用于实现收包确认，复用现有GTP-U包头中的序列号作为发送报文的序列号；如果支持选择重传，可以引入S-ACK序列号实现，S-ACK和ACK一起用于确认接收到一个区间的序列号的报文，其中S-ACK表征区间的开始序列 号，ACK表征区间的最后一个序列号；如果不支持选择重传，可以通过序列号和ACK实现窗口机制的重传(在此不详细说明)。
确认报文的接收端(也即RAN)在接收到的报文中包含ACK序列号时，如果没有包含S-ACK序列号，那么ACK序列号之前的报文都已接收到，可以删除缓存(如上图12中RAN接收到包1、2时，返回ACK为序号2)；如果包含了S-ACK序列号，可以删除S-ACK和ACK之间的帧(如上图中RAN接收到报文4、5后，返回的S-ACK为4，ACK为5)，并且如果有超时未确认的序列号(如上图中的报文3)，则对这些序列号对应的报文进行重传。
本申请可以支持更大粒度的重传控制，例如将相关的编号进行设备粒度的统一编号，即可实现设备粒度的重传控制。在双向通信的过程中，ACK可以随同数据报文一起发送，而在没有数据报文发送时，可以通过单独的报文发送ACK信息，此时发送ACK的报文中的序号同样需要递增，但对端接收到这种ACK报文时，不单独发送ACK应答，以避免循环发送ACK。
上述主要从设备交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，为了实现上述功能，各个设备可以包括执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请的实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对设备进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
在采用集成的单元的情况下，图13示出了本申请实施例中所涉及的通信装置的可能的示例性框图。如图13所示，通信装置可以包括：处理单元1301和收发单元1302。处理单元1301用于对通信装置的动作进行控制管理。收发单元1302用于支持通信装置与其他设备的通信。可选地，收发单元1302可以包括接收单元和/或发送单元，分别用于执行接收和发送操作。可选的，通信装置还可以包括存储单元，用于存储通信装置的程序代码和/或数据。所述收发单元可以称为输入输出单元、通信单元等，所述收发单元可以是收发器；所述处理单元可以是处理器。当通信装置是通信设备中的模块(如，芯片)时，所述收发单元可以是输入输出接口、输入输出电路或输入输出管脚等，也可以称为接口、通信接口或接口电路等；所述处理单元可以是处理器、处理电路或逻辑电路等。具体地，该装置可以为上述的终端、用户面网元等。
在一个实施例中，收发单元1302可用于接收来自终端的应用报文，应用报文包括应用数据和应用报文的接收端的应用地址；应用报文承载于会话或流中；处理单元1301可用于根据会话配置信息确定应用报文的源地址；会话配置信息用于指示为终端提供连接服务；根据应用地址确定应用报文的目的地址；收发单元1302还可用于发送第一报文至接收端，第一报文包括应用数据、应用报文的源地址以及应用报文的目的地址。
在一种可选的方式中，处理单元1301，可用于根据会话配置信息确定会话的源地址； 将会话的源地址作为应用报文的源地址。
在一种可选的方式中，收发单元1302可用于发送连接创建请求，创建请求包括应用地址；创建请求用于请求应用地址对应的目的地址；接收连接创建请求的响应信息，响应信息包括应用地址对应的目的地址。
在一种可选的方式中，收发单元1302可用于接收无线接入网设备的转发报文，转发报文为终端发送给无线接入网设备的，转发报文包括应用报文。
在一种可选的方式中，转发报文还包括应用报文的序列号；收发单元1302可用于向接入网设备反馈接收到的应用报文的序列号。
在一种可选的方式中，会话配置信息包括报文协议信息；报文协议信息为：传输应用报文的报文协议信息，和/或，应用报文对应的报文协议类型。
在一种可选的方式中，报文协议信息为HTTP。
在一种可选的方式中，源地址为用户面网元为终端分配的地址。
在又一实施例中，处理单元1301可用于确定应用报文，应用报文包括应用数据和应用报文的接收端的应用地址，且不包括应用报文的源地址；收发单元1302可用于向用户面网元发送应用报文。
在又一实施例中，收发单元1302可用于接收来自终端的指示信息，指示信息指示应用报文的接收端的目的地址；接收来自终端的应用报文，应用报文包括应用数据；处理单元1301可用于根据指示信息确定应用报文的目的地址；根据会话配置信息确定应用报文的源地址；会话配置信息用于指示为终端提供连接服务；收发单元1302还可用于送第一报文至接收端，第一报文包括应用数据、应用报文的源地址以及应用报文的目的地址。
在一种可选的方式中，指示信息是终端通过与用户面网元之间的协议层发送给用户面网元的。
在一种可选的方式中，处理单元1301可用于根据会话配置信息确定应用报文承载的会话的源地址；将应用报文承载的会话的源地址作为应用报文的源地址。
在一种可选的方式中，指示信息具体用于指示：根据应用报文中携带的连接标识确定接收端的目的地址；收发单元1302用于接收来自终端的应用报文，应用报文包括第一连接标识，第一连接标识对应的连接用于承载应用报文；处理单元1301，用于根据应用报文中包括的第一连接标识，确定应用报文的目的地址。
在一种可选的方式中，收发单元1302用于向终端发送连接标识信息，连接标识信息包括一个或多个连接标识，各连接标识分别用于标识用户面网元创建的连接；第一连接标识是终端从一个或多个连接标识中选择的。
在一种可选的方式中，收发单元1302可用于接收无线接入网设备的转发报文，转发报文为终端发送给无线接入网设备的，转发报文包括应用报文。
在一种可选的方式中，转发报文还包括应用报文的序列号；收发单元1302可用于向接入网设备反馈接收到的应用报文的序列号。
在一种可选的方式中，指示信息包括：终端对应的QoS需求信息、传输应用报文的报文协议信息、应用报文对应的报文协议类型。
在一种可选的方式中，报文协议信息为HTTP。
在又一实施例中，处理单元1301可用于确定指示信息，指示信息指示应用报文的接收端的目的地址；收发单元1302可用于发送指示信息至用户面网元；处理单元1301可用 于确定应用报文，应用报文包括应用数据，且不包括应用报文的源地址和目的地址；收发单元1302可用于发送应用报文至用户面网元，应用报文包括应用数据，且不包括应用报文的源地址和目的地址。
在一种可选的方式中，指示信息是终端通过与用户面网元之间的协议层发送给用户面网元的。
在一种可选的方式中，指示信息具体用于指示：用户面网元根据应用报文中携带的连接标识确定接收端的目的地址；收发单元1302用于向用户面网元发送应用报文，应用报文包括第一连接标识，第一连接标识对应的连接用于承载应用报文。
在一种可选的方式中，收发单元1302用于接收来自用户面网元的连接标识信息，连接标识信息包括一个或多个连接标识，各连接标识分别用于标识用户面网元创建的连接；第一连接标识是终端从一个或多个连接标识中选择的。
此外，如图14所示，为本申请还提供的一种通信装置1400。示例性地，通信装置1400可以是芯片或芯片系统。可选的，在本申请实施例中芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
通信装置1400可以包括至少一个处理器1410，通信装置1400还可以包括至少一个存储器1420，用于存储计算机程序、程序指令和/或数据。存储器1420和处理器1410耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1410可能和存储器1420协同操作。处理器1410可能执行存储器1420中存储的计算机程序。可选的，所述至少一个存储器1420也可与处理器1410集成在一起。
可选的，在实际应用中，通信装置1400中可以包括收发器1430也可不包括收发器1430，图中以虚线框来示意，通信装置1400可以通过收发器1430和其它设备进行信息交互。收发器1430可以是电路、总线、收发器或者其它任意可以用于进行信息交互的装置。
在一种可能的实施方式中，该通信装置1400可以应用于前述的终端设备，也可以是前述的用户面网元。存储器1420保存实施上述任一实施例中的用户面网元的功能的必要计算机程序、程序指令和/或数据。所述处理器1410可执行所述存储器1420存储的计算机程序，完成上述任一实施例中的方法。
本申请实施例中不限定上述收发器1430、处理器1410以及存储器1420之间的具体连接介质。本申请实施例在图14中以存储器1420、处理器1410以及收发器1430之间通过总线连接，总线在图14中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图14中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。在本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实施或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器还可以是能够用于携带或存储具 有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实施存储功能的装置，用于存储计算机程序、程序指令和/或数据。
基于以上实施例，参见图15，本申请实施例还提供另一种通信装置1500，包括：接口电路1510和逻辑电路1520；接口电路1510，可以理解为输入输出接口，可用于执行与上述图13示意的收发单元或如图14示意的收发器同样的操作步骤，本申请在此不再赘述。逻辑电路1520可用于运行所述代码指令以执行上述任一实施例中的方法，可以理解成上述图13中的处理单元或图14中的处理器，可以实现处理单元或处理器同样的功能，本申请在此不再赘述。
基于以上实施例，本申请实施例还提供一种可读存储介质，该可读存储介质存储有指令，当所述指令被执行时，使上述任一实施例中通信方法执行的方法被实施。该可读存储介质可以包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、装置(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理装置的处理器以产生一个机器，使得通过计算机或其他可编程数据处理装置的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理装置以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理装置上，使得在计算机或其他可编程装置上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程装置上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。

Claims (49)

  1. 一种通信方法，其特征在于，包括：
    用户面网元接收来自终端的应用报文，所述应用报文包括应用数据和所述应用报文的接收端的应用地址；所述应用报文承载于会话或流中；
    所述用户面网元根据会话配置信息确定所述应用报文的源地址；所述会话配置信息用于指示为所述终端提供连接服务；
    所述用户面网元根据所述应用地址确定所述应用报文的目的地址；
    所述用户面网元发送第一报文至所述接收端，所述第一报文包括所述应用数据、所述应用报文的源地址以及所述应用报文的目的地址。
  2. 根据权利要求1所述的方法，其特征在于，所述用户面网元根据会话配置信息确定所述应用报文的源地址，包括：
    所述用户面网元根据所述会话配置信息确定所述会话的源地址；
    所述用户面网元将所述会话的源地址作为所述应用报文的源地址。
  3. 根据权利要求1或2所述的方法，其特征在于，所述用户面网元根据所述应用地址确定所述应用报文的目的地址，包括：
    所述用户面网元发送连接创建请求，所述创建请求包括所述应用地址；所述创建请求用于请求所述应用地址对应的目的地址；
    所述用户面网元接收所述连接创建请求的响应信息，所述响应信息包括所述应用地址对应的目的地址。
  4. 根据权利要求1-3中任一所述的方法，其特征在于，所述用户面网元接收来自终端的应用报文，包括：
    所述用户面网元接收无线接入网设备的转发报文，所述转发报文为所述终端发送给所述无线接入网设备的，所述转发报文包括所述应用报文。
  5. 根据权利要求4所述的方法，其特征在于，所述转发报文还包括所述应用报文的序列号；所述方法还包括：
    所述用户面网元向所述接入网设备反馈接收到的所述应用报文的序列号。
  6. 根据权利要求1-5中任一所述的方法，其特征在于，所述会话配置信息包括报文协议信息；所述报文协议信息为：传输所述应用报文的报文协议信息，和/或，所述应用报文对应的报文协议类型。
  7. 根据权利要求6所述的方法，其特征在于，所述报文协议信息为超文本传输协议HTTP。
  8. 根据权利要求1-7中任一所述的方法，其特征在于，所述源地址为所述用户面网元为所述终端分配的地址。
  9. 一种通信方法，其特征在于，包括：
    终端确定应用报文，所述应用报文包括应用数据和所述应用报文的接收端的应用地址，且不包括所述应用报文的源地址；
    所述终端向用户面网元发送所述应用报文。
  10. 一种通信方法，其特征在于，包括：
    用户面网元接收来自终端的指示信息，所述指示信息指示应用报文的接收端的目的地 址；
    所述用户面网元接收来自所述终端的所述应用报文，所述应用报文包括应用数据；
    所述用户面网元根据所述指示信息确定所述应用报文的目的地址；
    所述用户面网元根据会话配置信息确定所述应用报文的源地址；所述会话配置信息用于指示为所述终端提供连接服务；
    所述用户面网元发送第一报文至所述接收端，所述第一报文包括所述应用数据、所述应用报文的源地址以及所述应用报文的目的地址。
  11. 根据权利要求10所述的方法，其特征在于，所述指示信息是所述终端通过与所述用户面网元之间的协议层发送给所述用户面网元的。
  12. 根据权利要求10或11所述的方法，其特征在于，所述用户面网元根据会话配置信息确定所述应用报文的源地址，包括：
    所述用户面网元根据所述会话配置信息确定所述应用报文承载的会话的源地址；
    所述用户面网元将所述应用报文承载的会话的源地址作为所述应用报文的源地址。
  13. 根据权利要求10-12中任一所述的方法，其特征在于，所述指示信息具体用于指示：根据应用报文中携带的连接标识确定接收端的目的地址；所述用户面网元接收来自所述终端的所述应用报文，包括：
    所述用户面网元接收来自所述终端的所述应用报文，所述应用报文包括第一连接标识，所述第一连接标识对应的连接用于承载所述应用报文；
    所述用户面网元根据所述指示信息确定所述应用报文的目的地址，包括：
    所述用户面网元根据所述应用报文中包括的第一连接标识，确定所述应用报文的目的地址。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    所述用户面网元向所述终端发送连接标识信息，所述连接标识信息包括一个或多个连接标识，各所述连接标识分别用于标识所述用户面网元创建的连接；所述第一连接标识是所述终端从所述一个或多个连接标识中选择的。
  15. 根据权利要求10-14中任一所述的方法，其特征在于，所述用户面网元接收来自终端的应用报文，包括：
    所述用户面网元接收无线接入网设备的转发报文，所述转发报文为所述终端发送给所述无线接入网设备的，所述转发报文包括所述应用报文。
  16. 根据权利要求15所述的方法，其特征在于，所述转发报文还包括所述应用报文的序列号；所述方法还包括：
    所述用户面网元向所述接入网设备反馈接收到的所述应用报文的序列号。
  17. 根据权利要求10-16中任一所述的方法，其特征在于，所述指示信息包括：所述终端对应的服务质量QoS需求信息、传输所述应用报文的报文协议信息、所述应用报文对应的报文协议类型。
  18. 根据权利要求17所述的方法，其特征在于，所述报文协议信息为超文本传输协议HTTP。
  19. 一种通信方法，其特征在于，包括：
    终端确定指示信息，所述指示信息指示应用报文的接收端的目的地址；
    所述终端发送所述指示信息至用户面网元；
    所述终端确定应用报文，所述应用报文包括应用数据，且不包括所述应用报文的源地址和目的地址
    所述终端发送所述应用报文至所述用户面网元。
  20. 根据权利要求19所述的方法，其特征在于，所述指示信息是所述终端通过与所述用户面网元之间的协议层发送给所述用户面网元的。
  21. 根据权利要求19或20所述的方法，其特征在于，所述指示信息具体用于指示：所述用户面网元根据应用报文中携带的连接标识确定接收端的目的地址；所述终端发送所述应用报文至所述用户面网元，包括：
    所述终端向所述用户面网元发送所述应用报文，所述应用报文包括第一连接标识，所述第一连接标识对应的连接用于承载所述应用报文。
  22. 根据权利要求21所述的方法，其特征在于，还包括：
    所述终端接收来自所述用户面网元的连接标识信息，所述连接标识信息包括一个或多个连接标识，各所述连接标识分别用于标识所述用户面网元创建的连接；所述第一连接标识是所述终端从所述一个或多个连接标识中选择的。
  23. 一种通信装置，其特征在于，包括：
    收发单元，用于接收来自终端的应用报文，所述应用报文包括应用数据和所述应用报文的接收端的应用地址；所述应用报文承载于会话或流中；
    处理单元，用于根据会话配置信息确定所述应用报文的源地址；所述会话配置信息用于指示为所述终端提供连接服务；根据所述应用地址确定所述应用报文的目的地址；
    所述收发单元，还用于发送第一报文至所述接收端，所述第一报文包括所述应用数据、所述应用报文的源地址以及所述应用报文的目的地址。
  24. 根据权利要求23所述的装置，其特征在于，所述处理单元，具体用于：
    根据所述会话配置信息确定所述会话的源地址；
    将所述会话的源地址作为所述应用报文的源地址。
  25. 根据权利要求23或24所述的装置，其特征在于，所述收发单元，具体用于：
    发送连接创建请求，所述创建请求包括所述应用地址；所述创建请求用于请求所述应用地址对应的目的地址；
    接收所述连接创建请求的响应信息，所述响应信息包括所述应用地址对应的目的地址。
  26. 根据权利要求23-25中任一所述的装置，其特征在于，所述收发单元，具体用于：
    接收无线接入网设备的转发报文，所述转发报文为所述终端发送给所述无线接入网设备的，所述转发报文包括所述应用报文。
  27. 根据权利要求26所述的装置，其特征在于，所述转发报文还包括所述应用报文的序列号；所述收发单元还用于：
    向所述接入网设备反馈接收到的所述应用报文的序列号。
  28. 根据权利要求23-27中任一所述的装置，其特征在于，所述会话配置信息包括报文协议信息；所述报文协议信息为：传输所述应用报文的报文协议信息，和/或，所述应用报文对应的报文协议类型。
  29. 根据权利要求28所述的装置，其特征在于，所述报文协议信息为超文本传输协议HTTP。
  30. 根据权利要求23-29中任一所述的装置，其特征在于，所述源地址为所述用户面网 元为所述终端分配的地址。
  31. 一种通信装置，其特征在于，包括：
    处理单元，用于确定应用报文，所述应用报文包括应用数据和所述应用报文的接收端的应用地址，且不包括所述应用报文的源地址；
    收发单元，用于向用户面网元发送所述应用报文。
  32. 一种通信装置，其特征在于，包括：
    收发单元，用于接收来自终端的指示信息，所述指示信息指示应用报文的接收端的目的地址；接收来自所述终端的所述应用报文，所述应用报文包括应用数据；
    处理单元，用于根据所述指示信息确定所述应用报文的目的地址；根据会话配置信息确定所述应用报文的源地址；所述会话配置信息用于指示为所述终端提供连接服务；
    所述收发单元，还用于发送第一报文至所述接收端，所述第一报文包括所述应用数据、所述应用报文的源地址以及所述应用报文的目的地址。
  33. 根据权利要求32所述的装置，其特征在于，所述指示信息是所述终端通过与所述用户面网元之间的协议层发送给所述用户面网元的。
  34. 根据权利要求32或33所述的装置，其特征在于，所述处理单元，用于：
    根据所述会话配置信息确定所述应用报文承载的会话的源地址；
    将所述应用报文承载的会话的源地址作为所述应用报文的源地址。
  35. 根据权利要求32-34中任一所述的装置，其特征在于，所述指示信息具体用于指示：根据应用报文中携带的连接标识确定接收端的目的地址；所述收发单元，用于：
    接收来自所述终端的所述应用报文，所述应用报文包括第一连接标识，所述第一连接标识对应的连接用于承载所述应用报文；
    所述处理单元，用于：
    根据所述应用报文中包括的第一连接标识，确定所述应用报文的目的地址。
  36. 根据权利要求35所述的装置，其特征在于，所述收发单元还用于：
    向所述终端发送连接标识信息，所述连接标识信息包括一个或多个连接标识，各所述连接标识分别用于标识所述用户面网元创建的连接；所述第一连接标识是所述终端从所述一个或多个连接标识中选择的。
  37. 根据权利要求32-36中任一所述的装置，其特征在于，所述收发单元，用于：
    接收无线接入网设备的转发报文，所述转发报文为所述终端发送给所述无线接入网设备的，所述转发报文包括所述应用报文。
  38. 根据权利要求37所述的装置，其特征在于，所述转发报文还包括所述应用报文的序列号；所述收发单元，还用于：
    向所述接入网设备反馈接收到的所述应用报文的序列号。
  39. 根据权利要求32-38中任一所述的装置，其特征在于，所述指示信息包括：所述终端对应的服务质量QoS需求信息、传输所述应用报文的报文协议信息、所述应用报文对应的报文协议类型。
  40. 根据权利要求39所述的装置，其特征在于，所述报文协议信息为超文本传输协议HTTP。
  41. 一种通信装置，其特征在于，包括：
    处理单元，用于确定指示信息，所述指示信息指示应用报文的接收端的目的地址；
    收发单元，用于发送所述指示信息至用户面网元；
    所述处理单元，还用于确定应用报文，所述应用报文包括应用数据，且不包括所述应用报文的源地址和目的地址
    所述收发单元，还用于发送所述应用报文至所述用户面网元。
  42. 根据权利要求41所述的装置，其特征在于，所述指示信息是所述终端通过与所述用户面网元之间的协议层发送给所述用户面网元的。
  43. 根据权利要求41或42所述的装置，其特征在于，所述指示信息具体用于指示：所述用户面网元根据应用报文中携带的连接标识确定接收端的目的地址；所述收发单元，用于：
    向所述用户面网元发送所述应用报文，所述应用报文包括第一连接标识，所述第一连接标识对应的连接用于承载所述应用报文。
  44. 根据权利要求43所述的装置，其特征在于，所述收发单元，用于：
    接收来自所述用户面网元的连接标识信息，所述连接标识信息包括一个或多个连接标识，各所述连接标识分别用于标识所述用户面网元创建的连接；所述第一连接标识是所述终端从所述一个或多个连接标识中选择的。
  45. 一种通信装置，其特征在于，包括：实现如权利要求1-8任一项或权利要求9或权利要求10-18任一项或权利要求19-22任一项所述的方法的功能模块。
  46. 一种通信装置，其特征在于，包括：至少一个处理器和存储器；
    所述存储器，用于存储计算机程序或指令；
    所述至少一个处理器，用于执行所述计算机程序或指令，以使得如权利要求1-8任一项或权利要求9或权利要求10-18任一项或权利要求19-22任一项所述的方法被执行。
  47. 一种芯片系统，其特征在于，所述芯片系统包括：处理电路；所述处理电路与存储介质耦合；
    所述处理电路，用于执行所述存储介质中的部分或者全部计算机程序或指令，当所述部分或者全部计算机程序或指令被执行时，用于实现如权利要求1-8任一项或权利要求9或权利要求10-18任一项或权利要求19-22任一项所述的方法。
  48. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有指令，当所述指令被计算机执行时，使得如权利要求1-8任一项或权利要求9或权利要求10-18任一项或权利要求19-22任一项所述的方法被执行。
  49. 一种包含计算机程序或指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得上述权利要求1-8任一项或权利要求9或权利要求10-18任一项或权利要求19-22任一项所述的方法被执行。
PCT/CN2022/121649 2021-12-24 2022-09-27 一种通信方法及装置 WO2023116102A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111599951.1A CN116347428A (zh) 2021-12-24 2021-12-24 一种通信方法及装置
CN202111599951.1 2021-12-24

Publications (1)

Publication Number Publication Date
WO2023116102A1 true WO2023116102A1 (zh) 2023-06-29

Family

ID=86875072

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/121649 WO2023116102A1 (zh) 2021-12-24 2022-09-27 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN116347428A (zh)
WO (1) WO2023116102A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101399838A (zh) * 2008-10-29 2009-04-01 成都市华为赛门铁克科技有限公司 报文处理方法、装置和系统
CN108353023A (zh) * 2015-11-28 2018-07-31 华为技术有限公司 一种信令报文处理方法和实体
WO2019137551A1 (zh) * 2018-01-15 2019-07-18 华为技术有限公司 一种会话管理方法及装置
CN110636151A (zh) * 2019-10-25 2019-12-31 新华三信息安全技术有限公司 一种报文处理方法、装置、防火墙及存储介质
CN113472651A (zh) * 2020-03-31 2021-10-01 华为技术有限公司 一种通信方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101399838A (zh) * 2008-10-29 2009-04-01 成都市华为赛门铁克科技有限公司 报文处理方法、装置和系统
CN108353023A (zh) * 2015-11-28 2018-07-31 华为技术有限公司 一种信令报文处理方法和实体
WO2019137551A1 (zh) * 2018-01-15 2019-07-18 华为技术有限公司 一种会话管理方法及装置
CN110636151A (zh) * 2019-10-25 2019-12-31 新华三信息安全技术有限公司 一种报文处理方法、装置、防火墙及存储介质
CN113472651A (zh) * 2020-03-31 2021-10-01 华为技术有限公司 一种通信方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MOTOROLA SOLUTIONS: "Overview of MCData IP connectivity service component", 3GPP DRAFT; S6-161448 WAS 161385 OVERVIEW OF IP CONNECTIVITY SERVICE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG6, no. Reno, Nevada, USA; 20161114 - 20161118, 13 November 2016 (2016-11-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051186778 *

Also Published As

Publication number Publication date
CN116347428A (zh) 2023-06-27

Similar Documents

Publication Publication Date Title
US11483680B2 (en) Method and system for multicast and broadcast services
WO2022206260A1 (zh) 地址信息发送方法、获取方法、装置、设备及介质
US11172054B2 (en) Cross-device segmentation offload
US9253015B2 (en) Transparent proxy architecture for multi-path data connections
CN108601043B (zh) 用于控制无线接入点的方法和设备
WO2021000827A1 (zh) 数据传输链路建立方法、装置以及计算机可读存储介质
JP4693908B2 (ja) ＷｉＢｒｏ端末におけるＩＰｖ６を支援するためのエミュレーション装置及びその方法
CN113206894B (zh) Dns服务器的发现方法、装置、计算机设备及存储介质
CN109417548B (zh) 封装媒体流量在基于数据报的传输层上的高效传输
US20230189368A1 (en) Associating transport identifiers with quality of service flows
WO2015161416A1 (zh) 一种报文传输方法、设备及通信系统
CN111418186A (zh) 用于路由终端与服务器之间初始化的会话的数据的方法
KR102397750B1 (ko) 앵커리스 백홀의 지원을 위한 gtp 터널
CN110771117B (zh) 一种采用面向id的网络的会话层通信
WO2023116102A1 (zh) 一种通信方法及装置
US20200137726A1 (en) Communications device and communication method
WO2022165787A1 (zh) 参数配置方法、装置、设备及存储介质
WO2021100178A1 (ja) 通信装置、通信システム、通信方法、及びプログラムが格納された非一時的なコンピュータ可読媒体
EP2139188B1 (en) A l2c method, device and system

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: 22909420

Country of ref document: EP

Kind code of ref document: A1