WO2019120073A1 - 数据传输方法、设备及系统 - Google Patents

数据传输方法、设备及系统 Download PDF

Info

Publication number
WO2019120073A1
WO2019120073A1 PCT/CN2018/119163 CN2018119163W WO2019120073A1 WO 2019120073 A1 WO2019120073 A1 WO 2019120073A1 CN 2018119163 W CN2018119163 W CN 2018119163W WO 2019120073 A1 WO2019120073 A1 WO 2019120073A1
Authority
WO
WIPO (PCT)
Prior art keywords
path
mlan
target
terminal
multicast
Prior art date
Application number
PCT/CN2018/119163
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 WO2019120073A1 publication Critical patent/WO2019120073A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a data transmission method, device, and system.
  • a local area network is a computer communication network composed of various computers, external devices, and databases connected to each other within a local geographic area, such as a school, a factory, and an organization. It can be connected to a remote local area network, database or processing center through a data communication network or a dedicated data circuit to form a large-scale information processing system.
  • LAN local area network
  • WLAN wireless LAN
  • MLAN mobile local area network
  • MLAN can be used within a wider range of mobile network coverage, that is, LAN-based data exchange or communication can be achieved by joining the same MLAN regardless of whether the user is in the same geographical area.
  • the creation of the MLAN and its scaling migration adjustment can be done automatically by the mobile network without manual intervention.
  • MLAN can be customized as needed, and different MLANs are safely isolated from each other.
  • the destination address of the data packet is replaced with the addressing address of each terminal under the MLAN, and then The addressing address is mapped to the path corresponding to each terminal addressing address, and the data packet is respectively sent to each terminal under the same MLAN through the corresponding path.
  • UPF user plane function
  • the embodiment of the present application provides a data transmission method, device, and system, which can save transmission bandwidth in an MLAN multicast scenario.
  • the embodiment of the present application provides the following technical solutions:
  • a data transmission method comprising: a user plane function entity receiving a data packet from a source device, wherein the data packet carries multicast information; and the user plane function entity determines a destination mobile area network MLAN corresponding to n Path downlink information of the multicast path; the user plane function entity sends the data packet to the corresponding n access devices through the n multicast paths corresponding to the path downlink information of the n multicast paths, where n is a positive integer .
  • the data transmission method provided by the embodiment of the present application can avoid the problem that the data packet in the prior art is repeatedly transmitted between the same user plane function entity and the access device, thereby saving the transmission bandwidth in the MLAN multicast scenario.
  • the user plane function entity determines the path downlink information of the n multicast paths corresponding to the target MLAN, and the user plane function entity determines the identifier according to the identifier of the target MLAN and the first correspondence.
  • the path downlink information of the n multicast paths corresponding to the target MLAN where the first correspondence includes the correspondence between the identifier of the target MLAN and the path downlink information of the n multicast paths.
  • the first correspondence includes the correspondence between the identifier of the target MLAN and the path downlink information of the n multicast paths. Therefore, if the user plane function entity knows the identifier of the target MLAN, the first correspondence may be timely.
  • the path downlink information of the n multicast paths corresponding to the target MLAN is quickly determined.
  • the method further includes: the user plane function entity receiving the first correspondence from the session management entity.
  • the information of the n multicast paths includes the information of the first multicast path
  • the method further includes: the session management entity establishing the first multicast path in the target MLAN; the session The management entity sends a correspondence between the identifier of the target MLAN and the path downlink information of the first multicast path to the user plane function entity. That is, after the session management entity establishes the first multicast path in the target MLAN, the user plane function entity needs to obtain the correspondence between the identifier of the target MLAN and the path downlink information of the first multicast path. Further, as described above, when the user plane function entity knows the identifier of the target MLAN, the path downlink information of the n multicast paths corresponding to the target MLAN may be quickly and timely determined according to the first correspondence.
  • the t target terminals corresponding to the first multicast path include a first terminal, where t is a positive integer; the session management entity establishes the first multicast path in the target MLAN, including And in the process that the first terminal establishes the MLAN session in the target MLAN, the session management entity establishes the first multicast path if the first multicast path is not established. That is to say, in this implementation manner, only one multicast path is established between each access device and the user plane functional entity.
  • the terminal initiates the MLAN session establishment process, if the access device and the user plane functional entity are established.
  • the multicast path eliminates the need to establish a path corresponding to the session, thereby saving session resources.
  • the method further includes: the downlink information of the path of the user plane function entity according to the n multicast paths And the second corresponding relationship, the path downlink information of the path corresponding to the target terminal corresponding to the path downlink information of each multicast path is determined, where the second correspondence includes the path downlink information of each multicast path and Corresponding relationship between the path downlink information of the path corresponding to the target terminal; the user plane function entity respectively sends the corresponding target terminal to the corresponding access device through the n multicast paths corresponding to the path downlink information of the n multicast paths The path downstream information of the corresponding path.
  • the access device may receive path downlink information corresponding to the target terminal corresponding to each access device of the user plane function entity.
  • the access device can send data to the target terminal according to the path downlink information corresponding to the corresponding target terminal, and implement data transmission in the MLAN multicast scenario.
  • the method further includes: the user plane function entity receiving the second correspondence from the session management entity.
  • the path downlink information of the n multicast paths includes the path downlink information of the second multicast path
  • the s target terminals corresponding to the second multicast path include the second terminal
  • the method further includes: the session management entity establishes the second multicast path and the path corresponding to the second terminal; the session management entity sends the identifier of the target MLAN and the second group to the user plane function entity
  • a multicast path needs to be established between each access device and the user plane function entity, so that the user plane function entity can establish the correspondence between the path downlink information of the multicast path and the path downlink information of the path corresponding to the corresponding terminal.
  • the relationship in turn, can perform data transmission according to the correspondence.
  • This method can implement data transmission in the MLAN multicast scenario under the premise of reducing the modification of the existing process.
  • the data packet carries the identity of the target MLAN.
  • the source device includes a source terminal
  • the method further includes: the user plane function entity according to the path information of the path corresponding to the source terminal, And determining, by the third correspondence, the identifier of the target MLAN, where the third correspondence includes the correspondence between the path uplink information of the path corresponding to the source terminal and the identifier of the target MLAN.
  • the user plane functional entity can determine the identity of the target MLAN.
  • the source device includes a server
  • the method further includes: the downlink information of the path of the user plane function entity according to the path corresponding to the server, and the The four correspondences are used to determine the identifier of the target MLAN, where the fourth correspondence includes the mapping between the path downlink information of the path corresponding to the server and the identifier of the target MLAN.
  • the user plane functional entity can determine the identity of the target MLAN.
  • a data transmission method includes: an access device receives a data packet from a user plane functional entity through a multicast path, where the data packet carries multicast information; and the access device targets the s target The terminal separately sends the data packet, wherein the target mobile terminal MLAN of the target terminal is the same as the target MLAN, and the target MLAN is the MLAN where the source device that sends the data packet is located, and s is a positive integer.
  • the data transmission method provided by the embodiment of the present application can avoid the problem that the data packet in the prior art is repeatedly transmitted between the same user plane function entity and the access device, thereby saving the transmission bandwidth in the MLAN multicast scenario.
  • the access device separately sends the data packet to the target terminals, including: the access device determines the information of the target terminals according to the identifier of the target MLAN and the first correspondence.
  • the first correspondence includes a correspondence between the identifier of the target MLAN and the information of the s target terminals; the access device separately sends the data packet to the s target terminals according to the information of the s target terminals. .
  • the first correspondence includes the correspondence between the identifier of the target MLAN and the information of the target terminals. Therefore, if the user plane function entity knows the identifier of the target MLAN, the first correspondence may be quickly determined according to the first correspondence. Information about the target terminal.
  • the s target terminals include the first terminal, and the method further includes: when the first terminal establishes an MLAN session in the target MLAN, the access device establishes the target MLAN The identifier is associated with the information of the first terminal.
  • the method further includes: in the process of establishing the MLAN session in the target MLAN by the first terminal, if the first multicast path has been established, the access device receives the session from the session And a notification message of the management entity, where the notification message is used to indicate that the access device establishes an identifier of the target MLAN and an information correspondence relationship of the first terminal. That is to say, in this implementation manner, only one multicast path is established between each access device and the user plane functional entity.
  • the terminal initiates the MLAN session establishment process, if the access device and the user plane functional entity are established.
  • the multicast path eliminates the need to establish a path corresponding to the session, thereby saving session resources.
  • the method further includes: the access device receiving, by using the multicast path, path downlink information of a path corresponding to the s target terminals of the user plane function entity; the access device to the s The target terminal separately sends the data packet, including: the access device determines information of the s target terminals according to the path downlink information of the path corresponding to the s target terminals, and the second correspondence, where the second correspondence is Corresponding relationship between the path downlink information of the path corresponding to the s target terminals and the information of the s target terminals; the access device separately transmits the data packet to the s target terminals according to the information of the s target terminals.
  • the access device may perform data transmission according to the received path downlink information corresponding to the s target terminals and the second correspondence.
  • This method can implement data transmission in the MLAN multicast scenario under the premise of reducing the modification of the existing process.
  • the s target terminals include the second terminal
  • the method further includes: in the process of establishing the MLAN session in the target MLAN by the second terminal, the access device establishes the second terminal Corresponding relationship between the path downlink information of the corresponding path and the information of the second terminal.
  • the data packet carries the identity of the target MLAN.
  • the method further includes: the access device according to the path of the multicast path, downlink information, and the third Corresponding relationship, the identifier of the target MLAN is determined, where the third correspondence includes a correspondence between the path downlink information of the multicast path and the target MLAN identifier. Based on this approach, the access device can determine the identity of the target MLAN.
  • a user plane functional entity having the functionality to implement the method described in the first aspect above.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a fourth aspect provides a user plane function entity, including: a processor and a memory; the memory is configured to store a computer execution instruction, and when the user plane function entity is running, the processor executes the computer execution instruction stored in the memory So that the user plane function entity performs the data transmission method as described in any of the above first aspects.
  • a fifth aspect a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the data transfer of any of the above first aspects method.
  • a computer program product comprising instructions for causing a computer to perform the data transfer method of any of the above first aspects when executed on a computer is provided.
  • a chip system in a seventh aspect, includes a processor for supporting a user plane function entity to implement the functions involved in the foregoing aspects, for example, determining path downlink information of n multicast paths corresponding to the target MLAN.
  • the chip system further includes a memory for storing program instructions and data necessary for the user plane function entity.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • an access device having the function of implementing the method described in the second aspect above.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a ninth aspect provides an access device, including: a processor and a memory; the memory is configured to store a computer execution instruction, and when the access device is in operation, the processor executes the computer execution instruction stored in the memory to The access device is caused to perform the data transmission method as described in any of the above second aspects.
  • a tenth aspect a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the data transfer of any of the above second aspects method.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the data transfer method of any of the above second aspects.
  • a chip system comprising a processor for supporting an access device to implement the functions involved in the foregoing aspects, for example, in a process in which the first terminal establishes an MLAN session in the target MLAN, Establish a correspondence between the identifier of the target MLAN and the information of the first terminal.
  • the chip system further includes a memory for storing program instructions and data necessary for accessing the device.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the invention provides a data transmission system, comprising the user plane function entity of any of the above aspects, and the n access devices of any of the foregoing aspects, wherein n is a positive integer.
  • FIG. 1 is a schematic structural diagram of a data transmission system according to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of application of a data transmission system in a 5G network according to an embodiment of the present application
  • FIG. 3 is a schematic structural diagram of hardware of a communication device according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic flowchart 1 of a data transmission method according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart 2 of a data transmission method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart 3 of a data transmission method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic flowchart of a method for configuring an identifier of an MLAN according to an embodiment of the present disclosure
  • FIG. 8 is a schematic structural diagram of a user plane function entity according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of an access device according to an embodiment of the present disclosure.
  • the MLAN's identity is used to identify an MLAN instance, a set of logical devices and users. If the MLAN is divided according to the scene, such as enterprise class, vehicle to everything communication (V2X), then a type of MLAN scenario can be identified by an MLAN type or a data network name (DNN), ie,
  • the MLAN ID is composed of a scene ID and MLAN number. The scene ID and MLAN number can uniquely identify an MLAN instance in a type of MLAN scenario. If the DNN resources are sufficient, the MLAN does not need to be divided according to the scene, and the identifier of one MLAN corresponds to a unique MLAN instance under one DNN.
  • the following embodiments of the present application do not specifically limit the MLAN according to the scenario. Only an MLAN identifier can uniquely identify an MLAN instance.
  • the MLAN ID can be a virtual local area network (VLAN). ID in technology. A unified explanation is given here, and will not be described below.
  • the identifier of the MLAN may be corresponding to a specific service scope, and may be available in the global scope.
  • the service scope corresponding to the identifier of the MLAN is not specifically limited in this embodiment.
  • the tunnel in the embodiment of the present application includes a next generation (N) interface 3 (N3 for short) tunnel and an N interface 9 (N9 for short) tunnel.
  • the N3 tunnel is a tunnel between an access device (such as a base station) and a user plane function (UPF) entity; the N9 tunnel is a tunnel between the UPF entity and the UPF entity.
  • an N3 tunnel is a tunnel of a session granularity
  • an N9 tunnel may be a tunnel of a session granularity or a tunnel of a device granularity.
  • the session granularity tunnel refers to a tunnel resource established for one session, and the tunnel is used only for one session.
  • a tunnel with a session granularity includes only one routing rule, and only the routing rule can forward data to the tunnel.
  • the lifetime of the tunnel of the session granularity is the life cycle of a session, that is, when a session disappears or is released, the tunnel of the session granularity needs to be released.
  • a device granular tunnel refers to a tunnel resource established for one or more sessions that can be used by one or more sessions.
  • the tunnel of one device granularity may include one or more routing rules, and the one or more routing rules may forward the data corresponding to the tunnel.
  • the lifetime of the tunnel of the device granularity is the lifetime of multiple sessions corresponding to the tunnel, that is, if the tunnel of the device granularity corresponds to M sessions, and M is a positive integer not less than 2, then multiple sessions corresponding to the tunnel When the first M-1 sessions in the session disappear or are released, only the routing rules corresponding to the corresponding session are released. When the Mth session in the multiple sessions corresponding to the tunnel disappears or is released, the device granular tunnel may be released. Certainly, when the Mth session in the multiple sessions corresponding to the tunnel disappears or is released, the tunnel of the device granularity may be reserved, so that the tunnel is not required to be re-established.
  • the session in the embodiment of the present application may be, for example, a packet data unit (PDU) session, which is not specifically limited in this embodiment of the present application.
  • PDU packet data unit
  • the path information in the embodiment of the present application may include at least one of path uplink information and path downlink information, for establishing a path between A and B.
  • the path uplink information may include an endpoint address or an endpoint identifier of the path on the A side, and an address of the A.
  • the path downlink information may include an endpoint address or an endpoint identifier of the path on the B side, and an address of the B. This is not specifically limited.
  • the path uplink information in the embodiment of the present application may also be referred to as uplink path information or other.
  • the path downlink information in the embodiment of the present application may also be referred to as downlink path information or other. No specific limitation.
  • the path in the embodiment of the present application may include the foregoing tunnel, and may also include other paths, which are not specifically limited in this embodiment of the present application.
  • the words “first”, “second”, and the like are used to distinguish the same items or similar items whose functions and functions are substantially the same. Those skilled in the art can understand that the words “first”, “second” and the like do not limit the number and execution order, and the words “first”, “second” and the like are not necessarily limited.
  • the network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.
  • FIG. 1 is a schematic structural diagram of a data transmission system 10 provided by an embodiment of the present application.
  • the data transmission system 10 includes a user plane functional entity 101 and n access devices 102, n being a positive integer.
  • the n access devices 102 may include, for example, a first access device 1021, a second access device 1022, ..., a nth access device 102n, and the like.
  • the user plane function entity 101 is configured to receive a data packet from the source device, where the data packet carries the multicast information.
  • the multicast information may be a multicast address or an indicator, which is used to indicate that the data packet needs to be sent to the target terminal in a multicast manner, which is not specifically limited in this embodiment of the present application.
  • the user plane function entity 101 is further configured to determine path downlink information of the n multicast paths corresponding to the target MLAN.
  • the target MLAN is the MLAN where the source device is located.
  • the user plane function entity 101 is further configured to send the data packet to the corresponding n access devices by using the n multicast paths corresponding to the path downlink information of the n multicast paths.
  • Each of the n access devices 102 is configured to receive a data packet from the user plane function entity 101 through the multicast path, and separately send the data packet to the s target terminals corresponding to the access device, Is a positive integer.
  • the contract MLAN of the target terminal is the same as the target MLAN, and is uniformly described herein, and details are not described herein again.
  • the path downlink information of each multicast path in the path downlink information of the n multicast paths includes the information of the corresponding access device, such as the address of the corresponding access device, where the application is implemented. This example does not specifically limit this.
  • the target terminals that access the same access device correspond to the same multicast path.
  • the target terminal that accesses the same access device may also correspond to multiple multicast paths, which is not specifically limited in this embodiment of the present application.
  • the source device in the embodiment of the present application may include a source terminal, a server, and the like, which is not specifically limited in this embodiment of the present application.
  • the user plane function entity 101 and each of the n access devices 102 may directly communicate with each other, and may also perform communication by forwarding of other devices. This is not specifically limited.
  • the multicast in the embodiment of the present application may be replaced by multicast or broadcast, which is not specifically limited in this embodiment of the present application.
  • n is greater than 1.
  • n may be equal to 1, and the description is not limited herein.
  • the user plane function entity may determine the path downlink information of the n multicast paths corresponding to the target MLAN, and then pass the n multicast paths.
  • the n multicast paths corresponding to the path downlink information respectively send the data packet to the corresponding n access devices, and the access device corresponds to the access device after receiving the data packet from the user plane function entity through the multicast path.
  • the s target terminals respectively send the data packet, so that the problem that the data packets in the prior art are repeatedly transmitted between the same user plane functional entity and the access device can be avoided, thereby saving the transmission bandwidth in the MLAN multicast scenario.
  • the foregoing data transmission system 10 can be applied to a 5th generation (5th generation, 5G) network and other networks in the future, which is not specifically limited in this embodiment of the present application.
  • 5G 5th generation
  • the first access device is included in the n access devices, and the target terminal corresponding to the first access device includes the terminal 1 and the terminal 2 as an example.
  • the network element or entity corresponding to the user plane function entity 101 may be a UPF entity; the network element or entity corresponding to the first access device 102 may be a first access network (AN) device.
  • the terminal 1 and the terminal 2 access the network through the first AN device.
  • the first AN device communicates with the UPF entity through an N3 interface (N3 for short).
  • the 5G network may further include an Access and Mobility Management Function (AMF) entity, a session management function (SMF) entity, and a source device.
  • AMF Access and Mobility Management Function
  • SMF session management function
  • a source device Both the terminal 1 and the terminal 2 communicate with the AMF entity through the N1 interface (N1 for short); the AN device communicates with the AMF entity through the N2 interface (N2 for short); the AMF entity communicates with the SMF entity through the N11 interface (N11 for short).
  • AMF Access and Mobility Management Function
  • SMF session management function
  • the 5G network may further include a unified data management (UDM) entity, an authentication server function (AUSF) entity, a policy control function (PCF) entity, and the like.
  • UDM unified data management
  • AUSF authentication server function
  • PCF policy control function
  • the name of the interface between the network elements in FIG. 2 is only an example. In the specific implementation, the interface name may be another name, which is not specifically limited in this embodiment of the present application.
  • the first AN device, the AMF entity, the SMF entity, the UPF entity, and the like of FIG. 2 are only one name, and the name does not limit the device itself.
  • the network element or entity corresponding to the first AN device, the AMF entity, the SMF entity, and the UPF entity may also be other names in the 5G network and other network in the future, which is not specifically limited in this embodiment of the present application.
  • the UPF entity may also be replaced with UPF, etc., and a unified description is provided herein, and details are not described below.
  • the terminal involved in the embodiment of the present application may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem; Including user unit (subscriber unit), cellular phone, smart phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem (modem), handheld device Handheld, laptop computer, cordless phone or wireless local loop (WLL) station, machine type communication (MTC) terminal, user equipment (user equipment) , UE), mobile station (MS), terminal device, etc.
  • PDA personal digital assistant
  • WLL wireless local loop
  • MTC machine type communication
  • user equipment user equipment
  • UE user equipment
  • MS mobile station
  • the access device involved in the embodiment of the present application refers to a device that accesses the core network, and may be, for example, a base station, a broadband network gateway (BNG), an aggregation switch, and a non-third generation. 3rd generation partnership project (3GPP) access equipment, etc.
  • the base station may include various forms of base stations, such as macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and the like.
  • the UPF entity involved in the embodiment of the present application has the functions of the user plane function entity shown in FIG. 1 , and can also implement a serving gateway (SGW) and a packet data network gateway. , PGW) user plane function.
  • SGW serving gateway
  • PGW packet data network gateway
  • the UPF entity may also be a software-defined network (SDN) switch (Switch), which is not specifically limited in this embodiment of the present application.
  • SDN software-defined network
  • the user plane function entity or the access device in FIG. 1 may be implemented by one physical device, or may be implemented by multiple physical devices, or may be a logical function module in a physical device. This is not specifically limited.
  • FIG. 3 is a schematic diagram showing the 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 can be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the execution of the program of the present application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication line 302 can include a path for communicating information between the components described above.
  • the communication interface 304 uses a device such as any transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • a device such as any transceiver for communicating 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 can 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 an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic 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 Any other media accessed, but not limited to this.
  • the memory may be present independently and connected to the processor via 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 solution of the present application, and is controlled by the processor 301 for execution.
  • the processor 301 is configured to execute computer execution instructions stored in the memory 303, thereby implementing the data transmission method provided by the following embodiments of the present application.
  • the computer-executed instructions in the embodiment of the present application may also be referred to as an application code, which is not specifically limited in this embodiment of the present application.
  • processor 301 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • communication device 300 can include multiple processors, such as processor 301 and processor 308 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • processors herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the communication device 300 can also include an output device 305 and an input device 306.
  • Output device 305 is in communication with processor 301 and can display information in a variety of ways.
  • the output device 305 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • Input device 306 is in communication with processor 301 and can receive user input in a variety of ways.
  • input device 306 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
  • the communication device 300 described above may be a general purpose device or a dedicated device.
  • the communication device 300 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or the like in FIG. device.
  • PDA personal digital assistant
  • the embodiment of the present application does not limit the type of the communication device 300.
  • the name of the message between the network elements or the name of each parameter in the message is only an example, and may be other names in the specific implementation, which is not specifically limited in this embodiment of the present application. .
  • the data transmission system shown in FIG. 1 is applied to the 5G network shown in FIG. 2, as shown in FIG. 4, which is a data transmission method provided by the embodiment of the present application, and the method includes the following steps:
  • the SMF entity determines a multicast path corresponding to the identifier of the MLAN.
  • the network management network element may send the subscription information to the SMF entity, and the SMF entity may determine the multicast path corresponding to the identifier of the MLAN.
  • the network management network element may be, for example, an operations support system (OSS).
  • S402 The SMF entity pre-establishes a multicast path corresponding to the identifier of the MLAN.
  • the SMF entity may pre-establish the multicast path corresponding to the identifier of the MLAN by:
  • the SMF entity After selecting the UPF entity according to the identifier of the MLAN, the SMF entity determines that n multicast paths between the UPF entity and the n access devices need to be established. In addition, referring to the existing manner of establishing the N3 tunnel, different UPP entities and different access devices in the n access devices are respectively established to establish different multicast paths. For example, for the multicast path 1 between the UPF entity and the first AN device in the n multicast paths, the UPF entity may send the path uplink information of the multicast path 1 to the first AN device by using the SMF entity, and the multicast path 1 The path uplink information includes the endpoint address or endpoint identifier of the multicast path 1 on the UPF entity side, and the address of the UPF entity.
  • the endpoint address or the endpoint identifier of the multicast path 1 on the UPF entity side may be allocated by the SMF entity and then sent to the UPF entity, or may be allocated by the UPF entity, which is not specifically limited in this embodiment.
  • the first AN device may allocate the endpoint address or the endpoint identifier of the multicast path 1 on the first AN device side, and then send the path downlink information of the multicast path 1 to the UPF entity through the SMF entity, and the path of the multicast path 1
  • the downlink information includes the endpoint address or the endpoint identifier of the multicast path 1 on the first AN device side, and the address of the first AN device, etc., so that the multicast path 1 between the UPF entity and the first AN device is established.
  • the UPF entity stores a correspondence between the identifier of the MLAN and the path downlink information of the n multicast paths.
  • the mapping between the identifier of the MLAN and the path downlink information of the n multicast paths may be sent by the SMF entity to the UPF entity, or may be established by the UPF entity. This example does not specifically limit this.
  • the embodiment of the present application can record the correspondence between the identifier of the MLAN and the path downlink information of the n multicast paths as the corresponding relationship 1, which is uniformly described herein, and will not be further described below.
  • the correspondence 1 can be as shown in Table 1:
  • MLAN logo Path downlink information of the multicast path MLAN1 Path downlink information of multicast path 1 MLAN1 Path downlink information of multicast path 2 ; whereas ; MLAN1 Path downlink information of multicast path m
  • the embodiment of the present application is described by taking the correspondence in the form of a table as an example.
  • the correspondence relationship may be represented in other forms, such as a text form or a session context form, etc.
  • the application examples are not specifically limited thereto.
  • the access device corresponding to the multicast path may also establish a correspondence between the identifier of the MLAN and the path uplink information of the multicast path. For example, for the first AN device corresponding to the multicast path 1, the correspondence between the identifier of the MLAN and the path uplink information of the multicast path 1 can be established.
  • the corresponding relationship between the identifier of the MLAN and the path downlink information of the multicast path 1 is recorded as the corresponding relationship 2 in the embodiment of the present application.
  • the correspondence 2 can be as shown in Table 3:
  • the terminal 1 sends an MLAN session establishment request to the AMF entity, so that the AMF entity receives the MLAN session establishment request from the terminal 1.
  • the MLAN session establishment request carries the identifier of the MLAN signed by the terminal 1 and the address of the first AN device.
  • the address of the first AN device may be characterized by the location information of the terminal 1 , which is not specifically limited in this embodiment of the present application.
  • the terminal 1 further configures information about the specific service area corresponding to the identifier of the MLAN. In this way, the terminal 1 can send an MLAN session establishment request to the AMF entity in the specific service area corresponding to the identifier of the MLAN according to the information of the specific service area corresponding to the identifier of the MLAN.
  • the terminal 1 sends an MLAN session establishment request to the AMF entity outside the specific service area corresponding to the identifier of the MLAN, the AMF entity or the SMF entity may determine that the current location of the terminal 1 is not in the specific service area corresponding to the identifier of the MLAN.
  • the embodiment of the present application does not specifically limit this.
  • the embodiment of the present application is only described by the example that the terminal 1 initiates a normal MLAN session establishment process, that is, when the identifier of the MLAN subscribed by the terminal 1 is available in the global scope, the terminal 1 sends an MLAN session establishment request to the AMF entity; or When the identifier of the MLAN to which the terminal 1 is subscribed corresponds to a specific service range, the terminal 1 transmits an MLAN session establishment request in a specific service area corresponding to the identifier of the MLAN that the terminal 1 has subscribed to, and a unified description will be given herein, and details are not described herein.
  • the AMF entity selects an SMF entity.
  • the specific manner for the AMF entity to select the SMF entity may refer to the existing solution, and details are not described herein.
  • the AMF entity sends the MLAN session establishment request to the SMF entity, so that the SMF entity receives the MLAN session establishment request from the AMF entity.
  • the SMF entity determines that the multicast path corresponding to the first AN device has been established.
  • the SMF entity may determine that the multicast corresponding to the first AN device has been established according to the address of the first AN device and Table 1 above. path.
  • the SMF entity may obtain the identifier of the MLAN that is signed by the terminal 1 from the UDM entity, and determine that the identifier of the MLAN carried in the MLAN session establishment request is the same as the identifier of the MLAN that the terminal 1 subscribes to.
  • the identifier of the MLAN carried in the MLAN session establishment request is the same as the identifier of the MLAN that is signed by the terminal 1, it may be determined that the identifier of the MLAN carried in the MLAN session establishment request is the identifier of the MLAN signed by the terminal 1, and the subsequent process may be performed;
  • the identifier of the MLAN carried in the MLAN session establishment request is different from the identifier of the MLAN that is signed by the terminal 1 , and the identifier of the MLAN carried in the MLAN session establishment request is not the identifier of the MLAN that is signed by the terminal 1 , and the process ends. This is not specifically limited.
  • the SMF entity sends a notification message to the first AN device, so that the first AN device receives the notification message from the SMF entity, where the notification message is used to indicate that the first AN device establishes a correspondence between the identifier of the MLAN and the information of the terminal 1.
  • the information of the terminal 1 is specifically the air interface transmission information of the terminal 1, and may include the air interface transmission identifier of the terminal 1, and the air interface transmission identifier may be, for example, a data radio bearer (DRB).
  • DRB data radio bearer
  • the embodiment of the present application can record the correspondence between the identifier of the MLAN and the information of the terminal 1 as the corresponding relationship 3, which is uniformly described herein, and will not be further described below.
  • the correspondence 3 can be as shown in Table 4:
  • the first AN device stores a correspondence between the identifier of the MLAN and the information of the terminal 1.
  • step S404b-S409b similar to steps S404a-S409a, except that in step S404b-S409b, the terminal in steps S404a-S409a is replaced by the terminal 2, and the steps S404a-S409a may be referred to, and details are not described herein.
  • the corresponding relationship between the identifier of the MLAN established by the first AN device and the information of the terminal 2 can be recorded as the corresponding relationship 4 in the step S409b.
  • the correspondence 4 can be as shown in Table 5:
  • the first AN device may also maintain the correspondence between the identifier of the MLAN and the information of the terminal as shown in Table 6.
  • the first AN device receives After the notification message from the SMF entity, the correspondence relationship 5 may be updated, and the correspondence between the identifier of the MLAN and the information of the terminal 1 is added in the corresponding relationship 5; similarly, in the process of establishing the MLAN session by the terminal 2, the first AN device receives After the notification message from the SMF entity, the corresponding relationship 5 can be updated, and the correspondence between the identifier of the MLAN and the information of the terminal 2 is added in the corresponding relationship 5, and so on, which is not specifically limited in this embodiment of the present application.
  • steps S404a-S409a and steps S404b-S409b there is no necessary execution sequence between steps S404a-S409a and steps S404b-S409b, and steps S404a-S409a may be performed first, and then steps S404b-S409b may be performed; Steps S404b-S409b, and then steps S404a-S409a are performed; steps S404a-S409a and steps S404b-S409b may be performed at the same time, which is not specifically limited in this embodiment of the present application.
  • the source device sends a data packet to the UPF entity, so that the UPF entity receives the data packet from the source device.
  • the data packet carries multicast information. For a description of the multicast information, refer to the foregoing embodiment, and details are not described herein again.
  • the data packet may carry the address information of the source device as the source address and the multicast address as the target address, which is not specifically limited in this embodiment.
  • the data packet may further carry the identifier of the target MLAN, where the target MLAN is the MLAN where the source device is located, which is not specifically limited in this embodiment.
  • the UPF entity determines path downlink information of the n multicast paths corresponding to the target MLAN.
  • the UPF entity may determine the path downlink information of the n multicast paths corresponding to the target MLAN according to Table 1 or Table 2.
  • the identifier of the target MLAN in the embodiment of the present application may be carried in the data packet, or may be determined after the UPF entity receives the data packet from the source device, which is not specifically limited in this embodiment of the present application.
  • the UPF entity may determine the identifier of the target MLAN according to the path uplink information corresponding to the source terminal and the corresponding relationship between the path uplink information and the target MLAN corresponding to the source terminal.
  • the UPF entity may determine the identifier of the target MLAN according to the path downlink information corresponding to the server and the correspondence between the path downlink information corresponding to the server and the target MLAN.
  • the embodiment of the present application does not specifically limit how the UPF entity knows the identifier of the target MLAN.
  • the data transmission method provided by the embodiment of the present application further includes the following steps:
  • the UPF entity sends the data packet to the first AN device by using the multicast path 1 corresponding to the path downlink information of the multicast path 1, so that the first AN device receives the data packet from the UPF entity through the multicast path 1.
  • the first AN device determines information of the corresponding s target terminals, where s is a positive integer.
  • the first AN device may determine the corresponding s targets according to Table 4 and Table 5 or according to Table 6 after receiving the data packet from the UPF entity.
  • the identifier of the target MLAN in the embodiment of the present application may be carried in the data packet, or may be determined after the first AN entity receives the data packet from the UPF entity by using the multicast path 1. This is not specifically limited.
  • the first AN device can determine the identifier of the target MLAN according to the path downlink information of the multicast path 1 and the corresponding relationship 2 shown in Table 3.
  • the embodiment of the present application does not specifically determine how the identifier of the target MLAN is obtained by the first AN device. limited.
  • the first AN device sends a data packet to the terminal 1 according to the information of the terminal 1, so that the terminal 1 receives the data packet from the first AN device.
  • the first AN device sends a data packet to the terminal 2 according to the information of the terminal 2, so that the terminal 2 receives the data packet from the first AN device.
  • step S414a and step S414b there is no necessary sequence of execution between step S414a and step S414b, which may be performed first step S414a, and then step S414b; or step S414b may be performed first, and then step S414a is performed; Step S414a and step S414b may be performed at the same time, which is not specifically limited in this embodiment of the present application.
  • steps S412-S414b in the embodiment of the present application provide a processing manner for the multicast path 1.
  • the multicast path 1 is used.
  • the processing method is processed, and will not be repeated here.
  • the data transmission method provided by the embodiment of the present application can avoid the problem that the data packet in the prior art is repeatedly transmitted between the same user plane function entity and the access device, thereby saving the transmission bandwidth in the MLAN multicast scenario.
  • the system embodiment For the analysis of the related technical effects, refer to the system embodiment, and details are not described herein again.
  • the action of the UPF entity and the first AN device in the foregoing steps S401 to S414b may be performed by the processor 301 in the communication device 300 shown in FIG. 3 by calling the application code stored in the memory 303. No restrictions are imposed.
  • the data transmission system shown in FIG. 1 is applied to the 5G network shown in FIG. 2, as shown in FIG. 5, which is another data transmission method provided by the embodiment of the present application, and the method includes the following steps. step:
  • the SMF entity determines that the multicast path corresponding to the first AN device is not established.
  • the SMF entity establishes a multicast path 1 corresponding to the first AN device.
  • step S402 For the manner in which the SMF entity establishes the multicast path 1 corresponding to the first AN device, refer to the related description in step S402, and details are not described herein again.
  • the UPF entity stores the correspondence between the identifier of the MLAN and the path downlink information of the m multicast paths.
  • the UPF entity stores the identifier of the MLAN and the multicast path.
  • the first AN device stores a correspondence between the identifier of the MLAN and the information of the terminal 1.
  • the steps S501-S507 in the embodiment of the present application provide the multicast path 1 mode corresponding to the identifier of the MLAN, and of course, the other multicast paths corresponding to the identifier of the MLAN may be established according to the foregoing.
  • the manner of the broadcast path 1 is processed, and will not be repeated here.
  • the UPF entity may store the correspondence 1 as shown in Table 1 or Table 2.
  • the data transmission method provided by the embodiment of the present application can avoid the problem that the data packet in the prior art is repeatedly transmitted between the same user plane function entity and the access device, thereby saving the transmission bandwidth in the MLAN multicast scenario.
  • the system embodiment For the analysis of the related technical effects, refer to the system embodiment, and details are not described herein again.
  • the action of the UPF entity and the first AN device in the foregoing steps S501 to S518b may be performed by the processor 301 in the communication device 300 shown in FIG. 3 by calling the application code stored in the memory 303. No restrictions are imposed.
  • the SMF entity selects a UPF entity.
  • the specific manner for the SMF entity to select the UPF entity may refer to the existing solution, and details are not described herein.
  • the SMF entity sends an N4 session message to the UPF entity, such that the UPF entity receives the N4 session message from the SMF entity.
  • the N4 session message carries the identifier of the MLAN signed by the terminal 1.
  • the UPF entity sends the path uplink information of the path corresponding to the terminal 1 to the first AN device, so that the first AN device receives the path uplink information of the path corresponding to the terminal 1 of the UPF entity.
  • the path corresponding to the terminal 1 is specifically the N3 tunnel between the UPF entity corresponding to the terminal 1 and the first AN device, which is not described herein.
  • the path uplink information of the path corresponding to the terminal 1 may be allocated by the SMF entity, or may be allocated by the UPF entity, which is not specifically limited in this embodiment of the present application.
  • the path uplink information of the path corresponding to the terminal 1 includes the endpoint address or the endpoint identifier of the path on the UPF entity side, and the address of the UPF entity, which is not specifically limited in this embodiment of the present application.
  • the UPF entity may store the correspondence between the identifier of the MLAN and the path uplink information of the path corresponding to the terminal 1, which is not specifically limited in this embodiment of the present application.
  • the first AN device sends the path downlink information of the path corresponding to the terminal 1 to the UPF entity, so that the UPF entity receives the path downlink information of the path corresponding to the terminal 1 of the first AN device.
  • the path downlink information of the path corresponding to the terminal 1 includes the endpoint address or the endpoint identifier of the path on the first AN device side, and the address of the first AN device, etc. No specific limitation.
  • the first AN device stores the correspondence between the path downlink information of the path corresponding to the terminal 1 and the information of the terminal 1.
  • the embodiment of the present application can record the correspondence between the path downlink information of the path corresponding to the terminal 1 and the information of the terminal 1 as the corresponding relationship 6, which is uniformly described herein, and will not be further described below.
  • the correspondence 6 can be as shown in Table 7:
  • the S609a and the UPF entity store the correspondence between the identifier of the MLAN and the path downlink information of the path corresponding to the terminal 1.
  • the embodiment of the present application can record the correspondence between the path downlink information of the path corresponding to the terminal 1 and the identifier of the MLAN as the corresponding relationship 7, which is uniformly described herein, and will not be further described below.
  • the correspondence 7 can be as shown in Table 8:
  • Step S607a may be performed first, and then the step S608a may be performed; or the step S608a may be performed first, and then the step S607a is performed; Steps S607a and S608a may be performed at the same time, which is not specifically limited in the embodiment of the present application.
  • step S601b-S609b similar to steps S601a-S609a, except that in step S601b-S609b, the terminal in steps S601a-S609a is replaced by the terminal 2, and the steps S601a-S609a may be referred to, and details are not described herein.
  • the corresponding relationship between the path downlink information of the path corresponding to the terminal 2 and the information of the terminal 2 stored in the first AN device is recorded in the corresponding relationship 8 in the step S608b, and is not described here.
  • the correspondence 8 can be as shown in Table 9:
  • the correspondence between the identifier of the MLAN stored by the UPF entity and the path downlink information of the path corresponding to the terminal 2 is recorded as a correspondence relationship 9, which is collectively described herein, and will not be described below.
  • the correspondence 9 can be as shown in Table 10:
  • the first AN device may also maintain the correspondence between the path downlink information of the path corresponding to the terminal and the information of the terminal, as shown in Table 11, in the process of establishing the MLAN session by the terminal 1. After acquiring the path downlink information of the path corresponding to the terminal 1 and the information of the terminal 1, the first AN device may update the correspondence 10, and add the path downlink information of the path corresponding to the terminal 1 and the information of the terminal 1 in the corresponding relationship 10.
  • the first AN device may update the correspondence 10 and add the corresponding relationship 10
  • the corresponding relationship between the path downlink information of the path corresponding to the terminal 2 and the information of the terminal 2, and so on, is not specifically limited in this embodiment of the present application.
  • Path downlink information of the path corresponding to the terminal Terminal information Path downlink information of the path corresponding to terminal 1.
  • Terminal 1 information Path downlink information of the path corresponding to terminal 2 Terminal 2 information ;
  • steps S601a-S609a and the steps S601b-S609b there is no necessary execution sequence between the steps S601a-S609a and the steps S601b-S609b, and the steps S601a-S609a may be performed first, and then the steps S601b-S609b may be performed; Steps S601b-S609b, and then steps S601a-S609a are performed; steps S601a-S609a and steps S601b-S609b may be performed at the same time, which is not specifically limited in the embodiment of the present application.
  • the SMF entity determines a multicast path corresponding to the identifier of the MLAN.
  • the SMF entity may send the subscription information to the SMF entity after the network management network element detects the new MLAN subscription information, and the SMF entity may determine the multicast path corresponding to the identifier of the MLAN.
  • the SMF entity may determine the multicast path corresponding to the identifier of the MLAN after the one or more MLAN session establishment requests are received, which is not specifically limited in this embodiment of the present application.
  • FIG. 4 For example, the embodiment shown in FIG. 4 is omitted, and details are not described herein again.
  • the UPF entity stores the identifier of the MLAN, the path downlink information of the m multicast paths, and the path downlink information of the path corresponding to the terminal corresponding to each multicast path.
  • the embodiment of the present application can record the correspondence between the MLAN identifier, the path downlink information of the m multicast paths, and the path downlink information of the path corresponding to the terminal corresponding to each multicast path as the correspondence relationship 11 .
  • the correspondence 11 can be as shown in Table 12:
  • the UPF entity when storing the correspondence 11 shown in Table 12, may separately store the correspondence between the identifier of the MLAN and the path downlink information of the multicast path, and the path of the multicast path.
  • the corresponding relationship between the downlink information and the path downlink information of the path corresponding to the terminal is not specifically limited in this embodiment of the present application.
  • the data transmission method provided by the embodiment of the present application further includes the following steps:
  • the UPF entity sends the data packet and the path downlink information of the path corresponding to the s target terminals to the first AN device through the multicast path 1 corresponding to the path downlink information of the multicast path 1, so that the first AN device passes the group.
  • the broadcast path 1 receives the data packet from the UPF entity and the path downlink information of the path corresponding to the corresponding s target terminals.
  • the UPF entity may determine path downlink information of the path corresponding to the terminal 1 and path downlink information of the path corresponding to the terminal 2.
  • the first AN device determines information of the corresponding s target terminals, where s is a positive integer.
  • the first AN device may determine the information of the corresponding s target terminals according to Table 7 and Table 9 or according to Table 11. .
  • S617a-S617b the same as S414a-S414b, for details, refer to the embodiment shown in FIG. 4, and details are not described herein again.
  • steps S615-S617b in the embodiment of the present application provide a processing manner for the multicast path 1.
  • the multicast path 1 is used.
  • the processing method is processed, and will not be repeated here.
  • each terminal initiates the MLAN session establishment process.
  • a path corresponding to the session needs to be established.
  • a multicast path is set up between each AN device and the UPF. Therefore, the AN device does not need to maintain the corresponding relationship shown in Tables 4 to 6, but only As in the prior art, the correspondences shown in Table 7, Table 9, or Table 11 can be maintained.
  • the data transmission method provided by the embodiment of the present application can avoid the problem that the data packet in the prior art is repeatedly transmitted between the same user plane function entity and the access device, thereby saving the transmission bandwidth in the MLAN multicast scenario.
  • the system embodiment For the analysis of the related technical effects, refer to the system embodiment, and details are not described herein again.
  • the action of the UPF entity and the first AN device in the foregoing steps S601 to S617b may be performed by the processor 301 in the communication device 300 shown in FIG. 3 by calling the application code stored in the memory 303. No restrictions are imposed.
  • the following is a schematic diagram of the process of configuring the MLAN identifier as shown in FIG. 7 by using the identifier of the MLAN that is signed by the terminal 1 on the terminal 1 as shown in FIG. 7 , and includes the following steps:
  • the UDM entity stores the MLAN subscription information corresponding to the terminal 1.
  • the MLAN subscription information of the terminal 1 includes the identifier of the MLAN signed by the terminal 1.
  • the MLAN subscription information of the terminal 1 may further include information of a specific service area corresponding to the identifier of the MLAN that the terminal 1 subscribes to.
  • the information of the specific service area corresponding to the identifier of the MLAN that the terminal 1 subscribes to can be configured on other network devices, for example, the MLAN of the terminal 1 is configured on one or more of the PCF entity, the AMF entity, and the SMF entity.
  • the information of the specific service area is identified, so that when the terminal 1 initiates the MLAN session establishment process, the network device may determine the terminal 1 according to the current location of the terminal 1 and the information of the specific service area corresponding to the identifier of the MLAN signed by the terminal 1.
  • the embodiment of the present application does not specifically limit the specific service area corresponding to the identifier of the MLAN that is subscribed to by the terminal 1 .
  • the terminal 1 sends a registration or re-registration request to the AMF entity, so that the AMF entity receives the registration or re-registration request from the terminal 1.
  • the AMF entity acquires the identifier of the MLAN signed by the terminal 1 from the UDM entity.
  • the AMF entity also signs the MLAN from the configuration terminal 1.
  • the information of the specific service area corresponding to the identifier of the MLAN that the terminal 1 is subscribed to for example, from the UDM entity, the PCF entity, or the SMF entity, the embodiment of the present application does not specifically limited.
  • the AMF entity sends a registration response to the terminal 1 to cause the terminal 1 to receive a registration response from the AMF entity.
  • the registration response carries the identifier of the MLAN signed by the terminal 1.
  • the AMF entity after the AMF entity obtains the identifier of the MLAN signed by the terminal 1 from the UDM entity, if the identifier of the MLAN signed by the terminal 1 corresponds to a specific service range, the AMF entity needs to be based on the current registration area of the terminal 1.
  • the AMF The entity sends a registration response to the terminal 1, and the registration response carries the identifier of the MLAN signed by the terminal 1.
  • the information about the specific service area corresponding to the identifier of the MLAN that the terminal 1 subscribes to may be included in the registration response, so that the terminal 1 can obtain the information of the specific service area corresponding to the identifier of the MLAN that the terminal 1 subscribes to.
  • the process of establishing an MLAN session is initiated in a specific service area corresponding to the identifier of the MLAN that is subscribed by the terminal 1, which is not specifically limited in this embodiment of the present application.
  • the terminal 1 can obtain the identifier of the MLAN that the terminal 1 subscribes to, and the MLAN session establishment process can be initiated according to the identifier of the MLAN that the terminal 1 subscribes to.
  • the MLAN session establishment process can be initiated according to the identifier of the MLAN that the terminal 1 subscribes to. For details, refer to the embodiment shown in FIG. 4 to FIG. Narration.
  • the process of configuring the identifier of the MLAN that is subscribed to by the terminal on the other terminal may be referred to the process of configuring the identifier of the MLAN that is subscribed to by the terminal 1 on the terminal 1, and details are not described herein again.
  • the solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between the network elements.
  • the above-mentioned user plane function entity or access device includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application may divide the function module of the user plane function entity or the access device according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one process.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 8 shows a schematic structural diagram of a user plane functional entity 80.
  • the user plane function entity 80 includes a processing module 801 and a transceiver module 802.
  • the transceiver module 802 is configured to receive a data packet from the source device, where the data packet carries the multicast information
  • the processing module 801 is configured to determine path downlink information of the n multicast paths corresponding to the target MLAN, and the transceiver module 802.
  • the n multicast paths corresponding to the path downlink information of the n multicast paths respectively send data packets to the corresponding n access devices, where n is a positive integer.
  • the processing module 801 is specifically configured to: determine path downlink information of the n multicast paths corresponding to the target MLAN according to the identifier of the target MLAN, and the first correspondence, where the first correspondence includes the identifier of the target MLAN. Correspondence between the downlink information and the path of the n multicast paths.
  • the transceiver module 802 is further configured to receive a first correspondence from the session management entity.
  • the processing module 801 is further configured to determine, according to the path downlink information of the n multicast paths, and the second correspondence, the path downlink information corresponding to the target terminal corresponding to each multicast path, where the second corresponding The relationship includes the correspondence between the path downlink information of each multicast path and the path downlink information of the path corresponding to the corresponding target terminal.
  • the transceiver module 802 is further configured to send the path downlink information of the path corresponding to the corresponding target terminal to the corresponding access device by using the n multicast paths corresponding to the path downlink information of the n multicast paths.
  • the transceiver module 802 is further configured to receive a second correspondence from the session management entity.
  • the data packet carries the identity of the target MLAN.
  • the source device includes a source terminal
  • the processing module 801 is further configured to determine, according to the path uplink information of the path corresponding to the source terminal, and the third correspondence, the identifier of the target MLAN, where the third correspondence is Corresponding relationship between the path uplink information of the path corresponding to the source terminal and the identifier of the target MLAN.
  • the source device includes a server
  • the processing module 801 is further configured to determine the identifier of the target MLAN according to the path downlink information of the path corresponding to the server and the fourth correspondence, where the fourth correspondence includes the server. Correspondence between the path downlink information of the corresponding path and the identifier of the target MLAN.
  • the user plane function entity 80 is presented in a form that divides each function module in an integrated manner.
  • a “module” herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the user plane functional entity 80 may take the form shown in FIG.
  • the processor 301 in FIG. 3 can execute the instruction by calling the computer stored in the memory 303, so that the user plane function entity 80 executes the data transmission method in the above method embodiment.
  • the function/implementation process of the processing module 801 and the transceiver module 802 in FIG. 8 can be implemented by the processor 301 in FIG. 3 calling a computer execution instruction stored in the memory 303.
  • the function/implementation process of the processing module 801 in FIG. 8 can be implemented by the processor 301 in FIG. 3 calling the computer execution instruction stored in the memory 303, and the function/implementation process of the transceiver module 802 in FIG.
  • the communication interface 304 in 3 is implemented.
  • the user plane function entity provided by the embodiment of the present application can be used to perform the foregoing data transmission method. Therefore, the technical effects that can be obtained can be referred to the foregoing method embodiments, and details are not described herein again.
  • FIG. 9 shows a schematic structural diagram of an access device 90.
  • the access device 90 includes a receiving module 901 and a sending module 902.
  • the receiving module 901 is configured to receive, by using a multicast path, a data packet from a user plane function entity, where the data packet carries the multicast information
  • the sending module 902 is configured to separately send the data packet to the target terminal, where the target terminal
  • the contracted MLAN is the same as the target MLAN, and the target MLAN is the MLAN where the source device that sends the packet is located, and s is a positive integer.
  • the sending module 902 is specifically configured to: determine information of the target terminals according to the identifier of the target MLAN and the first correspondence, where the first correspondence includes the identifier of the target MLAN and the information of the target terminals. Correspondence relationship; according to the information of the s target terminals, the data packets are respectively sent to the s target terminals.
  • the access device 90 further includes a processing module 903.
  • the processing module 903 is configured to establish an information correspondence between the identifier of the target MLAN and the first terminal in the process of establishing the MLAN session in the target MLAN by the first terminal.
  • the receiving module 901 is further configured to: when the first terminal establishes the MLAN session in the target MLAN, receive the notification message from the session management entity, where the first multicast path has been established, the notification message It is used to instruct the access device 90 to establish an information correspondence between the identifier of the target MLAN and the first terminal.
  • the receiving module 901 is further configured to: receive the path downlink information of the path corresponding to the s target terminals of the user plane function entity by using the multicast path;
  • the sending module 902 is specifically configured to: downlink according to the path corresponding to the s target terminals The information, and the second correspondence, determining the information of the target terminals, wherein the second correspondence includes the correspondence between the path downlink information of the path corresponding to the target terminals and the information of the target terminals; The information is sent to the target terminals separately.
  • the second terminal is included in the s target terminals.
  • the access device 90 further includes a processing module 903.
  • the processing module 903 is configured to establish, in the process of establishing the MLAN session in the target MLAN, the path downlink information of the path corresponding to the second terminal and the information correspondence relationship of the second terminal.
  • the data packet carries the identity of the target MLAN.
  • the access device 90 further includes a processing module 903.
  • the processing module 903 is configured to determine the identifier of the target MLAN according to the path downlink information of the multicast path and the third correspondence, where the third correspondence includes the correspondence between the path downlink information of the multicast path and the target MLAN identifier.
  • the access device 90 is presented in a form that divides each functional module in an integrated manner.
  • a “module” herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • access device 90 can take the form shown in FIG.
  • the processor 301 in FIG. 3 can execute an instruction by calling a computer stored in the memory 303, so that the access device 90 executes the data transmission method in the above method embodiment.
  • the function/implementation process of the receiving module 901, the sending module 902, and the processing module 903 in FIG. 9 can be implemented by the processor 301 in FIG. 3 calling a computer executing instruction stored in the memory 303.
  • the function/implementation process of the processing module 903 in FIG. 8 can be implemented by the processor 301 in FIG. 3 calling the computer execution instruction stored in the memory 303, and the function/implementation of the receiving module 901 and the transmitting module 902 in FIG.
  • the process can be implemented by the communication interface 304 in FIG.
  • the access device provided by the embodiment of the present application can be used to perform the foregoing data transmission method. Therefore, the technical effects that can be obtained by reference to the foregoing method embodiments are not described herein.
  • the user plane function entity 80 and the access device 90 are all presented in the form of dividing each function module in an integrated manner.
  • the embodiments of the present application may also be corresponding to the function modules of the function, the control device, and the session management entity, which are not specifically limited in this embodiment.
  • the embodiment of the present application provides a chip system, where the chip system includes a processor, and is configured to support a user plane function entity to implement the foregoing data transmission method, for example, determining path downlink information of n multicast paths corresponding to the target MLAN. .
  • the chip system also includes a memory. This memory is used to store the necessary program instructions and data for the user plane function entity.
  • the chip system may be composed of a chip, and may also include a chip and other discrete devices. This embodiment of the present application does not specifically limit this.
  • the embodiment of the present application provides a chip system, where the chip system includes a processor, and is configured to support the access device to implement the foregoing data transmission method, for example, in a process in which the first terminal establishes an MLAN session in the target MLAN, Establish a correspondence between the identifier of the target MLAN and the information of the first terminal.
  • the chip system also includes a memory. This memory is used to store the necessary program instructions and data for the access device.
  • the chip system may be composed of a chip, and may also include a chip and other discrete devices. This embodiment of the present application does not specifically limit this.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a solid state disk (SSD)

