WO2019233381A1 - 用户面数据处理方法及装置 - Google Patents

用户面数据处理方法及装置 Download PDF

Info

Publication number
WO2019233381A1
WO2019233381A1 PCT/CN2019/089852 CN2019089852W WO2019233381A1 WO 2019233381 A1 WO2019233381 A1 WO 2019233381A1 CN 2019089852 W CN2019089852 W CN 2019089852W WO 2019233381 A1 WO2019233381 A1 WO 2019233381A1
Authority
WO
WIPO (PCT)
Prior art keywords
user plane
plane data
terminal device
access device
preset protocol
Prior art date
Application number
PCT/CN2019/089852
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 WO2019233381A1 publication Critical patent/WO2019233381A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling

Definitions

  • the present application relates to the field of mobile communication technology, and in particular, to a method and an apparatus for processing user plane data.
  • the 3rd Generation Partnership Project (3rd Generation, Partnership Project, 3GPP) released the next generation mobile communication network structure at the end of 2017, which is the 5G network architecture.
  • the 5G network architecture supports terminals accessing a 5G core network (CN) through a certain access technology to obtain services provided by the core network.
  • CN 5G core network
  • the user terminal accesses the 5G core network through a residential gateway (Residential Gateway).
  • the user terminal establishes one or more PDU sessions between the RG and the 5G core network element to access the core network.
  • Each PDU session corresponds to one or more channels, and each channel contains the channel between the user terminal (such as television) to the RG, the channel from the RG to the Fixed Access Network Gateway Function (FAGF), and the FAGF Channel to core network elements.
  • FAGF Fixed Access Network Gateway Function
  • multicast multicast technology
  • IPTV Internet Protocol Television
  • the RG receives an Internet Group Management Protocol (IGMP) join message sent by the user terminal and executes the message.
  • IGMP snooping binds the media access control (MAC) address of the user terminal to the multicast address.
  • the RG sends the IGMP join to the Access Network (AN) device in the channel between the RG and the FAGF, and the AN device performs IGMP snooping to bind the MAC address of the RG to the multicast address.
  • AN Access Network
  • the existing 5G network architecture is not suitable for multicast services.
  • the embodiments of the present application provide a user plane data processing method and device, which can solve the problems caused by using 5G protocol to encapsulate user plane data in a 5G system.
  • an embodiment of the present application provides a user plane data processing method, which is applied to an access device or a circuit system in the access device.
  • the method includes: the access device receives instruction information from a session management network element , And process user plane data between the access device and the terminal device according to the instruction information.
  • the indication information is used to indicate whether to use a preset protocol to process user plane data between the access device and the terminal device.
  • the access device after receiving the instruction information from the session management network element, the access device can process the user plane data between the access device and the terminal device according to the instruction information, which means that the access device Evidence-based processing of user plane data with terminal equipment.
  • the instruction information which means that the access device Evidence-based processing of user plane data with terminal equipment.
  • user protocol data needs to be processed with a preset protocol
  • user interface data with the terminal device is processed with a preset protocol
  • users are not processed with a preset protocol.
  • no preset protocol is used to process user-face data with terminal equipment, so that AN equipment can parse user-plane data of certain multicast services, such as multicast join messages, and will initiate user services for multicast services.
  • the probability of the user terminal successfully accessing the multicast service is improved.
  • the access device processes the user plane data between the access device and the terminal device according to the instruction information, and is specifically implemented as follows: according to the instruction information, the access device determines to use a preset protocol to process between the access device and the terminal device according to the instruction information.
  • User plane data, the user plane data sent by the terminal device is decapsulated using a preset protocol, or the user plane data sent by the access device to the terminal device is encapsulated using a preset protocol.
  • the access device processes user plane data between the access device and the terminal device according to the instruction information, and is specifically implemented as the following steps: according to the instruction information, the access device determines not to use a preset protocol to process the data between the access device and the terminal device.
  • the user plane data does not use a preset protocol to decapsulate the user plane data sent by the terminal device, or does not use the preset protocol to encapsulate the user plane data sent to the terminal device.
  • the access device processes user plane data between the access device and the terminal device according to the instruction information, and is specifically implemented as the following steps: according to the instruction information, the access device determines not to use a preset protocol to process the data between the access device and the terminal device.
  • User plane data establishing at least two user plane data channels with the terminal device.
  • the at least two user plane data channels include a first user plane data channel, and the first user plane data channel does not use a preset protocol to process user plane data between the access device and the terminal device.
  • the access device may further perform the following steps: the access device sends a request message to the session management network element, and the request message carries the data network identifier and / or Network slice selection auxiliary information NSSAI.
  • the access device receives the indication information from the session management network element, which is specifically implemented as follows: the access device receives the N2 message from the session management network element, and the N2 message carries the indication information.
  • the access device sends instruction information to the terminal device.
  • an embodiment of the present application provides a user plane data processing method.
  • the method is applied to a session management network element or a circuit system in the session management network element.
  • the method includes: the session management network element receives a request message from a terminal device , The session management network element receives the instruction information from the policy management network element according to the request message, and the session management network element sends the instruction information to the access device and / or the terminal device.
  • the indication information is used to indicate whether to use a preset protocol to process user plane data between the access device and the terminal device.
  • the session management network element sends the indication information to the access device.
  • the specific implementation is: the session management network element sends an N2 message to the access device, and the N2 message carries the indication information.
  • the session management network element sends the indication information to the terminal device, which is specifically implemented as follows: the session management network element sends a non-access stratum NAS message to the terminal device, and the NAS message carries the indication information.
  • an embodiment of the present application provides a user plane data processing method.
  • the method is applied to a terminal device or a circuit system in the terminal device.
  • the method includes: the terminal device receives instruction information from a session management network element or an access device. , And process user plane data between the access device and the terminal device according to the instruction information.
  • the indication information is used to indicate whether to use a preset protocol to process user plane data between the access device and the terminal device;
  • the terminal device processes the user plane data between the access device and the terminal device according to the instruction information
  • the specific implementation is: the terminal device determines to use a preset protocol to process the user plane data between the access device and the terminal device according to the instruction information.
  • the user plane data sent by the access device is decapsulated using a preset protocol, or the user plane data sent by the terminal device to the access device is encapsulated using a preset protocol.
  • the terminal device processes user plane data between the access device and the terminal device according to the instruction information, and may also be implemented as follows: The terminal device determines not to use a preset protocol to process the user plane data between the access device and the terminal device according to the instruction information. , The user plane data sent by the access device is not decapsulated using a preset protocol, or the user plane data sent to the access device is not encapsulated using a preset protocol.
  • the terminal device processes user plane data between the access device and the terminal device according to the instruction information, and may also be implemented as follows: The terminal device determines not to use a preset protocol to process the user plane data between the access device and the terminal device according to the instruction information. Establishing at least two user plane data channels between the access device and the access device, wherein the at least two user plane data channels include a first user plane data channel, and the first user plane data channel does not use a preset protocol to process the access device and the User plane data between terminal devices.
  • the terminal device may further perform the following steps: the terminal device sends a request message to the session management network element, and the request message carries the data network identifier and / Or network slice selection auxiliary information NSSAI.
  • the terminal device receives the indication information from the session management network element, which is specifically implemented as follows: the terminal device receives a non-access stratum NAS message from the session management network element, and the NAS message carries the indication information.
  • the request message carries at least one of a data network identifier, network slice selection assistance information NSSAI, and a terminal device identifier.
  • the preset protocol includes a fixed access control protocol, a user plane protocol, FCP, or an Ethernet point-to-point protocol, PPPoE.
  • the policy management network element includes a normalized data management network element UDM or a policy control function network element PCF.
  • the first user plane data channel is used to transmit control signaling of a multicast service, and the control signaling of the multicast service includes a multicast join message.
  • At least two user plane data channels correspond to one packet data unit PDU session.
  • an embodiment of the present application provides a user-plane data processing device.
  • the device is provided with a transceiver, a memory, and a processor.
  • the memory is used to store information including program instructions;
  • the transceiver is used to receive instruction information from the session management network element, and the instruction information is used to indicate whether to use a preset protocol to process the user plane between the access device and the terminal device Data;
  • a processor configured to process user plane data between the access device and the terminal device according to the instruction information.
  • the processor is configured to process user plane data between the access device and the terminal device according to the instruction information, and includes: determining to use a preset protocol to process the access device and the terminal device according to the instruction information. Between user plane data, the user plane data sent by the terminal device is decapsulated by using a preset protocol, or the user plane data sent by the access device to the terminal device is encapsulated by using a preset protocol.
  • the processor is configured to process user plane data between the access device and the terminal device according to the instruction information, including: determining to not use the preset protocol to process the access device and the terminal device according to the instruction information.
  • the user plane data between them does not use a preset protocol to decapsulate the user plane data sent by the terminal device, or does not use the preset protocol to encapsulate the user plane data sent to the terminal device.
  • the processor is configured to process user plane data between the access device and the terminal device according to the instruction information, including: determining to not use the preset protocol to process the access device and the terminal device according to the instruction information.
  • User plane data between them ; establish at least two user plane data channels with the terminal device, wherein at least two user plane data channels include a first user plane data channel, and the first user plane data channel does not use a preset protocol Processes user plane data between access devices and terminal devices.
  • the transceiver is further configured to send a request message to the session management network element, where the request message carries a data network identifier and / or network slice selection assistance information NSSAI.
  • the transceiver is configured to receive the indication information from the session management network element, including: receiving the N2 message from the session management network element, and the N2 message carries the indication information.
  • the transceiver is further configured to send instruction information to the terminal device.
  • an embodiment of the present application provides a user-plane data processing device.
  • the device is provided with a transceiver, a memory, and a processor.
  • the memory is used to store information including program instructions;
  • the transceiver is used to receive a request message from a terminal device; and the instruction information from the policy management network element is received according to the request message, and the instruction information is used to indicate whether to use a preset protocol processing User plane data between the access device and the terminal device; sending instruction information to the access device and / or the terminal device.
  • the transceiver is configured to send indication information to the access device, including: sending an N2 message to the access device, and the N2 message carries the indication information.
  • the transceiver is configured to send indication information to the terminal device, including: sending a non-access stratum NAS message to the terminal device, and the NAS message carries the indication information.
  • an embodiment of the present application provides a user-plane data processing device.
  • the device is provided with a transceiver, a memory, and a processor.
  • the memory is used to store information including program instructions.
  • the transceiver is used to receive information from the session management. Instruction information of a network element or an access device, the indication information is used to indicate whether to use a preset protocol to process user plane data between the access device and the terminal device; and the processor is used to process the access device and the terminal device according to the instruction information.
  • User plane data User plane data.
  • the processor is configured to process user plane data between the access device and the terminal device according to the instruction information, and includes: determining to use a preset protocol to process the access device and the terminal device according to the instruction information. Between user plane data, the user plane data sent by the access device is decapsulated by using a preset protocol, or the user plane data sent by the terminal device to the access device is encapsulated by using a preset protocol.
  • the processor is configured to process user plane data between the access device and the terminal device according to the instruction information, including: determining to not use the preset protocol to process the access device and the terminal device according to the instruction information.
  • the user plane data between them does not use a preset protocol to decapsulate the user plane data sent by the access device, or does not use the preset protocol to encapsulate the user plane data sent to the access device.
  • the processor is configured to process user plane data between the access device and the terminal device according to the instruction information, including: determining to not use the preset protocol to process the access device and the terminal device according to the instruction information.
  • User plane data between the two establish and access at least two user plane data channels between the access device, wherein at least two user plane data channels include a first user plane data channel, and the first user plane data channel does not adopt a preset
  • the protocol handles user plane data between the access device and the terminal device.
  • the request message carries at least one of a data network identifier, network slice selection assistance information NSSAI, and a terminal device identifier.
  • the preset protocol includes a fixed access control protocol, a user plane protocol, FCP, or an Ethernet point-to-point protocol, PPPoE.
  • the policy management network element includes a normalized data management network element UDM or a policy control function network element PCF.
  • the first user plane data channel is used to transmit control signaling of a multicast service, and the control signaling of the multicast service includes a multicast join message.
  • At least two user plane data channels correspond to one packet data unit PDU session.
  • an embodiment of the present application provides a user-plane data processing device, and the device has a function of implementing the method in any one of the first aspect, the second aspect, or the third aspect.
  • This function can be realized by hardware, and can also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a user plane data processing apparatus including: a processor and a memory; the memory is configured to store computer execution instructions; when the user plane data processing apparatus is running, the processor executes the computer execution stored in the memory; An instruction to cause the user plane data processing apparatus to execute the video encoding method according to any one of the first aspect, the second aspect, or the third aspect.
  • a user-plane data processing device including: a processor; the processor is configured to be coupled to the memory and read instructions in the memory, and then execute the first or second aspect or the third aspect according to the instructions according to the instructions.
  • a computer-readable storage medium stores instructions, and when the computer-readable storage medium is run on a computer, the computer can execute any of the first aspect, the second aspect, or the third aspect.
  • An item of user plane data processing method is provided.
  • a computer program product containing instructions which when run on a computer, enables the computer to execute the user-plane data processing method of any one of the first aspect, the second aspect, or the third aspect described above.
  • a circuit system includes a processing circuit configured to execute the user-plane data processing method according to any one of the first aspect, the second aspect, or the third aspect described above.
  • a user plane data processing system includes the user plane data processing device in the first aspect, the user plane data processing device in the second aspect, and the user plane data in the third aspect. Processing device.
  • FIG. 1 is a schematic structural diagram of a 5G system according to an embodiment of the present application.
  • FIG. 2 is a structural diagram of a user plane data processing system according to an embodiment of the present application.
  • FIG. 3 is a first schematic structural diagram of a user plane data processing apparatus according to an embodiment of the present application.
  • FIG. 4 is a first flowchart of a user plane data processing method according to an embodiment of the present application.
  • FIG. 5 is a second flowchart of a user plane data processing method according to an embodiment of the present application.
  • FIG. 6 is a second schematic structural diagram of a user plane data processing apparatus according to an embodiment of the present application.
  • the 5G network architecture involved in the embodiments of the present application is as follows:
  • the system includes a Network Slice Selection Function (NSSF), a Network Open Function (NEF), a Network Storage Function (NRF), and a Policy Control Function (Policy Control).
  • Function PCF
  • Unified Data Management UDM
  • Application Function AF
  • AUSF Authentication Server Function
  • Access and Mobility Management Function Core Access Access
  • Network elements or devices such as Mobility Management Function (AMF), Session Management Function (SMF), RG, AN, FAGF, User Plane Function (UPF), data network (DN) network element, etc.
  • AMF Mobility Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • DN data network
  • the user terminal accesses the RG wirelessly (for example, WIreless-FIdelity (WiFi)) or wired.
  • the RG communicates with the AMF through N1, the RG communicates with the V interface through the U interface, and communicates with the FAGF through the AN device.
  • N3 communicates with UPF
  • FAGP communicates with AMF through N2
  • UPF communicates with SMF through N4
  • UPF communicates with DN network elements through N6
  • SMF communicates with AMF through N11
  • SMF communicates with UDM through N10
  • SMF communicates with PCF through N7.
  • the user terminal involved in the embodiment of the present application may include various handheld devices, wearable devices, computing devices, or other processing devices connected to a modem with a communication function; and may also include a personal digital assistant (personal digital assistant (PDA) computer, tablet computer, laptop computer, machine type communication (MTC) terminal, user equipment (UE), etc.).
  • PDA personal digital assistant
  • MTC machine type communication
  • UE user equipment
  • the user terminal accesses the network through the RG.
  • the RG may have the function of a user terminal, or the user terminal may have the function of an RG.
  • the RG is referred to as a terminal device in this application.
  • the names of the network elements in FIG. 1 and the names of the interfaces between the network elements are only examples.
  • the names of the network elements or the interfaces between the network elements may be other names, or network elements. It may also be called an entity, which is not specifically limited in the embodiment of the present application. All or part of the network elements of the core network may be physical physical network elements or virtualized network elements, which is not limited herein.
  • words such as “first” and “second” are used to distinguish the same or similar items having substantially the same functions and functions.
  • words “first”, “second” and the like do not limit the number and execution order, and the words “first” and “second” are not necessarily different.
  • network element A when a certain network element (for example: network element A) obtains information from another network element (for example: network element B), it can mean that network element A receives information directly from network element B, or It means that network element A receives information from network element B through other network elements (for example, network element C).
  • network element C When network element A receives information from network element B through network element C, network element C can transparently transmit the information or process the information, such as carrying the information in different messages for transmission or filtering the information Only send the filtered information to network element A.
  • the network element A sends information to the network element B, which can refer to the network element A directly sending information to the network element B, or the network element A through other network elements (for example, the C network) Yuan) to send information to network element B.
  • the network element B can refer to the network element A directly sending information to the network element B, or the network element A through other network elements (for example, the C network) Yuan) to send information to network element B.
  • the network architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. With the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • an embodiment of the present application provides a user plane data processing system 20.
  • the user plane data processing system 20 includes: a terminal device 201, an access device 202, a session management network element 203, and a policy management network element 204.
  • the policy management network element 204 is configured to receive a request message from the session management network element, and determine the indication information according to the request message, and is also used to send the indication information to the session management network element.
  • the instruction information is used to indicate whether the terminal device 201 and the access device 202 use a preset protocol to process user plane data between the terminal device 201 and the access device 202.
  • the session management network element 203 is configured to receive the instruction information from the policy management network element 204 and send the instruction information to the terminal device 201 and / or the access device 202, and the instruction information is used to notify the terminal device 201 and / or the access Whether the device 202 uses a preset protocol to process user plane data between the terminal device 201 and the access device 202.
  • the terminal device 201 is configured to receive instruction information from the session management network element 203, and process user plane data between the terminal management device 201 and the access device 202 according to the instruction information.
  • the access device 202 is configured to receive instruction information from the session management network element 203, and process user plane data between the access management device and the terminal device 201 according to the instruction information.
  • the access device includes an access network device and an access network gateway device.
  • the access network device and the access network gateway device may be integrated into a unified device or may be two separate devices. That is, the access device may have the function of an access network gateway device, or the access device may have the functions of both an access network gateway device and an access network device.
  • the access network device may be, for example, the AN shown in FIG. 1 Device, the access network gateway device may be, for example, the FAGF shown in FIG. 1.
  • FIG. 2 only shows the connection relationship between the devices related to the technical solution of the embodiment of the present application, and there may be other connection relationships between the devices, which is not repeated here.
  • the user plane data processing system provided in the embodiment of the present application can be applied to the 5G system shown in FIG. 1 or a subsequent evolved system.
  • the above-mentioned terminal device 201 corresponds to
  • the network element or entity may be the RG in FIG. 1
  • the network element or entity corresponding to the access device 202 may be the FAGF in FIG. 1.
  • the The access device may be a FAGF with the function of an AN device.
  • the access device in this embodiment of the present application may be a FAGF.
  • the network element or entity corresponding to the foregoing session management network element 203 may be FIG. 1
  • the network element or entity corresponding to the foregoing policy management network element may be a UDM or a PCF in FIG. 1.
  • the terminal device, access device, session management network element, or policy management network element in FIG. 2 may be implemented by multiple devices, or may be implemented by one device, for example, may be implemented as different functional modules in one device.
  • This embodiment of the present application does not specifically limit this.
  • the foregoing function module may be a network element in a hardware device, a software function running on a hardware device, or a virtualized function instantiated on a platform (for example, a cloud platform).
  • FIG. 3 is a schematic diagram of a hardware structure of a communication device according to an embodiment of the present application.
  • the communication device 300 includes at least one processor 301, a communication line 302, a memory 303, and at least one communication interface 304.
  • the processor 301 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the execution of the program program of the present application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 302 may include a path for transmitting information between the aforementioned components.
  • the communication interface 304 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 303 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions
  • the dynamic storage device can also be electrically erasable and programmable read-only memory (EEPROM-ready-only memory (EEPROM)), compact disc (read-only memory (CD-ROM)) or other optical disk storage, optical disk storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
  • the memory may exist independently, and is connected to the processor through the communication line 302. The memory can also be integrated with the processor.
  • the memory 303 is configured to store computer execution instructions for executing the solutions in the embodiments of the present application, and the processor 301 controls the execution.
  • the processor 301 is configured to execute computer execution instructions stored in the memory 303, so as to implement the user-plane data processing method provided in the following embodiments of the present application.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
  • the processor 301 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 3.
  • the communication device 300 may include multiple processors. Each of these processors can be a single-CPU processor or a multi-CPU processor.
  • a processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).
  • FIG. 3 only shows an exemplary hardware structure diagram of a communication device.
  • the communication device 300 may further include other components. Limitation.
  • the above-mentioned communication device 300 may be a general-purpose device or a special-purpose device.
  • the communication device 300 may be a device having a similar structure as in FIG. 3.
  • the embodiment of the present application does not limit the type of the communication device 300.
  • the user plane data processing method provided in the embodiment of the present application is applied to a PDU session management process.
  • the user plane data processing method provided in the embodiment of the present application will be specifically described below with reference to FIGS. 1 to 3.
  • a UDM is used as a policy management network element in the user plane data processing system shown in FIG. 2.
  • the user plane data processing method provided in the embodiment of the present application includes the following steps:
  • RG sends a request message to the SMF.
  • the SMF receives a request message from the RG.
  • the request message carries data network identification and / or network slice selection assistance information (Network Assistant Selection Information (NSSAI)).
  • NSSAI Network Assistant Selection Information
  • the aforementioned data network identifier is a data network name (data network name, DNN).
  • the data network identifier may also include, for example, a data network number, which is not limited in the embodiment of the present application.
  • the data network identifier and / or NSSAI are related to the service type.
  • the service type can be divided into a multicast service and a non-multicast service according to whether data related to the multicast service is transmitted between the RG and the UPF. business. Therefore, the RG can notify the SMF of the current service type through a request message (carrying a data network identification and / or NSSAI).
  • the request message may also carry other information associated with the service type, for example, the request message may carry a terminal device identifier.
  • the RG sends a request message to the FAGF, and the FAGF sends the request message to the SMF.
  • the SMF receives instruction information from the UDM according to the request message.
  • the indication information is used to indicate whether to use a preset protocol to process user plane data between FAGF and RG.
  • the preset protocols include a fixed access control protocol (Fixed Access Control Protocol, User Plane Protocol, FCP UP) or an Ethernet point-to-point protocol (Point-to-Point Protocol Over Ethernet, PPPoE).
  • pre-configuration information is stored in the UDM, and the UDM may query the pre-configuration information according to the information contained in the request message, so as to determine the indication information capable of adapting to the current service type, and the SMF may obtain the indication information from the UDM.
  • the manner in which the SMF acquires the indication information may be implemented as follows: The SMF sends an acquisition message to the UDM, and the UDM determines the indication information according to the acquisition message, wherein the acquisition message carries at least one of a data network identifier, an NSSAI, and a terminal device identifier.
  • the acquisition message is a session management subscription request, and the SMF obtains the instruction information issued by the UDM by initiating a session management subscription request to the UDM.
  • the foregoing pre-configured information includes a correspondence between at least one of a data network identifier, an NSSAI, and a terminal device identifier and a user plane data processing method.
  • a data network identifier As shown in Tables 1 to 3, the pre-configuration information stored in the UDM is shown. In the following, Table 1 is used as an example for detailed description.
  • different processing methods are used for user plane data of different types of services.
  • Service types can be divided into multicast services and non-multicast services.
  • a preset protocol can be used to encapsulate / decapsulate user plane data between FAGF and RG.
  • the user plane data between the RG and the FAGF is not encapsulated / decapsulated with a preset protocol, so that the AN device can still identify the case that the AN device lacks a protocol stack that handles the preset protocol.
  • a multicast join message (for example, an IGMP join message) sent by the RG, and performing IGMP snooping to add a user terminal (such as a TV) requesting a multicast service to a multicast group (also referred to herein as a multicast group).
  • User terminals can access multicast services.
  • the pre-configuration information includes the correspondence between DNN and user-plane data processing methods.
  • the user-plane data processing method corresponding to DNN1 is to process user-plane data without using a preset protocol
  • DNN2 corresponds to user-plane data
  • the processing method is not to use a preset protocol to process user plane data
  • the DNN3 corresponding user plane data processing method is to use a preset protocol to process user plane data.
  • the user plane data processing method can be known from the DNN, that is, when the UDM receives the acquisition message sent from the SMF, it can determine the RG and / or FAGF based on the DNN carried in the acquisition message and the pre-configured information shown in Table 1.
  • User plane data processing method For example, the TV in FIG. 1 sends a request message to the SMF through the RG.
  • the request message is used to request the multicast service of the network element corresponding to DNN1 in the DN.
  • the request message carries DNN1, and the SMF sends an acquisition message to the UDM.
  • UDM can determine that the network element corresponding to DNN1 provides multicast services, and FAGF and / or does not use a preset protocol to process user plane data between RG and FAGF, that is, FAGF
  • the user plane data between the RG and the RG is not processed by a preset protocol, and the user plane data between the RG and the FAGF is not processed by the RG.
  • the pre-configuration information shown in Table 2 includes the correspondence between NSSAI3 and user plane data processing methods.
  • different NSSAI3s correspond to different types of services, and user plane data of different types of services adopt different processing methods.
  • the user plane data processing method can be known from NSSAI3, that is, when the UDM receives the acquisition message sent from the SMF, it can determine the user plane of FAGF and RG according to the NSSAI3 carried in the acquisition message and the pre-configured information shown in Table 2. Data processing methods.
  • the pre-configuration information shown in Table 3 includes a correspondence between a terminal device identifier (for example, a MAC address) and a user plane data processing method.
  • a terminal device identifier for example, a MAC address
  • different terminal devices correspond to different types of services
  • user plane data of different types of services adopt different processing methods.
  • the user plane data processing method can be known from the terminal device identifier. That is, when the UDM receives the acquisition message sent from the SMF, it can determine the user plane based on the terminal device identifier carried in the acquisition message and the pre-configured information shown in Table 3. Data processing methods.
  • the UDM determines the user plane data processing method according to the at least two identifiers carried by the acquisition message. For example, the acquisition message from the SMF carries the data network identifier and NSSAI, and the UDM determines the user plane data processing method based on the data network identifier, the NSSAI, and the pre-configured information shown in Tables 1 and 2 in the acquisition message.
  • the above only uses the UDM to store the pre-configuration information in a table format as an example for description.
  • the UDM can also store the pre-configuration information in other formats, which will be collectively described here and will not be described in detail below.
  • the SMF sends instruction information to the FAGF.
  • the FAGF receives the instruction information sent from the SMF.
  • the SMF sends an N2 message to the FAGF, and the N2 message carries the indication information.
  • the N2 message may be an N2 session management information cell, and the N2 session management information cell carries indication information.
  • the SMF may send an N2 session management information cell to the AMF, and the AMF sends an N2 session management information cell to the FAGF.
  • the SMF sends instruction information to the RG.
  • the RG receives the instruction information sent from the SMF.
  • the SMF can send instruction information to the RG in the following two ways.
  • Method 1 The SMF sends a non-access stratum (NAS) message to the RG, and the NAS message carries the indication information.
  • the NAS message is a session establishment acceptance message (PDU session establishment acceptance).
  • Method 2 The SMF sends instruction information to the FAGF, and the FAGF sends the instruction information to the RG.
  • the SMF sends an N2 message to the FAGF, where the N2 message carries the instruction information (that is, step S403 is performed first), and then the AGF sends AN signaling to the RG, and the AN signaling carries the instruction information.
  • the execution order of S403 and S404 is not limited, that is, the SMF can send instruction information to the RG first, and then send the instruction information to the FAGF, or send the instruction information to the FAGF, and then send the instruction information to the RG.
  • S403 and S404 can also be performed at the same time.
  • the FAGF processes user plane data between the FAGF and the RG according to the instruction information.
  • S405 can be implemented as the following steps:
  • step S405a and FAGF determine whether to use a preset protocol to process user plane data between FAGF and RG according to the instruction information. If it is determined to use a preset protocol to process user plane data between FAGF and RG, step S405b is performed. Assuming that the protocol processes user plane data between FAGF and RG, step S405c is performed.
  • FAGF uses a preset protocol to decapsulate the user plane data sent by the RG, or uses a preset protocol to encapsulate the user plane data sent to the RG.
  • the function of processing user plane data by using a preset protocol can be implemented by adding a protocol stack for FAGF.
  • Encapsulating user plane data by using a preset protocol includes adding a header to the user plane data. This embodiment of the present application does not limit this. .
  • the FAGF uses a preset protocol to process user plane data with the RG
  • the FAGF establishes a user plane data channel with the RG, and the user plane data channel processes the user plane data with a preset protocol.
  • FAGF does not use a preset protocol to decapsulate user plane data sent by RG, or FAGF does not use a preset protocol to encapsulate user plane data sent to RG.
  • the FAGF when the FAGF does not use a preset protocol to process user plane data with the RG, the FAGF establishes at least two user plane data channels with the RG.
  • the at least two user plane data channels may be channels based on a virtual local area network (VLAN), or Ethernet, or an Internet Protocol (IP), which is not limited in this application.
  • At least two user plane data channels correspond to a PDU session between RG and UPF, that is, at least two user plane data channels are associated with a PDU session between RG and UPF, and RG communicates with UPF through at least two user plane data channels. For communication.
  • At least two user plane data channels include channels that do not use a preset protocol to process user plane data, and are referred to as a first user plane data channel.
  • the first user plane data channel does not use a preset protocol to process user plane data between AGF and RG.
  • the first user plane data channel is used to transmit control signaling of a multicast service.
  • the control signaling of the multicast service includes, for example, the foregoing. Multicast join message.
  • the RG sends to the FAGF user plane data (such as a multicast join message) that is not encapsulated by a preset protocol, and the user plane data It is transmitted in the first user plane data channel.
  • the FAGF user plane data such as a multicast join message
  • the AN device can identify the multicast join message and add the user terminal (such as a TV) that initiated the multicast join message to In the broadcast group, on the other side of the first user plane data channel, after FAGF receives the user plane data that is not encapsulated with a preset protocol, correspondingly, the user plane data sent by the RG is not decapsulated using a preset protocol. Therefore, the user terminal can perform a multicast service after being added to the multicast group.
  • the user terminal such as a TV
  • FAGF does not use a preset protocol to encapsulate the user plane data sent to the RG, and the user plane data is transmitted in the first user plane data channel.
  • the RG receives user plane data that is not encapsulated with a preset protocol, correspondingly, the user plane data sent by FAGF is not decapsulated using a preset protocol.
  • At least two user plane data channels also include a second user plane data channel between FAGF and RG.
  • the second user plane data channel uses a preset protocol to process user plane data between FAGF and RG.
  • the second user plane data channel uses User plane data for transmitting non-multicast services or control signaling for transmitting multicast services.
  • the RG may send control signaling of the multicast service, such as a multicast join message, in both user plane data channels.
  • the FAGF receives a control signal from both user plane data channels. Only one copy of control signaling is sent to the core network element.
  • a user plane data channel between the FAGF and the RG is established, and the user plane data channel transmitted in the user plane data channel The data packet does not need to be processed by a preset protocol.
  • the RG processes user plane data between the FAGF and the RG according to the instruction information.
  • S405 can be implemented as the following steps:
  • RG determines whether to use a preset protocol to process user plane data between FAGF and RG according to the instruction information. If it is determined to use a preset protocol to process user plane data between FAGF and RG, step S406b is performed. Assuming that the protocol processes user plane data between FAGF and RG, step S406c is performed.
  • the RG uses a preset protocol to decapsulate user plane data sent by the FAGF, or uses a preset protocol to encapsulate user plane data sent to the FAGF.
  • the function of processing user plane data using a preset protocol can be implemented by adding a protocol stack to the RG.
  • Encapsulating user plane data using a preset protocol includes adding a header to the user plane data, and the embodiment of this application does not limit this.
  • RG uses a preset protocol to process user plane data with FAGF
  • RG establishes a user plane data channel with FAGF.
  • This user plane data channel uses a preset protocol to process user plane data.
  • This user plane data channel is used for User plane data for non-multicast services transmitted with FAGF.
  • RG does not use a preset protocol to decapsulate user plane data sent by FAGF, or RG does not use a preset protocol to encapsulate user plane data sent to FAGF.
  • the RG In the case that the RG does not use a preset protocol to process user plane data with the FAGF, the RG establishes at least two user plane data channels with the FAGF.
  • At least two user plane data channels correspond to one PDU session between RG and UPF, that is, at least two user plane data channels are associated with a PDU session between RG and UPF, and RG communicates with at least two user plane data channels.
  • UPF communicates.
  • At least two user plane data channels include a first user plane data channel, and the first user plane data channel does not use a preset protocol to process user plane data between FAGF and RG.
  • the optional first user plane data channel is used to transmit control signaling of a multicast service, and the control signaling of the multicast service includes, for example, the foregoing multicast join message.
  • the RG sends user plane data (such as a multicast join message) to the FAGF that is not encapsulated by a preset protocol, and the multicast join message is transmitted in the first user plane data channel.
  • the AN device can identify the multicast join message and join the user terminal (such as a TV) that initiated the multicast join message to the multicast group.
  • the user terminal is being After joining a multicast group, multicast services can be performed.
  • the description of the user plane data transmission in the downlink direction refer to the description of the user plane data transmission in the downlink direction of the above-mentioned FAGF, which is not repeated here.
  • S404 and S406 may be executed first, then S403 and S405 may be executed, and S403 and S404 may be executed before S405 and S406.
  • the execution sequence shown in the method flow of FIG. 4 is only an example.
  • the access device after receiving the instruction information from the session management network element, can process the user plane data between the terminal device and the terminal device according to the instruction information, where the instruction information is used to indicate whether Adopting a preset protocol to process user plane data with the terminal device, which means that when the access device processes the user plane data between the terminal device and the terminal device, it is necessary to use a preset protocol to process the user plane data in the scenario
  • the user-side data between the terminal device and the terminal device are processed by using a preset protocol.
  • the user-side data between the terminal device and the terminal device are not processed.
  • the user plane data of the multicast service such as the multicast join message, further improves the access rate of the multicast service.
  • whether to use a preset protocol to process user plane data can be adapted according to the service type, which can meet different service requirements of users.
  • the embodiment of the present application also provides another method for processing user plane data.
  • the method flow is shown in FIG. 5.
  • the method includes the following steps:
  • the RG sends a request message to the SMF.
  • the SMF receives instruction information from the PCF according to the request message.
  • the SMF sends instruction information to the FAGF.
  • the SMF sends instruction information to the RG.
  • the FAGF processes user plane data between the FAGF and the RG according to the instruction information.
  • S505 can be implemented as the following steps:
  • step S505a and FAGF determine whether to use a preset protocol to process user plane data between FAGF and RG according to the instruction information. If it is determined to use a preset protocol to process user plane data between FAGF and RG, step S505b is performed. Assuming that the protocol processes user plane data between FAGF and RG, step S505c is performed.
  • S505b and FAGF use a preset protocol to decapsulate the user plane data sent by the RG, or use a preset protocol to encapsulate the user plane data sent to the RG.
  • S505c and FAGF do not use a preset protocol to decapsulate user plane data sent by RG, or FAGF does not use a preset protocol to encapsulate user plane data sent to RG.
  • the RG processes user plane data between the FAGF and the RG according to the instruction information.
  • S405 can be implemented as the following steps:
  • RG determines whether to use a preset protocol to process user plane data between FAGF and RG according to the instruction information. If it is determined to use a preset protocol to process user plane data between FAGF and RG, step S506b is performed. Assuming that the protocol processes user plane data between FAGF and RG, step S506c is performed.
  • RG uses a preset protocol to decapsulate user plane data sent by FAGF, or uses a preset protocol to encapsulate user plane data sent to FAGF.
  • RG does not use a preset protocol to decapsulate user plane data sent by FAGF, or RG does not use a preset protocol to encapsulate user plane data sent to FAGF.
  • a method for processing user plane data is provided.
  • a PDU session management process for example, in a PDU session establishment process, if the access device does not receive an instruction from the session management network element Information, the access device uses a preset protocol to process user plane data with the terminal device. Similarly, if the terminal device does not receive instruction information from the session management network element, the terminal device also uses a preset protocol to process and access User plane data between devices.
  • the network element in the embodiment of the present application includes a hardware structure and / or a software module corresponding to each function.
  • the embodiments of this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present application.
  • the network element may be divided into functional units according to the foregoing method examples.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit.
  • the above integrated unit may be implemented in the form of hardware or in the form of software functional unit. It should be noted that the division of the units in the embodiments of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • FIG. 6 shows a schematic block diagram of a user plane data processing apparatus provided in an embodiment of the present application.
  • the user plane data processing apparatus may be the foregoing access device, terminal device, or session management network element.
  • the user plane data processing apparatus 600 may exist in the form of software, or may be a chip that can be used in a device.
  • the user plane data processing apparatus 600 includes a processing unit 602 and a communication unit 603.
  • the processing unit 602 may be used to support the access device to execute S405a, S405b, S405c in FIG. 4, S505a, S505b, S505c, etc. in FIG. 5, and / or used herein Other processes of the described scheme.
  • the communication unit 603 is used to support communication between the access device and other network elements (for example, the terminal device 201 in FIG. 2), for example, to support the access device to perform S401, S403, and S404 in FIG. 4, and S501 in FIG. , S503, S504, etc.
  • the processing unit 602 may be used to support the terminal device to execute S406a, S406b, S406c, S506a, S506b, S506c, etc. in FIG. 4, and / or other methods used in the scheme described herein. process.
  • the communication unit 603 is used to support communication between the terminal device and other network elements (for example, the access device 202 in FIG. 2), for example, to support the terminal device to perform S401 and S404 in FIG. 4 and S501 and S504 in FIG. 5 .
  • the processing unit 602 may be used to support the session management network element to perform the action of determining the indication information in the above embodiments, and / or other processes used in the solutions described herein.
  • the communication unit 603 is configured to support communication between the session management network element and other network elements (such as the terminal device 201 in FIG. 2), for example, support the session management network element to perform S401, S402, and S403 in FIG. 4, and FIG. 5 S501, S502, S503, etc.
  • the user plane data processing apparatus 600 may further include a storage unit 601 for storing program codes and data of the user plane data processing apparatus 600.
  • the data may include, but is not limited to, original data or intermediate data.
  • the processing unit 602 may be a controller or the processor 301 or the processor 305 shown in FIG. 3, for example, it may be a central processing unit (Central Processing Unit), a general-purpose processor, and digital signal processing ( Digital Signal Processing (DSP), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any of them combination. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of this application.
  • the processor may also be a combination that realizes computing functions, for example, a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication unit 603 may be a transceiver, a transceiver circuit, or the communication interface 304 shown in FIG. 3 and the like.
  • the storage unit 601 may be a memory 303 shown in FIG. 3.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, a computer, a server, or a data center. Transmission to another website site, computer, server, or data center through wired (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like that includes one or more available medium integration.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a Digital Video Disc (DVD)), or a semiconductor medium (for example, a solid state disk (Solid State Disk, SSD)) )Wait.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a Digital Video Disc (DVD)
  • DVD Digital Video Disc
  • semiconductor medium for example, a solid state disk (Solid State Disk, SSD)
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, the indirect coupling or communication connection of the device or unit, and may be electrical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, which may be located in one place, or may be distributed to multiple network devices (for example, Terminal device). Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each functional unit may exist independently, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware, or in the form of hardware plus software functional units.

