WO2019120073A1 - Procédé, dispositif et système de transmission de données - Google Patents

Procédé, dispositif et système de transmission de données 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)
Chinese (zh)
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/fr

Links

Images

Classifications

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

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

La présente invention concerne, dans un de ses modes de réalisation, un procédé, un dispositif et un système de transmission de données, susceptibles d'économiser la bande passante de transmission dans un scénario de multidiffusion en réseau local mobile (MLAN). Le procédé comporte les étapes suivantes: une entité fonctionnelle de plan d'utilisateur reçoit un paquet de données en provenance d'un équipement source, le paquet de données transportant des informations de multidiffusion; l'entité fonctionnelle de plan d'utilisateur détermine des informations de liaison descendante de trajets de n trajets de multidiffusion qui correspondent à un MLAN de destination; et au moyen des n trajets de multidiffusion qui correspondent aux informations de liaison descendante de trajets des n trajets de multidiffusion, l'entité fonctionnelle de plan d'utilisateur envoie respectivement le paquet de données à n dispositifs d'accès correspondants, n étant un entier positif.
PCT/CN2018/119163 2017-12-18 2018-12-04 Procédé, dispositif et système de transmission de données WO2019120073A1 (fr)

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 (fr) 2019-06-27

Family

ID=66982945

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/119163 WO2019120073A1 (fr) 2017-12-18 2018-12-04 Procédé, dispositif et système de transmission de données

Country Status (2)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021138558A1 (fr) * 2020-01-03 2021-07-08 Nokia Technologies Oy Sélection d'une fonction de gestion de session apte à stocker une multidiffusion par protocole internet

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 华为技术有限公司 通信方法、装置及设备
CN113645712A (zh) * 2020-05-11 2021-11-12 华为技术有限公司 通信方法及装置
WO2021232998A1 (fr) * 2020-05-22 2021-11-25 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil permettant de gérer un service de multidiffusion et de diffusion
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 ゲートウェイ装置及び移動端末機とｌａｎ間接続方法
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
US8522312B2 (en) * 2008-05-13 2013-08-27 At&T Mobility Ii Llc Access control lists and profiles 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 ゲートウェイ装置及び移動端末機とｌａｎ間接続方法
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 (fr) * 2020-01-03 2021-07-08 Nokia Technologies Oy Sélection d'une fonction de gestion de session apte à stocker une multidiffusion par protocole internet

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 (fr) Procédé, dispositif et système de transmission de données
JP7139522B2 (ja) ローカルエリアネットワーク通信方法、装置、およびシステム
US11558346B2 (en) Address management method and system, and device
US11812484B2 (en) Data transmission method, device, and data transmission system
WO2019137553A1 (fr) Procédé, dispositif, et système de configuration d'une politique d'eu
WO2019214343A1 (fr) Procédé, dispositif et système de mise à jour d'abonnement
WO2019137125A1 (fr) Procédé, dispositif et système de gestion de session
WO2019062830A1 (fr) Procédé et dispositif de génération d'exemple de topologie de service
WO2019024747A1 (fr) Procédé, dispositif et système de communication
WO2019223702A1 (fr) Procédé, appareil, et système de gestion de session pdu
WO2019184723A1 (fr) Procédé, dispositif et système d'acquisition de règle de commande de politique et de facturation
WO2019174437A1 (fr) Procédé, dispositif et système de gestion d'adresse
WO2020001319A1 (fr) Procédé, dispositif et système de mise en réseau dynamique
JP2023547051A (ja) アプリケーションがネットワーク、装置、およびシステムにアクセスするための方法
WO2019210779A1 (fr) Procédé, dispositif et système de commutation

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