Landscapes

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

Abstract

本申请实施例提供数据传输方法、设备及系统,可以在MLAN组播场景下节省传输带宽。方法包括:用户面功能实体接收来自源设备的数据包,其中,该数据包携带组播信息;用户面功能实体确定目标移动局域网MLAN对应的n个组播路径的路径下行信息;用户面功能实体通过该n个组播路径的路径下行信息对应的n个组播路径分别向对应的n个接入设备发送该数据包,n为正整数。

Description

数据传输方法、设备及系统
本申请要求于2017年12月18日提交中国国家知识产权局、申请号为201711368645.0、发明名称为“数据传输方法、设备及系统”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域,尤其涉及数据传输方法、设备及系统。
背景技术
局域网(local area network,LAN)是在一个局部的地理范围内,例如一个学校、工厂和机关内,将各种计算机、外部设备和数据库等互相联接起来组成的计算机通信网。它可以通过数据通信网或专用数据电路,与远方的局域网、数据库或处理中心相连接,构成一个大范围的信息处理系统。随着新兴企业办公模式及智能居家模式的出现,有线LAN和无线LAN(wireless LAN,WLAN)显现了其在部署复杂、灵活性、移动性、覆盖范围等方面的不足,这促使LAN技术再发展以适应未来应用对LAN的需求。
利用移动网络其本身的广覆盖特点,来直接提供LAN服务,称之为移动局域网(mobile local area network,MLAN)。MLAN可以在更广泛的移动网络覆盖范围内使用,即无论用户是否在同一地域,只要加入同一MLAN,即可实现基于LAN的数据交换或通信。利用已经广覆盖的移动网络,MLAN的创建及其伸缩迁移调整均可由移动网络自动完成,不需要人工干预。此外,MLAN可按需定制,不同MLAN之间互相安全隔离。
目前,在MLAN组播场景下中,当用户面功能(user plane function,UPF)实体接收到一个数据包时,将该数据包的目标地址替换为该MLAN下各终端的寻址地址,再根据寻址地址映射到各终端寻址地址对应的路径,通过相应路径将数据包分别发送给同一MLAN下的各各终端。
然而,该数据传输方法中,若多个终端接入相同的接入设备,则将浪费传输带宽。因此,如何在MLAN组播场景下,节省传输带宽,是目前亟待解决的问题。
发明内容
本申请实施例提供数据传输方法、设备及系统,可以在MLAN组播场景下节省传输带宽。
为达到上述目的,本申请实施例提供如下技术方案:
第一方面,提供一种数据传输方法,该方法包括:用户面功能实体接收来自源设备的数据包,其中,该数据包携带组播信息;该用户面功能实体确定目标移动局域网MLAN对应的n个组播路径的路径下行信息;该用户面功能实体通过该n个组播路径的路径下行信息对应的n个组播路径分别向对应的n个接入设备发送该数据包,n为正整数。基于本申请实施例提供的数据传输方法,可以避免现有技术中数据包在相同的用户面功能实体和接入设备之间重复传输的问题,从而可以节省MLAN组播场景下的传输带宽。
在一种可能的设计中,该用户面功能实体确定目标MLAN对应的n个组播路径的路径下行信息,包括:该用户面功能实体根据该目标MLAN的标识、以及第一对应关系,确定该目标MLAN对应的n个组播路径的路径下行信息,其中,该第一对应关系包括该目标MLAN 的标识和该n个组播路径的路径下行信息的对应关系。由于第一对应关系包括目标MLAN的标识和该n个组播路径的路径下行信息的对应关系,因此,在用户面功能实体获知目标MLAN的标识的情况下,可以根据该第一对应关系,及时快速的确定该目标MLAN对应的n个组播路径的路径下行信息。
在一种可能的设计中,该方法还包括:该用户面功能实体接收来自会话管理实体的该第一对应关系。
在一种可能的设计中,该n个组播路径的信息中包括第一组播路径的信息,该方法还包括:该会话管理实体在该目标MLAN中建立该第一组播路径;该会话管理实体向该用户面功能实体发送该目标MLAN的标识和该第一组播路径的路径下行信息的对应关系。也就是说,在会话管理实体在目标MLAN中建立第一组播路径之后,用户面功能实体需要获取目标MLAN的标识和该第一组播路径的路径下行信息的对应关系。进而,如上所述,在用户面功能实体获知目标MLAN的标识的情况下,可以根据第一对应关系,及时快速的确定该目标MLAN对应的n个组播路径的路径下行信息。
在一种可能的设计中,与该第一组播路径对应的t个目标终端中包括第一终端,t为正整数;该会话管理实体在该目标MLAN中建立该第一组播路径,包括:在该第一终端在该目标MLAN中建立MLAN会话的过程中,在未建立该第一组播路径的情况下,该会话管理实体建立该第一组播路径。也就是说,该实现方式中,每个接入设备和用户面功能实体之间仅建立一条组播路径,在终端发起MLAN会话建立流程时,若接入设备和用户面功能实体之间已经建立组播路径,则不需要再建立会话对应的路径,从而可以节省会话资源。
在一种可能的设计中,在该用户面功能实体确定该目标MLAN对应的n个组播路径的路径下行信息之后,还包括:该用户面功能实体根据该n个组播路径的路径下行信息、以及第二对应关系,确定与该每个组播路径的路径下行信息对应的目标终端对应的路径的路径下行信息,其中,该第二对应关系包括该每个组播路径的路径下行信息和对应的目标终端对应的路径的路径下行信息的对应关系;该用户面功能实体通过该n个组播路径的路径下行信息对应的n个组播路径分别向对应的接入设备发送对应的目标终端对应的路径的路径下行信息。基于该方案,可以使得接入设备接收来自用户面功能实体的每个接入设备对应的目标终端对应的路径下行信息。进而,接入设备可以根据对应的目标终端对应的路径下行信息,将数据发送给目标终端,实现MLAN组播场景下的数据传输。
在一种可能的设计中,该方法还包括:该用户面功能实体接收来自会话管理实体的该第二对应关系。
在一种可能的设计中,该n个组播路径的路径下行信息中包括第二组播路径的路径下行信息,与该第二组播路径对应的s个目标终端中包括第二终端,s为正整数;该方法还包括:该会话管理实体建立该第二组播路径和该第二终端对应的路径;该会话管理实体向该用户面功能实体发送该目标MLAN的标识和该第二组播路径的路径下行信息的对应关系、以及该目标MLAN的标识和该第二终端对应的路径的路径下行信息的对应关系。也就是说,该实现方式中,在每个终端发起MLAN会话建立流程时,可以像现有技术一样建立会话对应的路径。此外,每个接入设备和用户面功能实体之间还需要建立一条组播路径,这样,用户面功能实体可以建立组播路径的路径下行信息和对应的终端对应的路径的路径下行信息的对应关系,进而可以根据该对应关系进行数据传输。该方式可以在减少对现有流程的修改的前提下,实现MLAN组播场景下的数据传输。
在一种可能的设计中,该数据包携带该目标MLAN的标识。
在一种可能的设计中,该源设备包括源终端,在该用户面功能实体接收来自源设备的数据包之后,还包括:该用户面功能实体根据该源终端对应的路径的路径上行信息、以及第三对应关系,确定该目标MLAN的标识,其中,该第三对应关系包括该源终端对应的路径的路径上行信息和该目标MLAN的标识的对应关系。基于该方式,用户面功能实体可以确定目标MLAN的标识。
在一种可能的设计中,该源设备包括服务器,在该用户面功能实体接收来自源设备的数据包之后,还包括:该用户面功能实体根据该服务器对应的路径的路径下行信息、以及第四对应关系,确定该目标MLAN的标识,其中,该第四对应关系包括该服务器对应的路径的路径下行信息和该目标MLAN的标识的对应关系。基于该方式,用户面功能实体可以确定目标MLAN的标识。
第二方面,提供一种数据传输方法,该方法包括:接入设备通过组播路径接收来自用户面功能实体的数据包,其中,该数据包携带组播信息;该接入设备向s个目标终端分别发送该数据包,其中,该目标终端的签约移动局域网MLAN与目标MLAN相同,该目标MLAN为发送该数据包的源设备所在的MLAN,s为正整数。基于本申请实施例提供的数据传输方法,可以避免现有技术中数据包在相同的用户面功能实体和接入设备之间重复传输的问题,从而可以节省MLAN组播场景下的传输带宽。
在一种可能的设计中,该接入设备向s个目标终端分别发送该数据包,包括:该接入设备根据该目标MLAN的标识,以及第一对应关系,确定该s个目标终端的信息,其中,该第一对应关系包括该目标MLAN的标识和该s个目标终端的信息的对应关系;该接入设备根据该s个目标终端的信息,向该s个目标终端分别发送该数据包。由于第一对应关系包括目标MLAN的标识和s个目标终端的信息的对应关系,因此,在用户面功能实体获知目标MLAN的标识的情况下,可以根据该第一对应关系,及时快速的确定s个目标终端的信息。
在一种可能的设计中,该s个目标终端中包括第一终端,该方法还包括:在该第一终端在该目标MLAN中建立MLAN会话的过程中,该接入设备建立该目标MLAN的标识和该第一终端的信息对应关系。
在一种可能的设计中,该方法还包括:在该第一终端在该目标MLAN中建立MLAN会话的过程中,在已经建立该第一组播路径的情况下,该接入设备接收来自会话管理实体的通知消息,该通知消息用于指示该接入设备建立该目标MLAN的标识和该第一终端的信息对应关系。也就是说,该实现方式中,每个接入设备和用户面功能实体之间仅建立一条组播路径,在终端发起MLAN会话建立流程时,若接入设备和用户面功能实体之间已经建立组播路径,则不需要再建立会话对应的路径,从而可以节省会话资源。
在一种可能的设计中,该方法还包括:该接入设备通过该组播路径接收来自该用户面功能实体的该s个目标终端对应的路径的路径下行信息;该接入设备向s个目标终端分别发送该数据包,包括:该接入设备根据该s个目标终端对应的路径的路径下行信息,以及第二对应关系,确定该s个目标终端的信息,其中,该第二对应关系包括该s个目标终端对应的路径的路径下行信息和该s个目标终端的信息的对应关系;该接入设备根据该s个目标终端的信息,向该s个目标终端分别发送该数据包。也就是说,该实现方式中,接入设备可以根据接收到的s个目标终端对应的路径下行信息,以及第二对应关系进行数据传输。该方式可以在减少对现有流程的修改的前提下,实现MLAN组播场景下的数据传输。
在一种可能的设计中,该s个目标终端中包括第二终端,该方法还包括:在该第二终端在该目标MLAN中建立MLAN会话的过程中,该接入设备建立该第二终端对应的路径的路 径下行信息和该第二终端的信息对应关系。
在一种可能的设计中,该数据包携带该目标MLAN的标识。
在一种可能的设计中,在该接入设备通过组播路径接收来自该用户面功能实体的该数据包之后,还包括:该接入设备根据该组播路径的路径下行信息,以及第三对应关系,确定该目标MLAN的标识,其中,该第三对应关系包括该组播路径的路径下行信息和该目标MLAN标识的对应关系。基于该方式,接入设备可以确定目标MLAN的标识。
第三方面,提供了一种用户面功能实体,该用户面功能实体具有实现上述第一方面所述的方法的功能。该功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第四方面,提供了一种用户面功能实体,包括:处理器和存储器;该存储器用于存储计算机执行指令,当该用户面功能实体运行时,该处理器执行该存储器存储的该计算机执行指令,以使该用户面功能实体执行如上述第一方面中任一所述的数据传输方法。
第五方面,提供了一种计算机可读存储介质,该计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机可以执行上述第一方面中任意一项所述的数据传输方法。
第六方面,提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机可以执行上述第一方面中任意一项所述的数据传输方法。
第七方面,提供了一种芯片系统,该芯片系统包括处理器,用于支持用户面功能实体实现上述方面中所涉及的功能,例如确定目标MLAN对应的n个组播路径的路径下行信息。在一种可能的设计中,所述芯片系统还包括存储器,所述存储器,用于保存用户面功能实体必要的程序指令和数据。该芯片系统,可以由芯片构成,也可以包含芯片和其他分立器件。
其中,第三方面至第七方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果,此处不再赘述。
第八方面,提供了一种接入设备,该接入设备具有实现上述第二方面所述的方法的功能。该功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第九方面,提供了一种接入设备,包括:处理器和存储器;该存储器用于存储计算机执行指令,当该接入设备运行时,该处理器执行该存储器存储的该计算机执行指令,以使该接入设备执行如上述第二方面中任一所述的数据传输方法。
第十方面,提供了一种计算机可读存储介质,该计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机可以执行上述第二方面中任意一项所述的数据传输方法。
第十一方面,提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机可以执行上述第二方面中任意一项所述的数据传输方法。
第十二方面,提供了一种芯片系统,该芯片系统包括处理器,用于支持接入设备实现上述方面中所涉及的功能,例如在第一终端在目标MLAN中建立MLAN会话的过程中,建立目标MLAN的标识和第一终端的信息的对应关系。在一种可能的设计中,所述芯片系统还包括存储器,所述存储器,用于保存接入设备必要的程序指令和数据。该芯片系统,可以由芯片构成,也可以包含芯片和其他分立器件。
其中,第八方面至第十二方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果,此处不再赘述。
第十三方面,提供一种数据传输系统,包括上述任一方面所述的用户面功能实体和n个上述任一方面所述的接入设备,n为正整数。
其中,本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为本申请实施例提供的数据传输系统的架构示意图;
图2为本申请实施例提供的数据传输系统在5G网络中的应用示意图;
图3为本申请实施例提供的通信设备的硬件结构示意图;
图4为本申请实施例提供的数据传输方法的流程示意图一;
图5为本申请实施例提供的数据传输方法的流程示意图二;
图6为本申请实施例提供的数据传输方法的流程示意图三;
图7为本申请实施例提供的MLAN的标识的配置方法流程示意图;
图8为本申请实施例提供的用户面功能实体的结构示意图;
图9为本申请实施例提供的接入设备的结构示意图。
具体实施方式
为了方便理解本申请实施例的技术方案,首先给出本申请相关技术的简要介绍如下。
第一,MLAN的标识(identity,ID):
MLAN的标识用于标识一个MLAN实例,即一组逻辑上的设备和用户。若MLAN根据场景划分,例如企业类,车与外界的通信(vehicle to everything communication,V2X),则一类MLAN场景可以通过一个MLAN类型或数据网络名称(Data network name,DNN)来标识,即一个MLAN的标识由一个场景标识+MLAN编号组成,结合场景标识和MLAN编号能唯一标识一类MLAN场景下的某个MLAN实例。若DNN资源充足,MLAN无需根据场景划分,则一个MLAN的标识对应一个DNN下的唯一MLAN实例。本申请下述实施例对是否根据场景划分MLAN不作具体限定,仅以一个MLAN的标识能唯一标识一个MLAN实例为例进行说明,特别地,MLAN ID可以是虚拟局域网(virtual local area network,VLAN)技术中的ID。在此进行统一说明,以下不再赘述。
此外,本申请实施例中,MLAN的标识可以对应一个特定的服务范围,也可以在全局范围内可用,本申请实施例对MLAN的标识对应的服务范围不作具体限定。
第二,隧道:
本申请实施例中的隧道包括下一代网络(next generation,N)接口3(简称N3)隧道和N接口9(简称N9)隧道。其中,N3隧道为接入设备(比如基站)与用户面功能(user plane function,UPF)实体之间的隧道;N9隧道为UPF实体与UPF实体之间的隧道。通常,N3隧道为会话粒度的隧道,N9隧道可以为会话粒度的隧道,也可以为设备粒度的隧道。
其中,会话粒度的隧道是指,针对一个会话建立的隧道资源,该隧道仅供一个会话使用。其中,一个会话粒度的隧道仅包括一个路由规则,只有该路由规则才能够对应该隧道转发数据。另外,会话粒度的隧道的生命周期是一个会话的生命周期,即当一个会话消失或释放时,会话粒度的隧道也需要释放。
设备粒度的隧道是指,针对一个或多个会话建立的隧道资源,该隧道可以供一个或多个会话使用。其中,一个设备粒度的隧道可以包括一个或者多个路由规则,该一个或多个路由规则均可以对应该隧道转发数据。另外,设备粒度的隧道的生命周期是该隧道对应的多个会话的生命周期,即假设设备粒度的隧道对应M个会话,M为不小于2的正整数,则当该隧道对应的多个会话中的前M-1个会话消失或释放时,仅释放相应会话对应的路由规则;当该隧 道对应的多个会话中的第M个会话消失或释放时,设备粒度的隧道才可能释放。当然,当该隧道对应的多个会话中的第M个会话消失或释放时,也可以保留该设备粒度的隧道,以便后续不需要重新建立该隧道,本申请实施例对此不作具体限定。
可选的,本申请实施例中的会话例如可以是分组数据单元(packet data unit,PDU)会话,本申请实施例对此不作具体限定。
第三,路径信息:
本申请实施例中的路径信息可以包括路径上行信息和路径下行信息中的至少一个,用于建立A和B之间的路径。其中,路径上行信息可以包括路径在A侧的端点地址或端点标识、以及A的地址等,路径下行信息可以包括路径在B侧的端点地址或端点标识、以及B的地址等,本申请实施例对此不作具体限定。
可选的,本申请实施例中的路径上行信息也可以称之为上行路径信息或其他,本申请实施例中的路径下行信息也可以称之为下行路径信息或其他,本申请实施例对此不作具体限定。
可选的,本申请实施例中的路径可以包括上述的隧道,也可以包括其他路径,本申请实施例对此不作具体限定。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述。其中,在本申请的描述中,除非另有说明,“/”表示或的意思,例如,A/B可以表示A或B;本文中的“和/或”仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。并且,在本申请的描述中,除非另有说明,“多个”是指两个或多于两个。另外,为了便于清楚描述本申请实施例的技术方案,在本申请的实施例中,采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定,并且“第一”、“第二”等字样也并不限定一定不同。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案,并不构成对于本申请实施例提供的技术方案的限定,本领域普通技术人员可知,随着网络架构的演变和新业务场景的出现,本申请实施例提供的技术方案对于类似的技术问题,同样适用。
如图1所示,为本申请实施例提供的数据传输系统10的架构示意图。该数据传输系统10包括用户面功能实体101和n个接入设备102,n为正整数。n个接入设备102例如可以包括第一接入设备1021、第二接入设备1022、……、第n接入设备102n等。
其中,用户面功能实体101,用于接收来自源设备的数据包,其中,该数据包携带组播信息。该组播信息具体可以是一个组播地址或者一个指示符,用于指示该数据包需要以组播形式发送给目标终端,本申请实施例对此不作具体限定。
用户面功能实体101,还用于确定目标MLAN对应的n个组播路径的路径下行信息。其中,该目标MLAN为源设备所在的MLAN。
用户面功能实体101,还用于通过n个组播路径的路径下行信息对应的n个组播路径分别向对应的n个接入设备发送该数据包。
n个接入设备102中的每个接入设备,用于通过组播路径接收来自用户面功能实体101的数据包,并向该接入设备对应的s个目标终端分别发送该数据包,s为正整数。
其中,本申请实施例中,目标终端的签约MLAN与目标MLAN相同,在此统一说明,以下不再赘述。
可选的,本申请实施例中,n个组播路径的路径下行信息中每个组播路径的路径下行信息 包括对应的接入设备的信息,比如对应的接入设备的地址,本申请实施例对此不作具体限定。
可选的,本申请实施例中,接入相同接入设备的目标终端对应同一个组播路径。当然,接入相同接入设备的目标终端也可以对应多个组播路径,本申请实施例对此不作具体限定。
可选的,本申请实施例中的源设备可以包括源终端或者服务器等,本申请实施例对此不作具体限定。
可选的,本申请实施例中,用户面功能实体101和n个接入设备102中的每个接入设备之间可以直接通信,也可以通过其他设备的转发进行通信,本申请实施例对此不作具体限定。
可选的,本申请实施例中的组播也可以替换为多播或广播,本申请实施例对此不作具体限定。
需要说明的是,图1所示的数据传输系统以n大于1为例进行示意,实际实现过程中,n可以等于1,在此统一说明,本申请实施例对此不作具体限定。
基于本申请实施例提供的数据传输系统,由于用户面功能实体在接收来自源设备的数据包之后,可以确定目标MLAN对应的n个组播路径的路径下行信息,进而通过n个组播路径的路径下行信息对应的n个组播路径分别向对应的n个接入设备发送该数据包,由接入设备在通过组播路径接收来自用户面功能实体的数据包之后,向该接入设备对应的s个目标终端分别发送该数据包,因此可以避免现有技术中数据包在相同的用户面功能实体和接入设备之间重复传输的问题,从而可以节省MLAN组播场景下的传输带宽。
可选的,上述数据传输系统10可以应用于第五代(5th generation,5G)网络以及未来其它的网络,本申请实施例对此不作具体限定。
其中,以n个接入设备中包括第一接入设备,第一接入设备对应的目标终端包括终端1和终端2为例,若上述数据传输系统10应用于5G网络,则如图2所示,用户面功能实体101所对应的网元或者实体可以为UPF实体;第一接入设备102所对应的网元或实体可以为第一接入网(access network,AN)设备。其中,终端1和终端2通过第一AN设备接入网络。第一AN设备通过N3接口(简称N3)与UPF实体通信。
此外,如图2所示,该5G网络还可以包括接入与移动管理功能(Access and Mobility Management Function,AMF)实体、会话管理功能(session management function,SMF)实体和源设备。终端1和终端2均通过N1接口(简称N1)与AMF实体通信;AN设备通过N2接口(简称N2)与AMF实体通信;AMF实体通过N11接口(简称N11)与SMF实体通信。
虽然未示出,该5G网络还可以包括统一数据管理(unified data management,UDM)实体、鉴权服务器功能(authentication server function,AUSF)实体、策略控制功能(policy control function,PCF)实体等,本申请实施例对此不作具体限定。
需要说明的是,图2中的各个网元之间的接口名字只是一个示例,具体实现中接口名字可能为其他名字,本申请实施例对此不作具体限定。
需要说明的是,图2的第一AN设备、AMF实体、SMF实体和UPF实体等仅是一个名字,名字对设备本身不构成限定。在5G网络以及未来其它的网络中,第一AN设备、AMF实体、SMF实体和UPF实体所对应的网元或实体也可以是其他的名字,本申请实施例对此不作具体限定。例如,该UPF实体还有可能被替换为UPF,等等,在此进行统一说明,以下不再赘述。
可选的,本申请实施例中所涉及到的终端(terminal)可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备;还 可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant,PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop,WLL)台、机器类型通信(machine type communication,MTC)终端、用户设备(user equipment,UE),移动台(mobile station,MS),终端设备(terminal device)等。为方便描述,本申请中,上面提到的设备统称为终端。
可选的,本申请实施例中所涉及到的接入设备指的是接入核心网的设备,例如可以是基站,宽带网络业务网关(broadband network gateway,BNG),汇聚交换机,非第三代合作伙伴计划(3rd generation partnership project,3GPP)接入设备等。基站可以包括各种形式的基站,例如:宏基站,微基站(也称为小站),中继站,接入点等。
可选的,本申请实施例中所涉及到的UPF实体除了具备图1所示的用户面功能实体的功能,还可实现服务网关(serving gateway,SGW)和分组数据网络网关(packet data network gateway,PGW)的用户面功能。此外,该UPF实体还可以是软件定义网络(software defined network,SDN)交换机(Switch),本申请实施例对此不作具体限定。
可选的,图1中的用户面功能实体或接入设备可以由一个实体设备实现,也可以由多个实体设备共同实现,还可以是一个实体设备内的一个逻辑功能模块,本申请实施例对此不作具体限定。
例如,图1中的用户面功能实体或接入设备可以通过图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可以包括多个处理器,例如图3中的处理器301和处理器308。这些处理器中的每一个可以是一个单核(single-CPU)处理器,也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中,作为一种实施例,通信设备300还可以包括输出设备305和输入设备306。输出设备305和处理器301通信,可以以多种方式来显示信息。例如,输出设备305可以是液晶显示器(liquid crystal display,LCD),发光二级管(light emitting diode,LED)显示设备,阴极射线管(cathode ray tube,CRT)显示设备,或投影仪(projector)等。输入设备306和处理器301通信,可以以多种方式接收用户的输入。例如,输入设备306可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的通信设备300可以是一个通用设备或者是一个专用设备。在具体实现中,通信设备300可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant,PDA)、移动手机、平板电脑、无线终端设备、嵌入式设备或有图3中类似结构的设备。本申请实施例不限定通信设备300的类型。
下面将结合图1至图3对本申请实施例提供的数据传输方法进行具体阐述。
需要说明的是,本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字只是一个示例,具体实现中也可以是其他的名字,本申请实施例对此不作具体限定。
以图1所示的数据传输系统应用于如图2所示的5G网络为例,如图4所示,为本申请实施例提供的一种数据传输方法,该方法包括如下步骤:
S401、SMF实体确定建立MLAN的标识对应的组播路径。
可选的,本申请实施例中,网络管理网元在检测到新的MLAN签约信息之后,可以将签约信息发送给SMF实体,进而SMF实体可以确定建立MLAN的标识对应的组播路径。其中,该网络管理网元例如可以是运营支撑系统(operations support system,OSS)。
S402、SMF实体预先建立MLAN的标识对应的组播路径。
可选的,SMF实体可以通过如下方式预先建立MLAN的标识对应的组播路径:
SMF实体在根据MLAN的标识选择UPF实体之后,确定需要建立UPF实体和n个接入设备之间的n条组播路径。进而,参照现有的N3隧道的建立方式,分别建立UPF实体和n个接入设备中的不同接入设备建立不同的组播路径。比如,对于n条组播路径中UPF实体和第一AN设备之间的组播路径1,UPF实体可以通过SMF实体向第一AN设备发送组播路径1的路径上行信息,该组播路径1的路径上行信息包括组播路径1在UPF实体侧的端点地址或端点标识,以及UPF实体的地址等。其中,该组播路径1在UPF实体侧的端点地址或端点标识可以是由SMF实体分配后发送给UPF实体的,也可以是由UPF实体分配的,本申请实施例对此不作具体限定。进一步的,第一AN设备可以分配组播路径1在第一AN设备侧的端点地址或端点标识,进而通过SMF实体向UPF实体发送组播路径1的路径下行信息,该组播路径1的路径下行信息包括该组播路径1在第一AN设备侧的端点地址或端点标识,以及第一AN设备的地址等,至此,UPF实体和第一AN设备之间的组播路径1建立完成。
S403、UPF实体存储MLAN的标识和n个组播路径的路径下行信息的对应关系。
可选的,本申请实施例中,MLAN的标识和n个组播路径的路径下行信息的对应关系可以是由SMF实体建立后发送给UPF实体的,也可以是UPF实体建立的,本申请实施例对此不作具体限定。
为方便描述,本申请实施例可以将MLAN的标识和n个组播路径的路径下行信息的对应关系记作对应关系1,在此统一说明,以下不再赘述。其中,该对应关系1可以如表一:
表一
MLAN的标识 组播路径的路径下行信息
MLAN1 组播路径1的路径下行信息
MLAN1 组播路径2的路径下行信息
…… ……
MLAN1 组播路径m的路径下行信息
当然,在上述表一中,由于组播路径1的路径下行信息、组播路径2的路径下行信息、……、组播路径n的路径下行信息对应的MLAN的标识相同,因此也可以将不同组播路径的路径下行信息对应的MLAN的标识进行合并,结果如表二所示,本申请实施例对此不作具体限定。
表二
Figure PCTCN2018119163-appb-000001
可选的,本申请实施例以对应关系以表格的形式进行表征为例进行说明,当然,对应关系除了以表格的形式表征,还可以以其他形式表征,比如文本形式或会话上下文形式等,本申请实施例对此不作具体限定。
可选的,本申请实施例中,在SMF实体建立MLAN的标识对应的组播路径之后,组播路径对应的接入设备也可以建立MLAN的标识和该组播路径的路径上行信息的对应关系,比如,对于组播路径1对应的第一AN设备,可以建立MLAN的标识和组播路径1的路径上行信息的对应关系。
为方便描述,本申请实施例可以将MLAN的标识和组播路径1的路径下行信息的对应关系记作对应关系2,在此统一说明,以下不再赘述。其中,该对应关系2可以如表三:
表三
MLAN的标识 组播路径1的路径下行信息
S404a、终端1向AMF实体发送MLAN会话建立请求,以使得AMF实体接收来自终端1的MLAN会话建立请求。其中,该MLAN会话建立请求携带终端1签约的MLAN的标识和第一AN设备的地址。
其中,第一AN设备的地址可以通过终端1的位置信息进行表征,本申请实施例对此不作具体限定。
其中,终端1签约的MLAN的标识的配置过程将在下述实施例中说明,在此不再赘述。
可选的,本申请实施例中,若终端1签约的MLAN的标识对应特定的服务范围,则终端1中还配置该MLAN的标识对应的特定服务区域的信息。这样,终端1可以根据该MLAN的标识对应的特定服务区域的信息,在该MLAN的标识对应的特定服务区域内向AMF实体发送MLAN会话建立请求。当然,若终端1在该MLAN的标识对应的特定服务区域外向AMF实体发送MLAN会话建立请求,则AMF实体或SMF实体可以在确定该终端1的当前位置不 在该MLAN的标识对应的特定服务区域之内之后,拒绝终端1发送的MLAN会话建立请求,本申请实施例对此不作具体限定。本申请实施例仅以终端1发起了一个正常的MLAN会话建立流程为例进行说明,即终端1签约的MLAN的标识在全局范围内可用时,终端1向AMF实体发送MLAN会话建立请求;或者,终端1签约的MLAN的标识对应特定的服务范围时,终端1在终端1签约的MLAN的标识对应的特定服务区域内发送MLAN会话建立请求,在此进行统一说明,以下不再赘述。
S405a、AMF实体选择SMF实体。
其中,AMF实体选择SMF实体的具体方式可参考现有方案,在此不予赘述。
S406a、AMF实体向SMF实体发送该MLAN会话建立请求,以使得SMF实体接收来自AMF实体的该MLAN会话建立请求。
S407a、SMF实体确定已经建立第一AN设备对应的组播路径。
示例性的,假设第一AN设备对应的组播路径为上述的组播路径1,则SMF实体可以根据第一AN设备的地址以及上述的表一,确定已经建立第一AN设备对应的组播路径。
可选的,本申请实施例中,SMF实体还可以从UDM实体获取终端1签约的MLAN的标识,并确定MLAN会话建立请求中携带的MLAN的标识与该终端1签约的MLAN的标识相同。若MLAN会话建立请求中携带的MLAN的标识与该终端1签约的MLAN的标识相同,可以确定MLAN会话建立请求中携带的MLAN的标识是终端1签约的MLAN的标识,进而可以执行后续流程;若MLAN会话建立请求中携带的MLAN的标识与该终端1签约的MLAN的标识不同,可以确定MLAN会话建立请求中携带的MLAN的标识不是终端1签约的MLAN的标识,流程结束,本申请实施例对此不作具体限定。
S408a、SMF实体向第一AN设备发送通知消息,以使得第一AN设备接收来自SMF实体的通知消息,该通知消息用于指示第一AN设备建立MLAN的标识和终端1的信息的对应关系。
可选的,本申请实施例中,终端1的信息具体是指终端1的空口传输信息,可以包括终端1的空口传输标识,该空口传输标识例如可以是数据无线承载(data radio bearer,DRB)标识,本申请实施例对此不作具体限定。
为方便描述,本申请实施例可以将MLAN的标识和终端1的信息的对应关系记作对应关系3,在此统一说明,以下不再赘述。其中,该对应关系3可以如表四:
表四
MLAN的标识 终端1的信息
S409a、第一AN设备存储MLAN的标识和终端1的信息的对应关系。
S404b-S409b、与步骤S404a-S409a类似,区别仅在于,步骤S404b-S409b中,将步骤S404a-S409a中的终端替1换为终端2,具体可参考步骤S404a-S409a,在此不再赘述。
其中,在步骤S409b中,第一AN设备建立MLAN的标识和终端2的信息的对应关系可以记作对应关系4,在此统一说明,以下不再赘述。其中,其中,该对应关系4可以如表五所示:
表五
MLAN的标识 终端2的信息
可选的,本申请实施例中,第一AN设备也可以维护如表六所示的MLAN的标识和终端的信息的对应关系5,在终端1建立MLAN会话的过程中,第一AN设备接收来自SMF实体的通知消息之后,可以更新对应关系5,在对应关系5中添加MLAN的标识和终端1的信息 的对应关系;类似的,在终端2建立MLAN会话的过程中,第一AN设备接收来自SMF实体的通知消息之后,可以更新对应关系5,在对应关系5中添加MLAN的标识和终端2的信息的对应关系,以此类推,本申请实施例对此不作具体限定。
表六
Figure PCTCN2018119163-appb-000002
需要说明的是,本申请实施例中,步骤S404a-S409a和步骤S404b-S409b之间没有必然的执行先后顺序,可以是先执行步骤S404a-S409a,再执行步骤S404b-S409b;也可以是先执行步骤S404b-S409b,再执行步骤S404a-S409a;也可以是同时执行步骤S404a-S409a和步骤S404b-S409b,本申请实施例对此不作具体限定。
S410、源设备向UPF实体发送数据包,以使得UPF实体接收来自源设备的数据包。其中,该数据包携带组播信息。该组播信息的相关描述可参考上述实施例,在此不再赘述。
可选的,本申请实施例中,该数据包可以携带源设备的地址信息作为源地址,携带组播地址作为目标地址,本申请实施例对此不作具体限定。
可选的,本申请实施例中,该数据包还可以携带目标MLAN的标识,该目标MLAN为源设备所在的MLAN,本申请实施例对此不作具体限定。
S411、UPF实体确定目标MLAN对应的n个组播路径的路径下行信息。
具体的,假设目标MLAN的标识为MLAN1,则UPF实体可以根据表一或表二,确定目标MLAN对应的n个组播路径的路径下行信息。
可选的,本申请实施例中的目标MLAN的标识可以是携带在数据包中的,也可以是UPF实体接收来自源设备的数据包之后确定的,本申请实施例对此不作具体限定。
比如,若源设备为源终端,则UPF实体可以根据源终端对应的路径上行信息,以及源终端对应的路径上行信息和目标MLAN的对应关系,确定目标MLAN的标识;
或者,比如,若源设备为服务器,则UPF实体可以根据服务器对应的路径下行信息,以及服务器对应的路径下行信息和目标MLAN的对应关系,确定目标MLAN的标识。
本申请实施例对UPF实体如何获知目标MLAN的标识不作具体限定。
假设n个组播路径中的组播路径1对应第一AN设备,则本申请实施例提供的数据传输方法还包括如下步骤:
S412、UPF实体通过组播路径1的路径下行信息对应的组播路径1向第一AN设备发送该数据包,以使得第一AN设备通过组播路径1接收来自UPF实体的数据包。
S413、第一AN设备确定对应的s个目标终端的信息,s为正整数。
假设组播路径1对应的目标终端包括终端1和终端2,则第一AN设备在接收来自UPF实体的数据包之后,可以根据表四和表五,或者根据表六,确定对应的s个目标终端的信息。此时s=2,对应的2个目标终端的信息分别包括终端1的信息和终端2的信息。
可选的,本申请实施例中的目标MLAN的标识可以是携带在数据包中的,也可以是第一AN实体通过组播路径1接收来自UPF实体的数据包之后确定的,本申请实施例对此不作具体限定。
比如,第一AN设备可以根据组播路径1的路径下行信息,以及表三所示的对应关系2,确定目标MLAN的标识,本申请实施例对第一AN设备如何获知目标MLAN的标识不作具 体限定。
S414a、第一AN设备根据终端1的信息,向终端1发送数据包,以使得终端1接收来自第一AN设备的数据包。
S414b、第一AN设备根据终端2的信息,向终端2发送数据包,以使得终端2接收来自第一AN设备的数据包。
需要说明的是,本申请实施例中,步骤S414a和步骤S414b之间没有必然的执行先后顺序,可以是先执行步骤S414a,再执行步骤S414b;也可以是先执行步骤S414b,再执行步骤S414a;也可以是同时执行步骤S414a和步骤S414b,本申请实施例对此不作具体限定。
需要说明的是,本申请实施例中的步骤S412-S414b给出了针对组播路径1的处理方式,当然,对于n个组播路径中的其他组播路径,均按照上述针对组播路径1的处理方式进行处理,在此不再一一赘述。
基于本申请实施例提供的数据传输方法,可以避免现有技术中数据包在相同的用户面功能实体和接入设备之间重复传输的问题,从而可以节省MLAN组播场景下的传输带宽。相关技术效果分析可参考系统实施例,在此不再赘述。
其中,上述步骤S401至S414b中UPF实体和第一AN设备的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行,本申请实施例对此不作任何限制。
可选的,以图1所示的数据传输系统应用于如图2所示的5G网络为例,如图5所示,为本申请实施例提供的另一种数据传输方法,该方法包括如下步骤:
S501-S503、同步骤S404a-S406a,具体可参考图4所示的实施例,在此不再赘述。
S504、SMF实体确定未建立第一AN设备对应的组播路径。
S505、SMF实体建立第一AN设备对应的组播路径1。
其中,SMF实体建立第一AN设备对应的组播路径1的方式可参考步骤S402中的相关描述,在此不再赘述。
S506、与步骤S403类似,区别在于步骤S403中,UPF实体存储MLAN的标识和m个组播路径的路径下行信息的对应关系,本申请实施例中,UPF实体存储MLAN的标识和组播路径1的路径下行信息的对应关系,相关描述可参考图4所示的实施例,在此不再赘述。
S507、第一AN设备存储MLAN的标识和终端1的信息的对应关系。
其中,MLAN的标识和终端1的信息的对应关系的相关描述可参考图4所示的实施例中的对应关系3,本申请实施例在此不再赘述。
需要说明的是,本申请实施例中的步骤S501-S507给出了建立MLAN的标识对应的组播路径1方式,当然,对于该MLAN的标识对应的其他组播路径,也可以按照上述建立组播路径1的方式进行处理,在此不再一一赘述。其中,在该MLAN的标识对应的m个组播路径建立完成后,UPF实体可以存储如表一或表二所示的对应关系1。
S508-S518b、同步骤S404b-S414b,具体可参考图4所示的实施例,在此不再赘述。
基于本申请实施例提供的数据传输方法,可以避免现有技术中数据包在相同的用户面功能实体和接入设备之间重复传输的问题,从而可以节省MLAN组播场景下的传输带宽。相关技术效果分析可参考系统实施例,在此不再赘述。
其中,上述步骤S501至S518b中UPF实体和第一AN设备的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行,本申请实施例对此不作任何限制。
可选的,以图1所示的数据传输系统应用于如图2所示的5G网络为例,如图6所示,为本申请实施例提供的另一种数据传输方法,该方法包括如下步骤:
S601a-S603a、同步骤S404a-S406a,具体可参考图4所示的实施例,在此不再赘述。
S604a、SMF实体选择UPF实体。
其中,SMF实体选择UPF实体的具体方式可参考现有方案,在此不予赘述。
S605a、SMF实体向UPF实体发送N4会话消息,以使得UPF实体接收来自SMF实体的N4会话消息。其中,该N4会话消息携带终端1签约的MLAN的标识。
S606a、UPF实体向第一AN设备发送终端1对应的路径的路径上行信息,以使得第一AN设备接收来自UPF实体的终端1对应的路径的路径上行信息。
其中,本申请实施例中,终端1对应的路径具体是指终端1对应的UPF实体和第一AN设备之间的N3隧道,在此统一说明,以下不再赘述。
可选的,本申请实施例中,终端1对应的路径的路径上行信息可以是由SMF实体分配的,也可以是由UPF实体分配的,本申请实施例对此不作具体限定。
可选的,本申请实施例中,终端1对应的路径的路径上行信息包括该路径在UPF实体侧的端点地址或端点标识,以及UPF实体的地址等,本申请实施例对此不作具体限定。
可选的,本申请实施例中,UPF实体可以存储MLAN的标识和终端1对应的路径的路径上行信息的对应关系,本申请实施例对此不作具体限定。
S607a、第一AN设备向UPF实体发送终端1对应的路径的路径下行信息,以使得UPF实体接收来自第一AN设备的终端1对应的路径的路径下行信息。
可选的,本申请实施例中,终端1对应的路径的路径下行信息包括该路径在第一AN设备侧的端点地址或端点标识,以及第一AN设备的地址等,本申请实施例对此不作具体限定。
S608a、第一AN设备存储终端1对应的路径的路径下行信息和终端1的信息的对应关系。
为方便描述,本申请实施例可以将终端1对应的路径的路径下行信息和终端1的信息的对应关系记作对应关系6,在此统一说明,以下不再赘述。其中,该对应关系6可以如表七:
表七
终端1对应的路径的路径下行信息 终端1的信息
S609a、UPF实体存储MLAN的标识和终端1对应的路径的路径下行信息的对应关系。
为方便描述,本申请实施例可以将终端1对应的路径的路径下行信息和MLAN的标识的对应关系记作对应关系7,在此统一说明,以下不再赘述。其中,该对应关系7可以如表八:
表八
MLAN的标识 终端1对应的路径的路径下行信息
需要说明的是,本申请实施例中的步骤S607a与S608a之间没有必然的执行先后顺序,可以是先执行步骤S607a,再执行步骤S608a;也可以是先执行步骤S608a,再执行步骤S607a;还可以是同时执行步骤S607a和S608a,本申请实施例对此不作具体限定。
S601b-S609b、与步骤S601a-S609a类似,区别仅在于,步骤S601b-S609b中,将步骤S601a-S609a中的终端替1换为终端2,具体可参考步骤S601a-S609a,在此不再赘述。
其中,在步骤S608b中,第一AN设备存储的终端2对应的路径的路径下行信息和终端2的信息的对应关系记作对应关系8,在此统一说明,以下不再赘述。其中,该对应关系8可以如表九:
表九
终端2对应的路径的路径下行信息 终端2的信息
其中,在步骤S609b中,UPF实体存储的MLAN的标识和终端2对应的路径的路径下行信息的对应关系记作对应关系9,在此统一说明,以下不再赘述。其中,该对应关系9可以如表十:
表十
MLAN的标识 终端2对应的路径的路径下行信息
可选的,本申请实施例中,第一AN设备也可以维护如表十一所示的终端对应的路径的路径下行信息和终端的信息的对应关系10,在终端1建立MLAN会话的过程中,第一AN设备在获取终端1对应的路径的路径下行信息和终端1的信息之后,可以更新对应关系10,在对应关系10中添加终端1对应的路径的路径下行信息和终端1的信息的对应关系;类似的,在终端2建立MLAN会话的过程中,第一AN设备在获取终端2对应的路径的路径下行信息和终端2的信息之后,可以更新对应关系10,在对应关系10中添加终端2对应的路径的路径下行信息和终端2的信息的对应关系,以此类推,本申请实施例对此不作具体限定。
表十一
终端对应的路径的路径下行信息 终端的信息
终端1对应的路径的路径下行信息 终端1的信息
终端2对应的路径的路径下行信息 终端2的信息
…… ……
需要说明的是,本申请实施例中,步骤S601a-S609a和步骤S601b-S609b之间没有必然的执行先后顺序,可以是先执行步骤S601a-S609a,再执行步骤S601b-S609b;也可以是先执行步骤S601b-S609b,再执行步骤S601a-S609a;也可以是同时执行步骤S601a-S609a和步骤S601b-S609b,本申请实施例对此不作具体限定。
S610、SMF实体确定建立MLAN的标识对应的组播路径。
可选的,本申请实施例中,SMF实体可以是在网络管理网元检测到新的MLAN签约信息之后,将签约信息发送给SMF实体,进而SMF实体可以确定建立MLAN的标识对应的组播路径;或者,SMF实体可以是在接收到一个或多个MLAN会话建立请求后确定建立MLAN的标识对应的组播路径,本申请实施例对此不作具体限定。
S611、同步骤S402,具体可参考图4所示的实施例,在此不再赘述。
S612、UPF实体存储MLAN的标识、m个组播路径的路径下行信息和每个组播路径对应的终端对应的路径的路径下行信息的对应关系。
为方便描述,本申请实施例可以将MLAN的标识、m个组播路径的路径下行信息和每个组播路径对应的终端对应的路径的路径下行信息的对应关系记作对应关系11,在此统一说明,以下不再赘述。其中,该对应关系11可以如表十二:
表十二
Figure PCTCN2018119163-appb-000003
Figure PCTCN2018119163-appb-000004
可选的,本申请实施例中,UPF实体在存储表十二所示的对应关系11时,也可以分别存储MLAN的标识和组播路径的路径下行信息的对应关系,以及组播路径的路径下行信息和终端对应的路径的路径下行信息的对应关系,本申请实施例对此不作具体限定。
S613-S614、同步骤S410-S411,具体可参考图4所示的实施例,在此不再赘述。
假设n个组播路径中的组播路径1对应第一AN设备,则本申请实施例提供的数据传输方法还包括如下步骤:
S615、UPF实体通过组播路径1的路径下行信息对应的组播路径1向第一AN设备发送数据包以及对应的s个目标终端对应的路径的路径下行信息,以使得第一AN设备通过组播路径1接收来自UPF实体的数据包以及对应的s个目标终端对应的路径的路径下行信息。
示例性的,UPF实体根据表十二,可以确定终端1对应的路径的路径下行信息和终端2对应的路径的路径下行信息。
S616、第一AN设备确定对应的s个目标终端的信息,s为正整数。
示例性的,第一AN设备在接收来自UPF实体的s个目标终端对应的路径的路径下行信息之后,可以根据表七和表九,或者根据表十一,确定对应的s个目标终端的信息。
S617a-S617b、同S414a-S414b,具体可参考图4所示的实施例,在此不再赘述。
需要说明的是,本申请实施例中的步骤S615-S617b给出了针对组播路径1的处理方式,当然,对于n个组播路径中的其他组播路径,均按照上述针对组播路径1的处理方式进行处理,在此不再一一赘述。
与图4或图5所示的实施例的区别在于,图4或图5所示的实施例中,每个AN设备和UPF之间仅建立一条组播路径,在终端发起MLAN会话建立流程时,若AN设备和UPF之间已经建立组播路径,则不需要再建立会话对应的路径,从而可以节省会话资源;而图6所示的实施例中,每个终端发起MLAN会话建立流程时均需要建立会话对应的路径,除此之外,每个AN设备和UPF之间还建立一条组播路径,这样AN设备上可以不需要维护如表四至表六所示的对应关系,而仅是像现有技术一样,维护如表七、表九或表十一所示的对应关系即可。
基于本申请实施例提供的数据传输方法,可以避免现有技术中数据包在相同的用户面功能实体和接入设备之间重复传输的问题,从而可以节省MLAN组播场景下的传输带宽。相关技术效果分析可参考系统实施例,在此不再赘述。
其中,上述步骤S601至S617b中UPF实体和第一AN设备的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行,本申请实施例对此不作任何限制。
下面以在终端1上配置终端1签约的MLAN的标识为例,给出MLAN的标识的配置过程的流程示意图如图7所示,包括如下步骤:
S701、在终端1签约MLAN业务时,UDM实体存储终端1对应的MLAN签约信息。其中,该终端1的MLAN签约信息中包括终端1签约的MLAN的标识。
可选的,若终端1签约的MLAN的标识对应特定的服务区域,则终端1的MLAN签约信息中还可以包括终端1签约的MLAN的标识对应的特定服务区域的信息。
当然,还可以在其它网络设备上配置终端1签约的MLAN的标识对应的特定服务区域的信息,比如在PCF实体、AMF实体、SMF实体中的一个或多个设备上配置终端1签约的MLAN的标识对应的特定服务区域的信息,以使得这些网络设备在终端1发起MLAN会话建立流程时,可以根据终端1当前的位置和终端1签约的MLAN的标识对应的特定服务区域的信息,确定终端1是否在终端1签约的MLAN的标识对应的特定服务区域内,本申请实施例对此不作具体限定。
S702、终端1向AMF实体发送注册或重注册请求,以使得AMF实体接收来自终端1的注册或重注册请求。
S703、AMF实体从UDM实体获取终端1签约的MLAN的标识。
可选的,若终端1签约的MLAN的标识对应特定的服务范围,且AMF实体中未配置终端1签约的MLAN的标识对应的特定服务区域的信息,则AMF实体还从配置终端1签约的MLAN的标识对应的特定服务区域的信息的设备中获取终端1签约的MLAN的标识对应的特定服务区域的信息,比如从UDM实体中,PCF实体、或SMF实体中,本申请实施例对此不作具体限定。
S704、AMF实体向终端1发送注册应答,以使得终端1接收来自AMF实体的注册应答。其中,该注册应答中携带终端1签约的MLAN的标识。
可选的,本申请实施例中,在AMF实体从UDM实体获取终端1签约的MLAN的标识之后,若终端1签约的MLAN的标识对应特定的服务范围,则AMF实体需要根据终端1当前注册区域的信息以及终端1签约的MLAN的标识对应的特定服务区域的信息,确定终端1的当前注册区域与终端1签约的MLAN的标识对应的特定服务区域是否有重叠,在有重叠的情况下,AMF实体向终端1发送注册应答,该注册应答中携带终端1签约的MLAN的标识。可选的,该情况下,注册应答中还可以包括及终端1签约的MLAN的标识对应的特定服务区域的信息,以使得终端1可以根据终端1签约的MLAN的标识对应的特定服务区域的信息,在终端1签约的MLAN的标识对应的特定服务区域内发起MLAN会话建立流程,本申请实施例对此不作具体限定。
至此,终端1可以获取终端1签约的MLAN的标识,后续可以根据该终端1签约的MLAN的标识,发起MLAN会话建立流程,具体可参考图4至图6所示的实施例,在此不再赘述。
此外,在其他终端上配置该终端签约的MLAN的标识的流程可参考上述在终端1上配置终端1签约的MLAN的标识的流程,在此不再赘述。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是,上述用户面功能实体或接入设备为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对用户面功能实体或接入设备进行功能模块的划分,例如,可以对应各个功能划分各个功能模块,也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。需要说明的是,本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。
比如,以采用集成的方式划分各个功能模块的情况下,图8示出了一种用户面功能实体80的结构示意图。该用户面功能实体80包括:处理模块801和收发模块802。收发模块802,用于接收来自源设备的数据包,其中,该数据包携带组播信息;处理模块801,用于确定目标MLAN对应的n个组播路径的路径下行信息;收发模块802,还用于通过n个组播路径的路径下行信息对应的n个组播路径分别向对应的n个接入设备发送数据包,n为正整数。
可选的,处理模块801具体用于:根据目标MLAN的标识、以及第一对应关系,确定目标MLAN对应的n个组播路径的路径下行信息,其中,该第一对应关系包括目标MLAN的标识和n个组播路径的路径下行信息的对应关系。
进一步的,收发模块802,还用于接收来自会话管理实体的第一对应关系。
可选的,处理模块801,还用于根据n个组播路径的路径下行信息、以及第二对应关系,确定与每个组播路径对应的目标终端对应的路径下行信息,其中,第二对应关系包括每个组播路径的路径下行信息和对应的目标终端对应的路径的路径下行信息的对应关系。收发模块802,还用于通过n个组播路径的路径下行信息对应的n个组播路径分别向对应的接入设备发送对应的目标终端对应的路径的路径下行信息。
进一步的,收发模块802,还用于接收来自会话管理实体的第二对应关系。
一种可能的实现方式中,数据包携带目标MLAN的标识。
一种可能的实现方式中,源设备包括源终端;处理模块801,还用于根据源终端对应的路径的路径上行信息、以及第三对应关系,确定目标MLAN的标识,其中,第三对应关系包括源终端对应的路径的路径上行信息和目标MLAN的标识的对应关系。
一种可能的实现方式中,源设备包括服务器;处理模块801,还用于根据服务器对应的路径的路径下行信息、以及第四对应关系,确定目标MLAN的标识,其中,第四对应关系包括服务器对应的路径的路径下行信息和目标MLAN的标识的对应关系。
其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。
在本申请实施例中,该用户面功能实体80以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC,电路,执行一个或多个软件或固件程序的处理器和存储器,集成逻辑电路,和/或其他可以提供上述功能的器件。在一个简单的实施例中,本领域的技术人员可以想到用户面功能实体80可以采用图3所示的形式。
比如,图3中的处理器301可以通过调用存储器303中存储的计算机执行指令,使得用户面功能实体80执行上述方法实施例中的数据传输方法。
具体的,图8中的处理模块801和收发模块802的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现。或者,图8中的处理模块801的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现,图8中的收发模块802的功能/实现过程可以通过图3中的通信接口304来实现。
由于本申请实施例提供的用户面功能实体可用于执行上述数据传输方法,因此其所能获得的技术效果可参考上述方法实施例,在此不再赘述。
比如,以采用集成的方式划分各个功能模块的情况下,图9示出了一种接入设备90的结构示意图。该接入设备90包括:接收模块901和发送模块902。接收模块901,用于通过组播路径接收来自用户面功能实体的数据包,其中,该数据包携带组播信息;发送模块902,用于向s个目标终端分别发送数据包,其中,目标终端的签约MLAN与目标MLAN相同,目标MLAN为发送数据包的源设备所在的MLAN,s为正整数。
可选的,发送模块902具体用于:根据目标MLAN的标识,以及第一对应关系,确定s个目标终端的信息,其中,第一对应关系包括目标MLAN的标识和s个目标终端的信息的对应关系;根据s个目标终端的信息,向s个目标终端分别发送数据包。
进一步的,s个目标终端中包括第一终端。如图9所示,接入设备90还包括处理模块903。处理模块903,用于在第一终端在目标MLAN中建立MLAN会话的过程中,建立目标MLAN的标识和第一终端的信息对应关系。
可选的,接收模块901,还用于在第一终端在目标MLAN中建立MLAN会话的过程中,在已经建立第一组播路径的情况下,接收来自会话管理实体的通知消息,该通知消息用于指示接入设备90建立目标MLAN的标识和第一终端的信息对应关系。
可选的,接收模块901,还用于通过组播路径接收来自用户面功能实体的s个目标终端对应的路径的路径下行信息;发送模块902具体用于:根据s个目标终端对应的路径下行信息,以及第二对应关系,确定s个目标终端的信息,其中,第二对应关系包括s个目标终端对应的路径的路径下行信息和s个目标终端的信息的对应关系;根据s个目标终端的信息,向s个目标终端分别发送数据包。
可选的,s个目标终端中包括第二终端。如图9所示,接入设备90还包括处理模块903。处理模块903,用于在第二终端在目标MLAN中建立MLAN会话的过程中,建立第二终端对应的路径的路径下行信息和第二终端的信息对应关系。
一种可能的实现方式中,数据包携带目标MLAN的标识。
或者,一种可能的实现方式中,如图9所示,接入设备90还包括处理模块903。处理模块903,用于根据组播路径的路径下行信息,以及第三对应关系,确定目标MLAN的标识,其中,第三对应关系包括组播路径的路径下行信息和目标MLAN标识的对应关系。
其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。
在本申请实施例中,该接入设备90以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC,电路,执行一个或多个软件或固件程序的处理器和存储器,集成逻辑电路,和/或其他可以提供上述功能的器件。在一个简单的实施例中,本领域的技术人员可以想到接入设备90可以采用图3所示的形式。
比如,图3中的处理器301可以通过调用存储器303中存储的计算机执行指令,使得接入设备90执行上述方法实施例中的数据传输方法。
具体的,图9中的接收模块901、发送模块902和处理模块903的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现。或者,图8中的处理模块903的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现,图9中的接收模块901和发送模块902的功能/实现过程可以通过图3中的通信接口304来实现。
由于本申请实施例提供的接入设备可用于执行上述数据传输方法,因此其所能获得的技术效果可参考上述方法实施例,在此不再赘述。
上述实施例中,用户面功能实体80和接入设备90均以采用集成的方式划分各个功能模块的形式来呈现。当然,本申请实施例也可以对应各个功能划分装置、控制设备和会话管理实体的各个功能模块,本申请实施例对此不作具体限定。
可选的,本申请实施例提供了一种芯片系统,该芯片系统包括处理器,用于支持用户面功能实体实现上述数据传输方法,例如确定目标MLAN对应的n个组播路径的路径下行信息。 在一种可能的设计中,该芯片系统还包括存储器。该存储器,用于保存用户面功能实体必要的程序指令和数据。该芯片系统,可以由芯片构成,也可以包含芯片和其他分立器件,本申请实施例对此不作具体限定。
可选的,本申请实施例提供了一种芯片系统,该芯片系统包括处理器,用于支持接入设备实现上述数据传输方法,例如在第一终端在目标MLAN中建立MLAN会话的过程中,建立目标MLAN的标识和第一终端的信息对应关系。在一种可能的设计中,该芯片系统还包括存储器。该存储器,用于保存接入设备必要的程序指令和数据。该芯片系统,可以由芯片构成,也可以包含芯片和其他分立器件,本申请实施例对此不作具体限定。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时,可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line,DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如,软盘、硬盘、磁带),光介质(例如,DVD)、或者半导体介质(例如固态硬盘(solid state disk,SSD))等。
尽管在此结合各实施例对本申请进行了描述,然而,在实施所要求保护的本申请过程中,本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书,可理解并实现所述公开实施例的其他变化。在权利要求中,“包括”(comprising)一词不排除其他组成部分或步骤,“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施,但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述,显而易见的,在不脱离本申请的精神和范围的情况下,可对其进行各种修改和组合。相应地,本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明,且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然,本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样,倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。