Landscapes

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

Abstract

本申请实施例提供一种用户面数据处理方法及装置，涉及通信技术领域。该方法包括：接入设备接收来自会话管理网元的指示信息，并根据指示信息处理接入设备和终端设备之间的用户面数据。其中，指示信息用于指示是否采用预设协议处理接入设备和终端设备之间的用户面数据。

Description

用户面数据处理方法及装置
本申请要求于2018年6月4日提交国家知识产权局、申请号为201810562638.2、发明名称为“用户面数据处理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及用户面数据处理方法及装置。
背景技术
第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)在2017年底发布了下一代移动通信网络结构，即5G网络架构。
5G网络架构支持终端通过一定的接入技术接入5G核心网(Core network，CN)，以获取核心网提供的业务。其中，在)用户终端通过固定宽带接入网络接入核心网的场景中，用户终端通过家庭网关(Residential Gateway，RG)接入5G核心网。具体的，用户终端通过RG与5G核心网网元之间建立一个或多个PDU会话以接入核心网。每个PDU会话对应一个或多个通道，每一通道包含用户终端(例如电视(television))到RG间的通道、RG到固定接入网网关功能(Fixed Access Gateway Function，FAGF)的通道以及FAGF到核心网网元间的通道。
在5G网络架构中，对于一些带宽占用较大的业务，可使用组播(多播)技术来减少冗余流量，以降低网络负载。以网络协议电视(Internet Protocol Television，IPTV)业务为例，在现有的IPTV机制中，RG接收到用户终端发送的因特网组管理协议(Internet Group Management Protocol，IGMP)加入(join)消息，并执行IGMP窥探(snooping)，将该用户终端的媒体接入控制(Media Access Control，MAC)地址与多播地址绑定。之后，RG向RG与FAGF间通道中的接入网(Access Network，AN)设备发送该IGMP join，由AN设备执行IGMP snooping，将RG的MAC地址与多播地址绑定。如此，将该用户终端加入组播组，从而在后续该用户终端可进行多播业务。
然而，在一些场景下，现有的5G网络架构不适用于组播业务。
发明内容
本申请实施例提供用户面数据处理方法及装置，可以解决在5G系统中采用5G协议封装用户面数据带来的问题。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，本申请实施例提供一种用户面数据处理方法，该方法应用于接入设备或者接入设备中的电路系统中，该方法包括：接入设备接收来自会话管理网元的指示信息，并根据指示信息处理接入设备和终端设备之间的用户面数据。其中，指示信息用于指示是否采用预设协议处理接入设备和终端设备之间的用户面数据。
本申请实施例提供的用户面数据处理方法，接入设备在接收来自会话管理网元的指示信息后，可以根据指示信息处理与终端设备之间的用户面数据，也就意味着，接入设备有所依据的处理与终端设备之间的用户面数据，在需采用预设协议处理用户面 数据的场景下采用预设协议处理与终端设备间的用户面数据，在不需预设协议处理用户面数据的场景下不采用预设协议处理与终端设备间的用户面数据，使得AN设备可以解析某些多播业务的用户面数据，如组播加入消息，并将发起多播业务的用户终端加入相应的多播组，从而用户终端成功访问多播业务的概率有所提升。
可选的，接入设备根据指示信息处理接入设备和终端设备之间的用户面数据，具体实现为如下步骤：接入设备根据指示信息确定采用预设协议处理接入设备和终端设备之间的用户面数据，则采用预设协议解封装终端设备发送的用户面数据，或者采用预设协议封装接入设备向终端设备发送的用户面数据。
或者，接入设备根据指示信息处理接入设备和终端设备之间的用户面数据，具体实现为如下步骤：接入设备根据指示信息确定不采用预设协议处理接入设备和终端设备之间的用户面数据，则不采用预设协议解封装终端设备发送的用户面数据，或者不采用预设协议封装向终端设备发送的用户面数据。
或者，接入设备根据指示信息处理接入设备和终端设备之间的用户面数据，具体实现为如下步骤：接入设备根据指示信息确定不采用预设协议处理接入设备和终端设备之间的用户面数据，建立和终端设备之间的至少两个用户面数据通道。其中，至少两个用户面数据通道包含第一用户面数据通道，第一用户面数据通道不采用预设协议处理接入设备和终端设备之间的用户面数据。
在一种可能的设计中，在接入设备接收来自会话管理网元的指示信息之前，还可以执行如下步骤：接入设备向会话管理网元发送请求消息，请求消息携带数据网络标识和/或者网络切片选择辅助信息NSSAI。
在一种可能的设计中，接入设备接收来自会话管理网元的指示信息，具体实现为如下步骤：接入设备接收来自会话管理网元的N2消息，N2消息携带指示信息。
在一种可能的设计中，还可执行如下步骤：接入设备向终端设备发送指示信息。
第二方面，本申请实施例提供一种用户面数据处理方法，该方法应用于会话管理网元或者会话管理网元中的电路系统，该方法包括：会话管理网元接收来自终端设备的请求消息，会话管理网元根据请求消息接收来自策略管理网元的指示信息，会话管理网元向接入设备和/或终端设备发送指示信息。其中，指示信息用于指示是否采用预设协议处理接入设备和终端设备之间的用户面数据。
在一种可能的设计中，会话管理网元向接入设备发送指示信息，具体实现为：会话管理网元向接入设备发送N2消息，N2消息携带指示信息。
在一种可能的设计中，会话管理网元向终端设备发送指示信息，具体实现为：会话管理网元向终端设备发送非接入层NAS消息，NAS消息携带指示信息。
第三方面，本申请实施例提供一种用户面数据处理方法，该方法应用于终端设备或者终端设备中的电路系统，该方法包括：终端设备接收来自会话管理网元或者接入设备的指示信息，并根据指示信息处理接入设备和终端设备之间的用户面数据。其中，指示信息用于指示是否采用预设协议处理接入设备和终端设备之间的用户面数据；
可选的，终端设备根据指示信息处理接入设备和终端设备之间的用户面数据，具体实现为：终端设备根据指示信息确定采用预设协议处理接入设备和终端设备之间的用户面数据，则采用预设协议解封装接入设备发送的用户面数据，或者采用预设协议 封装终端设备向接入设备发送的用户面数据。
或者，终端设备根据指示信息处理接入设备和终端设备之间的用户面数据，还可以实现为：终端设备根据指示信息确定不采用预设协议处理接入设备和终端设备之间的用户面数据，则不采用预设协议解封装接入设备发送的用户面数据，或者不采用预设协议封装向接入设备发送的用户面数据。
或者，终端设备根据指示信息处理接入设备和终端设备之间的用户面数据，还可以实现为：终端设备根据指示信息确定不采用预设协议处理接入设备和终端设备之间的用户面数据，建立和接入设备之间的至少两个用户面数据通道，其中，至少两个用户面数据通道包含第一用户面数据通道，第一用户面数据通道不采用预设协议处理接入设备和终端设备之间的用户面数据。
在一种可能的设计中，在终端设备接收来自会话管理网元或者接入设备的指示信息之前，还可以执行如下步骤：终端设备向会话管理网元发送请求消息，请求消息携带数据网络标识和/或者网络切片选择辅助信息NSSAI。
在一种可能的设计中，终端设备接收来自会话管理网元的指示信息，具体实现为：终端设备接收来自会话管理网元的非接入层NAS消息，NAS消息携带指示信息。
在第一方面或第二方面或第三方面的一种可能的设计中，请求消息携带数据网络标识、网络切片选择辅助信息NSSAI、终端设备标识中的至少一个。
在第一方面或第二方面或第三方面的一种可能的设计中，预设协议包括固定接入控制协议用户面协议FCP UP或者以太网点到点协议PPPoE。
在第二方面的一种可能的设计中，策略管理网元包括归一化数据管理网元UDM或者策略控制功能网元PCF。
在第一方面或第三方面的一种可能的设计中，第一用户面数据通道用于传输多播业务的控制信令，多播业务的控制信令包括组播加入消息。
在第一方面或第三方面的一种可能的设计中，至少两个用户面数据通道对应一个分组数据单元PDU会话。
第四方面，本申请实施例提供一种用户面数据处理装置，装置设置有收发器、存储器和处理器。其中，存储器，用于存储包括程序指令的信息；收发器，用于接收来自会话管理网元的指示信息，指示信息用于指示是否采用预设协议处理接入设备和终端设备之间的用户面数据；处理器，用于根据指示信息处理接入设备和终端设备之间的用户面数据。
在一种可能的设计中，处理器，用于根据指示信息处理接入设备和终端设备之间的用户面数据，包括：用于根据指示信息确定采用预设协议处理接入设备和终端设备之间的用户面数据，则采用预设协议解封装终端设备发送的用户面数据，或者采用预设协议封装接入设备向终端设备发送的用户面数据。
在一种可能的设计中，处理器，用于根据指示信息处理接入设备和终端设备之间的用户面数据，包括：用于根据指示信息确定不采用预设协议处理接入设备和终端设备之间的用户面数据，则不采用预设协议解封装终端设备发送的用户面数据，或者不采用预设协议封装向终端设备发送的用户面数据。
在一种可能的设计中，处理器，用于根据指示信息处理接入设备和终端设备之间 的用户面数据，包括：用于根据指示信息确定不采用预设协议处理接入设备和终端设备之间的用户面数据；建立和终端设备之间的至少两个用户面数据通道，其中，至少两个用户面数据通道包含第一用户面数据通道，第一用户面数据通道不采用预设协议处理接入设备和终端设备之间的用户面数据。
在一种可能的设计中，收发器，还用于向会话管理网元发送请求消息，请求消息携带数据网络标识和/或者网络切片选择辅助信息NSSAI。
在一种可能的设计中，收发器，用于接收来自会话管理网元的指示信息，包括：用于接收来自会话管理网元的N2消息，N2消息携带指示信息。
在一种可能的设计中，收发器，还用于向终端设备发送指示信息。
第五方面，本申请实施例提供一种用户面数据处理装置，装置设置有收发器、存储器和处理器。其中，存储器，用于存储包括程序指令的信息；收发器，用于接收来自终端设备的请求消息；根据请求消息接收来自策略管理网元的指示信息，指示信息用于指示是否采用预设协议处理接入设备和终端设备之间的用户面数据；向接入设备和/或终端设备发送指示信息。
在一种可能的设计中，收发器，用于向接入设备发送指示信息，包括：用于向接入设备发送N2消息，N2消息携带指示信息。
在一种可能的设计中，收发器，用于向终端设备发送指示信息，包括：用于向终端设备发送非接入层NAS消息，NAS消息携带指示信息。
第六方面，本申请实施例提供一种用户面数据处理装置，装置设置有收发器、存储器和处理器，其中，存储器，用于存储包括程序指令的信息；收发器，用于接收来自会话管理网元或者接入设备的指示信息，指示信息用于指示是否采用预设协议处理接入设备和终端设备之间的用户面数据；处理器，用于根据指示信息处理接入设备和终端设备之间的用户面数据。
在一种可能的设计中，处理器，用于根据指示信息处理接入设备和终端设备之间的用户面数据，包括：用于根据指示信息确定采用预设协议处理接入设备和终端设备之间的用户面数据，则采用预设协议解封装接入设备发送的用户面数据，或者采用预设协议封装终端设备向接入设备发送的用户面数据。
在一种可能的设计中，处理器，用于根据指示信息处理接入设备和终端设备之间的用户面数据，包括：用于根据指示信息确定不采用预设协议处理接入设备和终端设备之间的用户面数据，则不采用预设协议解封装接入设备发送的用户面数据，或者不采用预设协议封装向接入设备发送的用户面数据。
在一种可能的设计中，处理器，用于根据指示信息处理接入设备和终端设备之间的用户面数据，包括：用于根据指示信息确定不采用预设协议处理接入设备和终端设备之间的用户面数据；建立和接入设备之间的至少两个用户面数据通道，其中，至少两个用户面数据通道包含第一用户面数据通道，第一用户面数据通道不采用预设协议处理接入设备和终端设备之间的用户面数据。
在第四方面或第五方面或第六方面的一种可能的设计中，请求消息携带数据网络标识、网络切片选择辅助信息NSSAI、终端设备标识中的至少一个。
在第四方面或第五方面或第六方面的一种可能的设计中，预设协议包括固定接入 控制协议用户面协议FCP UP或者以太网点到点协议PPPoE。
在第五方面的一种可能的设计中，策略管理网元包括归一化数据管理网元UDM或者策略控制功能网元PCF。
在第四方面或第六方面的一种可能的设计中，第一用户面数据通道用于传输多播业务的控制信令，多播业务的控制信令包括组播加入消息。
在第四方面或第六方面的一种可能的设计中，至少两个用户面数据通道对应一个分组数据单元PDU会话。
第七方面，本申请实施例提供一种用户面数据处理装置，该装置具有实现上述第一方面或第二方面或第三方面任一项的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第八方面，提供一种用户面数据处理装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该用户面数据处理装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该用户面数据处理装置执行如上述第一方面或第二方面或第三方面中任一项的视频编码方法。
第九方面，提供一种用户面数据处理装置，包括：处理器；处理器用于与存储器耦合，并读取存储器中的指令之后，根据指令执行如上述第一方面或第二方面或第三方面中任一项的用户面数据处理方法。
第十方面，提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面或第二方面或第三方面中任一项的用户面数据处理方法。
第十一方面，提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面或第二方面或第三方面中任一项的用户面数据处理方法。
第十二方面，提供一种电路系统，电路系统包括处理电路，处理电路被配置为执行如上述第一方面或第二方面或第三方面中任一项的用户面数据处理方法。
第十三方面，提供一种用户面数据处理系统，该系统包括上述第一方面中的用户面数据处理装置、上述第二方面中的用户面数据处理装置以及上述第三方面中的用户面数据处理装置。
其中，第二方面至十三方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果，此处不再赘述。
附图说明
图1为本申请实施例提供的5G系统的架构示意图；
图2为本申请实施例提供的用户面数据处理系统的架构图；
图3为本申请实施例提供的用户面数据处理装置的结构示意图一；
图4为本申请实施例提供的用户面数据处理方法的流程图一；
图5为本申请实施例提供的用户面数据处理方法的流程图二；
图6为本申请实施例提供的用户面数据处理装置的结构示意图二。
具体实施方式
首先给出本申请实施例所涉及的5G网络架构如下：
如图1所示，该系统包括网络切片选择功能(Network Slice Selection Function，NSSF)、网络开放功能(Network Exposure Function，NEF)、网络存储功能(Network Repository Function，NRF)、策略控制功能(Policy Control Function，PCF)、归一化数据管理(Unified Data Management，UDM)、应用功能(Application Function，AF)、鉴权服务器功能(Authentication Server Function，AUSF)、接入和移动性管理功能(Core Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)、RG、AN、FAGF、用户面功能(User Plane Function，UPF)、数据网(data network，DN)网元等网元或设备以及用户终端。
其中，用户终端通过无线(例如无线保真(WIreless-FIdelity，WiFi))或有线方式接入RG，RG通过N1与AMF通信，RG通过U接口与V接口，经由AN设备与FAGF通信，FAGF通过N3与UPF通信，FAGP通过N2与AMF通信，UPF通过N4与SMF通信，UPF通过N6与DN网元通信，SMF通过N11与AMF通信，SMF通过N10与UDM通信，SMF通过N7与PCF通信。
可以理解的是，根据5G系统部署的需求，相应网元网元之间可采用一定方式通信(例如，RG通过N1与AMF通信)，上述仅列举了与本申请实施例的技术方案相关的网元之间通信的方式，为简化描述，本申请实施例不再对其他网元之间的通信方式进行赘述。
可选的，本申请实施例中所涉及到的用户终端(terminal)可以包括各种具有通信功能的手持设备、可穿戴设备、计算设备或连接到调制解调器的其它处理设备；还可以包括个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、膝上型电脑(laptop computer)、机器类型通信(machine type communication,MTC)终端、用户设备(user equipment，UE)等。用户终端通过RG接入网络。在本申请的实施例中，RG可以有用户终端的功能，或者用户终端具有RG的功能。为了方便描述，本申请将RG称为终端设备。
可选的，图1中的各个网元的名字以及各个网元之间的接口名字只是一个示例，具体实现中各个网元或者各个网元之间的接口的名字可能为其他名字，或者网元也可以称之为实体，本申请实施例对此不作具体限定。核心网的全部或者部分网元可以是物理上的实体网元，也可以是虚拟化的网元，在此不做限定。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
在本申请的实施例中，某一网元(例如：A网元)获取来自另一网元(例如：B网元) 的信息，可以指A网元直接从B网元接收信息，也可以指A网元经其他网元(例如：C网元)从B网元接收信息。当A网元经C网元从B网元接收信息时，C网元可以对信息进行透传，也可以将信息进行处理，例如：将信息携带在不同的消息中进行传输或者对信息进行筛选，只发送筛选后的信息给A网元。类似的，在本申请的各实施例中，A网元向B网元发送信息，可以指A网元直接向B网元发送信息，也可以指A网元经其他网元(例如：C网元)向B网元发送信息。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图2所示，本申请实施例提供一种用户面数据处理系统20，该用户面数据处理系统20包括：终端设备201、接入设备202、会话管理网元203以及策略管理网元204。
其中，策略管理网元204，用于接收来自会话管理网元的请求消息，并根据该请求消息确定指示信息，还用于将向会话管理网元发送该指示信息。其中，指示信息用于指示终端设备201、接入设备202是否采用预设协议处理终端设备201与接入设备202间的用户面数据。
会话管理网元203，用于接收来自策略管理网元204的指示信息，并向终端设备201和/或接入设备202发送该指示信息，该指示信息用于通知终端设备201和/或接入设备202是否采用预设协议处理终端设备201和接入设备202之间的用户面数据。
终端设备201，用于接收来自会话管理网元203的指示信息，根据该指示信息，处理其与接入设备202之间的用户面数据。
接入设备202，用于接收来自会话管理网元203的指示信息，并根据该指示信息，处理其与终端设备201之间的用户面数据。
在本申请的实施例中,接入设备包括接入网设备和接入网网关设备。其中，接入网设备和接入网网关设备可以集成到统一设备或者可以是两个分离的设备。也就是，接入设备可以具有接入网网关设备的功能，或者，接入设备可以同时具有接入网网关设备和接入网设备的功能，接入网设备例如可以为图1所示的AN设备，接入网网关设备例如可以为图1所示的FAGF。
需要说明的是，图2中仅示出了与本申请实施例技术方案相关的设备之间的连接关系，各个设备之间可能还存在其他连接关系，这里不再赘述。
本申请实施例提供的用户面数据处理系统可以应用于如图1所示的5G系统或者后续的演进系统中，当应用于如图1所示的5G系统时，上述的终端设备201所对应的网元或者实体可以为图1中的RG，上述的接入设备202所对应的网元或者实体可以为图1中的FAGF，这里，当FAGF与AN设备合设时，本申请实施例中的接入设备可以为具有AN设备功能的FAGF，当FAGF与AN设备分开时，本申请实施例中的接入设备可以为FAGF，上述的会话管理网元203对应的网元或者实体可以为图1中的SMF，上述的策略管理网元对应的网元或者实体可以为图1中的UDM或者PCF。
可选的，图2中的终端设备、接入设备、会话管理网元或者策略管理网元可以分别由多个设备实现，还可以由一个设备实现，例如可以实现为一个设备内的不同功能 模块，本申请实施例对此不作具体限定。可以理解的是，上述功能模块既可以是硬件设备中的网络元件，也可以是在硬件设备上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
例如，本申请实施例中的终端设备、接入设备、会话管理网元或者策略管理网元可以通过图3中的通信设备来实现。图3所示为本申请实施例提供的通信设备的硬件结构示意图。该通信设备300包括至少一个处理器301，通信线路302，存储器303以及至少一个通信接口304。
处理器301可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路302可包括一通路，在上述组件之间传送信息。
通信接口304，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器303可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路302与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器303用于存储执行本申请实施例方案的计算机执行指令，并由处理器301来控制执行。处理器301用于执行存储器303中存储的计算机执行指令，从而实现本申请下述实施例提供的用户面数据处理方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器301可以包括一个或多个CPU，例如图3中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信设备300可以包括多个处理器。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
可以理解的是，图3仅示出了通信设备的一种示例性的硬件结构示意图，为了实现本申请实施例的技术方案，通信设备300还可能包括其他的组件，本申请实施例并不对此进行限制。
上述的通信设备300可以是一个通用设备或者是一个专用设备。在具体实现中，通信设备300可以是具有如图3中类似结构的设备。本申请实施例不限定通信设备300 的类型。
可选的，本申请实施例提供的用户面数据处理方法应用于PDU会话管理流程中，下面将结合图1至图3对本申请实施例提供的用户面数据处理方法进行具体阐述。
需要说明的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，在此统一说明，以下不再赘述。
首先，以图2所示的用户面数据处理系统中的策略管理网元为UDM为例，如图4所示，本申请实施例提供的用户面数据处理方法，包括如下步骤：
S401、RG向SMF发送请求消息。
相应的，SMF接收来自RG发送的请求消息。
请求消息携带数据网络标识和/或者网络切片选择辅助信息(Network Slice Selection Assistance Information，NSSAI)。可选的，上述的数据网络标识为数据网络名称(data network name，DNN)。当然，数据网络标识还可以包括例如数据网络编号等，本申请实施例对此不进行限制。
其中，数据网络标识和/或NSSAI均与业务类型相关，在本申请实施例中，按照RG与UPF之间是否传输多播业务的相关数据，可将业务类型分为多播业务和非多播业务。从而，RG通过请求消息(携带数据网络标识和/或NSSAI)可将当前的业务类型通知给SMF。
当然，请求消息还可以携带其他与业务类型关联的信息，例如，请求消息可以携带终端设备标识。
可选的，RG向FAGF发送请求消息，由FAGF向SMF发送该请求消息。
S402、SMF根据请求消息接收来自UDM的指示信息。
其中，指示信息用于指示是否采用预设协议处理FAGF和RG之间的用户面数据。预设协议包括固定接入控制协议用户面协议(Fixed Access Control Protocol User Plane Protocol，FCP UP)或者以太网点到点协议(Point-to-Point Protocol Over Ethernet，PPPoE)。
在本申请实施例中，UDM中存储有预配置信息，UDM可根据请求消息包含的信息查询预配置信息，从而确定能够适配当前业务类型的指示信息，SMF可从UDM中获取该指示信息。可选的，SMF获取该指示信息的方式可实现为：SMF向UDM发送获取消息，UDM根据该获取消息确定指示信息，其中，获取消息携带数据网络标识、NSSAI、终端设备标识中的至少一个。示例性的，该获取消息为会话管理签约请求，SMF通过向UDM发起会话管理签约请求获取UDM下发的指示信息。
可选的，上述预配置信息包括数据网络标识、NSSAI、终端设备标识中的至少一项与用户面数据处理方式的对应关系。如表1至表3所示，示出了UDM中存储的预配置信息。其中，下文以表1为例进行详细说明。
表1
Figure PCTCN2019089852-appb-000001
Figure PCTCN2019089852-appb-000002
在本申请实施例中，对不同类型业务的用户面数据采用不同的处理方式。业务类型可划分为多播业务和非多播业务。对于非多播业务的用户面数据，可采用预设协议封装/解封装FAGF与RG间的用户面数据。对于多播业务的用户面数据，不采用预设协议封装/解封装RG与FAGF之间的用户面数据，从而在AN设备缺少处理预设协议的协议栈的情况下，该AN设备仍然能够识别RG发送的组播加入消息(例如可以为IGMP join消息)，并执行IGMP snooping，将请求多播业务的用户终端(例如TV)加入多播组(本文中也称为组播组)，如此，用户终端能够访问多播业务。
通常，不同数据网络的网元提供不同类型业务，结合上述对不同类型业务的用户面数据采用不同的处理方式，因此，根据不同的数据网络可获知用户面数据的处理方式。结合表1的预配置信息，预配置信息包括DNN和用户面数据处理方式的对应关系，其中，DNN1对应的用户面数据处理方式为不采用预设协议处理用户面数据，DNN2对应的用户面数据处理方式也为不采用预设协议处理用户面数据，DNN3对应的用户面数据处理方式为采用预设协议处理用户面数据。如此，可由DNN获知用户面数据处理方式，即当UDM接收到来自SMF发送的获取消息后，可根据获取消息中携带的DNN以及例如表1所示的预配置信息，确定RG和/或FAGF的用户面数据处理方式。示例性的，当前图1中的TV通过RG向SMF发送请求消息，该请求消息用于请求DN中DNN1对应网元的多播业务，请求消息携带DNN1，SMF向UDM发送获取消息，获取消息携带DNN1，那么，UDM可根据例如表1所示的预配置信息确定DNN1对应的网元提供多播业务时，FAGF和/或不采用预设协议处理RG与FAGF之间的用户面数据，即FAGF不采用预设协议处理与RG间的用户面数据，RG不采用预设协议处理与FAGF间的用户面数据。
表2
Figure PCTCN2019089852-appb-000003
表2示出的预配置信息包括NSSAI3和用户面数据处理方式的对应关系。同样的，不同NSSAI3对应不同类型的业务，不同类型业务的用户面数据采用不同的处理方式。如此，可由NSSAI3获知用户面数据处理方式，即当UDM接收到来自SMF发送的获取消息后，可根据获取消息中携带的NSSAI3以及例如表2所示的预配置信息，确定FAGF、RG的用户面数据处理方式。
表3
Figure PCTCN2019089852-appb-000004
表3示出的预配置信息包括终端设备标识(例如可以为MAC地址)和用户面数据处理方式的对应关系。同样的，不同终端设备对应不同类型的业务，不同类型业务的用户面数据采用不同的处理方式。如此，可由终端设备标识获知用户面数据处理方式，即当UDM接收到来自SMF发送的获取消息后，可根据获取消息中携带的终端设备标识以及例如表3所示的预配置信息，确定用户面数据处理方式。
类似的，表2、表3的详细说明可参见表1的说明，这里不再赘述。
此外，当来自SMF的获取消息携带有数据网络标识、NSSAI、终端设备标识中的至少两个标识时，UDM根据获取消息携带的至少两个标识确定用户面数据处理方式。比如，来自SMF的获取消息携带数据网络标识和NSSAI，UDM根据获取消息中的数据网络标识、NSSAI以及表1、表2所示的预配置信息确定用户面数据处理方式。
当然，上述仅以UDM存储表格格式的预配置信息为例进行说明，UDM还可以存储其他格式的预配置信息，在此统一说明，下文不再赘述。
S403、SMF向FAGF发送指示信息。
相应的，FAGF接收来自SMF发送的指示信息。
可选的，SMF向FAGF发送N2消息，N2消息携带该指示信息。其中，N2消息可以为N2会话管理信息信元，由该N2会话管理信息信元携带指示信息。作为一种可能的实现方式，SMF可以向AMF发送N2会话管理信息信元，AMF向FAGF发送N2会话管理信息信元。
S404、SMF向RG发送指示信息。
相应的，RG接收来自SMF发送的指示信息。
其中，SMF可以采取以下两种方式向RG发送指示信息。
方式1：SMF向RG发送非接入层(Non-access stratum，NAS)消息，该NAS消息携带指示信息。可选的，在PDU会话管理流程中，该NAS消息为会话建立接受消息(PDU session establishment accept)。
方式2：SMF向FAGF发送指示信息，再由FAGF将指示信息发送给RG。可选的，SMF向FAGF发送N2消息，该N2消息携带指示信息(即先执行S403步骤)，再由AGF向RG发送AN信令，该AN信令携带指示信息。
在本申请实施例中，对S403与S404的执行顺序不加以限制，即SMF可以先向RG发送指示信息，再向FAGF发送指示信息，也可以先向FAGF发送指示信息，再向RG发送指示信息，当然，也可以同时执行S403和S404。
S405、FAGF根据指示信息处理FAGF和RG之间的用户面数据。
具体的，S405可以实现为如下步骤：
S405a、FAGF根据指示信息判断是否采用预设协议处理FAGF和RG之间的用户面数据，若确定采用预设协议处理FAGF和RG之间的用户面数据，则执行步骤S405b，若确定不采用预设协议处理FAGF和RG之间的用户面数据，则执行步骤S405c。
S405b、FAGF采用预设协议解封装RG发送的用户面数据，或者采用预设协议封装向RG发送的用户面数据。
其中，可以通过为FAGF新增协议栈来实现采用预设协议处理用户面数据的功能，采用预设协议封装用户面数据包括为用户面数据增加包头等方式，本申请实施例对此不进行限制。
在FAGF采用预设协议处理与RG间的用户面数据的情况下，FAGF建立与RG间的用户面数据通道，该用户面数据通道采用预设协议处理用户面数据。
S405c、FAGF不采用预设协议解封装RG发送的用户面数据，或者FAGF不采用预设协议封装向RG发送的用户面数据。
在一种可能的实现方式中，在FAGF不采用预设协议处理与RG间的用户面数据的情况下，FAGF建立和RG之间的至少两个用户面数据通道。
其中，至少两个用户面数据通道可以是基于虚拟局域网(Virtual Local Area Network，VLAN)、或者以太(Ethernet)、或者网络互连协议(Internet Protocol，IP)等的通道，本申请不作限定。至少两个用户面数据通道对应RG和UPF之间的一个PDU会话，也就是，至少两个用户面数据通道与RG和UPF之间的PDU会话关联，RG通过至少两个用户面数据通道与UPF进行通信。
可选的，至少两个用户面数据通道包含不采用预设协议处理用户面数据的通道，称为第一用户面数据通道。第一用户面数据通道不采用预设协议处理AGF和RG之间的用户面数据，该第一用户面数据通道用于传输多播业务的控制信令，多播业务的控制信令包括例如上述的组播加入消息。
如此，在上行方向(RG到FAGF的方向)，在第一用户面数据通道的一侧，RG向FAGF发送不采用预设协议封装的用户面数据(例如组播加入消息)，该用户面数据在第一用户面数据通道中传输，由于该用户面数据并未采用预设协议封装，因此，AN设备可以识别该组播加入消息，将发起组播加入消息的用户终端(例如TV)加入多播组，在第一用户面数据通道的另一侧，FAGF接收到该不采用预设协议封装的用户面数据之后，相应的，不采用预设协议解封装RG发送的用户面数据。由此，用户终端在被加入多播组后可以进行多播业务。在下行方向(FAGF到RG的方向)，在第一用户面数据通道的一侧，FAGF不采用预设协议封装向RG发送的用户面数据，该用户面数据在第一用户面数据通道中传输，之后，在第一用户面数据通道的另一侧，RG接收到不采用预设协议封装的用户面数据后，相应的，不采用预设协议解封装FAGF发送的用户面数据。
当然，至少两个用户面数据通道还包含FAGF与RG间的第二用户面数据通道，第二用户面数据通道采用预设协议处理FAGF与RG间的用户面数据，第二用户面数据通道用于传输非多播业务的用户面数据或者用于传输多播业务的控制信令。
可选地，RG可以在两个用户面数据通道中都发送多播业务的控制信令，如组播加入消息，此时FAGF从两个用户面数据通道中都接收到一份控制信令，只向核心网网元发送一份控制信令。
在另一种可能的实现方式中，在FAGF不采用预设协议处理与RG间的用户面数据的情况下，FAGF建立和RG之间的一个用户面数据通道，该用户面数据通道中传输的数据包不需要采用预设协议处理。
S406、RG根据指示信息处理FAGF和RG之间的用户面数据。
具体的，S405可以实现为如下步骤：
S406a、RG根据指示信息判断是否采用预设协议处理FAGF和RG之间的用户面数据，若确定采用预设协议处理FAGF和RG之间的用户面数据，则执行步骤S406b，若确定不采用预设协议处理FAGF和RG之间的用户面数据，则执行步骤S406c。
S406b、RG采用预设协议解封装FAGF发送的用户面数据，或者采用预设协议封装向FAGF发送的用户面数据。
其中，可以通过为RG增加协议栈来实现采用预设协议处理用户面数据的功能，采用预设协议封装用户面数据包括为用户面数据增加包头等方式，本申请实施例对此不进行限制。
在RG采用预设协议处理与FAGF间的用户面数据的情况下，RG建立与FAGF间的用户面数据通道，该用户面数据通道采用预设协议处理用户面数据，该用户面数据通道用于传输与FAGF间的非多播业务的用户面数据。
S406c、RG不采用预设协议解封装FAGF发送的用户面数据，或者RG不采用预设协议封装向FAGF发送的用户面数据。
RG不采用预设协议处理与FAGF间的用户面数据的情况下，RG建立和FAGF之间的至少两个用户面数据通道。
其中，至少两个用户面数据通道对应RG和UPF之间的一个PDU会话，也就是，至少两个用户面通道与RG和UPF之间的PDU会话关联，RG通过至少两个用户面数据通道与UPF进行通信。
可选的，至少两个用户面数据通道包含第一用户面数据通道，第一用户面数据通道不采用预设协议处理FAGF和RG之间的用户面数据。
可选的该第一用户面数据通道用于传输多播业务的控制信令，多播业务的控制信令包括例如上述的组播加入消息。
如此，在上行方向(RG到FAGF的方向)，RG向FAGF发送不采用预设协议封装的用户面数据(例如组播加入消息)，该组播加入消息在第一用户面数据通道中传输，由于该用户面数据并未采用预设协议封装，因此，AN设备可以识别该组播加入消息，将发起组播加入消息的用户终端(例如TV)加入多播组，由此，用户终端在被加入多播组后可以进行多播业务。下行方向的用户面数据传输的相关描述可参见上述FAGF的下行方向的用户面数据传输的描述，这里不再赘述。
需要说明的是，本申请实施例并不限制S403至S406的执行顺序，例如，可以先执行S404、S406，再执行S403、S405，也可以先执行S403、S404，再执行S405、S406。图4的方法流程所示的执行顺序仅为一个示例。
本申请实施例提供的用户面数据处理方法，接入设备在接收来自会话管理网元的指示信息后，可以根据指示信息处理与终端设备之间的用户面数据，其中，指示信息用以指示是否采用预设协议处理与终端设备之间的用户面数据，也就意味着，接入设备有所依据的处理与终端设备之间的用户面数据，在需采用预设协议处理用户面数据的场景下采用预设协议处理与终端设备间的用户面数据，在不需预设协议处理用户面数据的场景下不采用预设协议处理与终端设备间的用户面数据，使得AN设备可以解析某些多播业务的用户面数据，如组播加入消息，进而提升多播业务的接入率。
进一步的，采用本申请实施例的用户面数据处理方法，可根据业务类型来适配是否采用预设协议处理用户面数据，能够满足用户不同的业务需求。
本申请实施例还提供另一种用户面数据处理方法，如图5给出该方法流程，该方法包括如下步骤：
S501、RG向SMF发送请求消息。
其中，S501的详细介绍可参见S401相关描述，这里不再赘述。
S502、SMF根据请求消息接收来自PCF的指示信息。
需要说明的是，该步骤的执行与可参见S402的相关描述，所不同的是，在S502中，PCF中存储预配置信息，SMF从PCF中获取指示信息。
S503、SMF向FAGF发送指示信息。
S504、SMF向RG发送指示信息。
S505、FAGF根据指示信息处理FAGF和RG之间的用户面数据。
具体的，S505可以实现为如下步骤：
S505a、FAGF根据指示信息判断是否采用预设协议处理FAGF和RG之间的用户面数据，若确定采用预设协议处理FAGF和RG之间的用户面数据，则执行步骤S505b，若确定不采用预设协议处理FAGF和RG之间的用户面数据，则执行步骤S505c。
S505b、FAGF采用预设协议解封装RG发送的用户面数据，或者采用预设协议封装向RG发送的用户面数据。
S505c、FAGF不采用预设协议解封装RG发送的用户面数据，或者FAGF不采用预设协议封装向RG发送的用户面数据。
S506、RG根据指示信息处理FAGF和RG之间的用户面数据。
具体的，S405可以实现为如下步骤：
S506a、RG根据指示信息判断是否采用预设协议处理FAGF和RG之间的用户面数据，若确定采用预设协议处理FAGF和RG之间的用户面数据，则执行步骤S506b，若确定不采用预设协议处理FAGF和RG之间的用户面数据，则执行步骤S506c。
S506b、RG采用预设协议解封装FAGF发送的用户面数据，或者采用预设协议封装向FAGF发送的用户面数据。
S506c、RG不采用预设协议解封装FAGF发送的用户面数据，或者RG不采用预设协议封装向FAGF发送的用户面数据。
其中，本实施例的上述S503至S506的详细介绍可参见图4方法流程实施例中S403至S406的相关描述，这里不再赘述。
此外，在本申请的另一些实施例中，还提供一种用户面数据处理方法，在PDU会 话管理流程，比如在PDU会话建立流程中，若接入设备未接收到来自会话管理网元的指示信息，则接入设备采用预设协议处理与终端设备间的用户面数据，同样的，若终端设备未接收到来自会话管理网元的指示信息，则终端设备也采用预设协议处理与接入设备间的用户面数据。
可以理解的是，本申请实施例中的网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。结合本申请中所公开的实施例描述的各示例的单元及算法步骤，本申请实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能，但是这种实现不应认为超出本申请实施例的技术方案的范围。
本申请实施例可以根据上述方法示例对网元进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图6示出了本申请实施例中提供的用户面数据处理装置的一种示意性框图，其中，用户面数据处理装置可以为上述的接入设备或者终端设备或者会话管理网元。该用户面数据处理装置600可以以软件的形式存在，还可以为可用于设备的芯片。用户面数据处理装置600包括：处理单元602和通信单元603。
若用户面数据处理装置600为接入设备，处理单元602可以用于支持接入设备执行图4中的S405a、S405b、S405c，图5中的S505a、S505b、S505c等，和/或用于本文所描述的方案的其它过程。通信单元603用于支持接入设备和其他网元(例如图2中的终端设备201等)之间的通信，例如支持接入设备执行图4中的S401、S403、S404，图5中的S501、S503、S504等。
若用户面数据处理装置600为终端设备，处理单元602可以用于支持终端设备执行图4中的S406a、S406b、S406c，S506a、S506b、S506c等，和/或用于本文所描述的方案的其它过程。通信单元603用于支持终端设备和其他网元(例如图2中的接入设备202等)之间的通信，例如支持终端设备执行图4中的S401、S404，图5中的S501、S504等。
若用户面数据处理装置600为会话管理网元，处理单元602可以用于支持会话管理网元执行上述实施例中确定指示信息的动作，和/或用于本文所描述的方案的其它过程。通信单元603用于支持会话管理网元和其他网元(例如图2中的终端设备201等)之间的通信，例如支持会话管理网元执行图4中的S401、S402、S403，图5中的S501、S502、S503等。
可选的,用户面数据处理装置600还可以包括存储单元601，用于存储用户面数据处理装置600的程序代码和数据，数据可以包括不限于原始数据或者中间数据等。
一种可能的方式中，处理单元602可以是控制器或图3所示的处理器301或处理器305，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理(Digital Signal Processing，DSP)，应用专用集成电路(Application  Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field－Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元603可以是收发器、收发电路或图3所示的通信接口304等。存储单元601可以是图3所示的存储器303。
本领域普通技术人员可以理解：在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(Digital Video Disc，DVD))、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络设备(例如终端设备)上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个功能单元独立存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在可读取的存储介质中，如计算机的软盘，硬盘或光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种用户面数据处理方法，其特征在于，包括：
    接入设备接收来自会话管理网元的指示信息，所述指示信息用于指示是否采用预设协议处理所述接入设备和终端设备之间的用户面数据；
    所述接入设备根据所述指示信息处理所述接入设备和所述终端设备之间的所述用户面数据。
  2. 根据权利要求1所述的方法，其特征在于，所述接入设备根据所述指示信息处理所述接入设备和所述终端设备之间的所述用户面数据，包括：
    所述接入设备根据所述指示信息确定采用所述预设协议处理所述接入设备和所述终端设备之间的所述用户面数据，则采用所述预设协议解封装所述终端设备发送的用户面数据，或者采用所述预设协议封装所述接入设备向所述终端设备发送的用户面数据。
  3. 根据权利要求1所述的方法，其特征在于，所述接入设备根据所述指示信息处理所述接入设备和所述终端设备之间的所述用户面数据，包括：
    所述接入设备根据所述指示信息确定不采用所述预设协议处理所述接入设备和所述终端设备之间的所述用户面数据，则不采用所述预设协议解封装所述终端设备发送的用户面数据，或者不采用所述预设协议封装向所述终端设备发送的用户面数据。
  4. 根据权利要求1所述的方法，其特征在于，所述接入设备根据所述指示信息处理所述接入设备和所述终端设备之间的所述用户面数据，包括：
    所述接入设备根据所述指示信息确定不采用所述预设协议处理所述接入设备和所述终端设备之间的所述用户面数据；
    所述接入设备建立和所述终端设备之间的至少两个用户面数据通道，其中，所述至少两个用户面数据通道包含第一用户面数据通道，第一用户面数据通道不采用所述预设协议处理所述接入设备和所述终端设备之间的用户面数据。
  5. 根据权利要求4所述的方法，其特征在于，所述第一用户面数据通道用于传输多播业务的控制信令，所述多播业务的控制信令包括组播加入消息。
  6. 根据权利要求4所述的方法，其特征在于，所述至少两个用户面数据通道对应一个分组数据单元PDU会话。
  7. 根据权利要求1所述的方法，其特征在于，在所述接入设备接收来自会话管理网元的指示信息之前，所述方法还包括：
    所述接入设备向会话管理网元发送请求消息，所述请求消息携带数据网络标识和/或者网络切片选择辅助信息NSSAI。
  8. 根据权利要求1所述的方法，其特征在于，所述接入设备接收来自会话管理网元的指示信息，包括：
    所述接入设备接收来自会话管理网元的N2消息，所述N2消息携带所述指示信息。
  9. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述接入设备向所述终端设备发送所述指示信息。
  10. 根据权利要求1至9任意一项所述的方法，其特征在于，所述预设协议包括固定接入控制协议用户面协议FCP UP或者以太网点到点协议PPPoE。
  11. 一种用户面数据处理方法，其特征在于，包括：
    会话管理网元接收来自终端设备的请求消息；
    所述会话管理网元根据请求消息接收来自策略管理网元的指示信息，所述指示信息用于指示是否采用预设协议处理接入设备和所述终端设备之间的用户面数据；
    所述会话管理网元向所述接入设备和/或所述终端设备发送所述指示信息。
  12. 根据权利要求11所述的方法，其特征在于，所述会话管理网元向接入设备发送所述指示信息，包括：
    所述会话管理网元向所述接入设备发送N2消息，所述N2消息携带所述指示信息。
  13. 根据权利要求11所述的方法，其特征在于，所述会话管理网元向终端设备发送所述指示信息，包括：
    所述会话管理网元向所述终端设备发送非接入层NAS消息，所述NAS消息携带所述指示信息。
  14. 一种用户面数据处理装置，其特征在于，所述装置设置有收发器和处理器；
    所述收发器，用于接收来自会话管理网元的指示信息，所述指示信息用于指示是否采用预设协议处理接入设备和终端设备之间的用户面数据；
    所述处理器，用于根据所述指示信息处理所述接入设备和所述终端设备之间的所述用户面数据。
  15. 根据权利要求14所述的装置，其特征在于，所述处理器，用于根据所述指示信息处理所述接入设备和所述终端设备之间的所述用户面数据，包括：用于根据所述指示信息确定采用所述预设协议处理所述接入设备和所述终端设备之间的所述用户面数据，采用所述预设协议解封装所述终端设备发送的用户面数据，或者采用所述预设协议封装所述接入设备向所述终端设备发送的用户面数据。
  16. 根据权利要求14所述的装置，其特征在于，所述处理器，用于根据所述指示信息处理所述接入设备和所述终端设备之间的所述用户面数据，包括：用于根据所述指示信息确定不采用所述预设协议处理所述接入设备和所述终端设备之间的所述用户面数据，不采用所述预设协议解封装所述终端设备发送的用户面数据，或者不采用所述预设协议封装向所述终端设备发送的用户面数据。
  17. 根据权利要求14所述的装置，其特征在于，所述处理器，用于根据所述指示信息处理所述接入设备和所述终端设备之间的所述用户面数据，包括：用于根据所述指示信息确定不采用所述预设协议处理所述接入设备和所述终端设备之间的所述用户面数据；建立和所述终端设备之间的至少两个用户面数据通道，其中，所述至少两个用户面数据通道包含第一用户面数据通道，第一用户面数据通道不采用所述预设协议处理所述接入设备和所述终端设备之间的用户面数据。
  18. 根据权利要求17所述的装置，其特征在于，所述第一用户面数据通道用于传输多播业务的控制信令，所述多播业务的控制信令包括组播加入消息。
  19. 根据权利要求17所述的装置，其特征在于，所述至少两个用户面数据通道对应一个分组数据单元PDU会话。
  20. 根据权利要求14所述的装置，其特征在于，
    所述收发器，还用于向会话管理网元发送请求消息，所述请求消息携带数据网络 标识和/或者网络切片选择辅助信息NSSAI。
  21. 根据权利要求14所述的装置，其特征在于，所述收发器，用于接收来自会话管理网元的指示信息，包括：用于接收来自会话管理网元的N2消息，所述N2消息携带所述指示信息。
  22. 根据权利要求14所述的装置，其特征在于，
    所述收发器，还用于向所述终端设备发送所述指示信息。
  23. 一种用户面数据处理装置，其特征在于，所述装置设置有收发器和处理器；
    所述收发器，用于接收来自终端设备的请求消息；根据请求消息接收来自策略管理网元的指示信息，所述指示信息用于指示是否采用预设协议处理接入设备和终端设备之间的用户面数据；向所述接入设备和/或所述终端设备发送所述指示信息。
  24. 根据权利要求23所述的装置，其特征在于，所述收发器，用于向接入设备发送所述指示信息，包括：用于向所述接入设备发送N2消息，所述N2消息携带所述指示信息。
  25. 根据权利要求23所述的装置，其特征在于，所述收发器，用于向终端设备发送所述指示信息，包括：用于向所述终端设备发送非接入层NAS消息，所述NAS消息携带所述指示信息。
  26. 一种用户面数据处理装置，其特征在于，所述装置设置有收发器和处理器；
    所述收发器，用于接收来自会话管理网元或者接入设备的指示信息，所述指示信息用于指示是否采用预设协议处理所述接入设备和终端设备之间的用户面数据；
    所述处理器，用于根据所述指示信息处理所述接入设备和所述终端设备之间的所述用户面数据。
  27. 根据权利要求26所述的装置，其特征在于，所述处理器，用于根据所述指示信息处理所述接入设备和所述终端设备之间的所述用户面数据，包括：用于根据所述指示信息确定采用所述预设协议处理所述接入设备和所述终端设备之间的所述用户面数据，采用所述预设协议解封装所述接入设备发送的用户面数据，或者采用所述预设协议封装所述终端设备向所述接入设备发送的用户面数据。
  28. 根据权利要求26所述的装置，其特征在于，所述处理器，用于根据所述指示信息处理所述接入设备和所述终端设备之间的所述用户面数据，包括：用于根据所述指示信息确定不采用所述预设协议处理所述接入设备和所述终端设备之间的所述用户面数据，不采用所述预设协议解封装所述接入设备发送的用户面数据，或者不采用所述预设协议封装向所述接入设备发送的用户面数据。
  29. 根据权利要求26所述的装置，其特征在于，所述处理器，用于根据所述指示信息处理所述接入设备和所述终端设备之间的所述用户面数据，包括：用于根据所述指示信息确定不采用所述预设协议处理所述接入设备和所述终端设备之间的所述用户面数据；建立和所述接入设备之间的至少两个用户面数据通道，其中，所述至少两个用户面数据通道包含第一用户面数据通道，第一用户面数据通道不采用所述预设协议处理所述接入设备和所述终端设备之间的用户面数据。
  30. 根据权利要求29所述的装置，其特征在于，所述第一用户面数据通道用于传输多播业务的控制信令，所述多播业务的控制信令包括组播加入消息。
