WO2022213792A1 - 通信方法和通信装置 - Google Patents

通信方法和通信装置 Download PDF

Info

Publication number
WO2022213792A1
WO2022213792A1 PCT/CN2022/081611 CN2022081611W WO2022213792A1 WO 2022213792 A1 WO2022213792 A1 WO 2022213792A1 CN 2022081611 W CN2022081611 W CN 2022081611W WO 2022213792 A1 WO2022213792 A1 WO 2022213792A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
multicast group
multicast
session
management network
Prior art date
Application number
PCT/CN2022/081611
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 WO2022213792A1 publication Critical patent/WO2022213792A1/zh

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • the present application relates to the field of communication, and more particularly, to a communication method and a communication device.
  • hosts can communicate in a one-to-one group multicast mode.
  • Multicast is a kind of group communication.
  • the multicast source can transmit data to multiple devices that need (join the group) at one time, and can ensure that the communication of other devices that do not need (not join the group) is not affected.
  • multicast data needs to be forwarded through some network elements, resulting in a circuitous multicast transmission path and a large number of hops, which may result in a relatively large transmission delay in the multicast communication process. Therefore, it is desirable to provide a technology that can solve the problem of large transmission delay caused by circuitous paths in the multicast communication process.
  • the communication method and the communication device of the embodiments of the present application can reduce the transmission delay of the multicast communication process.
  • a first aspect provides a communication method, the method can be executed by a session management network element, or can also be executed by a chip or a chip system or circuit configured in the session management network element, the method includes: receiving a first request information and the identifier of the first multicast group, the first request information is used to request the terminal device to become the multicast source of the first multicast group, or the first request information is used to request the terminal device to join the first multicast group ; Send the second request information and the identifier of the first multicast group to the data management network element, the second request information is used to request to obtain the identifier of the first session management network element, and the first session management network element is used for grouping multicast session management, the first session management network element is associated with the identifier of the first multicast group; and the identifier of the first session management network element is received from the data management network element.
  • the UE by querying the first session management network element used for multicast session management, the UE can construct multicast data transmission directly from the UE to the first user plane function network element when establishing a session. It can reduce the detour of the transmission path and reduce the transmission delay.
  • the identifier of the first multicast group may be a multicast address of the first multicast group.
  • the terminal device sends a second session establishment request message to the mobility management network element, where the second session establishment request message is used to request to establish a second session between the terminal device and the data network, and the second session establishment request message contains It includes the first request information and the identifier of the first multicast group.
  • the mobility management network element selects the second session management network element, and sends a session management context request message to the second session management network element, where the session management context request message includes the first request information and the identifier of the first multicast group.
  • the terminal device sends a second session modification request message to the mobility management network element, where the second session modification request message is used to request modification of parameters of the second session, and the second session modification request message includes the first request information and the ID of the first multicast group.
  • the mobility management network element sends a session management context update request message to the second session management network element, where the session management context update request message includes the first request information and the identifier of the first multicast group.
  • the second session management network element may further receive the first request information and the first multicast group identifier from the application function network element.
  • first request information and the first multicast group identifier may be carried in the same message, or may be carried in two consecutively sent messages, which are not limited in this application.
  • the second session management network element determines that the terminal device requests to become a multicast source of the first multicast group, or the second request information is used to request the terminal device to join the first multicast group.
  • the second session management network element sends the data management network element sends second request information and the identifier of the first multicast group, the second request information is used to request to obtain the identifier of the first session management network element, the first session management network element is used for multicast session management, and the The first session management network element is associated with the identifier of the first multicast group.
  • the second session management network element sends third request information to the data management network element, the first The third request information is used to request to verify the authorization of the terminal device to become the multicast source of the first multicast group.
  • the data management network element verifies whether the terminal device has the authorization to become the multicast source of the first multicast group.
  • the second session management network element continues to execute the subsequent process only when the terminal device has the authorization to become the multicast source of the first multicast group, otherwise the second session management network element sends a response message to the terminal device, the response information It is used to reject the first request information, or to indicate that the terminal device fails to become the multicast source of the first multicast group, or the second session management network element ignores the first request information, and the specific manner is not limited in this application.
  • the first The second session management network element sends the second request information and the identifier of the first multicast group to the data management network element.
  • the second session management network element sends third request information to the data management network element, the first The third request information is used to request to verify the authorization of the terminal device to join the first multicast group.
  • the data management network element verifies whether the terminal device has the authorization to join the first multicast group. Only when the terminal device has the authorization to join the first multicast group, the second session management network element continues to perform the subsequent process.
  • the second request information and the first multicast group identifier may be carried in the same message, or may be carried in two consecutively sent messages, which are not limited in this application.
  • the method further includes: sending the identifier of the first session management network element to the mobility management network element.
  • the method before sending the second request information and the first multicast group identifier to the data management network element, the method further includes: sending to the data management network element
  • the third request information in the case that the first request information is used to request the terminal device to become the multicast source of the first multicast group, the third request information is used to request to verify the terminal device as the first multicast group
  • the authorization of the multicast source of the group in the case that the first request information is used to request the terminal device to join the first multicast group, the third request information is used to request to verify that the terminal device joins the first multicast group. authorization.
  • the data management network element can store the authorization information of the terminal device as the multicast source of the first multicast group or the authorization information of the terminal device to join the first multicast group in advance, and the terminal device requests Before acquiring the identifier of the first session management network element, the authorization status of the terminal device is first verified, which can avoid the failure of the subsequent process because the terminal device is not authorized, and ensure the reliability of communication.
  • the method further includes: sending first indication information and an identifier of the first session management network element to the terminal device, where the first session management network element is used for Multicast session management is performed, and the first indication information is used to instruct the terminal device to establish the first session.
  • the terminal device by sending the identifier of the first session management network element to the terminal device, and at the same time instructing the terminal device to establish the first session, the terminal device can establish a session through the first session management network element, so that the terminal device can establish a session through the first session management network element.
  • the terminal device can construct a multicast data transmission path with the first user plane functional network element, which can reduce the detour of the transmission path and reduce the transmission delay.
  • the method further includes: acquiring information of a first user plane function network element, where the first user plane function network element is used for forwarding processing of multicast data, The first user plane function network element is associated with the first multicast group identifier.
  • the method further includes: constructing data transmission between the first user plane function network element and the terminal device according to the information of the first user plane function network element path.
  • the information of the first user plane function network element is, for example, the address information of the first user plane function network element or the data network access identifier (DNAI) of the first user plane function network element.
  • DNAI data network access identifier
  • the session management network element constructs a data transmission path between the first user plane function network element and the terminal device after acquiring the information of the first user plane function network element , so the multicast data can be directly transmitted from the terminal equipment to the first user plane functional network element, or directly transmitted from the first user plane functional network element to the terminal equipment, thereby reducing the detour of the multicast data transmission path and reducing the transmission time. extension.
  • the acquiring information of the first user plane function network element includes: sending fourth request information and the identifier of the first multicast group to the data management network element , the fourth request information is used to request to obtain the information of the first user plane function network element; to receive the information of the first user plane function network element from the data management network element; or, to the first session management network element Send the fourth request information and the identifier of the first multicast group; and receive the information of the first user plane function network element from the first session management network element.
  • the session management network element receives the information of the first user plane function network element
  • the first user plane function network element is used as an additional session anchor point session management network element of the first session, and according to the first user plane function network element
  • the information of the network element is inserted into the second user plane function network element in the user plane, or the existing second user plane function network element is selected, and the corresponding configuration is performed through the N4 session, so that the second user plane function network element has the UL CL or BP function.
  • the first user plane function network element corresponding to the first multicast group identifier is selected as the additional session anchor user plane function network element
  • the multicast data of the terminal equipment is distributed to the first user plane function network element, and the multicast source terminal equipment is constructed.
  • the transmission path of the multicast data to the first user plane functional network element can reduce the detour of the transmission path and reduce the transmission delay.
  • the receiving the first request information and the identifier of the first multicast group includes: receiving the first request information and the first multicast group from the terminal device The identifier of the group; or, the first request information and the identifier of the first multicast group are received from the application function network element.
  • a communication method can be executed by a mobility management network element, or can also be executed by a chip or chip system or circuit configured in the mobility management network element, the method includes: receiving data from a terminal device
  • the first session establishment request message is used to request the establishment of the first session between the terminal device and the data network
  • the first session establishment request message includes the identifier of the first session management network element
  • the The first session management network element is used for multicast session management; the first request information and the identifier of the first multicast group are sent to the first session management network element, and the first request information is used to request the terminal device to become the first session management network element.
  • the multicast source of the multicast group, or the first request information is used to request the terminal device to join the first multicast group.
  • a multicast data transmission path from the UE directly to the first user plane function network element can be constructed, which can reduce the transmission rate.
  • the circuitous path reduces the transmission delay.
  • the method before the receiving the first session establishment request message from the terminal device, the method further includes: receiving the first request information and the first request message from the terminal device The identifier of the multicast group; sending the first request information and the identifier of the first multicast group to the second session management network element.
  • the receiving the first request information and the identifier of the first multicast group from the terminal device includes: receiving a second session establishment from the terminal device request message, the second session establishment request message includes the first request information and the identifier of the first multicast group; or receives a second session modification request message from the terminal device, the second session modification request message includes the first session modification request message a request message and the identifier of the first multicast group.
  • a communication method is provided.
  • the method can be performed by a terminal device or by a component (eg, a chip or a circuit) configured in the terminal device.
  • the method includes: receiving a communication message from a second session management network element.
  • the first indication information and the identifier of the first session management network element, the first session management network element is used for multicast session management, and the first indication information is used to instruct the terminal device to establish a first session; to the mobility management network element sending a first session establishment request message, where the first session establishment request message is used to request the establishment of the first session between the terminal device and the data network, where the first session establishment request message includes the identifier of the first session management network element,
  • the first session management network element is used for multicast session management.
  • the communication method of the embodiment of the present application can construct a multicast data transmission path from the UE directly to the first user plane functional network element, which can reduce the detour of the transmission path and reduce the transmission delay.
  • the method before the session establishment request message is sent to the mobility management network element, the method further includes: sending the first request information and the first multicast to the mobility management network element Group identifier, the first request message is used to request the terminal device to become the multicast source of the first multicast group, or the first request message is used to request the terminal device to join the first multicast group.
  • the sending the first request information and the first multicast group identifier to the mobility management network element includes: sending a second session establishment request message to the mobility management network element , the second session establishment request message includes the first request information and the identifier of the first multicast group; or, send a second session modification request message to the mobility management network element, where the second session modification request message includes the first session modification request message a request message and the identifier of the first multicast group.
  • a communication device comprising: a transceiver module configured to receive first request information and an identifier of a first multicast group, where the first request information is used to request a terminal device to become the first multicast group or the first request information is used to request the terminal device to join the first multicast group; the transceiver module is also used to send the second request information and the identifier of the first multicast group to the data management network element , the second request information is used to request to obtain the identifier of the first session management network element, the first session management network element is used for multicast session management, the first session management network element and the identifier of the first multicast group associated; the transceiver module is further configured to receive the identifier of the first session management network element from the data management network element.
  • the transceiver module may perform the processing of reception and transmission in the aforementioned first aspect; the communication device may further include a processing module, and the processing module may perform other processing in addition to reception and transmission in the aforementioned first aspect.
  • a fifth aspect provides a communication device, the device comprising: a transceiver module configured to receive a first session establishment request message from a terminal device, where the first session establishment request message is used to request to establish a communication between the terminal device and a data network.
  • the first session between the two, the first session establishment request message includes the identifier of the first session management network element, and the first session management network element is used for multicast session management; the transceiver module is also used to manage the first session.
  • the network element sends first request information and the identifier of the first multicast group, where the first request information is used to request the terminal device to become the multicast source of the first multicast group, or the first request information is used to request the terminal device to become a multicast source of the first multicast group Join the first multicast group.
  • the transceiver module may perform the processing of receiving and sending in the second aspect; the communication device may further include a processing module, and the processing module may perform other processing than the receiving and sending in the second aspect.
  • a communication device comprising: a transceiver module configured to receive first indication information and an identifier of the first session management network element from a second session management network element, the first session management network element Used for multicast session management, the first indication information is used to instruct the terminal device to establish a first session; the transceiver module is further configured to send a first session establishment request message to the mobility management network element, the first session establishment request message It is used for requesting to establish the first session between the terminal device and the data network, and the first session establishment request message includes the identifier of the first session management network element, and the first session management network element is used for multicast session management.
  • the transceiver module may perform the processing of reception and transmission in the aforementioned third aspect; the communication device may further include a processing module, and the processing module may perform other processing in addition to reception and transmission in the aforementioned third aspect.
  • a communication apparatus comprising: a processor for executing a computer program stored in a memory, so that the communication apparatus executes any one of the possible implementations of the first aspect or the second aspect .
  • a computer-readable storage medium is provided, a computer program is stored on the computer-readable storage medium, and when the computer program runs on a computer, the computer is made to execute any of the first to third aspects. one possible implementation.
  • a computer program product includes computer program instructions, and when the computer program instructions are run on a computer, the computer program instructions cause the computer to execute any one of the possible implementations of the first aspect to the third aspect. .
  • a chip system in a tenth aspect, includes: a processor for calling and running a computer program from a memory, so that a communication device installed with the chip system executes any of the first to third aspects. one possible implementation.
  • FIG. 1 is a schematic diagram of a network architecture suitable for the method provided by the embodiment of the present application.
  • FIG. 2 is a schematic diagram of another network architecture applicable to the method provided by this embodiment of the present application.
  • FIG. 3 is a schematic diagram of a system architecture for multicast communication.
  • FIG. 4 is a schematic diagram of another system architecture for multicast communication.
  • FIG. 5 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a communication method provided by another embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a communication method provided by another embodiment of the present application.
  • FIG. 8 is a schematic diagram of a system architecture for multicast communication provided by an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a communication method provided by another embodiment of the present application.
  • FIG. 10 is a schematic diagram of another system architecture for multicast communication provided by an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of a communication method provided by another embodiment of the present application.
  • FIG. 12 is a schematic flowchart of a communication method provided by another embodiment of the present application.
  • FIG. 13 is a schematic diagram of another system architecture for multicast communication provided by an embodiment of the present application.
  • FIG. 14 is a schematic flowchart of a communication method provided by another embodiment of the present application.
  • FIG. 15 is a schematic diagram of another system architecture for multicast communication provided by an embodiment of the present application.
  • FIG. 16 is a schematic block diagram of a communication apparatus provided by an embodiment of the present application.
  • FIG. 17 is a schematic block diagram of a communication apparatus provided by another embodiment of the present application.
  • FIG. 18 is a schematic block diagram of a communication apparatus provided by another embodiment of the present application.
  • FIG. 19 is a schematic block diagram of a communication apparatus provided by another embodiment of the present application.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • UMTS universal mobile telecommunication system
  • WiMAX worldwide interoperability for microwave access
  • the names of network elements may be different. The following describes this application by taking the naming of network elements in a 5G network as an example.
  • FIG. 1 and FIG. 2 are schematic diagrams of network architectures applicable to the methods provided by the embodiments of the present application.
  • Figure 1 is a schematic diagram of a 5G network architecture based on a service interface
  • Figure 2 is a 5G network architecture diagram based on a point-to-point interface.
  • User equipment can include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of terminals, mobile Station (mobile station, MS), terminal (terminal), soft terminal and so on. For example, water meters, electricity meters, sensors, etc.
  • Radio access network radio access network, RAN
  • RAN Radio access network
  • It is used to provide network access functions for authorized user equipment in a specific area, and can use different quality transmission tunnels according to the level of user equipment and service requirements.
  • the RAN network element can manage radio resources, provide access services for the user equipment, and then complete the forwarding of control signals and user equipment data between the user equipment and the core network.
  • the RAN network element can also be understood as a base station in a traditional network.
  • RAN can be NB, eNB, gNB, ng-eNB, or any other access network device.
  • User plane function used for packet routing and forwarding and quality of service (QoS) processing of user plane data.
  • QoS quality of service
  • the user plane network element may be a user plane function (UPF) network element.
  • the user plane network element may still be the UPF network element, or may have other names, which are not limited in this application.
  • DN Data network
  • the data network element may be a data network element.
  • the data network element may still be a DN network element, or may have other names, which are not limited in this application.
  • AMF mainly used for mobility management and access management, etc., and can be used to implement other functions in the MME function except session management, such as legal interception and access authorization/authentication functions.
  • the access and mobility management network element may be an access and mobility management function (AMF).
  • AMF access and mobility management function
  • the access and mobility management device may still be AMF, or may have other names, which are not limited in this application.
  • Session management function It is mainly used for session management, network interconnection protocol (IP) address allocation and management of user equipment, selection and management of user plane functions, policy control and charging function interfaces The endpoint and downlink data notification, etc.
  • IP network interconnection protocol
  • the session management network element may be a session management function network element.
  • the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.
  • PCF Policy control function
  • the policy control network element may be a policy and charging rules function (policy and charging rules function, PCRF) network element.
  • policy control network element may be a policy control function PCF network element.
  • the policy control network element may still be the PCF network element, or may have other names, which are not limited in this application.
  • Application function used for data routing affected by applications, open function network elements of the wireless access network, interacting with the policy framework for policy control, etc.
  • the application network element may be an application function network element.
  • the application network element may still be the AF network element, or may have other names, which are not limited in this application.
  • Unified data management used to process UE identification, access authentication, registration, and mobility management.
  • the data management network element may be a unified data management network element; in a 4G communication system, the data management network element may be a home subscriber server (HSS) network element.
  • HSS home subscriber server
  • the unified data management may still be a UDM network element, or may have other names, which are not limited in this application.
  • Unified data repository It mainly includes the following functions: access functions of contract data, policy data, application data and other types of data.
  • AUSF Authentication server function
  • the authentication server may be an authentication server function network element.
  • the authentication server function network element may still be the AUSF network element, or may have other names, which are not limited in this application.
  • the above network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (eg, a cloud platform).
  • a platform eg, a cloud platform.
  • the network device is the access and mobility management network element AMF
  • the base station is the radio access network RAN as an example for description.
  • the user equipment is connected to the AMF through the N1 interface
  • the RAN is connected to the AMF through the N2 interface
  • the RAN is connected to the UPF through the N3 interface.
  • the UPFs are connected through the N9 interface
  • the UPFs are interconnected through the N6 interface DN.
  • the SMF controls the UPF through the N4 interface.
  • the AMF interfaces with the SMF through the N11 interface.
  • the AMF obtains user equipment subscription data from the UDM unit through the N8 interface
  • the SMF obtains the user equipment subscription data from the UDM unit through the N10 interface.
  • network function network element entities such as AMF, SMF network element, PCF network element, BSF network element, and UDM network element are all called network function (NF) network elements;
  • NF network function
  • a set of network elements such as AMF, SMF network element, PCF network element, BSF network element, and UDM network element may be called control plane functional network elements.
  • switches and routers in the network only forward data without copying it. If 10 clients need the same data, the server needs to transmit one by one, repeating the same work 10 times. However, because it can respond in time to the requirements of each customer, all current web browsing adopts the unicast mode, that is, the IP unicast protocol. Routers and switches in the network select transmission paths based on their destination addresses, and transmit IP unicast data to their designated destinations.
  • a unicast IP address is the IP address of a single host.
  • One-to-one communication mode between hosts that is, hosts that join the same group can receive all data in this group, and switches and routers in the network only copy and forward the data they need to those who need it.
  • a host can request a router to join or leave a group.
  • the routers and switches in the network selectively copy and transmit data, that is, only transmit the data in the group to those hosts that join the group. In this way, data can be transmitted to multiple hosts in need (joining the group) at one time, and other communications of other hosts that do not need (joining the group) can be guaranteed not to be affected.
  • the multicast IP address is a class D IP address in the range of 224.0.0.0 to 239.255.255.255.
  • a multicast group is a collection of receivers identified by an IP multicast address.
  • a host joins a multicast group and becomes a member of the multicast group to receive multicast data sent to the multicast group.
  • Membership in a multicast group is dynamic, and hosts can join or leave the multicast group at any time.
  • Multicast group members can be widely distributed anywhere in the network.
  • the host that sends information to the multicast group is the multicast source.
  • a multicast source usually does not need to join a multicast group.
  • a multicast source can send information to multiple multicast groups at the same time, and multiple multicast sources can also send information to a multicast group at the same time.
  • the network In the one-to-all communication mode between hosts, the network unconditionally replicates and forwards the signals sent by each host, and all hosts can receive all information (whether you need it or not). Network costs can be very low.
  • the cable TV network is a typical broadcast network. Our TV actually receives the signals of all channels, but only restores the signal of one channel into a picture.
  • the existence of broadcast is also allowed in the data network, but it is usually limited to the local area network of the Layer 2 switch, and the broadcast data is prohibited from passing through the router to prevent the broadcast data from affecting a large area of hosts.
  • the restricted broadcast address namely 255.255.255.255; the broadcast address pointing to the network, that is, the address with all 1s of the host number; the broadcast address pointing to the subnet, that is, the host number is all 1s and has a specific subnet
  • Protocol data unit (PDU) session PDU session
  • the 5G core network (5G corenet, 5GC) supports PDU connection services.
  • the PDU connection service may refer to the service of exchanging PDU data packets between the terminal device and the DN.
  • the PDU connection service is realized through the establishment of a PDU session initiated by the terminal device. After a PDU session is established, a data transmission channel between the terminal device and the DN is established. In other words, PDU sessions are UE-level. Each end device can establish one or more PDU sessions.
  • the terminal device can access the DN through the PDU session established between the terminal device and the DN.
  • the SMF primary user is responsible for session management in the mobile network.
  • the PDU session can be established, modified or released between the terminal device and the SMF through NAS session management (session management, SM) signaling.
  • NAS session management session management, SM
  • a terminal device may establish multiple PDU sessions or multiple PDU connection services, for example, a terminal device may establish two or more PDU sessions, which are not limited.
  • the DN identifiers (data network names, DNNs) of these PDU sessions may be different or the same.
  • different PDU sessions may be served by the same SMF, or may be served by different SMFs.
  • the establishment of these PDU sessions may be initiated simultaneously or sequentially.
  • any sender can become a multicast source, sending information to a multicast address.
  • the receiver can join or leave the multicast group at any time, but cannot know the address of the multicast source in advance.
  • SSM Source-specific multicast
  • the receiver can know the address of the multicast source in advance, and can specify the source at the client.
  • SSM uses a different multicast address range from that of ASM, and directly establishes a dedicated multicast forwarding path between the receiver and its designated multicast source.
  • Multicast/broadcast-session management function (MB-SMF)
  • MB-SMF is mainly responsible for multicast broadcast session management and control of multicast broadcast transmission.
  • MB-UPF and RAN are configured accordingly to complete the transmission of multicast broadcast streams. .
  • Multicast/broadcast user plane function (multicast/broadcast-user plane function, MB-UPF)
  • MB-UPF is mainly responsible for sending multicast broadcast streams to RAN (or UPF), which can filter and distribute multicast broadcast streams, and implement QoS enhancement and counting/reporting of multicast broadcast services.
  • Uplink classifier (ULCL)/branching point (BP)
  • Both ULCL and BP are the functions of UPF.
  • the function of UL CL is the upstream classifier of the data flow, that is, based on the identification of the upstream characteristics of the service flow, the data is distributed to the local DN or the remote protocol data unit session anchor (PDU session anchor, PSA). )UPF.
  • the UL CL aggregates the downstream flow.
  • the functions of BP and UL CL are the same, except that BP is a shunting point for internet protocol version 6 (IPv6), and UL CL is an uplink classifier for internet protocol version 4 (IPv4). .
  • UE1, UE2, and UE3 are members of the multicast group
  • UE4 is the multicast source of the multicast group
  • the application server (AS) is the anchor point for data processing and forwarding, namely UE4
  • the uplink for sending multicast data must reach the AS, the AS processes the data (for example, parses the data, or just forwards it), and then the AS sends the downlink multicast data.
  • UE 4 sends multicast data to the multicast group as a multicast source, sends the multicast data to AS via unicast PSA UPF, AS performs data processing on the multicast data and forwards it to MB-UPF , the MB-UPF sends the multicast data to the RAN through the N3 multicast tunnel, and the RAN further sends the multicast data to the multicast members UE1, UE2 and UE3.
  • the multicast communication through the transmission path shown in FIG. lead to an increase in transmission delay.
  • UE1, UE2, and UE3 are members of the multicast group.
  • RAN1 where UE1 and UE2 are located also supports multicast services, but UE3
  • multicast data needs to be sent to UE3 by unicast mode.
  • MB-UPF receives the multicast data (which can be sent by UE or AS), it forwards the multicast data to RAN 1 through the shared multicast tunnel, and RAN 1 uses point-to-multipoint (point-to-multipoint) to forward the multicast data to RAN 1.
  • point-to-multipoint point-to-multipoint
  • PTM point-to-point
  • PTP point-to-point
  • MB-UPF forwards multicast packets to multicast members
  • MB-UPF and RAN 2 can be directly connected, or when PSA UPF is located at a higher distance from RAN 2 than MB-UPF
  • MB-UPF The forwarding path from UPF to PSA UPF and then to RAN 2 is circuitous or has a large number of hops, resulting in increased transmission delay.
  • FIG. 5 is a schematic flowchart of a method 500 provided by an embodiment of the present application. As can be seen from Figure 5, the method 500 includes:
  • the second session management network element receives the first request information and the identifier of the first multicast group from the terminal device.
  • the first request information is used to request the terminal device to become a multicast source of the first multicast group, or the first request information is used to request the terminal device to join the first multicast group.
  • the identifier of the first multicast group may be, for example, the multicast address of the first multicast group.
  • the terminal device sends a second session establishment request message to the mobility management network element, where the second session establishment request message is used to request to establish a second session between the terminal device and the data network, and the second session establishment request message contains It includes the first request information and the identifier of the first multicast group.
  • the mobility management network element selects the second session management network element, and sends a session management context request message to the second session management network element, where the session management context request message includes the first request information and the identifier of the first multicast group.
  • the terminal device sends a second session modification request message to the mobility management network element, where the second session modification request message is used to request modification of parameters of the second session, and the second session modification request message includes the first request information and the ID of the first multicast group.
  • the mobility management network element sends a session management context update request message to the second session management network element, where the session management context update request message includes the first request information and the identifier of the first multicast group.
  • the second session management network element may further receive the first request information and the first multicast group identifier from the application function network element.
  • first request information and the first multicast group identifier may be carried in the same message, or may be carried in two consecutively sent messages, which are not limited in this application.
  • the second session management network element sends the second request information and the identifier of the first multicast group to the data management network element.
  • the second session management network element determines that the terminal device requests to become a multicast source of the first multicast group, or the second request information is used to request the terminal device to join the first multicast group.
  • the second session management network element sends the data management network element sends second request information and the identifier of the first multicast group, the second request information is used to request to obtain the identifier of the first session management network element, the first session management network element is used for multicast session management, and the The first session management network element is associated with the identifier of the first multicast group.
  • the second session management network element sends third request information to the data management network element, the first The third request information is used to request to verify the authorization of the terminal device to become the multicast source of the first multicast group.
  • the data management network element verifies whether the terminal device has the authorization to become the multicast source of the first multicast group.
  • the second session management network element continues to execute the subsequent process only when the terminal device has the authorization to become the multicast source of the first multicast group, otherwise the second session management network element sends a response message to the terminal device, the response information It is used to reject the first request information, or to indicate that the terminal device fails to become the multicast source of the first multicast group, or the second session management network element ignores the first request information, and the specific manner is not limited in this application.
  • the first The second session management network element sends the second request information and the identifier of the first multicast group to the data management network element.
  • the second session management network element sends third request information to the data management network element, the first The third request information is used to request to verify the authorization of the terminal device to join the first multicast group.
  • the data management network element verifies whether the terminal device has the authorization to join the first multicast group. Only when the terminal device has the authorization to join the first multicast group, the second session management network element continues to perform the subsequent process.
  • the second request information and the first multicast group identifier may be carried in the same message, or may be carried in two consecutively sent messages, which are not limited in this application.
  • the data management network element sends the identifier of the first session management network element to the second session management network element.
  • the data management network element determines the first session management network element corresponding to the first multicast group identifier according to the first multicast group identifier, and then sends the identifier of the first session management network element to the second session management network. Yuan.
  • the second session management network element obtains the information of the first user plane function network element, the first user plane function network element is used for multicast data management, and the first user plane function network element is used for multicast data management.
  • the user plane functional network element is associated with the first multicast group identifier.
  • the information of the first user plane function network element is, for example, the ID of the first user plane function network element or the DNAI of the first user plane function network element.
  • the second session management network element obtains the information of the first user plane function network element through the first session management network element. Specifically, the second session management network element sends fourth request information and the identifier of the first multicast group to the first session management network element, where the fourth request information is used to request to obtain information of the first user plane function network element.
  • the first session management network element determines the information of the first user plane functional network element according to the identifier of the first multicast group, and sends the information of the first user plane kinetic energy network element to the second session management network element.
  • the second session management network element obtains the information of the first user plane function network element through the data management network element. Specifically, the second session function network element sends the fourth request information and the identifier of the first multicast group to the data management network element. The data management network element determines the information of the first user plane function network element according to the identifier of the first multicast group, and sends the information of the first user plane function network element to the second session management network element. It should be understood that, in the solution provided in this example, the first session management network element saves the information of the first user plane function network element in the data management network element during the first multicast configuration process.
  • the second session management network element sends the first indication information and the identifier of the first session management network element to the terminal device.
  • the second session management network element after acquiring the identifier of the first session management network element from the data management network element, the second session management network element sends the first indication information and the identifier of the first session management network element to the mobility management network element.
  • the indication information is used to instruct the terminal device to establish the first session, and the mobility management network element transparently transmits the first indication information and the identifier of the first session management network element to the terminal device.
  • the terminal device sends a first session establishment request message to the mobility management network element.
  • the terminal device sends a first session establishment request message to the mobility management network element according to the first indication information, where the first session establishment request message is used to request to establish a first session between the terminal device and the data network, the The first session establishment request message includes the identifier of the first session management network element.
  • the mobility management network element sends the first request information and the identifier of the first multicast group to the first session management network element.
  • the mobility management network element after receiving the first session establishment request message, acquires the identifier of the first session management network element, and then selects the first session management network element to establish the first session.
  • the mobility management network element sends the first request information and the identifier of the first multicast group to the first session management network element to instruct the terminal device to request to become a multicast source of the first multicast group, or to request to join the first multicast group.
  • the session management network element in this embodiment is a network element used for session management
  • the data management network element in this embodiment is a network element used for accessing various types of data.
  • the first session management network element in this embodiment is a network element associated with the identifier of the first multicast group and used for multicast session management
  • the mobility management network element in this embodiment is a mobility management and
  • the network elements for access management may have different names for implementing similar functions in different systems.
  • the session management network element may be an SMF
  • the data management network element may be a UDR
  • the first session management network element may be an MB-SMF corresponding to the first multicast group
  • the mobility management network Meta can be AMF.
  • the communication method of the embodiment of the present application can construct a multicast data transmission path from the UE directly to the multicast session management network element, which can reduce the detour of the transmission path and reduce the transmission delay.
  • FIG. 6 is a schematic flowchart of a method 600 provided by an embodiment of the present application.
  • the UE requests to be the multicast source of the first multicast group, and the multicast data sent by the UE as the multicast source does not require AS parsing processing.
  • method 600 includes:
  • a first multicast group configuration is completed between the network device and the UE.
  • the UE sends a first PDU session establishment request message to the AMF.
  • the UE sends a first PDU session establishment request message to the AMF through the RAN, where the first PDU session establishment request message is used to request to establish a first PDU session between the UE and the data network DN.
  • the first PDU session establishment request message includes a first multicast group identifier and first request information, where the first multicast group identifier is used to identify the first multicast group, and the first multicast group identifier may be, for example, the first The multicast address of the multicast group, and the first request information is used to request to be the multicast source of the first multicast group.
  • first request information may also be used to request the network device to forward the multicast data sent by the UE. It should also be understood that the first request information and the multicast group identifier may also be sent in other messages, which are not limited in this application.
  • AMF selects SMF.
  • the AMF selects the SMF to establish the first PDU session.
  • the AMF sends a session management context request message to the SMF.
  • the AMF sends a session management context request message to the SMF selected in S603, where the session management context request message is used to request the establishment of the first PDU session management context.
  • the session management context request message includes first request information and a first multicast group identifier.
  • the SMF sends a session management context response message to the AMF.
  • the SMF after receiving the session management context request message sent by the AMF, the SMF creates a session management context for the first PDU session, and then sends a session management context response message to the AMF, where the session management context response message is used to indicate the status of the first PDU session.
  • the session management context is established.
  • the SMF checks the authorization of the UE as a multicast source, and obtains the MB-SMF ID.
  • the SMF determines the type of the first multicast group according to the first multicast group identifier.
  • the types of multicast groups include ASM mode and SSM mode.
  • the SMF checks the authorization of the UE as a multicast source. For example, the SMF obtains authorization information of the multicast source of the first multicast group from the UDR, and judges whether the UE is authorized as the multicast source according to the authorization information.
  • the SMF obtains the MB-SMF identifier, such as the MB-SMF ID, from the UDR according to the first multicast group identifier.
  • the SMF sends a first message to the UE, where the first message includes the first information, the second information and the MB-SMF ID.
  • the SMF when the UE has authorization as the multicast source of the first multicast group, the SMF sends the first information, the second information and the MB-SMF ID to the UE through a first message, wherein the first information is used to reject The first PDU session establishment request message, and the second information is used to instruct the UE to re-establish the PDU session.
  • the SMF calls the Namf_N1N2MessageTransfer service of the AMF to send the first message to the UE, the AMF transmits the first message to the RAN through the N2 PDU Session Request, and the RAN transparently transmits the first message through the AN-specific resource setup process to the UE.
  • the UE sends a second PDU session establishment request message to the AMF.
  • the UE sends a second PDU session establishment request message to the AMF according to the second information, where the second PDU session establishment request message is used to request establishment of the second PDU session.
  • the second PDU session establishment request message includes the MB-SMF ID.
  • the second PDU session establishment request message further includes first request information and a first multicast group identifier, where the first request information is used to request to be a multicast source of the first multicast group.
  • AMF selects MB-SMF.
  • the AMF receives the second PDU session establishment request message from the UE, and obtains the MB-SMF ID carried in the second PDU session establishment request message, and the AMF selects the MB-SMF to establish the second PDU according to the MB-SMF ID. session.
  • the AMF sends a session management context request message to the MB-SMF.
  • the AMF sends a session management context request message to the MB-SMF, where the session management context request message is used to request the establishment of the second PDU session management context.
  • the session management context request message includes first request information and a first multicast group identifier.
  • the SMF sends the first correspondence between the MB-SMF ID, the first request information and the first PDU session ID to the AMF.
  • the AMF receives the first correspondence from the SMF, and stores the first correspondence locally.
  • the second PDU session establishment request message sent by the UE to the AMF includes the second PDU session ID and the first PDU session ID.
  • the AMF receives the second PDU session establishment request message from the UE, and obtains the second PDU session ID and the first PDU session ID, and then the AMF determines the MB-SMF ID and the first PDU session ID according to the first PDU session ID and the first corresponding relationship.
  • the AMF selects the corresponding MB-SMF as the session management network element of the second PDU session according to the MB-SMF ID, and then the AMF carries the first request message corresponding to the first PDU session in the session management context request message of S610 .
  • the network side selects the MB-UPF to complete the second PDU session establishment process.
  • the MB-SMF after receiving the session management context request message sent by the AMF, the MB-SMF obtains the first request information and the first multicast group identifier in the session management context request message, and determines, according to the first request information, that the UE requests as the The multicast source of the first multicast group.
  • the MB-SMF finds the MB-UPF from the corresponding first multicast context according to the first multicast group identifier, and selects the MB-UPF as the PSA UPF of the second PDU session.
  • the network side continues to complete the establishment of the second PDU session, and the specific manner is not limited.
  • the PDU session establishment process by directly selecting the MB-UPF of the multicast group corresponding to the multicast source UE as the PSA UPF of the new session of the multicast source UE, a multicast is constructed.
  • the transmission path of the multicast data from the source UE to the MB-UPF can reduce the detour of the transmission path and reduce the transmission delay.
  • FIG. 7 is a schematic flowchart of a method 700 provided by an embodiment of the present application.
  • the UE requests to be the multicast source of the first multicast group, and the multicast data sent by the UE as the multicast source does not require AS parsing processing.
  • method 700 includes:
  • a first multicast group configuration is completed between the network device and the UE.
  • the UE sends a first PDU session modification request message to the AMF, where the first PDU session modification request message is used to request modification of a quality of service (quality of service, QoS) parameter of the first PDU session, the first PDU session modification
  • the request message includes first request information and a first multicast group identifier, where the first multicast group identifier is used to identify the first multicast group, and the first multicast group identifier can be, for example, a multicast group of the first multicast group. address, and the first request information is used to request the UE to be the multicast source of the first multicast group.
  • the AMF sends a session management context update request message to the SMF, where the session management context update request message includes the first request information and the first multicast group identifier.
  • the AF may also send the first request information and the first multicast group identifier to the SMF.
  • the AF sends a second message to the SMF, where the second message includes the first request information and the first multicast group identifier.
  • the second message may be, for example, a request message for the UE to act as a multicast source. It should be understood that the AF can directly send the second message to the SMF, or it can be forwarded through a network exposure function (NEF).
  • NEF network exposure function
  • the SMF checks the authorization of the UE as a multicast source, and obtains the MB-SMF ID.
  • S705 is similar to S606 in the method 600, and the description will not be repeated here in this application.
  • the SMF sends a first message to the UE, where the first message includes the second information and the MB-SMF ID.
  • the SMF when the UE has the authorization to be the multicast source of the first multicast group, the SMF sends the second information and the MB-SMF ID to the UE through the first message, where the second information is used to instruct the UE to rebuild the PDU session .
  • the SMF invokes the Namf_N1N2MessageTransfer service of the AMF to send the first message to the UE, where the first message includes the second information and the MB-SMF ID, and the AMF sends the first message to the UE via the RAN.
  • the first message may also be a PDU session modification command message.
  • the UE sends a second PDU session establishment request message to the AMF.
  • AMF selects MB-SMF.
  • the AMF sends a session management context request message to the MB-SMF.
  • the network side selects the MB-UPF to complete the second PDU session establishment process.
  • S707-S710 are similar to S608-S611 in the method 600, and for the sake of brevity, the description is not repeated here in this application.
  • the SMF sends the first correspondence between the MB-SMF ID, the first request information and the first PDU session ID to the AMF.
  • the AMF receives the first correspondence from the SMF, and stores the first correspondence locally.
  • the second PDU session establishment request message sent by the UE to the AMF includes the second PDU session ID and the first PDU session ID.
  • the AMF receives the second PDU session establishment request message from the UE, and obtains the second PDU session ID and the first PDU session ID, and then the AMF determines the MB-SMF ID and the first PDU session ID according to the first PDU session ID and the first corresponding relationship.
  • the AMF selects the corresponding MB-SMF as the session management network element of the second PDU session according to the MB-SMF ID, and then the AMF carries the first request message corresponding to the first PDU session in the session management context request message of S709 .
  • the PDU session establishment process by directly selecting the MB-UPF of the multicast group corresponding to the multicast source UE as the PSA UPF of the new session of the multicast source UE, a multicast is constructed.
  • the transmission path of the multicast data from the source UE to the MB-UPF can reduce the detour of the transmission path and reduce the transmission delay.
  • FIG. 8 is a schematic diagram of a system architecture 800 to which method 600 and method 700 are applied.
  • UE1, UE2, and UE3 are members of a multicast group
  • UE4 is a multicast source of the multicast group.
  • the MB-UPF corresponding to the multicast group is selected as the PSA UPF of the new session of UE4.
  • the UPF sends the multicast data to the AS, and then forwards the multicast data to the MB-UPF through the AS, which avoids the detour of the transmission path during the multicast communication and reduces the transmission delay of the multicast communication.
  • FIG. 9 is a schematic flowchart of a method 900 provided by an embodiment of the present application.
  • the UE requests to be the multicast source of the first multicast group, and the multicast data sent by the UE as the multicast source does not require AS parsing processing.
  • method 900 includes:
  • a first multicast group configuration is completed between the network device and the UE.
  • the UE sends a first PDU session modification request message to the AMF, where the first PDU session modification request message includes the first request information and the first multicast group identifier.
  • the first multicast group identifier is used to identify the first multicast group, and the first multicast group identifier may be, for example, the multicast address of the first multicast group, and the first request information is used to request the UE as the first group The multicast source of the broadcast group.
  • the AMF sends a session management context update request message to the SMF, where the session management context update request message includes the first request information and the first multicast group identifier.
  • the AF may also send the first request information and the first multicast group identifier to the SMF.
  • the AF sends a second message to the SMF, where the second message includes the first request information and the first multicast group identifier.
  • S901-S904 are similar to S701-S704 in the method 700, and for the sake of brevity, the description is not repeated here in this application.
  • the SMF acquires the information of the MB-UPF.
  • the SMF checks the authorization of the UE as a multicast source, and obtains the MB-SMF ID.
  • S905 is similar to S606 in the method 600, and for the sake of brevity, the description is not repeated here in this application.
  • the type of the first multicast group is the ASM model or the SSM model, the solution in this embodiment is applicable.
  • the SMF obtains the information of the MB-UPF through the MB-SMF.
  • the SMF sends a request message to the MB-SMF for requesting to obtain the MB-UPF address information according to the MB-SMF ID, where the request message carries the first multicast group identifier; correspondingly, after the MB-SMF receives the request message, , and obtain the MB-UPF information corresponding to the first multicast group identifier according to the first multicast group identifier, for example, the address information of the MB-UPF, or the DNAI of the MB-UPF.
  • the MB-SMF replies the MB-UPF information to the SMF.
  • the SMF checks the authorization of the UE as a multicast source, and obtains the MB-UPF ID.
  • the SMF obtains MB-UMF information from the UDR according to the first multicast group identifier, for example, the address information of the MB-UPF or the DNAI of the MB-UPF.
  • the MB-SMF stores the address information of the MB-UPF or the DNAI of the MB-UPF into the UDR.
  • the network side uses the MB-UPF as the additional PSA UPF of the first PDU session, inserts or selects an existing UPF on the user plane, and configures the UPF to have the function of UL CL or BP.
  • the SMF uses the MB-UPF as the additional PSA UPF of the first PDU session, and inserts the UPF on the user plane according to the information of the MB-UPF or selects the existing UPF,
  • the N4 session is configured accordingly, so that the UPF has the function of UL CL or BP, so as to realize the effect of offloading the multicast data of the UE to the MB-UPF.
  • the UPF with UL CL or BP function may be the same UPF entity as the MB-UPF, or may be the same UPF entity as the PSA UPF of the PDU session.
  • the MB-UPF of the multicast group corresponding to the multicast source UE is selected as the additional PSA UPF of the first PDU session, and the inserted UPF or the selected UPF is selected by the MB-UPF of the multicast group corresponding to the multicast source UE.
  • UL CL/BP it realizes the offloading of multicast data from UE to MB-UPF, and constructs the transmission path of multicast data from multicast source UE to MB-UPF, which can reduce the detour of the transmission path and reduce the transmission delay.
  • FIG. 10 is a schematic diagram of a system architecture 1000 to which the method 900 is applied.
  • UE1, UE2, and UE3 are members of a multicast group
  • UE4 is a multicast source of the multicast group.
  • UE4 sets the MB-UPF of the multicast group corresponding to UE4 as the additional PSA UPF of the PDU session.
  • the UE4 By inserting a UPF on the line between the RAN and the original PSA UPF, or selecting an existing UPF on the line between the RAN and the original PSA UPF, and configuring the UL CL or BP function on the UPF, the UE4 to The transmission path of MB-UPF multicast data.
  • UE4 acts as a multicast source to send multicast data to a multicast group
  • Forwarding to MB-UPF avoids the detour of the transmission path during multicast communication and can reduce the transmission delay of multicast communication.
  • FIG. 11 is a schematic flowchart of a method 1100 provided by an embodiment of the present application.
  • the UE requests to join the first multicast group, and the UE does not support receiving multicast data in a multicast manner, or the RAN where the UE is located does not support multicast services.
  • method 1100 includes:
  • a first multicast group configuration is completed between the network device and the UE.
  • the UE sends a first PDU session establishment request message to the AMF.
  • the UE sends a first PDU session establishment request message to the AMF through the RAN, where the first PDU session establishment request message is used to request to establish a first PDU session between the UE and the data network DN.
  • the first PDU session establishment request message includes a first multicast group identifier, where the first multicast group identifier is used to identify the first multicast group, and the first multicast group identifier may be, for example, a group of the first multicast group
  • the first multicast address is used to instruct the UE to request to join the first multicast group.
  • AMF selects SMF.
  • the AMF selects the SMF to establish the first PDU session.
  • the AMF sends a session management context request message to the SMF.
  • the AMF sends a session management context request message to the SMF selected in S603, where the session management context request message is used to request the establishment of the first PDU session management context.
  • the session management context request message includes the first multicast group identifier.
  • the SMF sends a session management context response message to the AMF.
  • the SMF after receiving the session management context request message sent by the AMF, the SMF creates the session management context of the first PDU session, and then sends the session management context response message to the AMF.
  • the SMF checks the authorization of the UE to join the multicast group, and obtains the MB-SMF ID.
  • the SMF obtains authorization information of the multicast members of the first multicast group from the UDR, and judges whether the UE is authorized to join the multicast group according to the authorization information.
  • the SMF obtains the MB-SMF identifier, such as the MB-SMF ID, from the UDR according to the first multicast group identifier.
  • the SMF sends a first message to the UE, where the first message includes the first information, the second information and the MB-SMF ID.
  • S1107 is similar to S607 in the method 600, and for the sake of brevity, details are not described herein again in this application.
  • the UE sends a second PDU session establishment request message to the AMF.
  • the UE sends a second PDU session establishment request message to the AMF according to the second information, where the second PDU session establishment request message is used to request establishment of the second PDU session.
  • the second PDU session establishment request message includes the MB-SMF ID and the first multicast group identifier.
  • AMF selects MB-SMF.
  • the AMF receives the second PDU session establishment request message from the UE, and obtains the MB-SMF ID carried in the second PDU session establishment request message, and the SMF selects the MB-SMF to establish the second PDU according to the MB-SMF ID. session.
  • the AMF sends a session management context request message to the MB-SMF.
  • the AMF sends a session management context request message to the MB-SMF, where the session management context request message is used to request the establishment of the second PDU session management context.
  • the session management context request message includes the first multicast group identifier.
  • the SMF sends the first correspondence between the MB-SMF ID, the first multicast group identifier and the first PDU session ID to the AMF.
  • the AMF receives the first correspondence from the SMF, and stores the first correspondence locally.
  • the second PDU session establishment request message sent by the UE to the AMF includes the second PDU session ID and the first PDU session ID.
  • the AMF receives the second PDU session establishment request message from the UE, and obtains the second PDU session ID and the first PDU session ID, and then the AMF determines the MB-SMF ID and the first PDU session ID according to the first PDU session ID and the first corresponding relationship.
  • the AMF selects the corresponding MB-SMF as the session management network element of the second PDU session according to the MB-SMF ID, and then the AMF carries the first multicast corresponding to the first PDU session in the session management context request message of S1110 Group ID.
  • the network side selects the MB-UPF to complete the second PDU session establishment process.
  • the MB-SMF after receiving the session management context request message sent by the AMF, the MB-SMF obtains the first multicast group identifier in the session management context request message, and determines according to the first multicast group identifier that the UE requests to join the first group. broadcast group. The MB-SMF finds the MB-UPF from the corresponding first multicast context according to the first multicast group identifier, and selects the MB-UPF as the PSA UPF of the second PDU session. The network side continues to complete the establishment of the second PDU session, and the specific manner is not limited.
  • the UE that is a member of the multicast group does not support receiving multicast data in a multicast manner, or the RAN where the UE is located does not support the multicast service
  • the PDU session establishment process By directly selecting the MB-UPF of the multicast group corresponding to the multicast group member UE as the PSA UPF of the new session of the UE, the transmission path of the multicast data from the MB-UPF to the multicast member UE is constructed, which can reduce the transmission rate.
  • the circuitous path reduces the transmission delay.
  • FIG. 12 is a schematic flowchart of a method 1200 provided by an embodiment of the present application.
  • the UE requests to join the first multicast group, the UE does not support receiving multicast data in a multicast manner, or the RAN where the UE is located does not support multicast services.
  • method 1200 includes:
  • a first multicast group configuration is completed between the network device and the UE.
  • the UE sends a first PDU session modification request message to the AMF, where the first PDU session modification request message includes a first multicast group identifier, where the first multicast group identifier is used to identify a first multicast group, and the first PDU session modification request message includes a first multicast group identifier.
  • the multicast group identifier may be, for example, a multicast address of the first multicast group, where the first multicast group identifier is used to instruct the UE to request to join the first multicast group.
  • the AMF sends a session management context update request message to the SMF, where the session management context update request message includes the first multicast group identifier.
  • the AF may also send the first multicast group identifier to the SMF.
  • the AF sends a first message to the SMF, where the first message includes the first multicast group identifier.
  • the first message may be, for example, a request message for the UE to join the first multicast group. It should be understood that the AF may directly send the first message to the SMF, or may forward the first message via the NEF.
  • the SMF checks the authorization of the UE to join the multicast group, and obtains the MB-SMF ID.
  • S1205 is similar to S1106 in the method 1100, and the description is not repeated here in this application.
  • the SMF sends a first message to the UE, where the first message includes the second information and the MB-SMF ID.
  • the SMF when the UE has the authorization to be the multicast source of the first multicast group, the SMF sends the second information and the MB-SMF ID to the UE through the first message, where the second information is used to instruct the UE to rebuild the PDU session .
  • the UE sends a second PDU session establishment request message to the AMF, where the second PDU session establishment request message includes the first multicast group identifier and the MB-SMFID.
  • the UE sends a second PDU session establishment request message to the AMF according to the second information, where the second PDU session establishment request message is used to request establishment of the second PDU session.
  • the second PDU session establishment request message includes the MB-SMF ID and the first multicast group identifier, where the first multicast group identifier is used to instruct the UE to request to join the first multicast group.
  • AMF selects MB-SMF.
  • the AMF sends a session management context request message to the MB-SMF.
  • the network side selects the MB-UPF to complete the second PDU session establishment process.
  • S1208-S1210 are similar to S609-S611 in the method 600, and for brevity, the description is not repeated here in this application.
  • the SMF sends the first correspondence between the MB-SMF ID, the first multicast group identifier and the first PDU session ID to the AMF.
  • the AMF receives the first correspondence from the SMF, and stores the first correspondence locally.
  • the second PDU session establishment request message sent by the UE to the AMF includes the second PDU session ID and the first PDU session ID.
  • the AMF receives the second PDU session establishment request message from the UE, and obtains the second PDU session ID and the first PDU session ID, and then the AMF determines the MB-SMF ID and the first PDU session ID according to the first PDU session ID and the first corresponding relationship.
  • the AMF selects the corresponding MB-SMF as the session management network element of the second PDU session according to the MB-SMF ID, and then the AMF carries the first multicast corresponding to the first PDU session in the session management context request message of S1209 Group ID.
  • the UE that is a member of the multicast group does not support receiving multicast data in a multicast manner, or the RAN where the UE is located does not support the multicast service
  • the PDU session establishment process By directly selecting the MB-UPF of the multicast group corresponding to the multicast group member UE as the PSA UPF of the new session of the UE, the transmission path of the multicast data from the MB-UPF to the multicast member UE is constructed, which can reduce the transmission path. roundabout, reducing the transmission delay.
  • FIG. 13 is a schematic diagram of a system architecture 1300 to which method 1100 and method 1200 are applied.
  • UE1, UE2, and UE3 are all members of a multicast group, wherein UE1 and UE2 support receiving multicast data in a multicast manner, and RAN1 where UE1 and UE2 are located also supports multicast services, while UE3 does not Support for receiving multicast data in multicast mode, or RAN 2 where UE 3 is located does not support multicast services.
  • the MB-UPF corresponding to the multicast group is selected as the PSA UPF of the newly created session of UE3.
  • the multicast data packet After the multicast data packet arrives at the MB-UPF, it does not need to forward the data to the PSAUPF.
  • the multicast data is sent to RAN2, which avoids the detour of the transmission path during multicast communication, and can reduce the transmission delay of multicast communication.
  • FIG. 14 is a schematic flowchart of a method 1400 provided by an embodiment of the present application.
  • the UE requests to join the first multicast group, the UE does not support receiving multicast data in a multicast manner, or the RAN where the UE is located does not support multicast services.
  • method 1400 includes:
  • a first multicast group configuration is completed between the network device and the UE.
  • the UE sends a first PDU session modification request message to the AMF, where the first PDU session modification request message includes a first multicast group identifier.
  • the first multicast group identifier is used to identify the first multicast group, and the first multicast group identifier may be, for example, the multicast address of the first multicast group, and the first multicast group identifier is used to instruct the UE to request to join the first multicast group.
  • the AMF sends a session management context update request message to the SMF, where the session management context update request message includes the first multicast group identifier.
  • the AF may also send the first multicast group identifier to the SMF.
  • the AF sends a first message to the SMF, where the first message includes the first multicast group identifier.
  • the first message may be, for example, a request message for the UE to join the first multicast group. It should be understood that the AF may directly send the first message to the SMF, or may forward the first message via the NEF.
  • the SMF acquires the information of the MB-UPF.
  • S1405 to S1407 are similar to S905 to S907 in the method 900, the only difference is that the SMF in S1405 and S1407 checks the authorization of the UE to join the multicast group. For brevity, the description is not repeated in this application.
  • the network side uses the MB-UPF as the additional PSA UPF of the first PDU session, inserts or selects an existing UPF on the user plane, and configures the UPF to have the function of UL CL or BP.
  • S1408 is similar to S908 in the method 900, and for the sake of brevity, the description will not be repeated in this application.
  • the UE that is a member of the multicast group does not support receiving multicast data in a multicast manner, or the RAN where the UE is located does not support the multicast service
  • the PDU session modification process Select the MB-UPF of the multicast group corresponding to the multicast group member UE as the additional PSA UPF of the first PDU session, and realize the offloading of multicast data to the UE through the inserted UPF or the selected UPF as the UL CL/BP.
  • the transmission path of the multicast data from the MB-UPF to the multicast member UE can reduce the detour of the transmission path and reduce the transmission delay.
  • FIG. 15 is a schematic diagram of a system architecture 1500 to which the method 1400 is applied.
  • UE1, UE2, and UE3 are all members of a multicast group.
  • UE1 and UE2 support receiving multicast data in a multicast manner
  • RAN1 where UE1 and UE2 are located also supports multicast services
  • UE3 does not Support for receiving multicast data in multicast mode
  • RAN 2 where UE 3 is located does not support multicast services.
  • UE3 sets the MB-UPF of the multicast group corresponding to UE3 as the additional PSA UPF of the PDU session.
  • the transmission path of multicast data from UE3 to MB-UPF is constructed. At this time, after the multicast data packets arrive at MB-UPF, there is no need to forward the data to the main PSAUPF, and then send the multicast data to RAN2 through the main PSAUPF to avoid It avoids the detour of the transmission path during multicast communication, and can reduce the transmission delay of multicast communication.
  • FIG. 16 is a schematic block diagram of a communication apparatus 10 provided by an embodiment of the present application.
  • the communication device 10 may include a transceiver module 11 and a processing module 12 .
  • the communication apparatus 10 may correspond to the terminal equipment or UE in the above method embodiments.
  • the communication apparatus 10 may correspond to a terminal device or UE in methods 500 to 700, 900, 1100 to 1200, and method 1400 according to the embodiments of the present application, and the communication apparatus 10 may include a device for executing Method 500 in FIG. 5 , method 600 in FIG. 6 , method 700 in FIG. 7 , method 900 in FIG. 9 , method 1100 in FIG. 11 , method 1200 in FIG. 12 , and method 1400 in FIG. 14 A module of a method performed by a terminal device or UE.
  • each unit in the communication device 10 and the above-mentioned other operations and/or functions are for implementing the corresponding processes of method 500 to method 700 , method 900 , method 1100 to method 1200 , and method 1400 respectively.
  • the transceiver module 11 in the communication device 10 performs the receiving and sending operations performed by the terminal device or the UE in the above method embodiments, and the processing module 12 performs operations other than the receiving and sending operations.
  • the communication device 10 may correspond to the session management network element or SMF in the above method embodiments.
  • the communication device 10 may correspond to the session management network element or SMF in the methods 500 to 700, 900, 1100 to 1200, and method 1400 according to the embodiments of the present application, and the communication device 10 may include a method 500 in FIG. 5 , method 600 in FIG. 6 , method 700 in FIG. 7 , method 900 in FIG. 9 , method 1100 in FIG. 11 , method 1200 in FIG. 12 and method 1400 in FIG.
  • the session management network element in the module or the module of the method performed by the SMF.
  • each unit in the communication device 10 and the above-mentioned other operations and/or functions are for implementing the corresponding processes of method 500 to method 700 , method 900 , method 1100 to method 1200 , and method 1400 respectively.
  • the transceiver module 11 in the communication device 10 performs the receiving and sending operations performed by the session management network element or the SMF in the above method embodiments, and the processing module 12 performs operations other than the receiving and sending operations.
  • the communication device 10 may correspond to the mobility management network element or AMF in the above method embodiments.
  • the communication device 10 may correspond to the mobility management network element or AMF in the methods 500 to 700, 900, 1100 to 1200, and method 1400 according to the embodiments of the present application, and the communication device 10 may include: method 500 in FIG. 5 , method 600 in FIG. 6 , method 700 in FIG. 7 , method 900 in FIG. 9 , method 1100 in FIG. 11 , method 1200 in FIG. 12 and method 1400 in FIG.
  • the module of the method performed by the mobility management network element in the AMF or the AMF.
  • each unit in the communication device 10 and the above-mentioned other operations and/or functions are for implementing the corresponding processes of method 500 to method 700 , method 900 , method 1100 to method 1200 , and method 1400 respectively.
  • the transceiver module 11 in the communication device 10 performs the receiving and sending operations performed by the mobility management network element or AMF in the above method embodiments, and the processing module 12 performs operations other than the receiving and sending operations.
  • FIG. 17 is a schematic diagram of a communication apparatus 20 provided by an embodiment of the present application.
  • the apparatus 20 may be a terminal device or a network device, and the network device may be, for example, a session management network element, It can also be a mobile management network element.
  • the apparatus 20 may include a processor 21 (ie, an example of a processing module) and a memory 22 .
  • the memory 22 is used for storing instructions
  • the processor 21 is used for executing the instructions stored in the memory 22, so that the device 20 can realize the corresponding functions as shown in FIGS. 5, 6, 7, 9, 11, 12, and 14.
  • the terminal equipment or the UE or the session management network element or the SMF or the mobility management network element or the AMF performs the steps.
  • the device 20 may further include an input port 23 (ie, an example of a transceiver module) and an output port 24 (ie, another example of a transceiver module).
  • the processor 21, the memory 22, the input port 23 and the output port 24 can communicate with each other through an internal connection path to transmit control and/or data signals.
  • the memory 22 is used to store a computer program, and the processor 21 can be used to call and run the computer program from the memory 22 to control the input port 23 to receive signals, control the output port 24 to send signals, and complete the network device in the above method. step.
  • the memory 22 may be integrated in the processor 21 or may be provided separately from the processor 21 .
  • the input port 23 is a receiver
  • the output port 24 is a transmitter.
  • the receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.
  • the input port 23 is an input interface
  • the output port 24 is an output interface
  • the functions of the input port 23 and the output port 24 can be considered to be implemented by a transceiver circuit or a dedicated chip for transceiver.
  • the processor 21 can be considered to be implemented by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.
  • a general-purpose computer may be used to implement the communication device provided by the embodiments of the present application.
  • the program codes that will implement the functions of the processor 21 , the input port 23 and the output port 24 are stored in the memory 22 , and the general-purpose processor implements the functions of the processor 21 , the input port 23 and the output port 24 by executing the codes in the memory 22 .
  • FIG. 18 is a schematic structural diagram of a terminal device 30 provided by this application. For convenience of explanation, FIG. 18 only shows the main components of the communication device. As shown in FIG. 18 , the terminal device 30 includes a processor, a memory, a control circuit, an antenna, and an input and output device.
  • the processor is mainly used to process communication protocols and communication data, and to control the entire terminal device, execute software programs, and process data of the software programs, for example, for supporting the terminal device to execute the above-mentioned transmission precoding matrix instruction method embodiment. the described action.
  • the memory is mainly used to store software programs and data, such as the codebook described in the above embodiments.
  • the control circuit is mainly used for the conversion of the baseband signal and the radio frequency signal and the processing of the radio frequency signal.
  • the control circuit together with the antenna can also be called a transceiver, which is mainly used to send and receive radio frequency signals in the form of electromagnetic waves.
  • Input and output devices such as touch screens, display screens, and keyboards, are mainly used to receive data input by users and output data to users.
  • the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program.
  • the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the radio frequency circuit.
  • the radio frequency circuit performs radio frequency processing on the baseband signal and sends the radio frequency signal through the antenna in the form of electromagnetic waves.
  • the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, which converts the baseband signal into data and processes the data.
  • FIG. 18 only shows one memory and a processor. In an actual terminal device, there may be multiple processors and memories.
  • the memory may also be referred to as a storage medium or a storage device, etc., which is not limited in this embodiment of the present application.
  • the processor may include a baseband processor and a central processing unit.
  • the baseband processor is mainly used to process communication protocols and communication data
  • the central processing unit is mainly used to control the entire terminal device, execute A software program that processes data from the software program.
  • the processor in FIG. 18 integrates the functions of the baseband processor and the central processing unit.
  • the baseband processor and the central processing unit may also be independent processors, interconnected by technologies such as a bus.
  • a terminal device may include multiple baseband processors to adapt to different network standards, a terminal device may include multiple central processors to enhance its processing capability, and various components of the terminal device may be connected through various buses.
  • the baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip.
  • the central processing unit can also be expressed as a central processing circuit or a central processing chip.
  • the function of processing the communication protocol and communication data may be built in the processor, or may be stored in the storage unit in the form of a software program, and the processor executes the software program to realize the baseband processing function.
  • the terminal device 30 includes a transceiver unit 31 and a processing unit 32 .
  • the transceiving unit may also be referred to as a transceiver, a transceiver, a transceiving device, or the like.
  • the device for implementing the receiving function in the transceiver unit 31 may be regarded as a receiving unit
  • the device for implementing the transmitting function in the transceiver unit 31 may be regarded as a transmitting unit, that is, the transceiver unit 31 includes a receiving unit and a transmitting unit.
  • the receiving unit may also be referred to as a receiver, a receiver, a receiving circuit, and the like
  • the transmitting unit may be referred to as a transmitter, a transmitter, or a transmitting circuit, or the like.
  • the terminal device shown in FIG. 18 can perform the actions performed by the terminal device or UE in the above-mentioned methods 500 to 700, method 900, method 1100 to method 1200, and method 1400.
  • the detailed description thereof is omitted.
  • FIG. 19 shows a schematic structural diagram of a simplified network device 40 .
  • the network equipment includes 41 parts and 42 parts.
  • Part 41 is mainly used for transceiver of radio frequency signal and conversion of radio frequency signal and baseband signal; part 42 is mainly used for baseband processing, control of network equipment, etc.
  • Part 41 can usually be referred to as a transceiver module, a transceiver, a transceiver circuit, or a transceiver.
  • Part 42 is usually the control center of the network device, which can usually be called a processing module, and is used to control the network device to perform the processing operations on the network device side in the foregoing method embodiments.
  • the transceiver module of part 41 which can also be called a transceiver or a transceiver, etc., includes an antenna and a radio frequency circuit, wherein the radio frequency circuit is mainly used for radio frequency processing.
  • the device used to implement the receiving function in part 41 can be regarded as a receiving module
  • the device used to implement the transmitting function can be regarded as a transmitting module, that is, part 41 includes a receiving module and a transmitting module.
  • the receiving module may also be called a receiver, a receiver, or a receiving circuit, and the like
  • the sending module may be called a transmitter, a transmitter, or a transmitting circuit, and the like.
  • Section 42 may include one or more single boards, each of which may include one or more processors and one or more memories.
  • the processor is used to read and execute programs in the memory to implement baseband processing functions and control network devices. If there are multiple boards, each board can be interconnected to enhance the processing capability.
  • one or more processors may be shared by multiple boards, or one or more memories may be shared by multiple boards, or one or more processors may be shared by multiple boards at the same time. device.
  • the network device shown in FIG. 19 may be any network device shown in FIG. 5 , FIG. 6 , FIG. 7 , FIG. 9 , FIG. 11 , FIG. 12 , and FIG. 14 , such as a session management network element, mobility management network element, SMF, AMF, etc.
  • the transceiver module of part 41 is used to execute the method 500 in FIG. 5 , the method 600 in FIG. 6 , the method 700 in FIG. 7 , the method 900 in FIG. 9 , the method 1100 in FIG. 11 , the method 1200 in FIG. 12 and Steps related to sending and receiving of any network device in the method 1400 in FIG. 14 ; part 42 is used to execute the method 500 in FIG. 5 , the method 600 in FIG. 6 , the method 700 in FIG. 7 , the method 900 in FIG. Steps related to the processing of any network device in the method 1100 in FIG. 11 , the method 1200 in FIG. 12 , and the method 1400 in FIG. 14 .
  • FIG. 19 is only an example and not a limitation, and the above-mentioned network device including a transceiver module and a processing module may not depend on the structure shown in FIG. 19 .
  • the chip When the device 40 is a chip, the chip includes a transceiver module and a processing module.
  • the transceiver module may be an input/output circuit or a communication interface;
  • the processing module is a processor, a microprocessor or an integrated circuit integrated on the chip.
  • Embodiments of the present application further provide a computer-readable storage medium, on which computer instructions for implementing the method executed by the first network device in the foregoing method embodiments are stored.
  • the computer program when executed by a computer, the computer can implement the method executed by the network device in the above method embodiments.
  • Embodiments of the present application further provide a computer program product including instructions, which, when executed by a computer, cause the computer to implement the method executed by the first device or the method executed by the second device in the above method embodiments.
  • An embodiment of the present application further provides a communication system, where the communication system includes the network device in the above embodiment.
  • the network device may include a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory).
  • the operating system of the operating system layer may be any one or more computer operating systems that implement business processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system.
  • the application layer may include applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiments of the present application do not specifically limit the specific structure of the execution body of the methods provided by the embodiments of the present application, as long as the program in which the codes of the methods provided by the embodiments of the present application are recorded can be executed to execute the methods according to the embodiments of the present application.
  • the execution body of the method provided by the embodiment of the present application may be a network device, or a functional module in the network device that can call a program and execute the program.
  • Computer readable media may include, but are not limited to, magnetic storage devices (eg, hard disks, floppy disks, or magnetic tapes, etc.), optical disks (eg, compact discs (CDs), digital versatile discs (DVDs), etc. ), smart cards and flash memory devices (eg, erasable programmable read-only memory (EPROM), cards, stick or key drives, etc.).
  • magnetic storage devices eg, hard disks, floppy disks, or magnetic tapes, etc.
  • optical disks eg, compact discs (CDs), digital versatile discs (DVDs), etc.
  • smart cards and flash memory devices eg, erasable programmable read-only memory (EPROM), cards, stick or key drives, etc.
  • Various storage media described herein may represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.
  • processors mentioned in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), application-specific integrated circuits ( application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory mentioned in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM).
  • RAM can be used as an external cache.
  • RAM may include the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM) , double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) and Direct memory bus random access memory (direct rambus RAM, DR RAM).
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • Direct memory bus random access memory direct rambus RAM, DR RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components
  • the memory storage module
  • memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.
  • the disclosed apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, which may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to implement the solution provided in this application.
  • each functional unit in each embodiment of the present application may be integrated into one unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the computer may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can 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 may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer may be a personal computer, a server, or a network device or the like.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center is by wire (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), etc.
  • the medium may include, but is not limited to: U disk, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供了一种通信方法和通信装置，该通信方法包括：接收第一请求信息和第一组播组的标识，该第一请求信息用于请求终端设备成为第一组播组的组播源，或者该第一请求信息用于请求该终端设备加入该第一组播组；向数据管理网元发送第二请求信息和该第一组播组的标识，该第二请求信息用于请求获取第一会话管理网元的标识，该第一会话管理网元用于进行组播会话管理，该第一会话管理网元与该第一组播组的标识相关联；接收来自该数据管理网元的该第一会话管理网元的标识。本申请实施例的通信方法，可以构建UE直接到第一用户面功能网元的组播数据传输路径，从而减少传输路径的迂回，降低组播通信的传输时延。