Claims (40)

  1. 一种数据传输方法,其特征在于,所述方法包括:
    用户面功能实体接收来自源设备的数据包,其中,所述数据包携带组播信息;
    所述用户面功能实体确定目标移动局域网MLAN对应的n个组播路径的路径下行信息;
    所述用户面功能实体通过所述n个组播路径的路径下行信息对应的n个组播路径分别向对应的n个接入设备发送所述数据包,n为正整数。
  2. 根据权利要求1所述的方法,其特征在于,所述用户面功能实体确定目标MLAN对应的n个组播路径的路径下行信息,包括:
    所述用户面功能实体根据所述目标MLAN的标识、以及第一对应关系,确定所述目标MLAN对应的n个组播路径的路径下行信息,其中,所述第一对应关系包括所述目标MLAN的标识和所述n个组播路径的路径下行信息的对应关系。
  3. 根据权利要求2所述的方法,其特征在于,所述方法还包括:
    所述用户面功能实体接收来自会话管理实体的所述第一对应关系。
  4. 根据权利要求3所述的方法,其特征在于,所述n个组播路径的信息中包括第一组播路径的信息,所述方法还包括:
    所述会话管理实体在所述目标MLAN中建立所述第一组播路径;
    所述会话管理实体向所述用户面功能实体发送所述目标MLAN的标识和所述第一组播路径的路径下行信息的对应关系。
  5. 根据权利要求4所述的方法,其特征在于,与所述第一组播路径对应的t个目标终端中包括第一终端,t为正整数;所述会话管理实体在所述目标MLAN中建立所述第一组播路径,包括:
    在所述第一终端在所述目标MLAN中建立MLAN会话的过程中,在未建立所述第一组播路径的情况下,所述会话管理实体建立所述第一组播路径。
  6. 根据权利要求1或2所述的方法,其特征在于,在所述用户面功能实体确定所述目标MLAN对应的n个组播路径的路径下行信息之后,还包括:
    所述用户面功能实体根据所述n个组播路径的路径下行信息、以及第二对应关系,确定与所述每个组播路径的路径下行信息对应的目标终端对应的路径的路径下行信息,其中,所述第二对应关系包括所述每个组播路径的路径下行信息和对应的目标终端对应的路径的路径下行信息的对应关系;
    所述用户面功能实体通过所述n个组播路径的路径下行信息对应的n个组播路径分别向对应的接入设备发送对应的目标终端对应的路径的路径下行信息。
  7. 根据权利要求6所述的方法,其特征在于,所述方法还包括:
    所述用户面功能实体接收来自会话管理实体的所述第二对应关系。
  8. 根据权利要求7所述的方法,其特征在于,所述n个组播路径的路径下行信息中包括第二组播路径的路径下行信息,与所述第二组播路径对应的s个目标终端中包括第二终端,s为正整数;所述方法还包括:
    所述会话管理实体建立所述第二组播路径和所述第二终端对应的路径;
    所述会话管理实体向所述用户面功能实体发送所述目标MLAN的标识和所述第二组播路径的路径下行信息的对应关系、以及所述目标MLAN的标识和所述第二终端对应的路径 的路径下行信息的对应关系。
  9. 根据权利要求1-8任一项所述的方法,其特征在于,所述数据包携带所述目标MLAN的标识。
  10. 根据权利要求1-8任一项所述的方法,其特征在于,所述源设备包括源终端,在所述用户面功能实体接收来自源设备的数据包之后,还包括:
    所述用户面功能实体根据所述源终端对应的路径的路径上行信息、以及第三对应关系,确定所述目标MLAN的标识,其中,所述第三对应关系包括所述源终端对应的路径的路径上行信息和所述目标MLAN的标识的对应关系。
  11. 根据权利要求1-8任一项所述的方法,其特征在于,所述源设备包括服务器,在所述用户面功能实体接收来自源设备的数据包之后,还包括:
    所述用户面功能实体根据所述服务器对应的路径的路径下行信息、以及第四对应关系,确定所述目标MLAN的标识,其中,所述第四对应关系包括所述服务器对应的路径的路径下行信息和所述目标MLAN的标识的对应关系。
  12. 一种数据传输方法,其特征在于,所述方法包括:
    接入设备通过组播路径接收来自用户面功能实体的数据包,其中,所述数据包携带组播信息;
    所述接入设备向s个目标终端分别发送所述数据包,其中,所述目标终端的签约移动局域网MLAN与目标MLAN相同,所述目标MLAN为发送所述数据包的源设备所在的MLAN,s为正整数。
  13. 根据权利要求12所述的方法,其特征在于,所述接入设备向s个目标终端分别发送所述数据包,包括:
    所述接入设备根据所述目标MLAN的标识,以及第一对应关系,确定所述s个目标终端的信息,其中,所述第一对应关系包括所述目标MLAN的标识和所述s个目标终端的信息的对应关系;
    所述接入设备根据所述s个目标终端的信息,向所述s个目标终端分别发送所述数据包。
  14. 根据权利要求13所述的方法,其特征在于,所述s个目标终端中包括第一终端,所述方法还包括:
    在所述第一终端在所述目标MLAN中建立MLAN会话的过程中,所述接入设备建立所述目标MLAN的标识和所述第一终端的信息对应关系。
  15. 根据权利要求14所述的方法,其特征在于,所述方法还包括:
    在所述第一终端在所述目标MLAN中建立MLAN会话的过程中,在已经建立所述第一组播路径的情况下,所述接入设备接收来自会话管理实体的通知消息,所述通知消息用于指示所述接入设备建立所述目标MLAN的标识和所述第一终端的信息对应关系。
  16. 根据权利要求12所述的方法,其特征在于,所述方法还包括:
    所述接入设备通过所述组播路径接收来自所述用户面功能实体的所述s个目标终端对应的路径的路径下行信息;
    所述接入设备向s个目标终端分别发送所述数据包,包括:
    所述接入设备根据所述s个目标终端对应的路径的路径下行信息,以及第二对应关系,确定所述s个目标终端的信息,其中,所述第二对应关系包括所述s个目标终端对应的路径的路径下行信息和所述s个目标终端的信息的对应关系;
    所述接入设备根据所述s个目标终端的信息,向所述s个目标终端分别发送所述数据包。
  17. 根据权利要求16所述的方法,其特征在于,所述s个目标终端中包括第二终端,所述方法还包括:
    在所述第二终端在所述目标MLAN中建立MLAN会话的过程中,所述接入设备建立所述第二终端对应的路径的路径下行信息和所述第二终端的信息对应关系。
  18. 根据权利要求12-17任一项所述的方法,其特征在于,所述数据包携带所述目标MLAN的标识;
    或者,在所述接入设备通过组播路径接收来自所述用户面功能实体的所述数据包之后,还包括:
    所述接入设备根据所述组播路径的路径下行信息,以及第三对应关系,确定所述目标MLAN的标识,其中,所述第三对应关系包括所述组播路径的路径下行信息和所述目标MLAN标识的对应关系。
  19. 一种用户面功能实体,其特征在于,所述用户面功能实体包括:收发模块和处理模块;
    所述收发模块,用于接收来自源设备的数据包,其中,所述数据包携带组播信息;
    所述处理模块,用于确定目标移动局域网MLAN对应的n个组播路径的路径下行信息;
    所述收发模块,还用于通过所述n个组播路径的路径下行信息对应的n个组播路径分别向对应的n个接入设备发送所述数据包,n为正整数。
  20. 根据权利要求19所述的用户面功能实体,其特征在于,所述处理模块具体用于:
    根据所述目标MLAN的标识、以及第一对应关系,确定所述目标MLAN对应的n个组播路径的路径下行信息,其中,所述第一对应关系包括所述目标MLAN的标识和所述n个组播路径的路径下行信息的对应关系。
  21. 根据权利要求20所述的用户面功能实体,其特征在于,
    所述收发模块,还用于接收来自会话管理实体的所述第一对应关系。
  22. 根据权利要求19或20所述的用户面功能实体,其特征在于,
    所述处理模块,还用于根据所述n个组播路径的路径下行信息、以及第二对应关系,确定与所述每个组播路径的路径下行信息对应的目标终端对应的路径的路径下行信息,其中,所述第二对应关系包括所述每个组播路径的路径下行信息和对应的目标终端对应的路径的路径下行信息的对应关系;
    所述收发模块,还用于通过所述n个组播路径的路径下行信息对应的n个组播路径分别向对应的接入设备发送对应的目标终端对应的路径的路径下行信息。
  23. 根据权利要求22所述的用户面功能实体,其特征在于,
    所述收发模块,还用于接收来自会话管理实体的所述第二对应关系。
  24. 根据权利要求19-23任一项所述的用户面功能实体,其特征在于,所述源设备包括源终端;
    所述处理模块,还用于根据所述源终端对应的路径的路径上行信息、以及第三对应关系,确定所述目标MLAN的标识,其中,所述第三对应关系包括所述源终端对应的路径的路径上行信息和所述目标MLAN的标识的对应关系。
  25. 根据权利要求19-23任一项所述的用户面功能实体,其特征在于,所述源设备包括服务器;
    所述处理模块,还用于根据所述服务器对应的路径的路径下行信息、以及第四对应关系,确定所述目标MLAN的标识,其中,所述第四对应关系包括所述服务器对应的路径的路径下行信息和所述目标MLAN的标识的对应关系。
  26. 一种接入设备,其特征在于,所述接入设备包括:接收模块和发送模块;
    所述接收模块,用于通过组播路径接收来自用户面功能实体的数据包,其中,所述数据包携带组播信息;
    所述发送模块,用于向s个目标终端分别发送所述数据包,其中,所述目标终端的签约移动局域网MLAN与目标MLAN相同,所述目标MLAN为发送所述数据包的源设备所在的MLAN,s为正整数。
  27. 根据权利要求26所述的接入设备,其特征在于,所述发送模块具体用于:
    根据所述目标MLAN的标识,以及第一对应关系,确定所述s个目标终端的信息,其中,所述第一对应关系包括所述目标MLAN的标识和所述s个目标终端的信息的对应关系;
    根据所述s个目标终端的信息,向所述s个目标终端分别发送所述数据包。
  28. 根据权利要求27所述的接入设备,其特征在于,所述s个目标终端中包括第一终端,所述接入设备还包括处理模块;
    所述处理模块,用于在所述第一终端在所述目标MLAN中建立MLAN会话的过程中,建立所述目标MLAN的标识和所述第一终端的信息对应关系。
  29. 根据权利要求28所述的接入设备,其特征在于,
    所述接收模块,还用于在所述第一终端在所述目标MLAN中建立MLAN会话的过程中,在已经建立所述第一组播路径的情况下,接收来自会话管理实体的通知消息,所述通知消息用于指示所述接入设备建立所述目标MLAN的标识和所述第一终端的信息对应关系。
  30. 根据权利要求26所述的接入设备,其特征在于,
    所述接收模块,还用于通过所述组播路径接收来自所述用户面功能实体的所述s个目标终端对应的路径的路径下行信息;
    所述发送模块具体用于:根据所述s个目标终端对应的路径的路径下行信息,以及第二对应关系,确定所述s个目标终端的信息,其中,所述第二对应关系包括所述s个目标终端对应的路径的路径下行信息和所述s个目标终端的信息的对应关系;根据所述s个目标终端的信息,向所述s个目标终端分别发送所述数据包。
  31. 根据权利要求30所述的接入设备,其特征在于,所述s个目标终端中包括第二终端,所述接入设备还包括处理模块;
    所述处理模块,用于在所述第二终端在所述目标MLAN中建立MLAN会话的过程中,建立所述第二终端对应的路径的路径下行信息和所述第二终端的信息对应关系。
  32. 根据权利要求26-31任一项所述的接入设备,其特征在于,所述数据包携带所述目标MLAN的标识;
    或者,所述接入设备还包括处理模块;
    所述处理模块,用于根据所述组播路径的路径下行信息,以及第三对应关系,确定所述目标MLAN的标识,其中,所述第三对应关系包括所述组播路径的路径下行信息和所述目标MLAN标识的对应关系。
  33. 一种数据传输系统,其特征在于,所述数据传输系统包括如权利要求19-25任一项所述的用户面功能实体以及n个如权利要求26-32任一项所述的接入设备,n为正整数。
  34. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机可以执行如权利要求1-11任一项所述的数据传输方法。
  35. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机可以执行如权利要求12-18任一项所述的数据传输方法。
  36. 一种计算机程序产品,其特征在于,所述计算机程序产品中存储有指令,当其在计算机上运行时,使得计算机可以执行如权利要求1-11任一项所述的数据传输方法。
  37. 一种计算机程序产品,其特征在于,所述计算机程序产品中存储有指令,当其在计算机上运行时,使得计算机可以执行如权利要求12-18任一项所述的数据传输方法。
  38. 一种用来执行权利要求1-11任一项,或12-18任一项所述的数据传输方法的装置。
  39. 一种用户面功能实体,其特征在于,包括:处理器和存储器;所述存储器用于存储计算机执行指令,当所述用户面功能实体运行时,所述处理器执行所述存储器存储的该计算机执行指令,以使所述用户面功能实体执行如权利要求1-11任一项所述的数据传输方法。
  40. 一种接入设备,其特征在于,包括:处理器和存储器;所述存储器用于存储计算机执行指令,当所述接入设备运行时,所述处理器执行所述存储器存储的该计算机执行指令,以使所述接入设备执行如权利要求12-18任一项所述的数据传输方法。