PCT/CN2019/089852 2018-06-04 2019-06-03 用户面数据处理方法及装置 WO2019233381A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810562638.2 2018-06-04
CN201810562638.2A CN110620999B (zh) 2018-06-04 2018-06-04 用户面数据处理方法及装置

Publications (1)

Publication Number Publication Date
WO2019233381A1 true WO2019233381A1 (zh) 2019-12-12

Family

ID=68769113

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/089852 WO2019233381A1 (zh) 2018-06-04 2019-06-03 用户面数据处理方法及装置

Country Status (2)

Country Link
CN (1) CN110620999B (zh)
WO (1) WO2019233381A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111245702B (zh) * 2020-02-05 2021-05-11 联想(北京)有限公司 基于5gs的数据传输方法及装置、转发设备和upf通信设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296404A (zh) * 2007-04-28 2008-10-29 中兴通讯股份有限公司 在下一代移动通信网络架构下接入组播业务的系统和方法
US20160072699A1 (en) * 2013-04-12 2016-03-10 Selex Es S.P.A. Smf-type communication method for a manet network, network node and mobile network which implement this communication method

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101197832B (zh) * 2007-12-13 2012-01-25 华为技术有限公司 一种实现iptv业务的方法、系统、装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296404A (zh) * 2007-04-28 2008-10-29 中兴通讯股份有限公司 在下一代移动通信网络架构下接入组播业务的系统和方法
US20160072699A1 (en) * 2013-04-12 2016-03-10 Selex Es S.P.A. Smf-type communication method for a manet network, network node and mobile network which implement this communication method

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Solution to Support IPTV Service", SA WG2 MEETING #127 S 2-184153, 20 April 2018 (2018-04-20) *
HUAWEI: "Update Solution for IPTV support", SA WG2 MEETING #127BIS S2-185619, 1 June 2018 (2018-06-01), XP051456722 *
NOKIA: "23.716 solutions: Support of IPTV", SA WG2 MEETING #127 S2-184152, 20 April 2018 (2018-04-20), XP051432939 *