Description

通信方法和通信装置
本申请要求于2021年04月09日提交中国专利局、申请号为202110387335.3、申请名称为“通信方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更加具体地，涉及一种通信方法和通信装置。
背景技术
在计算机网络或者通信领域，主机之间可以采用一对一组的组播模式进行通信。组播是一种群组通信，组播源可以一次将数据传输给多个有需要(加入组)的设备，又能保证不影响其他不需要(未加入组)的设备的通信。
然而，在一些场景中，组播数据需要经过一些网元进行转发，从而造成组播的传输路径比较迂回，跳数比较多，因此可能导致组播通信过程的传输时延比较大。因此希望提供一种技术，可以解决组播通信过程因为路径迂回导致的传输时延较大的问题。
发明内容
本申请实施例的通信方法和通信装置，可以减少组播通信过程的传输时延。
第一方面，提供了一种通信方法，该方法可以由会话管理网元执行，或者，也可以由配置于会话管理网元中的芯片或芯片系统或电路执行，该方法包括：接收第一请求信息和第一组播组的标识，该第一请求信息用于请求终端设备成为第一组播组的组播源，或者该第一请求信息用于请求该终端设备加入该第一组播组；向数据管理网元发送第二请求信息和该第一组播组的标识，该第二请求信息用于请求获取第一会话管理网元的标识，该第一会话管理网元用于进行组播会话管理，该第一会话管理网元与该第一组播组的标识相关联；接收来自该数据管理网元的该第一会话管理网元的标识。
因此本申请实施例的通信方法，通过查询用于进行组播会话管理的第一会话管理网元，使得UE在建立会话的时候可以构建UE直接到第一用户面功能网元的组播数据传输路径，可以减少传输路径的迂回，降低传输时延。
可选地，第一组播组的标识可以是第一组播组的组播地址。
作为一个示例，终端设备向移动管理网元发送第二会话建立请求消息，该第二会话建立请求消息用于请求建立终端设备与数据网络之间的第二会话，该第二会话建立请求消息中包括第一请求信息和第一组播组的标识。移动管理网元选择第二会话管理网元，并向第二会话管理网元发送会话管理上下文请求消息，该会话管理上下文请求消息中包括该第一请求信息和第一组播组的标识。
作为又一个示例，终端设备向移动管理网元发送第二会话修改请求消息，该第二会话 修改请求消息用于请求修改第二会话的参数，该第二会话修改请求消息中包括第一请求信息和第一组播组的标识。移动管理网元向第二会话管理网元发送会话管理上下文更新请求消息，该会话管理上下文更新请求消息中包括该第一请求信息和第一组播组的标识。
在另一种可能的实现方案中，第二会话管理网元还可以从应用功能网元接收该第一请求信息和该第一组播组标识。
应理解，第一请求信息和第一组播组标识可以承载于同一个消息中，也可以承载于两个连续发送的消息中，本申请对此不作限定。
示例性地，根据第一请求信息，第二会话管理网元确定终端设备请求成为第一组播组的组播源，或者，第二请求信息用于请求终端设备加入第一组播组。
作为一个示例，当终端设备请求成为第一组播组的组播源，且该终端设备作为组播源发送的组播数据无需应用服务器进行解析处理时，第二会话管理网元向数据管理网元发送第二请求信息和第一组播组的标识，该第二请求信息用于请求获取第一会话管理网元的标识，该第一会话管理网元用于进行组播会话管理，且该第一会话管理网元与第一组播组的标识相关联。
可选地，在第二会话管理网元向数据管理网元发送第二请求信息和第一组播组的标识之前，第二会话管理网元向数据管理网元发送第三请求信息，该第三请求信息用于请求验证终端设备成为第一组播组的组播源的授权。对应地，数据管理网元接收到第三请求信息之后，验证终端设备是否具备成为第一组播组的组播源的授权。在终端设备具备成为第一组播组的组播源的授权的情形下，第二会话管理网元才继续执行后续流程，否则第二会话管理网元向终端设备发送一个响应信息，该响应信息用于拒绝第一请求信息，或者用于指示终端设备成为第一组播组的组播源失败，或者第二会话管理网元忽略第一请求信息，具体方式本申请不作限定。
作为又一个示例，当终端设备请求加入第一组播组，且该终端设备不支持以组播方式接受组播数据，或者该终端设备所在的无线接入网设备不支持组播服务时，第二会话管理网元向数据管理网元发送第二请求信息和第一组播组的标识。
可选地，在第二会话管理网元向数据管理网元发送第二请求信息和第一组播组的标识之前，第二会话管理网元向数据管理网元发送第三请求信息，该第三请求信息用于请求验证终端设备加入第一组播组的授权。对应地，数据管理网元接收到第三请求信息之后，验证终端设备是否具备加入第一组播组的授权。在终端设备具备加入第一组播组的授权的情形下，第二会话管理网元才继续执行后续流程。
应理解，第二请求信息和第一组播组标识可以承载于同一个消息中，也可以承载于两个连续发送的消息中，本申请对此不作限定。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：向移动管理网元发送该第一会话管理网元的标识。
结合第一方面，在第一方面的某些实现方式中，在该向数据管理网元发送第二请求信息和该第一组播组标识之前，该方法还包括：向该数据管理网元发送第三请求信息，在该第一请求信息用于请求该终端设备成为该第一组播组的组播源的情形下，该第三请求信息用于请求验证该终端设备作为该第一组播组的组播源的授权，在该第一请求信息用于请求该终端设备加入该第一组播组的情形下，该第三请求信息用于请求验证该终端设备加入该 第一组播组的授权。
因此，本申请实施例的通信方法中，数据管理网元能够事先存储终端设备作为第一组播组的组播源的授权信息或者终端设备加入第一组播组的授权信息，在终端设备请求获取第一会话管理网元的标识之前首先验证该终端设备的授权情况，可以避免后续流程因为终端设备未授权而失败的情况，保障通信的可靠性。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：向该终端设备发送第一指示信息和该第一会话管理网元的标识，该第一会话管理网元用于进行组播会话管理，该第一指示信息用于指示该终端设备建立该第一会话。
因此，本申请实施例的通信方法，通过向终端设备发送第一会话管理网元的标识，并同时指示终端设备建立第一会话，可以让终端设备通过第一会话管理网元建立一个会话，使得终端设备可以构建和第一用户面功能网元之间的组播数据传输路径，可以减少传输路径的迂回，降低传输时延。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：获取第一用户面功能网元的信息，该第一用户面功能网元用于进行组播数据的转发处理，该第一用户面功能网元与该第一组播组标识相关联。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：根据该第一用户面功能网元的信息构建该第一用户面功能网元和该终端设备之间的数据传输路径。
该第一用户面功能网元的信息例如是第一用户面功能网元的地址信息或是第一用户面功能网元的数据网络访问标识(data network access identifier，DNAI)。
因此，本申请实施例提供的通信方法，会话管理网元在获取到第一用户面功能网元的信息之后，构建所述第一用户面功能网元和所述终端设备之间的数据传输路径，因此组播数据可以直接从终端设备传输到第一用户面功能网元，或者直接从第一用户面功能网元直接传输到终端设备，从而可以减少组播数据传输路径的迂回，降低传输时延。
结合第一方面，在第一方面的某些实现方式中，该获取第一用户面功能网元的信息，包括：向该数据管理网元发送第四请求信息和该第一组播组的标识，该第四请求信息用于请求获取该第一用户面功能网元的信息；接收来自该数据管理网元的该第一用户面功能网元的信息；或者，向该第一会话管理网元发送该第四请求信息和该第一组播组的标识；接收来自该第一会话管理网元的该第一用户面功能网元的信息。
进一步地，会话管理网元接收到第一用户面功能网元的信息之后，将该第一用户面功能网元作为第一会话的额外会话锚点会话管理网元，并根据第一用户面功能网元的信息在用户面插入第二用户面功能网元，或者选择已经存在的第二用户面功能网元，通过N4会话进行相应的配置，使得第二用户面功能网元具备UL CL或BP的功能。
因此，本申请实施例的通信方法，选取第一组播组标识对应的第一用户面功能网元作为额外会话锚点用户面功能网元，
通过插入的第二用户面功能网元或选择的第二用户面功能网元作为UL CL/BP实现终端设备的组播数据到第一用户面功能网元的分流，构建了组播源终端设备到第一用户面功能网元的组播数据的传输路径，可以减少传输路径的迂回，降低传输时延。
结合第一方面，在第一方面的某些实现方式中，该接收第一请求信息和第一组播组的标识，包括：接收来自该终端设备的该第一请求信息和该第一组播组的标识；或者，接收 来自应用功能网元的该第一请求信息和该第一组播组的标识。
第二方面，提供了一种通信方法，该方法可以由移动管理网元执行，或者，也可以由配置于移动管理网元中的芯片或芯片系统或电路执行，该方法包括：接收来自终端设备的第一会话建立请求消息，该第一会话建立请求消息用于请求建立该终端设备与数据网络之间的第一会话，该第一会话建立请求消息包括第一会话管理网元的标识，该第一会话管理网元用于进行组播会话管理；向该第一会话管理网元发送第一请求信息和第一组播组的标识，该第一请求信息用于请求终端设备成为该第一组播组的组播源，或者该第一请求信息用于请求该终端设备加入该第一组播组。
因此本申请实施例的通信方法，通过选择用于进行组播会话管理的第一会话管理网元建立会话，可以构建UE直接到第一用户面功能网元的组播数据传输路径，可以减少传输路径的迂回，降低传输时延。
结合第二方面，在第二方面的某些实现方式中，在该接收来自终端设备的第一会话建立请求消息之前，该方法还包括：接收来自该终端设备的该第一请求信息和该第一组播组的标识；向第二会话管理网元发送该第一请求信息和该第一组播组的标识。
结合第二方面，在第二方面的某些实现方式中，该接收来自该终端设备的该第一请求信息和该第一组播组的标识，包括：接收来自该终端设备的第二会话建立请求消息，该第二会话建立请求消息包括该第一请求信息和该第一组播组的标识；或者接收来自该终端设备的第二会话修改请求消息，该第二会话修改请求消息包括该第一请求信息和该第一组播组的标识。
第三方面，提供了一种通信方法，该方法可以由终端设备执行，也可以由配置于终端设备中的部件(例如芯片或电路)执行，该方法包括：接收来自第二会话管理网元的第一指示信息和第一会话管理网元的标识，该第一会话管理网元用于进行组播会话管理，该第一指示信息用于指示该终端设备建立第一会话；向移动管理网元发送第一会话建立请求消息，该第一会话建立请求消息用于请求建立该终端设备与数据网络之间的该第一会话，该第一会话建立请求消息包括第一会话管理网元的标识，该第一会话管理网元用于进行组播会话管理。
因此本申请实施例的通信方法，可以构建UE直接到第一用户面功能网元的组播数据传输路径，可以减少传输路径的迂回，降低传输时延。
结合第三方面，在第三方面的某些实现方式中，在该向移动管理网元发送会话建立请求消息之前，该方法还包括：向移动管理网元发送第一请求信息和第一组播组标识，该第一请求消息用于请求终端设备成为第一组播组的组播源，或者该第一请求信息用于请求该终端设备加入该第一组播组。
结合第三方面，在第三方面的某些实现方式中，该向移动管理网元发送第一请求信息和第一组播组标识，包括：向该移动管理网元发送第二会话建立请求消息，该第二会话建立请求消息包括该第一请求信息和该第一组播组的标识；或者，向该移动管理网元发送第二会话修改请求消息，该第二会话修改请求消息包括该第一请求信息和该第一组播组的标识。
第四方面，提供了一种通信装置，该装置包括：收发模块，用于接收第一请求信息和第一组播组的标识，该第一请求信息用于请求终端设备成为第一组播组的组播源，或者该 第一请求信息用于请求该终端设备加入该第一组播组；该收发模块还用于向数据管理网元发送第二请求信息和该第一组播组的标识，该第二请求信息用于请求获取第一会话管理网元的标识，该第一会话管理网元用于进行组播会话管理，该第一会话管理网元与该第一组播组的标识相关联；该收发模块还用于接收来自该数据管理网元的该第一会话管理网元的标识。
该收发模块可以执行前述第一方面中的接收和发送的处理；该通信装置还可能包括处理模块，该处理模块可以执行前述第一方面中除了接收和发送之外的其他处理。
第五方面，提供了一种通信装置，该装置包括：收发模块，用于接收来自终端设备的第一会话建立请求消息，该第一会话建立请求消息用于请求建立该终端设备与数据网络之间的第一会话，该第一会话建立请求消息包括第一会话管理网元的标识，该第一会话管理网元用于进行组播会话管理；该收发模块还用于向该第一会话管理网元发送第一请求信息和第一组播组的标识，该第一请求信息用于请求终端设备成为该第一组播组的组播源，或者该第一请求信息用于请求该终端设备加入该第一组播组。
该收发模块可以执行前述第二方面中的接收和发送的处理；该通信装置还可能包括处理模块，该处理模块可以执行前述第二方面中除了接收和发送之外的其他处理。
第六方面，提供了一种通信装置，该装置包括：收发模块，用于接收来自第二会话管理网元的第一指示信息和第一会话管理网元的标识，该第一会话管理网元用于进行组播会话管理，该第一指示信息用于指示该终端设备建立第一会话；该收发模块还用于向移动管理网元发送第一会话建立请求消息，该第一会话建立请求消息用于请求建立该终端设备与数据网络之间的该第一会话，该第一会话建立请求消息包括第一会话管理网元的标识，该第一会话管理网元用于进行组播会话管理。
该收发模块可以执行前述第三方面中的接收和发送的处理；该通信装置还可能包括处理模块，该处理模块可以执行前述第三方面中除了接收和发送之外的其他处理。
第七方面，提供了一种通信装置，该装置包括：处理器，用于执行存储器中存储的计算机程序，以使得该通信装置执行第一方面或第二方面中的任一种可能的实现方式。
第八方面，提供了一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序，当该计算机程序在计算机上运行时，使得该计算机执行第一方面至第三方面中的任一种可能的实现方式。
第九方面，提供了一种计算机程序产品，该计算机程序产品包括计算机程序指令，该计算机程序指令在计算机上运行时，使得计算机执行第一方面至第三方面中的任一种可能实现的方式。
第十方面，提供了一种芯片系统，该芯片系统包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片系统地通信设备执行第一方面至第三方面中的任一种可能的实现方式。
附图说明
图1是一种适用于本申请实施例提供的方法的网络架构的示意图。
图2是另一种适用于本申请实施例提供的方法的网络架构的示意图。
图3是一种用于组播通信的系统架构示意图。
图4是另一种用于组播通信的系统架构示意图。
图5是本申请一个实施例提供的一种通信方法的示意性流程图。
图6是本申请另一个实施例提供的一种通信方法的示意性流程图。
图7是本申请又一个实施例提供的一种通信方法的示意性流程图。
图8是本申请实施例提供的一种用于组播通信的系统架构示意图。
图9是本申请又一个实施例提供的一种通信方法的示意性流程图。
图10是本申请实施例提供的另一种用于组播通信的系统架构示意图。
图11是本申请又一个实施例提供的一种通信方法的示意性流程图。
图12是本申请又一个实施例提供的一种通信方法的示意性流程图。
图13是本申请实施例提供的又一种用于组播通信的系统架构示意图。
图14是本申请又一个实施例提供的一种通信方法的示意性流程图。
图15是本申请实施例提供的又一种用于组播通信的系统架构示意图。
图16是本申请一个实施例提供的通信装置的示意性框图。
图17是本申请另一个实施例提供的通信装置的示意性框图。
图18是本申请又一个实施例提供的通信装置的示意性框图。
图19是本申请又一个实施例提供的通信装置的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请提供的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、第五代(5th generation，5G)系统或新无线(new radio，NR)等。
不同的网络系统中，网元命名可能有所不同。下文以5G网络中对网元的命名为例，来对本申请进行说明。
图1和图2是适用于本申请实施例提供的方法的网络架构的示意图。其中，图1是基于服务化接口的5G网络架构示意图，图2是基于点对点接口的5G网络架构图。下面首先结合图1和图2所示的5G网络架构示意图，对5G网络系统中涉及的主要网元进行简要说明。
1、用户设备(user equipment，UE)：可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的终端，移动台(mobile station，MS)，终端(terminal)，软终端等等。例如，水表、电表、传感器等。
2、无线接入网络(radio access network，RAN)网元：在下文中简称为RAN，对应接入网设备。
用于为特定区域的授权用户设备提供入网功能，并能够根据用户设备的级别，业务的需求等使用不同质量的传输隧道。
RAN网元能够管理无线资源，为用户设备提供接入服务，进而完成控制信号和用户 设备数据在用户设备和核心网之间的转发，RAN网元也可以理解为传统网络中的基站。举例来说，RAN可以是NB，eNB，gNB，ng-eNB，或者其他任何接入网设备。
3、用户面功能(user plane function，UPF)：用于分组路由和转发以及用户面数据的服务质量(quality of service，QoS)处理等。
在5G通信系统中，该用户面网元可以是用户面功能(user plane function，UPF)网元。在未来通信系统中，用户面网元仍可以是UPF网元，或者，还可以有其它的名称，本申请不做限定。
4、数据网络(data network，DN)：用于提供传输数据的网络。
在5G通信系统中，该数据网络网元可以是数据网络网元。在未来通信系统中，数据网络网元仍可以是DN网元，或者，还可以有其它的名称，本申请不做限定。
5、AMF：主要用于移动性管理和接入管理等，可以用于实现MME功能中除会话管理之外的其它功能，例如，合法监听以及接入授权/鉴权等功能。
在5G通信系统中，该接入和移动管理网元可以是接入和移动管理功能(access and mobility management function，AMF)。在未来通信系统中，接入和移动管理设备仍可以是AMF，或者，还可以有其它的名称，本申请不做限定。
6、会话管理功能(session management function，SMF)：主要用于会话管理、用户设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信系统中，该会话管理网元可以是会话管理功能网元。在未来通信系统中，会话管理网元仍可以是SMF网元，或者，还可以有其它的名称，本申请不做限定。
7、策略控制功能(policy control function，PCF)：用于指导网络行为的统一策略框架，为控制面功能网元(例如AMF，SMF等)提供策略规则信息等。
在4G通信系统中，该策略控制网元可以是策略和计费规则功能(policy and charging rules function，PCRF)网元。在5G通信系统中，该策略控制网元可以是策略控制功能PCF网元。在未来通信系统中，策略控制网元仍可以是PCF网元，或者，还可以有其它的名称，本申请不做限定。
8、应用功能(application function，AF)：用于进行应用影响的数据路由，无线接入网络开放功能网元，与策略框架交互进行策略控制等。
在5G通信系统中，该应用网元可以是应用功能网元。在未来通信系统中，应用网元仍可以是AF网元，或者，还可以有其它的名称，本申请不做限定。
9、统一数据管理(unified data management，UDM)：用于处理UE标识，接入鉴权，注册以及移动性管理等。
在5G通信系统中，该数据管理网元可以是统一数据管理网元；在4G通信系统中，该数据管理网元可以是归属用户服务器(home subscriber server，HSS)网元在未来通信系统中，统一数据管理仍可以是UDM网元，或者，还可以有其它的名称，本申请不做限定。
10、统一数据存储(unified data repository，UDR)：主要包括以下功能：签约数据、策略数据、应用数据等类型数据的存取功能。
11、认证服务器(authentication server function，AUSF)：用于鉴权服务、产生密钥实现对用户设备的双向鉴权，支持统一的鉴权框架。
在5G通信系统中，该认证服务器可以是认证服务器功能网元。在未来通信系统中，认证服务器功能网元仍可以是AUSF网元，或者，还可以有其它的名称，本申请不做限定。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。为方便说明，本申请后续，以网络设备为接入和移动管理网元AMF，基站为无线接入网络RAN为例进行说明。
在图2所示的网络架构中，用户设备通过N1接口与AMF连接，RAN通过N2接口与AMF连接，RAN通过N3接口与UPF连接。UPF之间通过N9接口连接，UPF通过N6接口DN互联。SMF通过N4接口控制UPF。AMF通过N11接口与SMF接口。AMF通过N8接口从UDM单元获取用户设备签约数据，SMF通过N10接口从UDM单元获取用户设备签约数据。
应理解，上述应用于本申请实施例的网络架构仅是一种举例说明，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
例如，在某些网络架构中，AMF、SMF网元、PCF网元、BSF网元以及UDM网元等网络功能网元实体都称为网络功能(network function，NF)网元；或者，在另一些网络架构中，AMF，SMF网元，PCF网元，BSF网元，UDM网元等网元的集合都可以称为控制面功能网元。
为易于理解本申请的实施例，首先对本申请所涉及的一些概念或者术语作简要说明。
1、单播
主机之间一对一的通信模式，网络中的交换机和路由器对数据只进行转发不进行复制。如果10个客户机需要相同的数据，则服务器需要逐一传送，重复10次相同的工作。但由于其能够针对每个客户的要求进行及时响应，所以现在的网页浏览全部都是采用单播模式，即IP单播协议。网络中的路由器和交换机根据其目标地址选择传输路径，将IP单播数据传送到其指定的目的地。单播IP地址即为单个主机的IP地址。
2、组播
主机之间一对一组的通信模式，也就是加入了同一个组的主机可以接受到此组内的所有数据，网络中的交换机和路由器只向有需求者复制并转发其所需数据。主机可以向路由器请求加入或退出某个组，网络中的路由器和交换机有选择的复制并传输数据，即只将组内数据传输给那些加入组的主机。这样既能一次将数据传输给多个有需要(加入组)的主机，又能保证不影响其他不需要(未加入组)的主机的其他通讯。组播IP地址是D类IP地址，范围是：224.0.0.0～239.255.255.255。
组播组是一个用IP组播地址进行标识的接收者集合。
主机通过加入某组播组成为该组播组的成员，从而接收发往该组播组的组播数据。组播组中的成员是动态的，主机可以在任何时候接入或离开组播组。组播组成员可以广泛分布在网络中的任何地方。
向组播组发送信息的主机为组播源。组播源通常不需要加入组播组，一个组播源可以同时向多个组播组发送信息，多个组播源也可以同时向一个组播组发送信息。
3、广播
主机之间一对所有的通讯模式，网络对其中每一台主机发出的信号都进行无条件复制并转发，所有主机都可以接收到所有信息(不管你是否需要)，由于其不用路径选择，所以其网络成本可以很低廉。有线电视网就是典型的广播型网络，我们的电视机实际上是接受到所有频道的信号，但只将一个频道的信号还原成画面。在数据网络中也允许广播的存在，但其通常被限制在二层交换机的局域网范围内，禁止广播数据穿过路由器，防止广播数据影响大面积的主机。有四种广播IP地址，受限的广播地址，即255.255.255.255；指向网络的广播地址，即主机号为全1的地址；指向子网的广播地址，即主机号为全1且有特定子网号的地址；指向所有子网的广播，需了解目的网络的子网掩码，且子网号及主机号全为1。
4、协议数据单元(protocol data unit，PDU)会话(PDU session)
5G核心网(5G corenet，5GC)支持PDU连接业务。PDU连接业务可以是指终端设备与DN之间交换PDU数据包的业务。PDU连接业务通过终端设备发起PDU会话的建立来实现。一个PDU会话建立后，也就是建立了一条终端设备和DN的数据传输通道。换句话说，PDU会话是UE级别的。每个终端设备可以建立一个或多个PDU会话。终端设备可以通过终端设备到DN之间建立的PDU会话，来访问DN。
如前所述，SMF主要用户负责移动网络中的会话管理。PDU会话在终端设备和SMF之间可以通过NAS会话管理(session management，SM)信令进行建立、修改或释放。
在本申请实施例中，终端设备可以建立多个PDU会话或者说多个PDU连接业务，如终端设备可以建立两个或两个以上的PDU会话，关于该多个PDU会话，不作限定。例如，这些PDU会话的DN标识(data network name，DNN)可以不同，也可以相同。又如，不同的PDU会话可以由相同的SMF服务，也可以由不同的SMF服务。又如，这些PDU会话的建立可以同时发起或先后发起。
5、任意源组播(any-source multicast，ASM)
在ASM模型中，任何发送者都可以成为组播源，向组播地址发送信息。接收者可以在任意时间加入或者离开该组播组，但无法预先知道组播源的地址。
6、指定源组播(source-specific multicast，SSM)
在SSM模型中，接收者能够预先知道组播源的地址，可以在客户端指定信源。SSM使用和ASM不同的组播地址范围，直接在接收者和其指定的组播源之间建立专用的组播转发路径。
7、组播/广播会话管理功能(multicast/broadcast-session management function，MB-SMF)
MB-SMF主要负责组播广播会话管理，控制组播广播传输，根据PCF提供或本地配置的组播广播服务是策略规则对MB-UPF和RAN进行相应的配置，以完成组播广播流的传输。
8、组播/广播用户面功能(multicast/broadcast-user plane function，MB-UPF)
MB-UPF主要负责将组播广播流传送到RAN(或者UPF)，可以进行组播广播流的包过滤、分发，实现组播广播服务的QoS增强以及计数/上报等。
9、上行分类器(uplink classifier，ULCL)/分支点(branching point，BP)
ULCL和BP均是UPF的功能，UL CL的作用是数据流的上行分类器，即基于业务流上行特征的识别，分流数据到本地DN或远端协议数据单元会话锚点(PDU session anchor， PSA)UPF。同时，UL CL对下行流进行聚合处理。BP与UL CL的作用是一样的，只是BP是针对互联网协议第六版(internet protocol version6，IPv6)的分流点，UL CL是针对互联网协议第四版(internet protocol version4，IPv4)的上行分类器。
为了便于理解本申请实施例提供的通信方法，下面结合图3至图4简单介绍5G网络中组播通信的两种方案。
在图3所示的方案中，UE1、UE2、UE3为组播组成员，UE4为该组播组的组播源，应用服务器(application server，AS)是数据处理和转发的锚点，即UE发送组播数据的上行链路必须到达AS，AS对数据进行处理(例如对数据进行解析，或者仅仅是转发)，然后AS进行下行组播数据的发送。从图3中可以看出，UE 4作为组播源向组播组发送组播数据，经单播PSA UPF将组播数据发送到AS，AS对组播数据进行数据处理，转发给MB-UPF，MB-UPF通过N3组播隧道将组播数据发送到RAN，RAN进一步向组播成员UE 1、UE 2和UE 3发送组播数据。
但是，当UE4发送的组播数据无需AS进行解析处理，即AS仅需要对组播数据进行转发的话，通过图3所示的传输路径进行组播通信存在路径迂回、跳数多的情况，从而导致传输时延的增加。
在图4所示的方案中，UE1、UE2、UE3为组播组成员，当UE 1和UE 2支持以组播方式接收组播数据，UE1和UE2所在的RAN1也支持组播服务，但UE3不支持以组播方式接收组播数据，或者UE 3所在的RAN 2不支持组播服务时，需要通过单播的方式将组播数据发送给UE3。此时MB-UPF收到组播数据(可以是UE发送的，也可以是AS发送的)后，通过共享组播隧道将组播数据转发到RAN 1，RAN 1通过点到多点(point-to-multipoint，PTM)或点到点(point-to-point，PTP)方式将组播数据发送到UE 1和UE 2；通过转发隧道将组播数据转发到UE 3的单播会话的PSA UPF，PSA UPF通过单播方式将组播数据发送到RAN 2，RAN 2通过PTP方式将组播数据发送给UE 3。
但是，针对MB-UPF向组播成员转发组播包的路径，当MB-UPF与RAN 2之间能够直连，或者PSA UPF相比于MB-UPF距离RAN 2的位置较高时，MB-UPF到PSA UPF再到RAN 2的转发路径迂回，或者跳数多，从而导致传输时延的增加。
根据图3和图4所示的方案，如何解决组播通信过程因为路径迂回导致的传输时延大的弊端，是我们需要考虑的问题。
图5是本申请实施例提供的方法500的示意性流程图。从图5中可以看出，该方法500包括：
S510，第二会话管理网元接收来自终端设备的第一请求信息和第一组播组的标识。
示例性地，该第一请求信息用于请求该终端设备成为第一组播组的组播源，或者，该第一请求信息用于请求该终端设备加入第一组播组。该第一组播组的标识例如可以是第一组播组的组播地址。
作为一个示例，终端设备向移动管理网元发送第二会话建立请求消息，该第二会话建立请求消息用于请求建立终端设备与数据网络之间的第二会话，该第二会话建立请求消息中包括第一请求信息和第一组播组的标识。移动管理网元选择第二会话管理网元，并向第二会话管理网元发送会话管理上下文请求消息，该会话管理上下文请求消息中包括该第一请求信息和第一组播组的标识。
作为又一个示例，终端设备向移动管理网元发送第二会话修改请求消息，该第二会话修改请求消息用于请求修改第二会话的参数，该第二会话修改请求消息中包括第一请求信息和第一组播组的标识。移动管理网元向第二会话管理网元发送会话管理上下文更新请求消息，该会话管理上下文更新请求消息中包括该第一请求信息和第一组播组的标识。
在另一种可能的实现方案中，第二会话管理网元还可以从应用功能网元接收该第一请求信息和该第一组播组标识。
应理解，第一请求信息和第一组播组标识可以承载于同一个消息中，也可以承载于两个连续发送的消息中，本申请对此不作限定。
S520，第二会话管理网元向数据管理网元发送第二请求信息和第一组播组的标识。
示例性地，根据第一请求信息，第二会话管理网元确定终端设备请求成为第一组播组的组播源，或者，第二请求信息用于请求终端设备加入第一组播组。
作为一个示例，当终端设备请求成为第一组播组的组播源，且该终端设备作为组播源发送的组播数据无需应用服务器进行解析处理时，第二会话管理网元向数据管理网元发送第二请求信息和第一组播组的标识，该第二请求信息用于请求获取第一会话管理网元的标识，该第一会话管理网元用于进行组播会话管理，且该第一会话管理网元与第一组播组的标识相关联。
可选地，在第二会话管理网元向数据管理网元发送第二请求信息和第一组播组的标识之前，第二会话管理网元向数据管理网元发送第三请求信息，该第三请求信息用于请求验证终端设备成为第一组播组的组播源的授权。对应地，数据管理网元接收到第三请求信息之后，验证终端设备是否具备成为第一组播组的组播源的授权。在终端设备具备成为第一组播组的组播源的授权的情形下，第二会话管理网元才继续执行后续流程，否则第二会话管理网元向终端设备发送一个响应信息，该响应信息用于拒绝第一请求信息，或者用于指示终端设备成为第一组播组的组播源失败，或者第二会话管理网元忽略第一请求信息，具体方式本申请不作限定。
作为又一个示例，当终端设备请求加入第一组播组，且该终端设备不支持以组播方式接受组播数据，或者该终端设备所在的无线接入网设备不支持组播服务时，第二会话管理网元向数据管理网元发送第二请求信息和第一组播组的标识。
可选地，在第二会话管理网元向数据管理网元发送第二请求信息和第一组播组的标识之前，第二会话管理网元向数据管理网元发送第三请求信息，该第三请求信息用于请求验证终端设备加入第一组播组的授权。对应地，数据管理网元接收到第三请求信息之后，验证终端设备是否具备加入第一组播组的授权。在终端设备具备加入第一组播组的授权的情形下，第二会话管理网元才继续执行后续流程。
应理解，第二请求信息和第一组播组标识可以承载于同一个消息中，也可以承载于两个连续发送的消息中，本申请对此不作限定。
S530，数据管理网元向第二会话管理网元发送第一会话管理网元的标识。
示例性地，数据管理网元根据第一组播组标识确定与该第一组播组标识对应的第一会话管理网元，然后将第一会话管理网元的标识发送给第二会话管理网元。
可选地，在一种可能的实现方式中，第二会话管理网元获取第一用户面功能网元的信息，该第一用户面功能网元用于进行组播数据管理，且该第一用户面功能网元与第一组播 组标识相关联。该第一用户面功能网元的信息例如是第一用户面功能网元的ID或是第一用户面功能网元的DNAI。
作为一个示例，第二会话管理网元通过第一会话管理网元获取第一用户面功能网元的信息。具体地，第二会话管理网元向第一会话管理网元发送第四请求信息和第一组播组的标识，该第四请求信息用于请求获取第一用户面功能网元的信息。第一会话管理网元根据第一组播组的标识确定第一用户面功能网元的信息，并将该第一用户面动能网元的信息发送给第二会话管理网元。
作为又一个示例，第二会话管理网元通过数据管理网元获取第一用户面功能网元的信息。具体地，第二会话功能网元向数据管理网元发送第四请求信息和第一组播组的标识。数据管理网元根据第一组播组的标识确定第一用户面功能网元的信息，并将该第一用户面功能网元的信息发送给第二会话管理网元。应理解，在该示例提供的方案中，第一会话管理网元在第一组播配置过程将第一用户面功能网元的信息保存在数据管理网元中。
S540，第二会话管理网元向终端设备发送第一指示信息和第一会话管理网元的标识。
示例性地，第二会话管理网元从数据管理网元获取到第一会话管理网元的标识之后，向移动管理网元发送第一指示信息和第一会话管理网元的标识，该第一指示信息用于指示终端设备建立第一会话，移动管理网元将第一指示信息和第一会话管理网元的标识透传给终端设备。
S550，终端设备向移动管理网元发送第一会话建立请求消息。
示例性地，终端设备根据第一指示信息，向移动管理网元发送第一会话建立请求消息，该第一会话建立请求消息用于请求建立终端设备与数据网路之间的第一会话，该第一会话建立请求消息中包括第一会话管理网元的标识。
S560，移动管理网元向第一会话管理网元发送第一请求信息和第一组播组的标识。
示例性地，移动管理网元接收到第一会话建立请求消息之后，获取第一会话管理网元的标识，然后选择第一会话管理网元建立第一会话。移动管理网元向第一会话管理网元发送第一请求信息和第一组播组的标识，以指示终端设备请求成为第一组播组的组播源，或者请求加入第一组播组。
应理解，该实施例中的会话管理网元是一种用于进行会话管理的网元，该实施例中的数据管理网元是一种用于对各类型数据进行存取功能的网元，该实施例中的第一会话管理网元是与第一组播组的标识相关联的用于进行组播会话管理的网元，该实施例中的移动管理网元是一种移动性管理和接入管理的网元，在不同系统中用于实现类似功能的网元的名称可能不同。例如，在5G系统中，该会话管理网元可以是SMF，该数据管理网元可以是UDR，该第一会话管理网元可以是第一组播组对应的MB-SMF，该移动性管理网元可以是AMF。
因此本申请实施例的通信方法，可以构建UE直接到组播会话管理网元的组播数据传输路径，可以减少传输路径的迂回，降低传输时延。
图6是本申请实施例提供的方法600的示意性流程图。在图6所示的实施例中，UE请求作为第一组播组的组播源，且UE作为组播源发送的组播数据无需AS解析处理。从图6中可以看出，方法600包括：
S601，网络设备与UE之间完成第一组播组配置。
S602，UE向AMF发送第一PDU会话建立请求消息。
示例性地，UE通过RAN向AMF发送第一PDU会话建立请求消息，该第一PDU会话建立请求消息用于请求建立UE与数据网络DN之间的第一PDU会话。该第一PDU会话建立请求消息中包括第一组播组标识和第一请求信息，该第一组播组标识用于标识第一组播组，该第一组播组标识例如可以是第一组播组的组播地址，该第一请求信息用于请求作为该第一组播组的组播源。
应理解，该第一请求信息还可以用于请求网络设备转发UE发送的组播数据。还应理解，该第一请求信息和该组播组标识也可以承载在其他消息中发送，本申请对此不作限定。
S603，AMF选择SMF。
示例性地，AMF接收到来自UE的第一PDU会话建立请求消息之后，选择SMF建立第一PDU会话。
S604，AMF向SMF发送会话管理上下文请求消息。
示例性地，AMF向S603中选择的SMF发送会话管理上下文请求消息，该会话管理上下文请求消息用于请求建立第一PDU会话管理上下文。可选地，该会话管理上下文请求消息包括第一请求信息和第一组播组标识。
S605，SMF向AMF发送会话管理上下文响应消息。
示例性地，SMF接收AMF发送的会话管理上下文请求消息之后，创建第一PDU会话的会话管理上下文，然后向AMF发送会话管理上下文响应消息，该会话管理上下文响应消息用于指示第一PDU会话的会话管理上下文建立完成。
S606，SMF检查UE作为组播源的授权，并获取MB-SMF ID。
示例性地，SMF根据第一组播组标识判断第一组播组的类型。应理解，组播组的类型包括ASM模式和SSM模型。当第一组播组的类型为ASM模式时，SMF检查UE作为组播源的授权。例如，SMF从UDR获取第一组播组的组播源的授权信息，根据该授权信息判断UE作为组播源是否得到了授权。
当UE具有作为第一组播组的组播源的授权时，SMF根据第一组播组标识从UDR获取MB-SMF的标识，例如MB-SMF ID。
S607，SMF向UE发送第一消息，该第一消息包括第一信息、第二信息和MB-SMF ID。
示例性地，当UE具有作为第一组播组的组播源的授权的时候，SMF通过第一消息向UE发送第一信息、第二信息和MB-SMF ID，其中第一信息用于拒绝第一PDU会话建立请求消息，第二信息用于指示UE重建PDU会话。
应理解，第一信息、第二信息和MB-SMF ID还可以承载在不同的消息中，本申请对此不作限定。在一种可能的实现方式中，SMF调用AMF的Namf_N1N2MessageTransfer服务向UE发送第一消息，AMF通过N2 PDU Session Request将第一消息传到RAN，RAN通过AN-specific resource setup过程将第一消息透传给UE。
S608，UE向AMF发送第二PDU会话建立请求消息。
示例性地，UE根据第二信息向AMF发送第二PDU会话建立请求消息，该第二PDU会话建立请求消息用于请求建立第二PDU会话。该第二PDU会话建立请求消息中包括MB-SMF ID。可选地，该第二PDU会话建立请求消息中还包括第一请求信息和第一组播组标识，该第一请求信息用于请求作为第一组播组的组播源。
S609，AMF选择MB-SMF。
示例性地，AMF接收来自UE的第二PDU会话建立请求消息，并获取该第二PDU会话建立请求消息中携带的MB-SMF ID，AMF根据该MB-SMF ID选择MB-SMF建立第二PDU会话。
S610，AMF向MB-SMF发送会话管理上下文请求消息。
示例性地，AMF向MB-SMF发送会话管理上下文请求消息，该会话管理上下文请求消息用于请求建立第二PDU会话管理上下文。该会话管理上下文请求消息包括第一请求信息和第一组播组标识。
作为另一种可能的实现方式，在S607，SMF向AMF发送MB-SMF ID、第一请求信息和第一PDU会话ID的第一对应关系。对应地，AMF从SMF接收该第一对应关系，并在本地保存该第一对应关系。在S608，UE向AMF发送的第二PDU会话建立请求消息中包括第二PDU会话ID和第一PDU会话ID。对应地，AMF接收来自UE的第二PDU会话建立请求消息，并获取第二PDU会话ID和第一PDU会话ID，然后AMF根据第一PDU会话ID和第一对应关系确定MB-SMF ID和第一请求信息，然后AMF根据MB-SMF ID选择对应的MB-SMF作为第二PDU会话的会话管理网元，然后AMF在S610的会话管理上下文请求消息中携带第一PDU会话对应的第一请求信息。
S611，网络侧选择MB-UPF完成第二PDU会话建立流程。
示例性地，MB-SMF接收到AMF发送的会话管理上下文请求消息之后，获取该会话管理上下文请求消息中的第一请求信息和第一组播组标识，根据该第一请求信息确定UE请求作为第一组播组的组播源。MB-SMF根据第一组播组标识从对应的第一组播上下文中找到MB-UPF，选择MB-UPF作为该第二PDU会话的PSA UPF。网络侧继续完成第二PDU会话的建立，具体方式不作限定。
因此，本申请实施例提供的通信方法，在PDU会话建立流程中，通过直接选取组播源UE对应的组播组的MB-UPF作为该组播源UE新建会话的PSA UPF，构建了组播源UE到MB-UPF的组播数据的传输路径，可以减少传输路径的迂回，降低传输时延。
图7是本申请实施例提供的方法700的示意性流程图。在图7所示的实施例中，UE请求作为第一组播组的组播源，且UE作为组播源发送的组播数据无需AS解析处理。从图7中可以看出，方法700包括：
S701，网络设备与UE之间完成第一组播组配置。
S702，UE向AMF发送第一PDU会话修改请求消息，该第一PDU会话修改请求消息用于请求对第一PDU会话的服务质量(quality of service，QoS)参数进行修改，该第一PDU会话修改请求消息中包括第一请求信息和第一组播组标识，该第一组播组标识用于标识第一组播组，该第一组播组标识例如可以是第一组播组的组播地址，该第一请求信息用于请求UE作为该第一组播组的组播源。
S703，AMF向SMF发送会话管理上下文更新请求消息，该会话管理上下文更新请求消息中包括该第一请求信息和该第一组播组标识。
在另一种可能的实现方式中，还可以由AF向SMF发送第一请求信息和第一组播组标识。例如，在S704，AF向SMF发送第二消息，该第二消息中包括第一请求信息和第一组播组标识。该第二消息例如可以是UE作为组播源的请求消息。应理解，AF可以直 接向SMF发送该第二消息，也可以经过网络开放功能(network exposure function，NEF)进行转发。
S705，SMF检查UE作为组播源的授权，并获取MB-SMF ID。
应理解，S705与方法600中的S606类似，本申请在此不再重复说明。
S706，SMF向UE发送第一消息，该第一消息中包括第二信息和MB-SMF ID。
示例性地，当UE具有作为第一组播组的组播源的授权的时候，SMF通过第一消息向UE发送第二信息和MB-SMF ID，其中第二信息用于指示UE重建PDU会话。
作为一个具体示例，SMF调用AMF的Namf_N1N2MessageTransfer服务向UE发送第一消息，该第一消息包括第二信息和MB-SMF ID，AMF经RAN将第一消息发送给UE。应理解，在某种实现方式中，该第一消息也可以是PDU会话修改命令消息。
S707，UE向AMF发送第二PDU会话建立请求消息。
S708，AMF选择MB-SMF。
S709，AMF向MB-SMF发送会话管理上下文请求消息。
S710，网络侧选择MB-UPF完成第二PDU会话建立流程。
应理解，S707-S710与方法600中的S608-S611类似，为了简洁，本申请在此不再重复说明。
作为另一种可能的实现方式，在S706，SMF向AMF发送MB-SMF ID、第一请求信息和第一PDU会话ID的第一对应关系。对应地，AMF从SMF接收该第一对应关系，并在本地保存该第一对应关系。在S707，UE向AMF发送的第二PDU会话建立请求消息中包括第二PDU会话ID和第一PDU会话ID。对应地，AMF接收来自UE的第二PDU会话建立请求消息，并获取第二PDU会话ID和第一PDU会话ID，然后AMF根据第一PDU会话ID和第一对应关系确定MB-SMF ID和第一请求信息，然后AMF根据MB-SMF ID选择对应的MB-SMF作为第二PDU会话的会话管理网元，然后AMF在S709的会话管理上下文请求消息中携带第一PDU会话对应的第一请求信息。
因此，本申请实施例提供的通信方法，在PDU会话建立流程中，通过直接选取组播源UE对应的组播组的MB-UPF作为该组播源UE新建会话的PSA UPF，构建了组播源UE到MB-UPF的组播数据的传输路径，可以减少传输路径的迂回，降低传输时延。
图8是应用方法600和方法700的一种系统架构800的示意图。在系统架构800中，UE1、UE2、UE3为组播组成员，UE4为该组播组的组播源。在UE4的PDU会话建立流程中，选取该组播组对应的MB-UPF作为UE4新建会话的PSA UPF，此时UE4作为组播源向组播组发送组播数据的时候，不再需要通过PSA UPF将组播数据发送给AS，再通过AS将组播数据转发给MB-UPF，避免了组播通信时传输路径的迂回，可以减少组播通信的传输时延。
图9是本申请实施例提供的方法900的示意性流程图。在图9所示的实施例中，UE请求作为第一组播组的组播源，且UE作为组播源发送的组播数据无需AS解析处理。从图9中可以看出，方法900包括：
S901，网络设备与UE之间完成第一组播组配置。
S902，UE向AMF发送第一PDU会话修改请求消息，该第一PDU会话修改请求消息中包括第一请求信息和第一组播组标识。该第一组播组标识用于标识第一组播组，该第 一组播组标识例如可以是第一组播组的组播地址，该第一请求信息用于请求UE作为该第一组播组的组播源。
S903，AMF向SMF发送会话管理上下文更新请求消息，该会话管理上下文更新请求消息中包括该第一请求信息和该第一组播组标识。
在另一种可能的实现方式中，还可以由AF向SMF发送第一请求信息和第一组播组标识。例如，在S904，AF向SMF发送第二消息，该第二消息中包括第一请求信息和第一组播组标识。
应理解，S901-S904与方法700中的S701-S704类似，为了简洁，本申请在此不再重复说明。
进一步地，SMF获取MB-UPF的信息。下面对SMF获取MB-UPF的信息的两种方案进行说明：
方案1：
S905，SMF检查UE作为组播源的授权，并获取MB-SMF ID。
应理解，S905与方法600中的S606类似，为了简洁，本申请在此不再重复说明。
需要说明的是，第一组播组的类型无论是ASM模型还是SSM模型，该实施例的方案都适用。
S906，SMF通过MB-SMF获取MB-UPF的信息。
示例性地，SMF根据MB-SMF ID向MB-SMF发送请求获取MB-UPF地址信息的请求消息，该请求消息中携带第一组播组标识；对应地，MB-SMF接收到该请求消息之后，根据第一组播组标识获取该第一组播组标识对应的MB-UPF的信息，例如是MB-UPF的地址信息，或者是MB-UPF的DNAI。然后MB-SMF向SMF回复MB-UPF的信息。
方案2：
S907，SMF检查UE作为组播源的授权，并获取MB-UPF ID。
应理解，SMF检查UE作为组播源的授权的方案与方法600中S606中的相关方案类似，本申请在此不再赘述。
当UE具有作为第一组播组的组播源的授权时，SMF根据第一组播组标识从UDR获取MB-UMF的信息，例如MB-UPF的地址信息或MB-UPF的DNAI。
应理解，对于方案2，在第一组播组配置过程中，MB-SMF将MB-UPF的地址信息或MB-UPF的DNAI存入到UDR当中。
S908，网络侧以MB-UPF作为第一PDU会话的额外PSA UPF，在用户面插入或选择已存在的UPF，并配置该UPF具备UL CL或BP的功能。
示例性地，SMF获取到MB-UPF的信息之后，将该MB-UPF作为第一PDU会话的额外PSA UPF，并根据MB-UPF的信息在用户面上插入UPF或者选择已经存在的UPF，通过N4会话进行相应的配置，使得该UPF具有UL CL或BP的功能，从而实现将UE的组播数据分流到MB-UPF的效果。应理解，该具有UL CL或BP功能的UPF可以与MB-UPF是同一个UPF实体，也可以与该PDU会话的PSA UPF是同一个UPF实体。
因此，本申请实施例提供的通信方法，在PDU会话修改流程中，选取组播源UE对应的组播组的MB-UPF作为第一PDU会话的额外PSA UPF，通过插入的UPF或选择的UPF作为UL CL/BP实现UE的组播数据到MB-UPF的分流，构建了组播源UE到MB-UPF 的组播数据的传输路径，可以减少传输路径的迂回，降低传输时延。
图10是应用方法900的一种系统架构1000的示意图。在系统架构1000中，UE1、UE2、UE3为组播组成员，UE4为该组播组的组播源。UE4通过对一个PDU会话进行修改，将UE4对应的组播组的MB-UPF设置为该PDU会话的额外PSA UPF。通过在RAN和原PSA UPF之间的线路上插入一个UPF，或者在RAN和原PSA UPF之间的线路上选择一个已经存在的UPF，并对该UPF配置UL CL或BP功能，构建了UE4到MB-UPF的组播数据的传输路径，此时UE4作为组播源向组播组发送组播数据的时候，不再需要通过PSA UPF将组播数据发送给AS，再通过AS将组播数据转发给MB-UPF，避免了组播通信时传输路径的迂回，可以减少组播通信的传输时延。
图11是本申请实施例提供的方法1100的示意性流程图。在图11所示的实施例中，UE请求加入第一组播组，且该UE不支持以组播方式接受组播数据，或该UE所在的RAN不支持组播服务。从图11中可以看出，方法1100包括：
S1101，网络设备与UE之间完成第一组播组配置。
S1102，UE向AMF发送第一PDU会话建立请求消息。
示例性地，UE通过RAN向AMF发送第一PDU会话建立请求消息，该第一PDU会话建立请求消息用于请求建立UE与数据网络DN之间的第一PDU会话。该第一PDU会话建立请求消息中包括第一组播组标识，该第一组播组标识用于标识第一组播组，该第一组播组标识例如可以是第一组播组的组播地址，该第一组播标识用于指示UE请求加入第一组播组。
S1103，AMF选择SMF。
示例性地，AMF接收到来自UE的第一PDU会话建立请求消息之后，选择SMF建立第一PDU会话。
S1104，AMF向SMF发送会话管理上下文请求消息。
示例性地，AMF向S603中选择的SMF发送会话管理上下文请求消息，该会话管理上下文请求消息用于请求建立第一PDU会话管理上下文。可选地，该会话管理上下文请求消息包括第一组播组标识。
S1105，SMF向AMF发送会话管理上下文响应消息。
示例性地，SMF接收AMF发送的会话管理上下文请求消息之后，创建第一PDU会话的会话管理上下文，然后向AMF发送会话管理上下文响应消息。
S1106，SMF检查UE加入组播组的授权，并获取MB-SMF ID。
示例性地，SMF从UDR获取第一组播组的组播成员的授权信息，根据该授权信息判断UE作为加入组播组是否得到了授权。
当UE具有作为第一组播组的组播源的授权时，SMF根据第一组播组标识从UDR获取MB-SMF的标识，例如MB-SMF ID。
S1107，SMF向UE发送第一消息，该第一消息包括第一信息、第二信息和MB-SMF ID。
应理解，S1107与方法600中的S607类似，为了简洁，本申请在此不再赘述。
S1108，UE向AMF发送第二PDU会话建立请求消息。
示例性地，UE根据第二信息向AMF发送第二PDU会话建立请求消息，该第二PDU 会话建立请求消息用于请求建立第二PDU会话。该第二PDU会话建立请求消息中包括MB-SMF ID和第一组播组标识。
S1109，AMF选择MB-SMF。
示例性地，AMF接收来自UE的第二PDU会话建立请求消息，并获取该第二PDU会话建立请求消息中携带的MB-SMF ID，SMF根据该MB-SMF ID选择MB-SMF建立第二PDU会话。
S1110，AMF向MB-SMF发送会话管理上下文请求消息。
示例性地，AMF向MB-SMF发送会话管理上下文请求消息，该会话管理上下文请求消息用于请求建立第二PDU会话管理上下文。该会话管理上下文请求消息包括第一组播组标识。
作为另一种可能的实现方式，在S1107，SMF向AMF发送MB-SMF ID、第一组播组标识和第一PDU会话ID的第一对应关系。对应地，AMF从SMF接收该第一对应关系，并在本地保存该第一对应关系。在S1108，UE向AMF发送的第二PDU会话建立请求消息中包括第二PDU会话ID和第一PDU会话ID。对应地，AMF接收来自UE的第二PDU会话建立请求消息，并获取第二PDU会话ID和第一PDU会话ID，然后AMF根据第一PDU会话ID和第一对应关系确定MB-SMF ID和第一请求信息，然后AMF根据MB-SMF ID选择对应的MB-SMF作为第二PDU会话的会话管理网元，然后AMF在S1110的会话管理上下文请求消息中携带第一PDU会话对应的第一组播组标识。
S1111，网络侧选择MB-UPF完成第二PDU会话建立流程。
示例性地，MB-SMF接收到AMF发送的会话管理上下文请求消息之后，获取该会话管理上下文请求消息中的第一组播组标识，根据该第一组播组标识确定UE请求加入第一组播组。MB-SMF根据第一组播组标识从对应的第一组播上下文中找到MB-UPF，选择MB-UPF作为该第二PDU会话的PSA UPF。网络侧继续完成第二PDU会话的建立，具体方式不作限定。
因此，本申请实施例提供的通信方法，当作为组播组成员的UE不支持以组播方式接受组播数据，或该UE所在的RAN不支持组播服务时，在PDU会话建立流程中，通过直接选取该组播组成员UE对应的组播组的MB-UPF作为该UE的新建会话的PSA UPF，构建了MB-UPF到该组播成员UE的组播数据的传输路径，可以减少传输路径的迂回，降低传输时延。
图12是本申请实施例提供的方法1200的示意性流程图。在图12所示的实施例中，UE请求加入第一组播组，该UE不支持以组播方式接受组播数据，或该UE所在的RAN不支持组播服务。从图12中可以看出，方法1200包括：
S1201，网络设备与UE之间完成第一组播组配置。
S1202，UE向AMF发送第一PDU会话修改请求消息，该第一PDU会话修改请求消息中包括第一组播组标识，该第一组播组标识用于标识第一组播组，该第一组播组标识例如可以是第一组播组的组播地址，该第一组播组标识用于指示UE请求加入第一组播组。
S1203，AMF向SMF发送会话管理上下文更新请求消息，该会话管理上下文更新请求消息中包括第一组播组标识。
在另一种可能的实现方式中，还可以由AF向SMF发送第一组播组标识。例如，在 S704，AF向SMF发送第一消息，该第一消息中包括第一组播组标识。该第一消息例如可以是UE加入第一组播组的请求消息。应理解，AF可以直接向SMF发送该第一消息，也可以经过NEF进行转发。
S1205，SMF检查UE加入组播组的授权，并获取MB-SMF ID。
应理解，S1205与方法1100中的S1106类似，本申请在此不再重复说明。
S1206，SMF向UE发送第一消息，该第一消息中包括第二信息和MB-SMF ID。
示例性地，当UE具有作为第一组播组的组播源的授权的时候，SMF通过第一消息向UE发送第二信息和MB-SMF ID，其中第二信息用于指示UE重建PDU会话。
S1207，UE向AMF发送第二PDU会话建立请求消息，该第二PDU会话建立请求消息中包括第一组播组标识和MB-SMFID。
示例性地，UE根据第二信息向AMF发送第二PDU会话建立请求消息，该第二PDU会话建立请求消息用于请求建立第二PDU会话。该第二PDU会话建立请求消息中包括MB-SMF ID和第一组播组标识，该第一组播组标识用于指示UE请求加入第一组播组。
S1208，AMF选择MB-SMF。
S1209，AMF向MB-SMF发送会话管理上下文请求消息。
S1210，网络侧选择MB-UPF完成第二PDU会话建立流程。
应理解，S1208-S1210与方法600中的S609-S611类似，为了简洁，本申请在此不再重复说明。
作为另一种可能的实现方式，在S1206，SMF向AMF发送MB-SMF ID、第一组播组标识和第一PDU会话ID的第一对应关系。对应地，AMF从SMF接收该第一对应关系，并在本地保存该第一对应关系。在S608，UE向AMF发送的第二PDU会话建立请求消息中包括第二PDU会话ID和第一PDU会话ID。对应地，AMF接收来自UE的第二PDU会话建立请求消息，并获取第二PDU会话ID和第一PDU会话ID，然后AMF根据第一PDU会话ID和第一对应关系确定MB-SMF ID和第一请求信息，然后AMF根据MB-SMF ID选择对应的MB-SMF作为第二PDU会话的会话管理网元，然后AMF在S1209的会话管理上下文请求消息中携带第一PDU会话对应的第一组播组标识。
因此，本申请实施例提供的通信方法，当作为组播组成员的UE不支持以组播方式接受组播数据，或该UE所在的RAN不支持组播服务时，在PDU会话建立流程中，通过直接选取该组播组成员UE对应的组播组的MB-UPF作为该UE新建会话的PSA UPF，构建了MB-UPF到该组播成员UE的组播数据的传输路径，可以减少传输路径的迂回，降低传输时延。
图13是应用方法1100和方法1200的一种系统架构1300的示意图。在系统架构1300中，UE1、UE2、UE3均为组播组成员，其中，UE 1和UE 2支持以组播方式接收组播数据，UE1和UE2所在的RAN1也支持组播服务，而UE3不支持以组播方式接收组播数据，或者UE 3所在的RAN 2不支持组播服务。在UE3的PDU会话建立流程中，选取该组播组对应的MB-UPF作为UE3新建会话的PSA UPF，组播数据包到达MB-UPF之后，不需要再将数据转发给PSAUPF，再通过PSAUPF将组播数据发送到RAN2，避免了组播通信时传输路径的迂回，可以减少组播通信的传输时延。
图14是本申请实施例提供的方法1400的示意性流程图。在图14所示的实施例中， UE请求加入第一组播组，该UE不支持以组播方式接受组播数据，或该UE所在的RAN不支持组播服务。从图14中可以看出，方法1400包括：
S1401，网络设备与UE之间完成第一组播组配置。
S1402，UE向AMF发送第一PDU会话修改请求消息，该第一PDU会话修改请求消息中包括第一组播组标识。该第一组播组标识用于标识第一组播组，该第一组播组标识例如可以是第一组播组的组播地址，该第一组播组标识用于指示UE请求加入第一组播组。
S1403，AMF向SMF发送会话管理上下文更新请求消息，该会话管理上下文更新请求消息中包括第一组播组标识。
在另一种可能的实现方式中，还可以由AF向SMF发送第一组播组标识。例如，在S1404，AF向SMF发送第一消息，该第一消息中包括第一组播组标识。该第一消息例如可以是UE加入第一组播组的请求消息。应理解，AF可以直接向SMF发送该第一消息，也可以经过NEF进行转发。
进一步地，SMF获取MB-UPF的信息。
应理解，S1405至S1407与方法900中的S905至S907类似，区别仅在于S1405和S1407中SMF检查的是UE加入组播组的授权，为了简洁，本申请不再重复说明。
S1408，网络侧以MB-UPF作为第一PDU会话的额外PSA UPF，在用户面插入或选择已存在的UPF，并配置该UPF具备UL CL或BP的功能。
应理解，S1408与方法900中的S908类似，为了简洁，本申请不再重复说明。
因此，本申请实施例提供的通信方法，当作为组播组成员的UE不支持以组播方式接受组播数据，或该UE所在的RAN不支持组播服务时，在PDU会话修改流程中，选取组播组成员UE对应的组播组的MB-UPF作为第一PDU会话的额外PSA UPF，通过插入的UPF或选择的UPF作为UL CL/BP实现组播数据到该UE的分流，构建了MB-UPF到该组播成员UE的组播数据的传输路径，可以减少传输路径的迂回，降低传输时延。
图15是应用方法1400的一种系统架构1500的示意图。在系统架构1500中，UE1、UE2、UE3均为组播组成员，其中，UE 1和UE 2支持以组播方式接收组播数据，UE1和UE2所在的RAN1也支持组播服务，而UE3不支持以组播方式接收组播数据，或者UE 3所在的RAN 2不支持组播服务。UE3通过对一个PDU会话进行修改，将UE3对应的组播组的MB-UPF设置为该PDU会话的额外PSA UPF。通过在RAN和主PSA UPF之间的用户面路径上插入一个UPF，或者在RAN和原PSA UPF之间的用户面路径上选择一个已经存在的UPF，并对该UPF配置UL CL或BP功能，构建了UE3到MB-UPF的组播数据的传输路径，此时组播数据包到达MB-UPF之后，不需要再将数据转发给主PSAUPF，再通过主PSAUPF将组播数据发送到RAN2，避免了组播通信时传输路径的迂回，可以减少组播通信的传输时延。
以上，结合图5至图15详细说明了本申请实施例提供的方法。以下，结合图16至图19详细说明本申请实施例提供的通信装置。
图16是本申请实施例提供的通信装置10的示意性框图。如图所示，该通信装置10可以包括收发模块11和处理模块12。
在一种可能的设计中，该通信装置10可对应于上文方法实施例中的终端设备或者UE。
示例性地，该通信装置10可对应于根据本申请实施例的方法500至方法700、方法 900、方法1100至方法1200、方法1400中的终端设备或者UE，该通信装置10可以包括用于执行图5中的方法500、图6中的方法600、图7中的方法700、图9中的方法900、图11中的方法1100、图12中的方法1200和图14中的方法1400中的终端设备或者UE执行的方法的模块。并且，该通信装置10中的各单元和上述其他操作和/或功能分别为了实现方法500至方法700、方法900、方法1100至方法1200、方法1400的相应流程。
该通信装置10中的该收发模块11执行上述各方法实施例中的终端设备或者UE所执行的接收和发送操作，该处理模块12则执行除了该接收和发送操作之外的操作。
在另一种可能的设计中，该通信装置10可对应于上文方法实施例中的会话管理网元或者SMF。
示例性地，该通信装置10可对应于根据本申请实施例的方法500至方法700、方法900、方法1100至方法1200、方法1400中的会话管理网元或者SMF，该通信装置10可以包括用于执行图5中的方法500、图6中的方法600、图7中的方法700、图9中的方法900、图11中的方法1100、图12中的方法1200和图14中的方法1400中的会话管理网元或者SMF执行的方法的模块。并且，该通信装置10中的各单元和上述其他操作和/或功能分别为了实现方法500至方法700、方法900、方法1100至方法1200、方法1400的相应流程。
该通信装置10中的该收发模块11执行上述各方法实施例中的会话管理网元或者SMF所执行的接收和发送操作，该处理模块12则执行除了该接收和发送操作之外的操作。
在又一种可能的设计中，该通信装置10可对应于上文方法实施例中的移动管理网元或者AMF。
示例性地，该通信装置10可对应于根据本申请实施例的方法500至方法700、方法900、方法1100至方法1200、方法1400中的移动管理网元或者AMF，该通信装置10可以包括用于执行图5中的方法500、图6中的方法600、图7中的方法700、图9中的方法900、图11中的方法1100、图12中的方法1200和图14中的方法1400中的移动管理网元或者AMF执行的方法的模块。并且，该通信装置10中的各单元和上述其他操作和/或功能分别为了实现方法500至方法700、方法900、方法1100至方法1200、方法1400的相应流程。
该通信装置10中的该收发模块11执行上述各方法实施例中的移动管理网元或者AMF所执行的接收和发送操作，该处理模块12则执行除了该接收和发送操作之外的操作。
根据前述方法，图17为本申请实施例提供的通信装置20的示意图，如图17所示，该装置20可以为终端设备，也可以为网络设备，该网络设备例如可以是会话管理网元，也可以是移动管理网元。
该装置20可以包括处理器21(即，处理模块的一例)和存储器22。该存储器22用于存储指令，该处理器21用于执行该存储器22存储的指令，以使该装置20实现如图5、图6、图7、图9、图11、图12、图14对应的方法中终端设备或UE或会话管理网元或SMF或移动管理网元或AMF执行的步骤。
进一步地，该装置20还可以包括输入口23(即，收发模块的一例)和输出口24(即，收发模块的另一例)。进一步地，该处理器21、存储器22、输入口23和输出口24可以通过内部连接通路互相通信，传递控制和/或数据信号。该存储器22用于存储计算机程序， 该处理器21可以用于从该存储器22中调用并运行该计算机程序，以控制输入口23接收信号，控制输出口24发送信号，完成上述方法中网络设备的步骤。该存储器22可以集成在处理器21中，也可以与处理器21分开设置。
可选地，若该通信装置20为通信设备，该输入口23为接收器，该输出口24为发送器。其中，接收器和发送器可以为相同或者不同的物理实体。为相同的物理实体时，可以统称为收发器。
可选地，若该通信装置20为芯片或电路，该输入口23为输入接口，该输出口24为输出接口。
作为一种实现方式，输入口23和输出口24的功能可以考虑通过收发电路或者收发的专用芯片实现。处理器21可以考虑通过专用处理芯片、处理电路、处理器或者通用芯片实现。
作为另一种实现方式，可以考虑使用通用计算机的方式来实现本申请实施例提供的通信设备。即将实现处理器21、输入口23和输出口24功能的程序代码存储在存储器22中，通用处理器通过执行存储器22中的代码来实现处理器21、输入口23和输出口24的功能。
该装置20所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
图18为本申请提供的一种终端设备30的结构示意图。为了便于说明，图18仅示出了通信装置的主要部件。如图18所示，终端设备30包括处理器、存储器、控制电路、天线以及输入输出装置。
处理器主要用于对通信协议以及通信数据进行处理，以及对整个终端设备进行控制，执行软件程序，处理软件程序的数据，例如用于支持终端设备执行上述传输预编码矩阵的指示方法实施例中所描述的动作。存储器主要用于存储软件程序和数据，例如存储上述实施例中所描述的码本。控制电路主要用于基带信号与射频信号的转换以及对射频信号的处理。控制电路和天线一起也可以叫做收发器，主要用于收发电磁波形式的射频信号。输入输出装置，例如触摸屏、显示屏，键盘等主要用于接收用户输入的数据以及对用户输出数据。
当通信装置开机后，处理器可以读取存储单元中的软件程序，解释并执行软件程序的指令，处理软件程序的数据。当需要通过无线发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端设备时，射频电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。
本领域技术人员可以理解，为了便于说明，图18仅示出了一个存储器和处理器。在实际的终端设备中，可以存在多个处理器和存储器。存储器也可以称为存储介质或者存储设备等，本申请实施例对此不做限制。
作为一种可选的实现方式，处理器可以包括基带处理器和中央处理器，基带处理器主要用于对通信协议以及通信数据进行处理，中央处理器主要用于对整个终端设备进行控制，执行软件程序，处理软件程序的数据。图18中的处理器集成了基带处理器和中央处理器的功能，本领域技术人员可以理解，基带处理器和中央处理器也可以是各自独立的处理器， 通过总线等技术互联。本领域技术人员可以理解，终端设备可以包括多个基带处理器以适应不同的网络制式，终端设备可以包括多个中央处理器以增强其处理能力，终端设备的各个部件可以通过各种总线连接。所述基带处理器也可以表述为基带处理电路或者基带处理芯片。所述中央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中，也可以以软件程序的形式存储在存储单元中，由处理器执行软件程序以实现基带处理功能。
如图18所示，终端设备30包括收发单元31和处理单元32。收发单元也可以称为收发器、收发机、收发装置等。可选的，可以将收发单元31中用于实现接收功能的器件视为接收单元，将收发单元31中用于实现发送功能的器件视为发送单元，即收发单元31包括接收单元和发送单元。示例性的，接收单元也可以称为接收机、接收器、接收电路等，发送单元可以称为发射机、发射器或者发射电路等。
图18所示的终端设备可以执行上述方法500至方法700、方法900、方法1100至方法1200、方法1400中终端设备或UE所执行的各动作，这里，为了避免赘述，省略其详细说明。
图19示出了一种简化的网络设备40的结构示意图。网络设备包括41部分以及42部分。41部分主要用于射频信号的收发以及射频信号与基带信号的转换；42部分主要用于基带处理，对网络设备进行控制等。41部分通常可以称为收发模块、收发机、收发电路、或者收发器等。42部分通常是网络设备的控制中心，通常可以称为处理模块，用于控制网络设备执行上述方法实施例中网络设备侧的处理操作。
41部分的收发模块，也可以称为收发机或收发器等，其包括天线和射频电路，其中射频电路主要用于进行射频处理。例如，可以将41部分中用于实现接收功能的器件视为接收模块，将用于实现发送功能的器件视为发送模块，即41部分包括接收模块和发送模块。接收模块也可以称为接收机、接收器、或接收电路等，发送模块可以称为发射机、发射器或者发射电路等。
42部分可以包括一个或多个单板，每个单板可以包括一个或多个处理器和一个或多个存储器。处理器用于读取和执行存储器中的程序以实现基带处理功能以及对网络设备的控制。若存在多个单板，各个单板之间可以互联以增强处理能力。作为一种可选的实施方式，也可以是多个单板共用一个或多个处理器，或者是多个单板共用一个或多个存储器，或者是多个单板同时共用一个或多个处理器。
例如，在一种实现方式中，图19所示的网络设备可以是图5、图6、图7、图9、图11、图12、图14中所示的任意网络设备，例如会话管理网元、移动管理网元、SMF、AMF等。
41部分的收发模块用于执行图5中的方法500、图6中的方法600、图7中的方法700、图9中的方法900、图11中的方法1100、图12中的方法1200和图14中的方法1400中任意网络设备的收发相关的步骤；42部分用于执行图5中的方法500、图6中的方法600、图7中的方法700、图9中的方法900、图11中的方法1100、图12中的方法1200和图14中的方法1400中的任意网络设备的处理相关的步骤。
应理解，图19仅为示例而非限定，上述包括收发模块和处理模块的网络设备可以不依赖于图19所示的结构。
当该装置40为芯片时，该芯片包括收发模块和处理模块。其中，收发模块可以是输入输出电路、通信接口；处理模块为该芯片上集成的处理器或者微处理器或者集成电路。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例中由第网络设备执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由网络设备执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中由第一设备执行的方法，或由第二设备执行的方法。
本申请实施例还提供一种通信系统，该通信系统包括上文实施例中的网络设备。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在本申请实施例中，网络设备可以包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。其中，硬件层可以包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。操作系统层的操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。应用层可以包含浏览器、通讯录、文字处理软件、即时通信软件等应用。
本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构进行特别限定，只要能够通过运行记录有本申请实施例提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可。例如，本申请实施例提供的方法的执行主体可以是网络设备，或者，是网络设备中能够调用程序并执行程序的功能模块。
本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本文中使用的术语“制品”可以涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。
本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可以包括但不限于：无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
应理解，本申请实施例中提及的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只 读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。例如，RAM可以用作外部高速缓存。作为示例而非限定，RAM可以包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的保护范围。
所属领域的技术人员可以清楚地了解到，为描述方便和简洁，上述描述的装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。此外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元实现本申请提供的方案。
另外，在本申请各个实施例中的各功能单元可以集成在一个单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如，所述计算机可以是个人计算机，服务器，或者网络设备等。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL)) 或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，(SSD))等。例如，前述的可用介质可以包括但不限于：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求和说明书的保护范围为准。