PCT/CN2018/119163 2017-12-18 2018-12-04 数据传输方法、设备及系统 WO2019120073A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711368645.0A CN109936506B (zh) 2017-12-18 2017-12-18 数据传输方法、设备及系统
CN201711368645.0 2017-12-18

Publications (1)

Publication Number Publication Date
WO2019120073A1 true WO2019120073A1 (zh) 2019-06-27

Family

ID=66982945

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/119163 WO2019120073A1 (zh) 2017-12-18 2018-12-04 数据传输方法、设备及系统

Country Status (2)

Country Link
CN (1) CN109936506B (zh)
WO (1) WO2019120073A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021138558A1 (en) * 2020-01-03 2021-07-08 Nokia Technologies Oy Selecting session management function capable of storing internet protocol multicast

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112312328B (zh) * 2019-07-30 2022-10-28 华为技术有限公司 通信方法及相关装置
CN112788544B (zh) * 2019-11-07 2022-08-26 华为技术有限公司 通信方法、装置及设备
CN113645712B (zh) * 2020-05-11 2024-07-30 华为技术有限公司 通信方法及装置
US20230300572A1 (en) * 2020-05-22 2023-09-21 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for handling multicast broadcast service
CN114531256A (zh) * 2020-11-03 2022-05-24 阿里巴巴集团控股有限公司 数据通信方法及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005244366A (ja) * 2004-02-24 2005-09-08 Ntt Docomo Inc ゲートウェイ装置及び移動端末機とlan間接続方法
CN101394577A (zh) * 2007-09-21 2009-03-25 华为技术有限公司 组播广播多媒体业务用户面传输通道创建方法
CN104813691A (zh) * 2013-03-22 2015-07-29 联发科技股份有限公司 基于lte增强型多媒体广播多播业务的群组通信的无线资源高效传输

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8209745B2 (en) * 2008-05-13 2012-06-26 At&T Mobility Ii Llc Automatic population of an access control list to manage femto cell coverage
US8792419B2 (en) * 2010-04-08 2014-07-29 At&T Intellectual Property I, L.P. Presence-based communication routing service and regulation of same
CN102761474A (zh) * 2011-04-28 2012-10-31 华为技术有限公司 一种报文的过滤方法和接入设备
CN104735734B (zh) * 2013-12-19 2019-07-30 中兴通讯股份有限公司 一种业务处理的方法、网络控制器及转发设备
CN104852847A (zh) * 2015-04-07 2015-08-19 胡汉强 一种数据传输方法及控制面设备、转发面设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005244366A (ja) * 2004-02-24 2005-09-08 Ntt Docomo Inc ゲートウェイ装置及び移動端末機とlan間接続方法
CN101394577A (zh) * 2007-09-21 2009-03-25 华为技术有限公司 组播广播多媒体业务用户面传输通道创建方法
CN104813691A (zh) * 2013-03-22 2015-07-29 联发科技股份有限公司 基于lte增强型多媒体广播多播业务的群组通信的无线资源高效传输

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021138558A1 (en) * 2020-01-03 2021-07-08 Nokia Technologies Oy Selecting session management function capable of storing internet protocol multicast