Also Published As

Publication number Publication date
CN110620999A (zh) 2019-12-27
CN110620999B (zh) 2021-04-20

Similar Documents

Publication Publication Date Title
US11917498B2 (en) Communication method and communications apparatus
US11122027B2 (en) End-to-end M2M service layer sessions
WO2020147760A1 (zh) 一种局域网通信方法、装置及系统
WO2021204003A1 (zh) 一种临近服务的业务处理方法、设备及系统
WO2020224559A1 (zh) 群组管理方法、装置及系统
WO2020108002A1 (zh) 一种传输策略确定方法、策略控制方法及装置
CN110166414B (zh) 一种通信方法、装置及系统
US20140160990A1 (en) Mechanisms for Quality of Service to Over the Top Applications for Use in Commercial Wireless Networks
WO2022033558A1 (zh) 一种中继管理方法及通信装置
WO2021135650A1 (zh) 通信方法及装置
EP3735092B1 (en) Transmission methods, transmission apparatus, computer readable storage medium and system
WO2022052875A1 (zh) 终端跨区域通信方法、网元设备及存储介质
WO2020034697A1 (zh) 通信方法和装置
WO2021254001A1 (zh) 会话建立方法、装置、系统及计算机存储介质
WO2021097858A1 (zh) 一种通信方法及装置
CN114124618A (zh) 一种报文传输方法及电子设备
WO2021037271A1 (zh) 通信方法、设备及系统
WO2019154160A1 (zh) 一种通信方法及装置
WO2019242525A1 (zh) 数据传输方法、相关装置及系统
WO2022021435A1 (zh) 数据传输方法、设备及存储介质
WO2019233381A1 (zh) 用户面数据处理方法及装置
WO2022007749A1 (zh) 一种数据传输方法和装置
WO2022099484A1 (zh) 标识发送方法和通信装置
WO2022067736A1 (zh) 一种通信方法及装置
WO2022198410A1 (zh) 通信方法及装置

Legal Events

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

Ref document number: 19814595

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19814595

Country of ref document: EP

Kind code of ref document: A1