Claims (30)

  1. 一种通信方法，其特征在于，包括：
    接收第一请求信息和第一组播组的标识，所述第一请求信息用于请求终端设备成为第一组播组的组播源，或者所述第一请求信息用于请求所述终端设备加入所述第一组播组；
    向数据管理网元发送第二请求信息和所述第一组播组的标识，所述第二请求信息用于请求获取第一会话管理网元的标识，所述第一会话管理网元用于进行组播会话管理，所述第一会话管理网元与所述第一组播组的标识相关联；
    接收来自所述数据管理网元的所述第一会话管理网元的标识。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    向移动管理网元发送所述第一会话管理网元的标识。
  3. 根据权利要求1或2所述的方法，其特征在于，在所述向数据管理网元发送第二请求信息和所述第一组播组标识之前，所述方法还包括：
    向所述数据管理网元发送第三请求信息，在所述第一请求信息用于请求所述终端设备成为所述第一组播组的组播源的情形下，所述第三请求信息用于请求验证所述终端设备作为所述第一组播组的组播源的授权，在所述第一请求信息用于请求所述终端设备加入所述第一组播组的情形下，所述第三请求信息用于请求验证所述终端设备加入所述第一组播组的授权。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    向所述终端设备发送第一指示信息和所述第一会话管理网元的标识，所述第一会话管理网元用于进行组播会话管理，所述第一指示信息用于指示所述终端设备建立所述第一会话。
  5. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    获取第一用户面功能网元的信息，所述第一用户面功能网元用于进行组播数据的转发处理，所述第一用户面功能网元与所述第一组播组标识相关联。
  6. 根据权利要求5所述的方法，其特征在于，所述获取第一用户面功能网元的信息之后，所述方法还包括：
    根据所述第一用户面功能网元的信息构建所述第一用户面功能网元和所述终端设备之间的数据传输路径。
  7. 根据权利要求5或6所述的方法，其特征在于，所述获取第一用户面功能网元的信息，包括：
    向所述数据管理网元发送第四请求信息和所述第一组播组的标识，所述第四请求信息用于请求获取所述第一用户面功能网元的信息；
    接收来自所述数据管理网元的所述第一用户面功能网元的信息；或者，
    向所述第一会话管理网元发送所述第四请求信息和所述第一组播组的标识；
    接收来自所述第一会话管理网元的所述第一用户面功能网元的信息。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述接收第一请求信息和第一组播组的标识，包括：
    接收来自所述终端设备的所述第一请求信息和所述第一组播组的标识；或者
    接收来自应用功能网元的所述第一请求信息和所述第一组播组的标识。
  9. 一种通信方法，其特征在于，包括：
    接收来自终端设备的第一会话建立请求消息，所述第一会话建立请求消息用于请求建立所述终端设备与数据网络之间的第一会话，所述第一会话建立请求消息包括第一会话管理网元的标识，所述第一会话管理网元用于进行组播会话管理；
    向所述第一会话管理网元发送第一请求信息和第一组播组的标识，所述第一请求信息用于请求终端设备成为所述第一组播组的组播源，或者所述第一请求信息用于请求所述终端设备加入所述第一组播组。
  10. 根据权利要求9所述的方法，其特征在于，在所述接收来自终端设备的第一会话建立请求消息之前，所述方法还包括：
    接收来自所述终端设备的所述第一请求信息和所述第一组播组的标识；
    向第二会话管理网元发送所述第一请求信息和所述第一组播组的标识。
  11. 根据权利要求10所述的方法，其特征在于，所述接收来自所述终端设备的所述第一请求信息和所述第一组播组的标识，包括：
    接收来自所述终端设备的第二会话建立请求消息，所述第二会话建立请求消息包括所述第一请求信息和所述第一组播组的标识；或者
    接收来自所述终端设备的第二会话修改请求消息，所述第二会话修改请求消息包括所述第一请求信息和所述第一组播组的标识。
  12. 一种通信方法，其特征在于，包括：
    接收来自第二会话管理网元的第一指示信息和第一会话管理网元的标识，所述第一会话管理网元用于进行组播会话管理，所述第一指示信息用于指示所述终端设备建立第一会话；
    向移动管理网元发送第一会话建立请求消息，所述第一会话建立请求消息用于请求建立所述终端设备与数据网络之间的所述第一会话，所述第一会话建立请求消息包括第一会话管理网元的标识，所述第一会话管理网元用于进行组播会话管理。
  13. 根据权利要求12所述的方法，其特征在于，在所述向移动管理网元发送会话建立请求消息之前，所述方法还包括：
    向移动管理网元发送第一请求信息和第一组播组标识，所述第一请求消息用于请求终端设备成为第一组播组的组播源，或者所述第一请求信息用于请求所述终端设备加入所述第一组播组。
  14. 根据权利要求13所述的方法，其特征在于，所述向移动管理网元发送第一请求信息和第一组播组标识，包括：
    向所述移动管理网元发送第二会话建立请求消息，所述第二会话建立请求消息包括所述第一请求信息和所述第一组播组的标识；或者，
    向所述移动管理网元发送第二会话修改请求消息，所述第二会话修改请求消息包括所述第一请求信息和所述第一组播组的标识。
  15. 一种通信装置，其特征在于，包括：
    收发模块，用于接收第一请求信息和第一组播组的标识，所述第一请求信息用于请求 终端设备成为第一组播组的组播源，或者所述第一请求信息用于请求所述终端设备加入所述第一组播组；
    所述收发模块还用于向数据管理网元发送第二请求信息和所述第一组播组的标识，所述第二请求信息用于请求获取第一会话管理网元的标识，所述第一会话管理网元用于进行组播会话管理，所述第一会话管理网元与所述第一组播组的标识相关联；
    所述收发模块还用于接收来自所述数据管理网元的所述第一会话管理网元的标识。
  16. 根据权利要求15所述的装置，其特征在于，所述收发模块还用于：
    向移动管理网元发送所述第一会话管理网元的标识。
  17. 根据权利要求15或16所述的装置，其特征在于，所述收发模块还用于：
    向所述数据管理网元发送第三请求信息，在所述第一请求信息用于请求所述终端设备成为所述第一组播组的组播源的情形下，所述第三请求信息用于请求验证所述终端设备作为所述第一组播组的组播源的授权，在所述第一请求信息用于请求所述终端设备加入所述第一组播组的情形下，所述第三请求信息用于请求验证所述终端设备加入所述第一组播组的授权。
  18. 根据权利要求15至17中任一项所述的装置，其特征在于，所述收发模块还用于：
    向所述终端设备发送第一指示信息和所述第一会话管理网元的标识，所述第一会话管理网元用于进行组播会话管理，所述第一指示信息用于指示所述终端设备建立所述第一会话。
  19. 根据权利要求17所述的装置，其特征在于，所述装置还包括：
    处理模块，用于获取第一用户面功能网元的信息，所述第一用户面功能网元用于进行组播数据的转发处理，所述第一用户面功能网元与所述第一组播组标识相关联。
  20. 根据权利要求19所述的装置，其特征在于，所述处理模块还用于：
    根据所述第一用户面功能网元的信息构建所述第一用户面功能网元和所述终端设备之间的数据传输路径。
  21. 根据权利要求19或20所述的装置，其特征在于，所述处理模块具体用于：
    通过所述收发模块向所述数据管理网元发送第四请求信息和所述第一组播组的标识，所述第四请求信息用于请求获取所述第一用户面功能网元的信息；以及
    通过所述收发模块接收来自所述数据管理网元的所述第一用户面功能网元的信息；或者，处理模块具体用于：
    通过所述收发模块向所述第一会话管理网元发送所述第四请求信息和所述第一组播组的标识；以及
    通过所述收发模块接收来自所述第一会话管理网元的所述第一用户面功能网元的信息。
  22. 根据权利要求15至21中任一项所述的装置，其特征在于，收发模块具体用于：
    接收来自所述终端设备的所述第一请求信息和所述第一组播组的标识；或者
    接收来自应用功能网元的所述第一请求信息和所述第一组播组的标识。
  23. 一种通信装置，其特征在于，包括：
    收发模块，用于接收来自终端设备的第一会话建立请求消息，所述第一会话建立请求消息用于请求建立所述终端设备与数据网络之间的第一会话，所述第一会话建立请求消息 包括第一会话管理网元的标识，所述第一会话管理网元用于进行组播会话管理；
    所述收发模块还用于向所述第一会话管理网元发送第一请求信息和第一组播组的标识，所述第一请求信息用于请求终端设备成为所述第一组播组的组播源，或者所述第一请求信息用于请求所述终端设备加入所述第一组播组。
  24. 根据权利要求23所述的装置，其特征在于，所述收发模块还用于：
    接收来自所述终端设备的所述第一请求信息和所述第一组播组的标识；以及
    向第二会话管理网元发送所述第一请求信息和所述第一组播组的标识。
  25. 根据权利要求24所述的装置，其特征在于，所述收发模块具体用于：
    接收来自所述终端设备的第二会话建立请求消息，所述第二会话建立请求消息包括所述第一请求信息和所述第一组播组的标识；或者
    接收来自所述终端设备的第二会话修改请求消息，所述第二会话修改请求消息包括所述第一请求信息和所述第一组播组的标识。
  26. 一种通信装置，其特征在于，包括：
    收发模块，用于接收来自第二会话管理网元的第一指示信息和第一会话管理网元的标识，所述第一会话管理网元用于进行组播会话管理，所述第一指示信息用于指示所述终端设备建立第一会话；
    所述收发模块还用于向移动管理网元发送第一会话建立请求消息，所述第一会话建立请求消息用于请求建立所述终端设备与数据网络之间的所述第一会话，所述第一会话建立请求消息包括第一会话管理网元的标识，所述第一会话管理网元用于进行组播会话管理。
  27. 根据权利要求26所述的装置，其特征在于，所述收发模块还用于：
    向移动管理网元发送第一请求信息和第一组播组标识，所述第一请求消息用于请求终端设备成为第一组播组的组播源，或者所述第一请求信息用于请求所述终端设备加入所述第一组播组。
  28. 根据权利要求27所述的装置，其特征在于，所述收发模块具体用于：
    向所述移动管理网元发送第二会话建立请求消息，所述第二会话建立请求消息包括所述第一请求信息和所述第一组播组的标识；或者，
    向所述移动管理网元发送第二会话修改请求消息，所述第二会话修改请求消息包括所述第一请求信息和所述第一组播组的标识。
  29. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序，当所述计算机程序在计算机上运行时，使得计算机执行如权利要求1至14中任一项所述的方法。
  30. 一种芯片，其特征在于，包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行如权利要求1至14中任一项所述的方法。