Also Published As

Publication number Publication date
CN109936506A (zh) 2019-06-25
CN109936506B (zh) 2020-10-09

Similar Documents

Publication Publication Date Title
US11612013B2 (en) Data transmission method, device, and system
WO2019120073A1 (zh) 数据传输方法、设备及系统
US11558346B2 (en) Address management method and system, and device
JP7139522B2 (ja) ローカルエリアネットワーク通信方法、装置、およびシステム
US11812484B2 (en) Data transmission method, device, and data transmission system
WO2019214343A1 (zh) 订阅更新方法、设备及系统
WO2019137125A1 (zh) 会话管理方法、设备及系统
WO2019062830A1 (zh) 实例业务拓扑的生成方法及装置
WO2019024747A1 (zh) 通信方法、设备及系统
WO2019184723A1 (zh) 策略和计费控制规则获取方法、装置及系统
WO2019174437A1 (zh) 地址管理方法、设备及系统
WO2019223702A1 (zh) 管理pdu会话的方法、装置和系统
WO2020001319A1 (zh) 动态组网方法、设备及系统
JP2023547051A (ja) アプリケーションがネットワーク、装置、およびシステムにアクセスするための方法
WO2019210779A1 (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: 18890834

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

Country of ref document: EP

Kind code of ref document: A1