PCT/CN2022/081611 2021-04-09 2022-03-18 通信方法和通信装置 WO2022213792A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110387335.3 2021-04-09
CN202110387335.3A CN115209354B (zh) 2021-04-09 2021-04-09 通信方法和通信装置

Publications (1)

Publication Number Publication Date
WO2022213792A1 true WO2022213792A1 (zh) 2022-10-13

Family

ID=83545148

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/081611 WO2022213792A1 (zh) 2021-04-09 2022-03-18 通信方法和通信装置

Country Status (2)

Country Link
CN (1) CN115209354B (zh)
WO (1) WO2022213792A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118215157A (zh) * 2022-12-16 2024-06-18 大唐移动通信设备有限公司 数据转发方法、组播地址配置方法、网络侧设备和终端

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110167190A (zh) * 2018-02-14 2019-08-23 华为技术有限公司 会话建立方法和设备
CN111010673A (zh) * 2018-10-08 2020-04-14 华为技术有限公司 一种通信方法及装置
CN111200791A (zh) * 2018-11-19 2020-05-26 华为技术有限公司 群组通信方法、设备及系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110557265B (zh) * 2018-06-04 2021-08-31 华为技术有限公司 一种组播方法及装置
US11330667B2 (en) * 2019-05-03 2022-05-10 Ofinno, Llc Group communication signaling overload mitigation

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110167190A (zh) * 2018-02-14 2019-08-23 华为技术有限公司 会话建立方法和设备
CN111010673A (zh) * 2018-10-08 2020-04-14 华为技术有限公司 一种通信方法及装置
CN111200791A (zh) * 2018-11-19 2020-05-26 华为技术有限公司 群组通信方法、设备及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Update to Solution 15", 3GPP DRAFT; S2-1812414 UPDATE TO SOLUTION 15 - V8, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 20 November 2018 (2018-11-20), XP051499117 *

Also Published As

Publication number Publication date
CN115209354A (zh) 2022-10-18
CN115209354B (zh) 2024-01-30

Similar Documents

Publication Publication Date Title
US11917498B2 (en) Communication method and communications apparatus
EP3910913B1 (en) Data transmission method, device, and system
WO2021164564A1 (zh) 传输组播业务的方法和装置
JP2024529890A (ja) 通信方法および装置
WO2022089164A1 (zh) 多路径传输方法和通信装置
US12001890B2 (en) Communication method and apparatus, and network architecture
WO2021135650A1 (zh) 通信方法及装置
WO2021208861A1 (zh) 授权方法、策略控制功能设备和接入和移动管理功能设备
WO2021254353A1 (zh) 一种释放中继连接的方法、设备及系统
US20230156833A1 (en) Packet Forwarding Method, Apparatus, and System
WO2021218563A1 (zh) 用于传输数据的方法与装置
WO2021184271A1 (zh) 一种消息转发方法及装置
WO2021037271A1 (zh) 通信方法、设备及系统
WO2022213792A1 (zh) 通信方法和通信装置
EP4044614A1 (en) Method for establishing multicast session and network device
CN113473525A (zh) 一种数据传输的方法及装置
CN115226039B (zh) 组播通信方法及通信装置
WO2023012155A1 (en) Method and publisher-subscriber network
WO2024027302A1 (zh) 一种传输消息的方法和通信装置
WO2024041216A1 (zh) 一种通信方法、装置及设备
WO2024169468A1 (zh) 通信方法和通信装置
WO2023246404A1 (zh) 一种通信方法及装置
EP4344329A1 (en) Communication method and apparatus
WO2023001046A1 (zh) 一种通信方法及装置
WO2023066022A1 (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: 22783859

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

Country of ref document: EP

Kind code of ref document: A1