WO2024120132A1 - 组播组建立方法、设备、装置及存储介质 - Google Patents
组播组建立方法、设备、装置及存储介质 Download PDFInfo
- Publication number
- WO2024120132A1 WO2024120132A1 PCT/CN2023/131504 CN2023131504W WO2024120132A1 WO 2024120132 A1 WO2024120132 A1 WO 2024120132A1 CN 2023131504 W CN2023131504 W CN 2023131504W WO 2024120132 A1 WO2024120132 A1 WO 2024120132A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- terminal
- multicast group
- request message
- pdu session
- session management
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 147
- 238000007726 management method Methods 0.000 claims description 244
- 230000006870 function Effects 0.000 claims description 166
- 230000004048 modification Effects 0.000 claims description 54
- 238000012986 modification Methods 0.000 claims description 54
- 238000004590 computer program Methods 0.000 claims description 33
- 238000013523 data management Methods 0.000 claims description 28
- 230000008569 process Effects 0.000 description 31
- 238000010586 diagram Methods 0.000 description 20
- 230000005540 biological transmission Effects 0.000 description 14
- 238000012545 processing Methods 0.000 description 11
- 101150119040 Nsmf gene Proteins 0.000 description 7
- 230000000977 initiatory effect Effects 0.000 description 7
- 230000003287 optical effect Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000011664 signaling Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000007774 longterm Effects 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 3
- 101001121408 Homo sapiens L-amino-acid oxidase Proteins 0.000 description 2
- 102100026388 L-amino-acid oxidase Human genes 0.000 description 2
- 101150107050 PSA2 gene Proteins 0.000 description 2
- 101100012902 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) FIG2 gene Proteins 0.000 description 2
- 238000013475 authorization Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 101000827703 Homo sapiens Polyphosphoinositide phosphatase Proteins 0.000 description 1
- 102100023591 Polyphosphoinositide phosphatase Human genes 0.000 description 1
- 101100233916 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) KAR5 gene Proteins 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
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
- H04W4/08—User group management
Definitions
- the present disclosure relates to the field of wireless communication technology, and in particular to a method, device, apparatus and storage medium for establishing a multicast group.
- the establishment of multicast groups in the 5th generation mobile communication (5G) Local Area Network (LAN) scenario is based on application configuration, and requires the terminal (also known as user equipment (UE)) to actively apply to join the target multicast group.
- 5G 5th generation mobile communication
- UE user equipment
- the conference notifier as a terminal, hopes to establish a multicast group so that all registered conference users can receive live broadcast-related information.
- 5G LAN does not have any solution for the process of establishing a multicast group within a virtual network (VN) group actively initiated by a group member terminal.
- VN virtual network
- the embodiments of the present disclosure provide a method, device, apparatus and storage medium for establishing a multicast group.
- an embodiment of the present disclosure provides a method for establishing a multicast group, which is applied to a first terminal and includes:
- PDU session establishment request message Sending a first protocol data unit (PDU) session establishment request message, where the first PDU session establishment request message includes an application layer identifier of the first terminal and an application layer identifier of a second terminal;
- PDU protocol data unit
- the second terminal and the first terminal belong to the same virtual network VN group.
- the method after sending the first PDU session establishment request message, the method further includes:
- a first PDU session establishment completion message is received, where the first PDU session establishment completion message includes first information, where the first information is used to indicate whether the network allows the first terminal to establish a multicast group.
- the embodiment of the present disclosure further provides a method for establishing a multicast group, which is applied to a session management function, including:
- the first create session management context request message includes an application layer identifier of a first terminal and an application layer identifier of a second terminal; wherein the first terminal is a terminal that initiates establishment of a multicast group, and the second terminal and the first terminal belong to the same virtual network VN group;
- determining whether to allow the first terminal to establish a multicast group according to the first create session management context request message includes:
- the application layer identifier of the first terminal query the unified data management function whether the first terminal is allowed to establish a multicast group.
- the method further includes:
- a first request message is sent to the second terminal, where the first request message is used to request the second terminal to join a target multicast group, where the target multicast group is a multicast group initiated and established by the first terminal.
- the first request message includes multicast address information of the target multicast group.
- the method further includes:
- determining whether to allow the second terminal to join the target multicast group according to the second create session management context request message or the first update session management context request message includes:
- the second create session management context request message or the first update session management context request message query a unified data management function and/or a policy control function whether the second terminal is allowed to join the target multicast group.
- the method further includes:
- the data matching and forwarding rule of the target multicast group is sent to a user plane function on a protocol data unit (PDU) session path of the second terminal.
- PDU protocol data unit
- the method further comprises:
- a group-level session modification request message is sent to a user plane function on the PDU session path of the first terminal, wherein the group-level session modification request message includes a data matching and forwarding rule of the target multicast group.
- the method further comprises:
- a first PDU session establishment completion message is sent to the first terminal, where the first PDU session establishment completion message includes first information, and the first information is used to indicate whether the network allows the first terminal to establish a multicast group.
- the method further comprises:
- a second PDU session establishment completion message is sent to the second terminal, where the second PDU session establishment completion message includes second information, and the second information is used to indicate whether the second terminal successfully joins the target multicast group.
- the embodiment of the present disclosure further provides a method for establishing a multicast group, which is applied to a second terminal, including:
- the target multicast group is a multicast group initiated and established by the first terminal, and the first terminal and the second terminal belong to the same virtual network VN group;
- a second protocol data unit PDU session establishment request message or a first PDU session modification request message is sent, wherein the second PDU session establishment request message or the first PDU session modification request message includes the application layer identifier of the second terminal and the multicast address information of the target multicast group.
- the first request message includes multicast address information of the target multicast group.
- the method further includes:
- a second PDU session establishment completion message is received, where the second PDU session establishment completion message includes second information, where the second information is used to indicate whether the second terminal successfully joins the target multicast group.
- an embodiment of the present disclosure further provides a first terminal, including a memory, a transceiver, and a processor;
- a memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
- PDU session establishment request message Sending a first protocol data unit (PDU) session establishment request message, where the first PDU session establishment request message includes an application layer identifier of the first terminal and an application layer identifier of a second terminal;
- PDU protocol data unit
- the second terminal and the first terminal belong to the same virtual network VN group.
- the operation after sending the first PDU session establishment request message, the operation further includes:
- a first PDU session establishment completion message is received, where the first PDU session establishment completion message includes first information, where the first information is used to indicate whether the network allows the first terminal to establish a multicast group.
- the embodiments of the present disclosure further provide a session management function, including a memory, a transceiver, and a processor;
- a memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
- the first create session management context request message includes an application layer identifier of a first terminal and an application layer identifier of a second terminal; wherein the first terminal is a terminal that initiates establishment of a multicast group, and the second terminal and the first terminal belong to the same virtual network VN group;
- determining whether to allow the first terminal to establish a multicast group according to the first create session management context request message includes:
- the application layer identifier of the first terminal query the unified data management function whether the first terminal is allowed to establish a multicast group.
- the operation when it is determined that the first terminal is allowed to establish a multicast group, the operation further includes:
- a first request message is sent to the second terminal, where the first request message is used to request the second terminal to join a target multicast group, where the target multicast group is a multicast group initiated and established by the first terminal.
- the first request message includes multicast address information of the target multicast group.
- the operation after sending the first request message to the second terminal, the operation further includes:
- the determining, according to the second create session management context request message or the first update session management context request message, whether to allow the second terminal to join the Target multicast group including:
- the second create session management context request message or the first update session management context request message query a unified data management function and/or a policy control function whether the second terminal is allowed to join the target multicast group.
- the operation when it is determined that the second terminal is allowed to join the target multicast group, the operation further includes:
- the data matching and forwarding rule of the target multicast group is sent to a user plane function on a protocol data unit (PDU) session path of the second terminal.
- PDU protocol data unit
- the operations further include:
- a group-level session modification request message is sent to a user plane function on the PDU session path of the first terminal, wherein the group-level session modification request message includes a data matching and forwarding rule of the target multicast group.
- the operations further include:
- a first PDU session establishment completion message is sent to the first terminal, where the first PDU session establishment completion message includes first information, and the first information is used to indicate whether the network allows the first terminal to establish a multicast group.
- the operations further include:
- a second PDU session establishment completion message is sent to the second terminal, where the second PDU session establishment completion message includes second information, and the second information is used to indicate whether the second terminal successfully joins the target multicast group.
- an embodiment of the present disclosure further provides a second terminal, including a memory, a transceiver, and a processor;
- a memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
- the target multicast group is a multicast group initiated and established by the first terminal, and the first terminal and the second terminal belong to the same virtual network VN group;
- a second protocol data unit PDU session establishment request message is sent Or a first PDU session modification request message, the second PDU session establishment request message or the first PDU session modification request message includes the application layer identifier of the second terminal and the multicast address information of the target multicast group.
- the first request message includes multicast address information of the target multicast group.
- the operation after sending the second PDU session establishment request message, the operation further includes:
- a second PDU session establishment completion message is received, where the second PDU session establishment completion message includes second information, where the second information is used to indicate whether the second terminal successfully joins the target multicast group.
- an embodiment of the present disclosure further provides a multicast group establishment device, including:
- a first sending unit configured to send a first protocol data unit (PDU) session establishment request message, wherein the first PDU session establishment request message includes an application layer identifier of a first terminal and an application layer identifier of a second terminal;
- PDU protocol data unit
- the second terminal and the first terminal belong to the same virtual network VN group.
- an embodiment of the present disclosure further provides a multicast group establishment device, including:
- a second receiving unit is used to receive a first create session management context request message sent by an access and mobility management function, wherein the first create session management context request message includes an application layer identifier of a first terminal and an application layer identifier of a second terminal; wherein the first terminal is a terminal that initiates establishment of a multicast group, and the second terminal and the first terminal belong to the same virtual network VN group;
- a determining unit is used to determine whether to allow the first terminal to establish a multicast group according to the first create session management context request message.
- an embodiment of the present disclosure further provides a multicast group establishment device, including:
- a third receiving unit is used to receive a first request message, where the first request message is used to request the second terminal to join a target multicast group;
- the target multicast group is a multicast group initiated and established by the first terminal, and the first terminal and the second terminal belong to the same virtual network VN group;
- the third sending unit is used to send a second protocol data unit PDU session establishment request message or a first PDU session modification request message according to the first request message, and the second PDU session establishment
- the request message or the first PDU session modification request message includes the application layer identifier of the second terminal and the multicast address information of the target multicast group.
- the embodiment of the present disclosure also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the multicast group establishment method described in the first aspect, or execute the multicast group establishment method described in the second aspect, or execute the multicast group establishment method described in the third aspect.
- the embodiment of the present disclosure also provides a communication device, in which a computer program is stored, and the computer program is used to enable the communication device to execute the multicast group establishment method described in the first aspect, or execute the multicast group establishment method described in the second aspect, or execute the multicast group establishment method described in the third aspect.
- an embodiment of the present disclosure further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the multicast group establishment method described in the first aspect as described above, or execute the multicast group establishment method described in the second aspect as described above, or execute the multicast group establishment method described in the third aspect as described above.
- the embodiment of the present disclosure also provides a chip product, in which a computer program is stored, and the computer program is used to enable the chip product to execute the multicast group establishment method described in the first aspect as described above, or execute the multicast group establishment method described in the second aspect as described above, or execute the multicast group establishment method described in the third aspect as described above.
- the multicast group establishment method, device, apparatus and storage medium provided by the embodiments of the present disclosure implement the process of establishing a multicast group initiated by the terminal by carrying the terminal application layer identifier of the multicast group that the terminal wants to establish when initiating a PDU session establishment request, thereby simplifying the method of establishing the multicast group and reducing signaling interaction.
- FIG1 is a schematic diagram of a terminal transmitting multicast data within a multicast group provided by a related art
- FIG. 2 is a flow chart of a terminal requesting to join a multicast group provided by the related art
- FIG3 is a flowchart of a method for establishing a multicast group according to an embodiment of the present disclosure
- FIG4 is a second flow chart of a method for establishing a multicast group provided in an embodiment of the present disclosure
- FIG5 is a third flow chart of a method for establishing a multicast group provided in an embodiment of the present disclosure
- FIG. 6 is a flow chart of a terminal establishing a PDU session and a multicast group according to an embodiment of the present disclosure
- FIG. 7 is a flowchart of a terminal joining a multicast group provided in an embodiment of the present disclosure.
- FIG. 8 is a second flowchart of a terminal joining a multicast group provided in an embodiment of the present disclosure
- FIG9 is a schematic diagram of the structure of a first terminal provided in an embodiment of the present disclosure.
- FIG10 is a schematic diagram of the structure of a session management function provided in an embodiment of the present disclosure.
- FIG. 11 is a schematic diagram of the structure of a second terminal provided in an embodiment of the present disclosure.
- FIG12 is a schematic diagram of a structure of a device for establishing a multicast group provided in an embodiment of the present disclosure
- FIG. 13 is a second structural diagram of a multicast group establishment device provided in an embodiment of the present disclosure.
- FIG. 14 is a third schematic diagram of the structure of the multicast group establishment device provided in an embodiment of the present disclosure.
- the term "and/or” describes the association relationship of associated objects, indicating that three relationships may exist.
- a and/or B may represent three situations: A exists alone, A and B exist at the same time, and B exists alone.
- the character "/" generally indicates that the associated objects before and after are in an "or” relationship.
- plurality in the embodiments of the present disclosure refers to two or more than two, and other quantifiers are similar thereto.
- FIG1 is a schematic diagram of a terminal transmitting multicast data in a multicast group provided by the related art.
- UE1, UE3, UE4 and UE6 belong to the same VN group, wherein UE1, UE3 and UE4 belong to the same multicast group in the VN group.
- Protocol Data Unit (PDU) Session Anchor (PSA) 1 is the PSA corresponding to the PDU session between UE1 and UE4, and PSA2 is the PSA corresponding to the PDU session between UE3 and UE6.
- PDU Protocol Data Unit
- PSA2 is the PSA corresponding to the PDU session between UE3 and UE6.
- UE1 sends multicast data to UE4 via PSA1, and sends multicast data to UE3 via PSA1 and PSA2.
- the process of UE1, UE3 and UE4 joining the multicast group is shown in Figure 2.
- FIG2 is a flow chart of a terminal requesting to join a multicast group provided by the related art. As shown in FIG2 , the process of UE1, UE3 and UE4 requesting to join a multicast group includes:
- Step 1 Group members UE1, UE3, UE4 and UE6 respectively establish PDU sessions to the same data network name (Data Network Name, DNN) and single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI).
- Data Network Name DNN
- S-NSSAI Single Network Slice Selection Assistance Information
- the Session Management Function sends the following user plane rules to PSA when the PDU session is established: SMF sets the relevant value to the Usage Reporting Rule (URR) reporting trigger (Reporting trigger) of "Internet Protocol (IP) multicast join/leave”.
- URR Usage Reporting Rule
- PCF Policy Control Function
- PCF Policy Control Request Trigger
- Step 2 UE1 uses the user of the PDU session to send an Internet Group Management Protocol (IGMP) join message to its PSA1.
- IGMP Internet Group Management Protocol
- Step 3a After PSA1 receives the IGMP join message, it processes the message according to the N4 rule in the PDU session:
- PSA1 adds this PDU session to the requested multicast
- PSA1 If SMF sends a URR to PSA1, PSA1 notifies SMF that UE1 joins a multicast group and carries the IP multicast address information to SMF;
- PSA1 will not add this PDU session to the multicast group.
- Step 3b PSA1 reports "IP multicast join" to SMF according to URR.
- Step 3c SMF triggers the session management (SM) policy modification process to PCF.
- SM session management
- Step 4 UE3 and UE4 request to join the multicast group.
- the steps are the same as the above steps 2-3.
- the establishment of multicast groups in 5G LAN scenarios is based on application configuration, and the UE needs to actively apply to join the target multicast group.
- some application scenarios such as large-scale live broadcasts to notify all users who have registered for a conference of live conference-related messages
- the UE needs to join the multicast group where the conference is located in order to receive relevant information about the conference live broadcast.
- the method that requires a UE to initiate the process of establishing a multicast group is not perfect.
- the conference notification party as a UE, hopes to establish a multicast group to complete the sending of live broadcast-related information to all users who have registered for the conference.
- the embodiments of the present disclosure provide a multicast group establishment method, device, electronic device and storage medium, which can implement the multicast group establishment process initiated by the UE during the PDU session establishment process.
- FIG. 3 is a flow chart of a method for establishing a multicast group provided in an embodiment of the present disclosure. The method is applied to a first terminal. As shown in FIG. 3 , the method includes the following steps:
- Step 300 Send a first PDU session establishment request message, where the first PDU session establishment request message includes an application layer identifier of a first terminal and an application layer identifier of a second terminal.
- the second terminal and the first terminal belong to the same virtual network VN group.
- the first terminal is any terminal that initiates the establishment of a multicast group
- the second terminal is a member terminal that the first terminal invites to join the multicast group.
- the first terminal and the second terminal belong to the same VN group.
- the second terminal may include one or more terminals.
- the first terminal When the first terminal needs to initiate the establishment of a multicast group, the first terminal can carry the application layer identifier of the first terminal and the application layer identifier of the second terminal in its PDU session establishment request message (i.e., PDU Session Establishment Request).
- PDU Session Establishment Request i.e., PDU Session Establishment Request
- the network side can decide whether to allow the first terminal to establish a group including the second terminal based on the application layer identifier of the first terminal and the application layer identifier of the second terminal. broadcast group.
- the application layer identifier of the terminal can be a Generic Public Subscription Identifier (GPSI).
- GPSI Generic Public Subscription Identifier
- the multicast group establishment method provided by the embodiment of the present disclosure implements the process of establishing a multicast group initiated by the terminal by carrying the terminal application layer identifier of the multicast group that the terminal wants to establish when initiating a PDU session establishment request, simplifies the way of establishing the multicast group, and reduces signaling interaction.
- the method after sending the first PDU session establishment request message, the method further includes:
- a first PDU session establishment completion message is received, where the first PDU session establishment completion message includes first information, and the first information is used to indicate whether the network allows the first terminal to establish a multicast group.
- the network side can decide whether to allow the first terminal to establish a multicast group including the second terminal based on the application layer identifier of the first terminal and the application layer identifier of the second terminal, and send a first PDU session establishment completion message (i.e., PDU Session Establishment Accept) to the first terminal.
- the first PDU session establishment completion message includes first information, indicating whether the network allows the first terminal to establish a multicast group.
- the first terminal After receiving the first PDU session establishment completion message, the first terminal can know whether the multicast group is allowed to be established, and then perform corresponding subsequent processing.
- the first terminal sends a first PDU session establishment request message to the AMF.
- the AMF can carry the application layer identifier of the first terminal and the application layer identifier of the second terminal in a first create session management context request message (i.e., Nsmf PDU Session CreateSMContext Request) and send it to the SMF.
- the SMF can determine whether the first terminal is allowed to establish a multicast group based on the first create session management context request message, and carry first information in a first PDU session establishment completion message sent to the first terminal, indicating whether the first terminal is allowed to establish a multicast group.
- FIG. 4 is a second flow chart of a method for establishing a multicast group provided in an embodiment of the present disclosure. The method is applied to a session management function. As shown in FIG. 4 , the method includes the following steps:
- Step 400 Receive a first create session management context request message sent by an access and mobility management function, wherein the first create session management context request message includes an application layer identifier of the first terminal. and the application layer identifier of the second terminal; wherein the first terminal is the terminal that initiates the establishment of a multicast group, and the second terminal and the first terminal belong to the same virtual network VN group.
- Step 410 Determine whether to allow the first terminal to establish a multicast group according to the first create session management context request message.
- the session management function described in the present disclosure includes the SMF in the 5G network system, or a network element with similar functions to the SMF in a future network system (such as 6G).
- the access and mobility management function includes AMF in the 5G network system, or a network element with similar functions to AMF in a future network system (such as 6G).
- the first terminal is any terminal that initiates the establishment of a multicast group
- the second terminal is a member terminal that the first terminal invites to join the multicast group.
- the first terminal and the second terminal belong to the same VN group.
- the second terminal may include one or more terminals.
- the first terminal can carry the application layer identifier of the first terminal and the application layer identifier of the second terminal in its PDU session establishment request message (i.e., PDU Session Establishment Request).
- the application layer identifier of the terminal can be GPSI.
- the first terminal may send a first PDU session establishment request message to the access and mobility management function.
- the access and mobility management function may carry the application layer identifier of the first terminal and the application layer identifier of the second terminal in a first create session management context request message (i.e., Nsmf PDU Session CreateSMContext Request) and send it to the session management function.
- a first create session management context request message i.e., Nsmf PDU Session CreateSMContext Request
- the session management function may determine whether to allow the first terminal to establish a multicast group based on the first create session management context request message.
- the multicast group establishment method provided by the embodiment of the present disclosure can determine whether the terminal is allowed to establish a multicast group based on the terminal application layer identifier carried by the terminal when initiating a PDU session establishment request, thereby supporting the terminal to initiate the establishment of a multicast group, simplifying the establishment method of the multicast group and reducing signaling interaction.
- determining whether to allow the first terminal to establish a multicast group according to the first create session management context request message includes:
- the unified data management function is queried whether the first terminal is allowed to establish a multicast group.
- the unified data management function described in the present disclosure includes UDM in a 5G network system, or a network element with similar functions to UDM in a future network system (such as 6G).
- the session management function can interact with the unified data management function and query the unified data management function for terminal information that can initiate multicast group establishment through the application layer identifier of the first terminal to determine whether the first terminal is allowed to establish a multicast group.
- the application function may pre-configure the terminal information in the relevant VN group that can initiate the establishment of a multicast group to the unified data management function, the policy control function, etc.
- the method when it is determined that the first terminal is allowed to establish a multicast group, the method further includes:
- a first request message is sent to the second terminal, where the first request message is used to request the second terminal to join a target multicast group, where the target multicast group is a multicast group initiated and established by the first terminal.
- the session management function may send a first request message to the second terminal to request the second terminal to join the multicast group established by the first terminal.
- the session management function may send the first request message to the second terminal via the access and mobility management function and a network device (eg, a base station).
- a network device eg, a base station
- the first request message may include multicast address information of the target multicast group.
- a multicast address can be allocated to the multicast group; alternatively, the session management function can determine the multicast address information of the target multicast group based on the configuration of the application function, such as the application function pre-configuring the multicast address information of the multicast group established by the first terminal to the unified data management function, and the session management function can query the unified data management function for the multicast address information of the target multicast group when needed; alternatively, the multicast address information of the target multicast group can be configured in the first terminal before or after the first terminal establishes the PDU session, such as the multicast address information of the target multicast group is pre-configured in the first terminal, and the first terminal can carry the multicast address information in the message of initiating the PDU session establishment request and send it to the session management function.
- the method further includes:
- the second terminal when the second terminal receives the first request message, if the PDU session has not been established, the second terminal can initiate a PDU session establishment request (i.e., PDU Session Establishment Request).
- PDU session Establishment Request carries the application layer identifier of the second terminal and the multicast address information of the target multicast group, for requesting to join the target multicast group.
- the multicast address information of the target multicast group may be sent to the second terminal by a session management function, or may be pre-configured in the second terminal.
- the access and mobility management function After the access and mobility management function receives the PDU session establishment request initiated by the second terminal, it can send a second create session management context request message (i.e., Nsmf PDU Session CreateSMContext Request) to the session management function.
- the second create session management context request message includes the application layer identifier of the second terminal and the multicast address information of the target multicast group.
- the session management function may determine whether to allow the second terminal to join the target multicast group according to the second create session management context request message.
- the second terminal when the second terminal receives the first request message, if a PDU session has been established, the second terminal can initiate a PDU session modification request (i.e., PDU Session Modification Request).
- PDU session modification request carries the application layer identifier of the second terminal and the multicast address information of the target multicast group, for requesting to join the target multicast group.
- the access and mobility management function After the access and mobility management function receives the PDU session establishment request initiated by the second terminal, it can send a first update session management context request message (i.e., Nsmf PDU Session_UpdateSMContext Request) to the session management function.
- the first update session management context request message includes the application layer identifier of the second terminal and the multicast address information of the target multicast group.
- the session management function After receiving the first update session management context request message, the session management function can According to the first update session management context request message, it is determined whether to allow the second terminal to join the target multicast group.
- determining whether to allow the second terminal to join the target multicast group according to the second create session management context request message or the first update session management context request message includes:
- the second create session management context request message or the first update session management context request message query the unified data management function and/or the policy control function whether the second terminal is allowed to join the target multicast group.
- the policy control function described in the present disclosure includes PCF in a 5G network system, or a network element with similar functions to PCF in a future network system (such as 6G).
- the session management function may interact with the unified data management function and/or the policy control function to determine whether to allow the second terminal to join the target multicast group.
- the session management function may query the unified data management function for configuration information of the second terminal or terminal information allowed to join the target multicast group (which may be configured to the unified data management function by the application function) to determine whether the second terminal is allowed to join the target multicast group.
- the session management function when acquiring session management related policy information from the policy control function, may determine whether the second terminal is allowed to join the target multicast group based on information about whether the second terminal is allowed to join the multicast group acquired by the policy control function.
- the method when it is determined that the second terminal is allowed to join the target multicast group, the method further includes:
- the data matching and forwarding rule of the target multicast group is sent to the user plane function on the protocol data unit PDU session path of the second terminal.
- the user plane function described in the present disclosure includes the UPF in the 5G network system, or a network element with similar functions to the UPF in a future network system (such as 6G).
- the session management function determines that the second terminal is allowed to join the target multicast group
- the user plane matching and forwarding rules can be issued for the PDU session of the second terminal, and the data matching and forwarding rules about the target multicast group are sent to the user plane function on the PDU session path of the second terminal. For example, when a data packet with a destination address of the multicast address of the target multicast group is received, it is forwarded to the second terminal.
- the method further comprises:
- a group-level session modification request message is sent to a user plane function on a PDU session path of the first terminal, where the group-level session modification request message includes data matching and forwarding rules of the target multicast group.
- the session management function when it determines that the second terminal is allowed to join the target multicast group, it can also send corresponding data matching and forwarding rules about the target multicast group to the user plane function on the PDU session path of the first terminal through a group-level session modification request message (such as a group-level N4 session modification request message, Group level N4Session Modification).
- a group-level session modification request message such as a group-level N4 session modification request message, Group level N4Session Modification.
- the method further comprises:
- a first PDU session establishment completion message is sent to the first terminal, where the first PDU session establishment completion message includes first information, and the first information is used to indicate whether the network allows the first terminal to establish a multicast group.
- the session management function receives the PDU session establishment request initiated by the first terminal and determines whether the first terminal is allowed to establish a multicast group
- the first information can be carried in the first PDU session establishment completion message (i.e., PDU Session Establishment Accept) sent to the first terminal, indicating whether the first terminal is allowed to establish a multicast group.
- the method further comprises:
- a second PDU session establishment completion message is sent to the second terminal, where the second PDU session establishment completion message includes second information, and the second information is used to indicate whether the second terminal successfully joins the target multicast group.
- the second information can be carried in the second PDU session establishment completion message (i.e., PDU Session Establishment Accept) sent to the second terminal, indicating whether the second terminal has successfully joined the target multicast group.
- PDU Session Establishment Accept i.e., PDU Session Establishment Accept
- FIG. 5 is a third flow chart of a method for establishing a multicast group provided in an embodiment of the present disclosure. The method is applied to a second terminal. As shown in FIG. 5 , the method includes the following steps:
- Step 500 Receive a first request message, where the first request message is used to request the second terminal to join a target multicast group; the target multicast group is a multicast group initiated and established by the first terminal, and the first terminal and the second terminal belong to the same virtual network VN group.
- Step 510 Send a second protocol data unit PDU session establishment request message or a first PDU session modification request message according to the first request message, the second PDU session establishment request message or the first
- the PDU session modification request message includes the application layer identifier of the second terminal and the multicast address information of the target multicast group.
- the first terminal is any terminal that initiates the establishment of a multicast group
- the second terminal is a member terminal that the first terminal invites to join the multicast group.
- the first terminal and the second terminal belong to the same VN group.
- the second terminal may include one or more terminals.
- the first terminal can carry the application layer identifier of the first terminal and the application layer identifier of the second terminal in its PDU session establishment request message (i.e., PDU Session Establishment Request).
- the application layer identifier of the terminal can be GPSI.
- the first terminal may send a first PDU session establishment request message to the access and mobility management function.
- the access and mobility management function may carry the application layer identifier of the first terminal and the application layer identifier of the second terminal in a first create session management context request message (i.e., Nsmf PDU Session CreateSMContext Request) and send it to the session management function.
- a first create session management context request message i.e., Nsmf PDU Session CreateSMContext Request
- the session management function may determine whether to allow the first terminal to establish a multicast group based on the first create session management context request message.
- the session management function After the session management function determines that the first terminal is allowed to establish a multicast group, it may send a first request message to the second terminal, requesting the second terminal to join the multicast group initiated and established by the first terminal.
- the session management function may send the first request message to the second terminal via the access and mobility management function and the network device (eg, a base station).
- the network device eg, a base station
- the first request message may include multicast address information of the target multicast group.
- the second terminal when the second terminal receives the first request message, if the PDU session has not been established, the second terminal may initiate a PDU session establishment request (i.e., PDU Session Establishment Request).
- PDU session Establishment Request carries the application layer identifier of the second terminal and the multicast address information of the target multicast group, for requesting to join the target multicast group.
- the multicast address information of the target multicast group may be sent to the second terminal by a session management function, or may be pre-configured in the second terminal.
- a second create session management context request message (ie, Nsmf PDU Session CreateSMContext Request) is sent to the session management function, wherein the second create session management context request message includes an application layer identifier of the second terminal and multicast address information of the target multicast group.
- the session management function may determine whether to allow the second terminal to join the target multicast group according to the second create session management context request message.
- the second terminal when the second terminal receives the first request message, if a PDU session has been established, the second terminal can initiate a PDU session modification request (i.e., PDU Session Modification Request).
- PDU session modification request carries the application layer identifier of the second terminal and the multicast address information of the target multicast group, for requesting to join the target multicast group.
- the multicast address information of the target multicast group may be sent to the second terminal by a session management function, or may be pre-configured in the second terminal.
- the access and mobility management function After the access and mobility management function receives the PDU session establishment request initiated by the second terminal, it can send a first update session management context request message (i.e., Nsmf PDU Session_UpdateSMContext Request) to the session management function.
- the first update session management context request message includes the application layer identifier of the second terminal and the multicast address information of the target multicast group.
- the session management function can determine whether to allow the second terminal to join the target multicast group according to the first update session management context request message.
- the multicast group establishment method implements the process of establishing a multicast group initiated by the terminal, simplifies the method of establishing a multicast group, and reduces signaling interaction after the terminal receives a request to join the multicast group sent by the session management function, and then joins the multicast group by creating or modifying a PDU session request.
- the method further includes:
- a second PDU session establishment completion message is received, where the second PDU session establishment completion message includes second information, and the second information is used to indicate whether the second terminal successfully joins the target multicast group.
- the second PDU session establishment completion message (ie, PDU Session Establishment Accept) sent to the second terminal may carry the second Information indicating whether the second terminal successfully joins the target multicast group.
- Embodiment 1 UE1 establishes a PDU session and a multicast group.
- FIG6 is a flow chart of establishing a PDU session and a multicast group by a terminal according to an embodiment of the present disclosure.
- UE1 requests to establish a multicast group including UE2 and UE3 while establishing a PDU session, and the main process includes:
- the application function AF configures the UE information that can initiate the establishment of a multicast group in the relevant VN group.
- UE1 sends a PDU session establishment request, carrying its own application layer identifier and the application layer identifier of the VN group member with which it wants to establish a multicast group, such as GPSI.
- the access and mobility management function AMF selects the session management function SMF.
- AMF forwards the application layer identifiers of UE1 and the members of the same VN group with which it wants to establish a multicast group to SMF.
- SMF interacts with the unified data management (UDM) to obtain SM-related contract information, as well as configuration information on whether UE1 configured by AF can initiate multicast group establishment, and subscribe to information updates.
- UDM unified data management
- SMF sends a create session management context response message to AMF.
- SMF selects the policy control function PCF.
- SMF initiates the session management policy association establishment or session management policy association modification process.
- SMF selects the user plane function UPF.
- SMF initiates the session management policy association modification process.
- SMF interacts with UPF (N4 session establishment request/response).
- the SMF determines whether to allow the current UE1 to establish a multicast group based on the information in steps 4 and 5.
- SMF continues to execute steps 13-14 related to other session establishment, and carries an indicator that multicast group establishment is not allowed in the PDU Session Establish Accept message.
- SMF determines whether the multicast group target members UE2 and UE3 have established a PDU session:
- UE2 or UE3 has not established a PDU session yet, refer to the second embodiment.
- the multicast address of the multicast group initiated by UE1 is:
- a. SMF can allocate a multicast address to the multicast group in this step.
- the multicast address of this multicast group can be configured based on AF.
- the multicast address of the multicast group may be configured in UE1 before or after UE1 establishes the PDU session.
- the network sends a PDU Session Establishment Accept message to the UE through SMF, which carries identification information of whether UE1 is allowed to establish a multicast group.
- Embodiment 2 UE2 or UE3 has not established a PDU session.
- FIG7 is one of the flowcharts of a terminal joining a multicast group provided by an embodiment of the present disclosure. As shown in FIG7 , when UE2 or UE3 joins a multicast group established by UE1 without establishing a PDU session, the main process includes:
- the session management function SMF sends a message to UE2/UE3 through the access and mobility management function AMF, carrying the multicast address of the multicast group established by the UE1 session.
- UE2/UE3 initiates a PDU session establishment request, carrying the multicast address it received.
- the multicast address of UE2/UE3 can also come from the configuration before the UE2/UE3 session is established.
- SMF obtains the configuration information of whether UE2/UE3 joins the multicast group from the unified data management UMD. (Optional)
- SMF sends a create session management context response message to AMF.
- SMF selects the policy control function PCF.
- SMF obtains SM-related policy information from PCF
- SMF can make a judgment based on PCF's information on whether the UE is allowed to join the multicast group. (Optional)
- SMF selects the user plane function UPF.
- SMF initiates session management policy association modification.
- SMF When SMF performs user plane matching and forwarding rules for this session, it carries the matching forwarding rules of the relevant multicast group. For example, when the received destination address is the above multicast address, it is forwarded to UE2/UE3.
- the network adds an indicator of whether the network has successfully joined the above multicast group to the PDU Session Establishment Accept message of UE2/UE3 through SMF.
- Embodiment 3 UE2 or UE3 has established a PDU session.
- FIG8 is a second flowchart of a terminal joining a multicast group provided by an embodiment of the present disclosure. As shown in FIG8 , when UE2 or UE3 has established a PDU session, it joins the multicast group established by UE1, and the main process includes:
- the session management function SMF sends a message to UE2/UE3 through the access and mobility management function AMF, carrying the multicast address of the multicast group established by UE1.
- UE2/UE3 informs SMF of the received multicast address and its own application layer identifier.
- SMF interacts with the policy management function PCF/unified data management UDM to determine whether the current UE is allowed to join the multicast group.
- the user plane function UPF on the PDU session path of SMF and UE2/UE3 interacts to add matching and forwarding rules for multicast group data.
- the SMF sends the data matching and forwarding rules of the multicast group to the UPF on the PDU session path of UE1 in the same multicast group through the group-level N4 session modification request.
- the methods and devices provided in the various embodiments of the present disclosure are based on the same application concept. Since the methods and devices solve problems based on similar principles, the implementation of the devices and methods can refer to each other, and the repeated parts will not be repeated.
- FIG9 is a schematic diagram of the structure of a first terminal provided in an embodiment of the present disclosure.
- the first terminal includes a memory 920, a transceiver 910, and a processor 900; wherein the processor 900 and the memory 920 may also be arranged physically separately.
- the memory 920 is used to store computer programs; the transceiver 910 is used to send and receive data under the control of the processor 900.
- the transceiver 910 is used to receive and send data under the control of the processor 900 .
- the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 900 and various circuits of memory represented by memory 920 are linked together.
- the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits together, which are all well known in the art, and therefore, the present disclosure will not further describe them.
- the bus interface provides an interface.
- the transceiver 910 can be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, and these transmission media include transmission media such as wireless channels, wired channels, and optical cables.
- the user interface 930 can also be an interface that can be connected to external and internal devices, and the connected devices include but are not limited to keypads, displays, speakers, microphones, joysticks, etc.
- the processor 900 is responsible for managing the bus architecture and general processing, and the memory 920 can store data used by the processor 900 when performing operations.
- the processor 900 can be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD).
- the processor can also adopt a multi-core architecture.
- the processor 900 is configured to execute any of the methods provided by the embodiments of the present disclosure according to the obtained executable instructions by calling the computer program stored in the memory 920, for example: sending a first protocol data unit PDU session establishment request message, where the first PDU session establishment request message includes an application layer identifier of the first terminal and an application layer identifier of the second terminal;
- the second terminal and the first terminal belong to the same virtual network VN group.
- the method after sending the first PDU session establishment request message, the method further includes:
- a first PDU session establishment completion message is received, where the first PDU session establishment completion message includes first information, and the first information is used to indicate whether the network allows the first terminal to establish a multicast group.
- FIG10 is a schematic diagram of the structure of the session management function provided in the embodiment of the present disclosure.
- the session management function includes a memory 1020, a transceiver 1010 and a processor 1000; wherein the processor The device 1000 and the memory 1020 may also be arranged physically separately.
- the memory 1020 is used to store computer programs; the transceiver 1010 is used to send and receive data under the control of the processor 1000.
- the transceiver 1010 is used to receive and send data under the control of the processor 1000 .
- the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1000 and various circuits of memory represented by memory 1020 are linked together.
- the bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described in this disclosure.
- the bus interface provides an interface.
- the transceiver 1010 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which may include a wireless channel, a wired channel, an optical cable, and other transmission media.
- the processor 1000 is responsible for managing the bus architecture and general processing, and the memory 1020 can store data used by the processor 1000 when performing operations.
- the processor 1000 may be a CPU, an ASIC, an FPGA or a CPLD, and the processor may also adopt a multi-core architecture.
- the processor 1000 is configured to execute any of the methods provided by the embodiments of the present disclosure according to the obtained executable instructions by calling the computer program stored in the memory 1020, for example: receiving a first create session management context request message sent by an access and mobility management function, wherein the first create session management context request message includes an application layer identifier of a first terminal and an application layer identifier of a second terminal; wherein the first terminal is a terminal that initiates establishment of a multicast group, and the second terminal and the first terminal belong to the same virtual network VN group;
- determining whether to allow the first terminal to establish a multicast group according to the first create session management context request message includes:
- the unified data management function is queried whether the first terminal is allowed to establish a multicast group.
- the method when it is determined that the first terminal is allowed to establish a multicast group, the method further include:
- a first request message is sent to the second terminal, where the first request message is used to request the second terminal to join a target multicast group, where the target multicast group is a multicast group initiated and established by the first terminal.
- the first request message includes multicast address information of the target multicast group.
- the method further includes:
- determining whether to allow the second terminal to join the target multicast group according to the second create session management context request message or the first update session management context request message includes:
- the second create session management context request message or the first update session management context request message query the unified data management function and/or the policy control function whether the second terminal is allowed to join the target multicast group.
- the method when it is determined that the second terminal is allowed to join the target multicast group, the method further includes:
- the data matching and forwarding rule of the target multicast group is sent to the user plane function on the protocol data unit PDU session path of the second terminal.
- the method further comprises:
- a group-level session modification request message is sent to a user plane function on a PDU session path of the first terminal, where the group-level session modification request message includes data matching and forwarding rules of the target multicast group.
- the method further comprises:
- a first PDU session establishment completion message is sent to the first terminal, where the first PDU session establishment completion message includes first information, and the first information is used to indicate whether the network allows the first terminal to establish a multicast group.
- the method further comprises:
- the second PDU session establishment is completed.
- the message includes second information, and the second information is used to indicate whether the second terminal successfully joins the target multicast group.
- FIG11 is a schematic diagram of the structure of a second terminal provided in an embodiment of the present disclosure.
- the second terminal includes a memory 1120, a transceiver 1110, and a processor 1100; wherein the processor 1100 and the memory 1120 may also be arranged physically separately.
- the memory 1120 is used to store computer programs; the transceiver 1110 is used to send and receive data under the control of the processor 1100.
- the transceiver 1110 is used to receive and send data under the control of the processor 1100 .
- the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1100 and various circuits of memory represented by memory 1120 are linked together.
- the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits together, which are all well known in the art, and therefore, the present disclosure will not further describe them.
- the bus interface provides an interface.
- the transceiver 1110 can be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, and these transmission media include transmission media such as wireless channels, wired channels, and optical cables.
- the user interface 1130 can also be an interface that can be connected to external and internal devices, and the connected devices include but are not limited to keypads, displays, speakers, microphones, joysticks, etc.
- the processor 1100 is responsible for managing the bus architecture and general processing, and the memory 1120 can store data used by the processor 1100 when performing operations.
- the processor 1100 may be a CPU, an ASIC, an FPGA or a CPLD, and the processor may also adopt a multi-core architecture.
- the processor 1100 is configured to execute any of the methods provided by the embodiments of the present disclosure according to the obtained executable instructions by calling the computer program stored in the memory 1120, for example: receiving a first request message, where the first request message is used to request the second terminal to join a target multicast group; the target multicast group is a multicast group initiated and established by the first terminal, and the first terminal and the second terminal belong to the same virtual network VN group;
- a second protocol data unit PDU session establishment request message or a first PDU session modification request message is sent, wherein the second PDU session establishment request message or the first PDU session modification request message includes an application layer identifier of the second terminal and multicast address information of the target multicast group.
- the first request message includes multicast address information of the target multicast group.
- the method further includes:
- a second PDU session establishment completion message is received, where the second PDU session establishment completion message includes second information, and the second information is used to indicate whether the second terminal successfully joins the target multicast group.
- first terminal, session management function and second terminal provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect.
- the parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.
- FIG. 12 is a schematic diagram of a structure of a device for establishing a multicast group provided in an embodiment of the present disclosure. As shown in FIG. 12 , the device includes:
- the first sending unit 1200 is configured to send a first protocol data unit (PDU) session establishment request message, where the first PDU session establishment request message includes an application layer identifier of a first terminal and an application layer identifier of a second terminal;
- PDU protocol data unit
- the second terminal and the first terminal belong to the same virtual network VN group.
- the apparatus further comprises:
- the first receiving unit is used to receive a first PDU session establishment completion message, where the first PDU session establishment completion message includes first information, and the first information is used to indicate whether the network allows the first terminal to establish a multicast group.
- FIG. 13 is a second structural diagram of a multicast group establishment device provided in an embodiment of the present disclosure. As shown in FIG. 13 , the device includes:
- the second receiving unit 1300 is used to receive a first create session management context request message sent by the access and mobility management function, wherein the first create session management context request message includes an application layer identifier of the first terminal and an application layer identifier of the second terminal; wherein the first terminal is a terminal that initiates establishment of a multicast group, and the second terminal and the first terminal belong to the same virtual network VN group;
- the determining unit 1310 is configured to determine whether to allow the first terminal to establish a multicast group according to the first create session management context request message.
- determining whether to allow the first terminal to establish a multicast group according to the first create session management context request message includes:
- the unified data management function is queried whether the first terminal is Allows the creation of multicast groups.
- the apparatus further includes a second sending unit, configured to:
- a first request message is sent to the second terminal, where the first request message is used to request the second terminal to join a target multicast group, where the target multicast group is the multicast group initiated and established by the first terminal.
- the first request message includes multicast address information of the target multicast group.
- the second receiving unit 1300 is further configured to:
- the determining unit 1310 is further configured to:
- determining whether to allow the second terminal to join the target multicast group according to the second create session management context request message or the first update session management context request message includes:
- the second create session management context request message or the first update session management context request message query the unified data management function and/or the policy control function whether the second terminal is allowed to join the target multicast group.
- the second sending unit is further configured to:
- the data matching and forwarding rule of the target multicast group is sent to the user plane function on the protocol data unit PDU session path of the second terminal.
- the second sending unit is further configured to:
- a group-level session modification request message is sent to a user plane function on a PDU session path of the first terminal, where the group-level session modification request message includes data matching and forwarding rules of the target multicast group.
- the second sending unit is further configured to:
- a first PDU session establishment completion message is sent to the first terminal, where the first PDU session establishment completion message includes first information, and the first information is used to indicate whether the network allows the first terminal to establish a multicast group.
- the second sending unit is further configured to:
- a second PDU session establishment completion message is sent to the second terminal, where the second PDU session establishment completion message includes second information, and the second information is used to indicate whether the second terminal successfully joins the target multicast group.
- FIG. 14 is a third structural diagram of a multicast group establishment device provided in an embodiment of the present disclosure. As shown in FIG. 14 , the device includes:
- the third receiving unit 1400 is used to receive a first request message, where the first request message is used to request the second terminal to join a target multicast group; the target multicast group is a multicast group initiated and established by the first terminal, and the first terminal and the second terminal belong to the same virtual network VN group;
- the third sending unit 1410 is used to send a second protocol data unit PDU session establishment request message or a first PDU session modification request message according to the first request message, and the second PDU session establishment request message or the first PDU session modification request message includes the application layer identifier of the second terminal and the multicast address information of the target multicast group.
- the first request message includes multicast address information of the target multicast group.
- the third receiving unit 1400 is further configured to:
- a second PDU session establishment completion message is received, where the second PDU session establishment completion message includes second information, and the second information is used to indicate whether the second terminal successfully joins the target multicast group.
- each functional unit in each embodiment of the present disclosure may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
- the above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
- the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium.
- the computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present disclosure.
- the aforementioned storage media include: USB flash drives, mobile hard drives, read-only hard drives, and other storage media.
- an embodiment of the present disclosure further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the multicast group establishment method provided by the above embodiments.
- the computer-readable storage medium can be any available medium or data storage device that can be accessed by a computer, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.
- magnetic storage such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.
- optical storage such as CD, DVD, BD, HVD, etc.
- semiconductor storage such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)
- the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new radio (NR) system, etc.
- GSM global system of mobile communication
- CDMA code division multiple access
- WCDMA wideband code division multiple access
- GPRS general packet radio service
- LTE long term evolution
- FDD LTE frequency division duplex
- TDD LTE time division duplex
- LTE-A advanced long term evolution
- UMTS universal mobile telecommunication system
- WiMAX world-wide interoperability for microwave access
- NR
- the terminal involved in the embodiments of the present disclosure may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem.
- the name of the terminal may also be different.
- the terminal may be called a user equipment (UE).
- a wireless terminal device may communicate with one or more core networks (CN) via a radio access network (RAN).
- the wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device.
- it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and/or data with a radio access network.
- the wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited to these in the embodiments of the present disclosure.
- the network device involved in the embodiments of the present disclosure may be a base station, which may include multiple cells providing services for the terminal.
- the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names.
- the network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network.
- IP Internet Protocol
- the network device may also coordinate the attribute management of the air interface.
- the network device involved in the embodiments of the present disclosure may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional NodeB) in the Long Term Evolution (LTE) system.
- the 5G base station (gNB) in the 5G network architecture (next generation system) may also be a home evolved Node B (HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present disclosure.
- the network equipment may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.
- Network devices and terminals can each use one or more antennas for multiple input multiple output (MIMO) transmission.
- MIMO transmission can be single user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO).
- MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoded transmission or beamforming transmission, etc.
- the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.
- a computer-usable storage media including but not limited to disk storage and optical storage, etc.
- each process and/or box in the flowchart and/or block diagram, as well as the combination of the process and/or box in the flowchart and/or block diagram can be implemented by computer executable instructions.
- These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.
- processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the processor readable memory produce a manufactured product including an instruction device, which implements a process in a flowchart. or multiple flows and/or block diagrams, functions specified in one or more blocks.
- processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本公开实施例提供一种组播组建立方法、设备、装置及存储介质,该方法包括:第一终端发送第一协议数据单元PDU会话建立请求消息,所述第一PDU会话建立请求消息中包含所述第一终端的应用层标识和第二终端的应用层标识;其中,所述第二终端与所述第一终端属于同一虚拟网络VN组。
Description
相关申请的交叉引用
本申请要求于2022年12月06日提交的申请号为202211559733.X,发明名称为“组播组建立方法、设备、装置及存储介质”的中国专利申请的优先权,其通过引用方式全部并入本文。
本公开涉及无线通信技术领域,尤其涉及一种组播组建立方法、设备、装置及存储介质。
目前第五代移动通信(the 5th generation mobile communication,5G)局域网(Local Area Network,LAN)场景下的组播组建立是基于应用配置的,并且需要终端(也称用户设备(User Equipment,UE))主动申请加入目标组播组。
然而,某些应用场景下,比如,大型直播通知所有已注册大会的用户直播会议相关消息时,会议通知方作为一个终端,希望建立一个组播组以便所有已注册大会的用户都收到直播相关信息,针对这种应用场景,目前5G LAN暂无某个组成员终端主动发起的虚拟网络(Virtual Network,VN)组组内的组播组建立过程相关方案。
发明内容
针对现有技术存在的问题,本公开实施例提供一种组播组建立方法、设备、装置及存储介质。
第一方面,本公开实施例提供一种组播组建立方法,应用于第一终端,包括:
发送第一协议数据单元PDU会话建立请求消息,所述第一PDU会话建立请求消息中包含所述第一终端的应用层标识和第二终端的应用层标识;
其中,所述第二终端与所述第一终端属于同一虚拟网络VN组。
在一些实施例中,所述发送第一PDU会话建立请求消息之后,所述方法还包括:
接收第一PDU会话建立完成消息,所述第一PDU会话建立完成消息中包含第一信息,所述第一信息用于指示网络是否允许所述第一终端建立组播组。
第二方面,本公开实施例还提供一种组播组建立方法,应用于会话管理功能,包括:
接收接入和移动性管理功能发送的第一创建会话管理上下文请求消息,所述第一创建会话管理上下文请求消息中包含第一终端的应用层标识和第二终端的应用层标识;其中,所述第一终端为发起建立组播组的终端,所述第二终端与所述第一终端属于同一虚拟网络VN组;
根据所述第一创建会话管理上下文请求消息,确定是否允许所述第一终端建立组播组。
在一些实施例中,所述根据所述第一创建会话管理上下文请求消息,确定是否允许所述第一终端建立组播组,包括:
根据所述第一终端的应用层标识,向统一数据管理功能查询所述第一终端是否被允许建立组播组。
在一些实施例中,在确定允许所述第一终端建立组播组的情况下,所述方法还包括:
向所述第二终端发送第一请求消息,所述第一请求消息用于请求所述第二终端加入目标组播组,所述目标组播组为所述第一终端发起建立的组播组。
在一些实施例中,所述第一请求消息中包含所述目标组播组的组播地址信息。
在一些实施例中,所述向所述第二终端发送第一请求消息之后,所述方法还包括:
接收接入和移动性管理功能发送的第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,所述第二创建会话管理上下文请求消息
或所述第一更新会话管理上下文请求消息中包含所述第二终端的应用层标识和所述目标组播组的组播地址信息;
根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,确定是否允许所述第二终端加入所述目标组播组。
在一些实施例中,所述根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,确定是否允许所述第二终端加入所述目标组播组,包括:
根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,向统一数据管理功能和/或策略控制功能查询所述第二终端是否被允许加入所述目标组播组。
在一些实施例中,在确定允许所述第二终端加入所述目标组播组的情况下,所述方法还包括:
向所述第二终端的协议数据单元PDU会话路径上的用户面功能发送所述目标组播组的数据匹配和转发规则。
在一些实施例中,所述方法还包括:
向所述第一终端的PDU会话路径上的用户面功能发送组级会话修改请求消息,所述组级会话修改请求消息中包含所述目标组播组的数据匹配和转发规则。
在一些实施例中,所述方法还包括:
向所述第一终端发送第一PDU会话建立完成消息,所述第一PDU会话建立完成消息中包含第一信息,所述第一信息用于指示网络是否允许所述第一终端建立组播组。
在一些实施例中,所述方法还包括:
向所述第二终端发送第二PDU会话建立完成消息,所述第二PDU会话建立完成消息中包含第二信息,所述第二信息用于指示所述第二终端是否成功加入所述目标组播组。
第三方面,本公开实施例还提供一种组播组建立方法,应用于第二终端,包括:
接收第一请求消息,所述第一请求消息用于请求所述第二终端加入目标组播组;所述目标组播组为第一终端发起建立的组播组,所述第一终端与所述第二终端属于同一虚拟网络VN组;
根据所述第一请求消息,发送第二协议数据单元PDU会话建立请求消息或第一PDU会话修改请求消息,所述第二PDU会话建立请求消息或所述第一PDU会话修改请求消息中包含所述第二终端的应用层标识和所述目标组播组的组播地址信息。
在一些实施例中,所述第一请求消息中包含所述目标组播组的组播地址信息。
在一些实施例中,所述发送第二PDU会话建立请求消息之后,所述方法还包括:
接收第二PDU会话建立完成消息,所述第二PDU会话建立完成消息中包含第二信息,所述第二信息用于指示所述第二终端是否成功加入所述目标组播组。
第四方面,本公开实施例还提供一种第一终端,包括存储器,收发机,处理器;
存储器,用于存储计算机程序;收发机,用于在所述处理器的控制下收发数据;处理器,用于读取所述存储器中的计算机程序并执行以下操作:
发送第一协议数据单元PDU会话建立请求消息,所述第一PDU会话建立请求消息中包含所述第一终端的应用层标识和第二终端的应用层标识;
其中,所述第二终端与所述第一终端属于同一虚拟网络VN组。
在一些实施例中,所述发送第一PDU会话建立请求消息之后,所述操作还包括:
接收第一PDU会话建立完成消息,所述第一PDU会话建立完成消息中包含第一信息,所述第一信息用于指示网络是否允许所述第一终端建立组播组。
第五方面,本公开实施例还提供一种会话管理功能,包括存储器,收发机,处理器;
存储器,用于存储计算机程序;收发机,用于在所述处理器的控制下收发数据;处理器,用于读取所述存储器中的计算机程序并执行以下操作:
接收接入和移动性管理功能发送的第一创建会话管理上下文请求消息,所述第一创建会话管理上下文请求消息中包含第一终端的应用层标识和第二终端的应用层标识;其中,所述第一终端为发起建立组播组的终端,所述第二终端与所述第一终端属于同一虚拟网络VN组;
根据所述第一创建会话管理上下文请求消息,确定是否允许所述第一终端建立组播组。
在一些实施例中,所述根据所述第一创建会话管理上下文请求消息,确定是否允许所述第一终端建立组播组,包括:
根据所述第一终端的应用层标识,向统一数据管理功能查询所述第一终端是否被允许建立组播组。
在一些实施例中,在确定允许所述第一终端建立组播组的情况下,所述操作还包括:
向所述第二终端发送第一请求消息,所述第一请求消息用于请求所述第二终端加入目标组播组,所述目标组播组为所述第一终端发起建立的组播组。
在一些实施例中,所述第一请求消息中包含所述目标组播组的组播地址信息。
在一些实施例中,所述向所述第二终端发送第一请求消息之后,所述操作还包括:
接收接入和移动性管理功能发送的第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息中包含所述第二终端的应用层标识和所述目标组播组的组播地址信息;
根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,确定是否允许所述第二终端加入所述目标组播组。
在一些实施例中,所述根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,确定是否允许所述第二终端加入所述
目标组播组,包括:
根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,向统一数据管理功能和/或策略控制功能查询所述第二终端是否被允许加入所述目标组播组。
在一些实施例中,在确定允许所述第二终端加入所述目标组播组的情况下,所述操作还包括:
向所述第二终端的协议数据单元PDU会话路径上的用户面功能发送所述目标组播组的数据匹配和转发规则。
在一些实施例中,所述操作还包括:
向所述第一终端的PDU会话路径上的用户面功能发送组级会话修改请求消息,所述组级会话修改请求消息中包含所述目标组播组的数据匹配和转发规则。
在一些实施例中,所述操作还包括:
向所述第一终端发送第一PDU会话建立完成消息,所述第一PDU会话建立完成消息中包含第一信息,所述第一信息用于指示网络是否允许所述第一终端建立组播组。
在一些实施例中,所述操作还包括:
向所述第二终端发送第二PDU会话建立完成消息,所述第二PDU会话建立完成消息中包含第二信息,所述第二信息用于指示所述第二终端是否成功加入所述目标组播组。
第六方面,本公开实施例还提供一种第二终端,包括存储器,收发机,处理器;
存储器,用于存储计算机程序;收发机,用于在所述处理器的控制下收发数据;处理器,用于读取所述存储器中的计算机程序并执行以下操作:
接收第一请求消息,所述第一请求消息用于请求所述第二终端加入目标组播组;所述目标组播组为第一终端发起建立的组播组,所述第一终端与所述第二终端属于同一虚拟网络VN组;
根据所述第一请求消息,发送第二协议数据单元PDU会话建立请求消息
或第一PDU会话修改请求消息,所述第二PDU会话建立请求消息或所述第一PDU会话修改请求消息中包含所述第二终端的应用层标识和所述目标组播组的组播地址信息。
在一些实施例中,所述第一请求消息中包含所述目标组播组的组播地址信息。
在一些实施例中,所述发送第二PDU会话建立请求消息之后,所述操作还包括:
接收第二PDU会话建立完成消息,所述第二PDU会话建立完成消息中包含第二信息,所述第二信息用于指示所述第二终端是否成功加入所述目标组播组。
第七方面,本公开实施例还提供一种组播组建立装置,包括:
第一发送单元,用于发送第一协议数据单元PDU会话建立请求消息,所述第一PDU会话建立请求消息中包含第一终端的应用层标识和第二终端的应用层标识;
其中,所述第二终端与所述第一终端属于同一虚拟网络VN组。
第八方面,本公开实施例还提供一种组播组建立装置,包括:
第二接收单元,用于接收接入和移动性管理功能发送的第一创建会话管理上下文请求消息,所述第一创建会话管理上下文请求消息中包含第一终端的应用层标识和第二终端的应用层标识;其中,所述第一终端为发起建立组播组的终端,所述第二终端与所述第一终端属于同一虚拟网络VN组;
确定单元,用于根据所述第一创建会话管理上下文请求消息,确定是否允许所述第一终端建立组播组。
第九方面,本公开实施例还提供一种组播组建立装置,包括:
第三接收单元,用于接收第一请求消息,所述第一请求消息用于请求第二终端加入目标组播组;所述目标组播组为第一终端发起建立的组播组,所述第一终端与所述第二终端属于同一虚拟网络VN组;
第三发送单元,用于根据所述第一请求消息,发送第二协议数据单元PDU会话建立请求消息或第一PDU会话修改请求消息,所述第二PDU会话建立
请求消息或所述第一PDU会话修改请求消息中包含所述第二终端的应用层标识和所述目标组播组的组播地址信息。
第十方面,本公开实施例还提供一种计算机可读存储介质,所述计算机可读存储介质存储有计算机程序,所述计算机程序用于使计算机执行如上所述第一方面所述的组播组建立方法,或执行如上所述第二方面所述的组播组建立方法,或执行如上所述第三方面所述的组播组建立方法。
第十一方面,本公开实施例还提供一种通信设备,所述通信设备中存储有计算机程序,所述计算机程序用于使通信设备执行如上所述第一方面所述的组播组建立方法,或执行如上所述第二方面所述的组播组建立方法,或执行如上所述第三方面所述的组播组建立方法。
第十二方面,本公开实施例还提供一种处理器可读存储介质,所述处理器可读存储介质存储有计算机程序,所述计算机程序用于使处理器执行如上所述第一方面所述的组播组建立方法,或执行如上所述第二方面所述的组播组建立方法,或执行如上所述第三方面所述的组播组建立方法。
第十三方面,本公开实施例还提供一种芯片产品,所述芯片产品中存储有计算机程序,所述计算机程序用于使芯片产品执行如上所述第一方面所述的组播组建立方法,或执行如上所述第二方面所述的组播组建立方法,或执行如上所述第三方面所述的组播组建立方法。
本公开实施例提供的组播组建立方法、设备、装置及存储介质,通过在终端发起PDU会话建立请求时携带其想要建立的组播组的终端应用层标识,实现了终端发起的组播组的建立过程,简化了组播组的建立方式,减少了信令交互。
为了更清楚地说明本公开实施例或相关技术中的技术方案,下面将对实施例或相关技术描述中所需要使用的附图作一简单地介绍,显而易见地,下面描述中的附图是本公开的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1是相关技术提供的终端在组播组内传输组播数据的示意图;
图2是相关技术提供的终端请求加入组播组的流程图;
图3是本公开实施例提供的组播组建立方法的流程示意图之一;
图4是本公开实施例提供的组播组建立方法的流程示意图之二;
图5是本公开实施例提供的组播组建立方法的流程示意图之三;
图6是本公开实施例提供的终端建立PDU会话及组播组的流程图;
图7是本公开实施例提供的终端加入组播组的流程图之一;
图8是本公开实施例提供的终端加入组播组的流程图之二;
图9是本公开实施例提供的第一终端的结构示意图;
图10是本公开实施例提供的会话管理功能的结构示意图;
图11是本公开实施例提供的第二终端的结构示意图;
图12是本公开实施例提供的组播组建立装置的结构示意图之一;
图13是本公开实施例提供的组播组建立装置的结构示意图之二;
图14是本公开实施例提供的组播组建立装置的结构示意图之三。
本公开实施例中术语“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本公开实施例中术语“多个”是指两个或两个以上,其它量词与之类似。
下面将结合本公开实施例中的附图,对本公开实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本公开一部分实施例,并不是全部的实施例。基于本公开中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本公开保护的范围。
为了便于更加清晰地理解本公开各实施例的技术方案,首先对本公开各实施例相关的一些技术内容进行介绍。
图1为相关技术提供的终端在组播组内传输组播数据的示意图。如图1
所示,UE1、UE3、UE4和UE6属于同一个VN组,其中,UE1、UE3和UE4属于该VN组中同一个组播组。协议数据单元(Protocol Data Unit,PDU)会话锚点(PDU Session Anchor,PSA)1为UE1和UE4的PDU会话对应的PSA,PSA2为UE3和UE6的PDU会话对应的PSA。UE1经PSA1向UE4发送组播数据,经PSA1和PSA2向UE3发送组播数据。UE1、UE3和UE4加入组播组的过程如图2所示。
图2为相关技术提供的终端请求加入组播组的流程图。如图2所示,UE1、UE3和UE4请求加入组播组的过程包括:
步骤1、组成员UE1、UE3、UE4和UE6分别建立到相同数据网络名称(Data Network Name,DNN)和单个网络切片选择辅助信息(Single Network Slice Selection Assistance Information,S-NSSAI)的PDU会话。
a、会话管理功能(Session Management Function,SMF)在PDU会话建立时向PSA下发如下用户面规则:SMF设置相关的值为“互联网协议(Internet Protocol,IP)组播加入/离开(IP multicast join/leave)”的使用报告规则(Usage Reporting Rule,URR)上报触发器(Reporting trigger)。
b、策略控制功能(Policy Control Function,PCF)向SMF下发策略控制请求触发器(Policy Control Request Trigger)——“终端加入一个组播组(UE join a multicast group)”。
步骤2、UE1使用PDU会话的用户面向其PSA1发送因特网组管理协议(Internet Group Management Protocol,IGMP)加入消息(join message)。
步骤3a、PSA1收到IGMP join message后,根据PDU会话中的N4规则,处理此消息:
若IGMP中包含的IP组播地址信息允许通过PDU会话接入,PSA1将此PDU会话加入请求的组播中;
若SMF向PSA1下发了URR,则PSA1通知SMF,UE1加入一个组播组,并携带IP组播地址信息给SMF;
若IGMP中包含的IP组播地址信息不允许通过此PDU会话接入,那么PSA1就不会将此PDU会话加入到组播组中。
步骤3b、PSA1根据URR向SMF报告“IP组播加入(IP multicast join)”。
步骤3c、SMF向PCF触发会话管理(Session Management,SM)策略修改流程。
步骤4、UE3、UE4请求加入组播组,步骤同上述步骤2-3。
目前5G LAN场景下的组播组建立是基于应用配置的,并且需要UE主动申请加入目标组播组。但是诸如某些应用场景如大型直播通知所有已注册大会的用户直播会议相关消息时,需要UE加入到该会议所在的组播组中,才能接受到会议直播的相关信息。在上述类似场景中,需要某个UE发起建立组播组的过程的方法尚不完善,比如会议通知方作为一个UE,希望建立一个组播组以完成向所有已注册大会的用户发送直播相关信息。
针对现有技术中暂无某个组成员UE主动发起的VN组组内的组播组建立过程相关方案,本公开实施例提供一种组播组建立方法、装置、电子设备及存储介质,可以在PDU会话建立过程中实现UE发起的组播组的建立过程。
示例性地,虽然本文采用5G LAN场景进行举例描述,但这并非限制性的,本领域技术人员所熟知的现有的或者将来的其他类似场景也可以应用本公开所述方案,对此不做限定。
图3为本公开实施例提供的组播组建立方法的流程示意图之一,该方法应用于第一终端,如图3所示,该方法包括如下步骤:
步骤300、发送第一PDU会话建立请求消息,第一PDU会话建立请求消息中包含第一终端的应用层标识和第二终端的应用层标识。
其中,第二终端与第一终端属于同一虚拟网络VN组。
具体地,第一终端为发起建立组播组的任意终端,第二终端为第一终端邀请加入组播组的成员终端。第一终端和第二终端属于同一VN组。其中,第二终端可以包括一个或多个终端。
第一终端需要发起建立组播组的情况下,第一终端可以在其PDU会话建立请求消息(即PDU Session Establishment Request)中携带第一终端的应用层标识和第二终端的应用层标识。从而网络侧可以根据第一终端的应用层标识和第二终端的应用层标识,决定是否允许第一终端建立包含第二终端的组
播组。
在一些实施例中,终端的应用层标识可以是通用公共订阅标识(Generic Public Subscription Identifier,GPSI)。
本公开实施例提供的组播组建立方法,通过在终端发起PDU会话建立请求时携带其想要建立的组播组的终端应用层标识,实现了终端发起的组播组的建立过程,简化了组播组的建立方式,减少了信令交互。
在一些实施例中,发送第一PDU会话建立请求消息之后,该方法还包括:
接收第一PDU会话建立完成消息,第一PDU会话建立完成消息中包含第一信息,第一信息用于指示网络是否允许第一终端建立组播组。
具体地,第一终端发送第一PDU会话建立请求消息之后,网络侧可以根据第一终端的应用层标识和第二终端的应用层标识,决定是否允许第一终端建立包含第二终端的组播组,并向第一终端发送第一PDU会话建立完成消息(即PDU Session Establishment Accept),该第一PDU会话建立完成消息中包含第一信息,指示网络是否允许第一终端建立组播组。
第一终端接收到第一PDU会话建立完成消息之后,便可以得知是否被允许建立组播组,从而进行相应的后续处理。
一种实施方式中,第一终端发送第一PDU会话建立请求消息给AMF,AMF接收到该第一PDU会话建立请求消息后,可以将第一终端的应用层标识和第二终端的应用层标识携带在第一创建会话管理上下文请求消息(即Nsmf PDU Session CreateSMContext Request)中,发送给SMF,SMF接收到第一创建会话管理上下文请求消息之后,便可以根据该第一创建会话管理上下文请求消息,确定是否允许第一终端建立组播组,并在发送给第一终端的第一PDU会话建立完成消息中携带第一信息,指示是否允许第一终端建立组播组。
图4为本公开实施例提供的组播组建立方法的流程示意图之二,该方法应用于会话管理功能,如图4所示,该方法包括如下步骤:
步骤400、接收接入和移动性管理功能发送的第一创建会话管理上下文请求消息,第一创建会话管理上下文请求消息中包含第一终端的应用层标识
和第二终端的应用层标识;其中,第一终端为发起建立组播组的终端,第二终端与第一终端属于同一虚拟网络VN组。
步骤410、根据第一创建会话管理上下文请求消息,确定是否允许第一终端建立组播组。
具体地,本公开所述的会话管理功能包括5G网络***中的SMF,或者未来网络***(比如6G)中具有与SMF类似功能的网元。
所述接入和移动性管理功能包括5G网络***中的AMF,或者未来网络***(比如6G)中具有与AMF类似功能的网元。
第一终端为发起建立组播组的任意终端,第二终端为第一终端邀请加入组播组的成员终端。第一终端和第二终端属于同一VN组。其中,第二终端可以包括一个或多个终端。
第一终端需要发起建立组播组的情况下,第一终端可以在其PDU会话建立请求消息(即PDU Session Establishment Request)中携带第一终端的应用层标识和第二终端的应用层标识。在一些实施例中,终端的应用层标识可以是GPSI。
一种实施方式中,第一终端可以向接入和移动性管理功能发送第一PDU会话建立请求消息,接入和移动性管理功能接收到该第一PDU会话建立请求消息后,可以将第一终端的应用层标识和第二终端的应用层标识携带在第一创建会话管理上下文请求消息(即Nsmf PDU Session CreateSMContext Request)中,发送给会话管理功能。会话管理功能接收到第一创建会话管理上下文请求消息之后,便可以根据该第一创建会话管理上下文请求消息,确定是否允许第一终端建立组播组。
本公开实施例提供的组播组建立方法,会话管理功能可以根据终端发起PDU会话建立请求时携带的终端应用层标识,确定是否允许终端建立组播组,从而可以支持终端发起建立组播组,简化了组播组的建立方式,减少了信令交互。
在一些实施例中,根据第一创建会话管理上下文请求消息,确定是否允许第一终端建立组播组,包括:
根据第一终端的应用层标识,向统一数据管理功能查询第一终端是否被允许建立组播组。
具体地,本公开所述的统一数据管理功能包括5G网络***中的UDM,或者未来网络***(比如6G)中具有与UDM类似功能的网元。
会话管理功能接收第一创建会话管理上下文请求消息后,可以与统一数据管理功能交互,通过第一终端的应用层标识向统一数据管理功能查询可以发起组播组建立的终端信息,以确定第一终端是否被允许建立组播组。
在一些实施例中,应用功能可以预先将相关VN组中可以发起组播组建立的终端信息配置给统一数据管理功能、策略控制功能等。
在一些实施例中,在确定允许第一终端建立组播组的情况下,该方法还包括:
向第二终端发送第一请求消息,第一请求消息用于请求第二终端加入目标组播组,目标组播组为第一终端发起建立的组播组。
具体地,会话管理功能判断允许第一终端建立组播组后,可以向第二终端发送第一请求消息,请求第二终端加入第一终端发起建立的组播组。
一种实施方式中,会话管理功能可以经由接入和移动性管理功能以及网络设备(例如基站),向第二终端发送第一请求消息。
在一些实施例中,第一请求消息中可以包含目标组播组的组播地址信息。
关于目标组播组的组播地址信息,会话管理功能判断允许第一终端建立组播组后,可以为该组播组分配组播地址;或者,会话管理功能可以基于应用功能的配置确定目标组播组的组播地址信息,比如应用功能预先将第一终端建立的组播组的组播地址信息配置给统一数据管理功能,会话管理功能可以在需要时向统一数据管理功能查询到目标组播组的组播地址信息;或者,目标组播组的组播地址信息可以是在第一终端建立PDU会话之前或之后,配置在第一终端中的,比如,目标组播组的组播地址信息预先配置在第一终端中,第一终端可以在发起PDU会话建立请求的消息中携带组播地址信息,发送给会话管理功能。
在一些实施例中,向第二终端发送第一请求消息之后,该方法还包括:
接收接入和移动性管理功能发送的第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息中包含第二终端的应用层标识和目标组播组的组播地址信息;
根据第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,确定是否允许第二终端加入目标组播组。
具体地,一种实施方式中,第二终端接收到第一请求消息时,若尚未建立PDU会话,则第二终端可以发起PDU会话建立请求(即PDU Session Establishment Request),PDU会话建立请求中携带第二终端的应用层标识和目标组播组的组播地址信息,用于请求加入目标组播组。
在一些实施例中,目标组播组的组播地址信息可以是会话管理功能发送给第二终端的,或者第二终端中预先配置的。
接入和移动性管理功能接收到第二终端发起的PDU会话建立请求后,可以向会话管理功能发送第二创建会话管理上下文请求消息(即Nsmf PDU Session CreateSMContext Request),该第二创建会话管理上下文请求消息中包含第二终端的应用层标识和目标组播组的组播地址信息。
会话管理功能接收到第二创建会话管理上下文请求消息之后,便可以根据该第二创建会话管理上下文请求消息,确定是否允许第二终端加入目标组播组。
一种实施方式中,第二终端接收到第一请求消息时,若已经建立PDU会话,则第二终端可以发起PDU会话修改请求(即PDU Session Modification Request),PDU会话修改请求中携带第二终端的应用层标识和目标组播组的组播地址信息,用于请求加入目标组播组。
接入和移动性管理功能接收到第二终端发起的PDU会话建立请求后,可以向会话管理功能发送第一更新会话管理上下文请求消息(即Nsmf PDU Session_UpdateSMContext Request),该第一更新会话管理上下文请求消息中包含第二终端的应用层标识和目标组播组的组播地址信息。
会话管理功能接收到第一更新会话管理上下文请求消息之后,便可以根
据该第一更新会话管理上下文请求消息,确定是否允许第二终端加入目标组播组。
在一些实施例中,根据第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,确定是否允许第二终端加入目标组播组,包括:
根据第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,向统一数据管理功能和/或策略控制功能查询第二终端是否被允许加入目标组播组。
具体地,本公开所述的策略控制功能包括5G网络***中的PCF,或者未来网络***(比如6G)中具有与PCF类似功能的网元。
会话管理功能接收到第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息之后,可以与统一数据管理功能和/或策略控制功能交互,判断是否允许第二终端加入目标组播组。
在一些实施例中,会话管理功能可以向统一数据管理功能查询第二终端的配置信息或者允许加入目标组播组的终端信息(可以是应用功能配置给统一数据管理功能的),以确定第二终端是否被允许加入目标组播组。
在一些实施例中,会话管理功能可以在向策略控制功能获取会话管理相关策略信息时,基于策略控制功能获取有关第二终端是否被允许加入组播组的信息,以确定第二终端是否被允许加入目标组播组。
在一些实施例中,在确定允许第二终端加入目标组播组的情况下,该方法还包括:
向第二终端的协议数据单元PDU会话路径上的用户面功能发送目标组播组的数据匹配和转发规则。
具体地,本公开所述的用户面功能包括5G网络***中的UPF,或者未来网络***(比如6G)中具有与UPF类似功能的网元。
会话管理功能确定允许第二终端加入目标组播组的情况下,可以为第二终端的PDU会话进行用户面匹配和转发规则下发,向第二终端的PDU会话路径上的用户面功能发送有关目标组播组的数据匹配和转发规则。例如,当收到目的地址为目标组播组的组播地址的数据包时,转发至第二终端。
在一些实施例中,该方法还包括:
向第一终端的PDU会话路径上的用户面功能发送组级会话修改请求消息,组级会话修改请求消息中包含目标组播组的数据匹配和转发规则。
具体地,会话管理功能确定允许第二终端加入目标组播组的情况下,还可以通过组级会话修改请求消息(比如组级N4会话修改请求消息,Group level N4Session Modification),向第一终端的PDU会话路径上的用户面功能下发相应的有关目标组播组的数据匹配和转发规则。
在一些实施例中,该方法还包括:
向第一终端发送第一PDU会话建立完成消息,第一PDU会话建立完成消息中包含第一信息,第一信息用于指示网络是否允许第一终端建立组播组。
具体地,会话管理功能接收到第一终端发起的PDU会话建立请求,并确定是否允许第一终端建立组播组之后,可以在发送给第一终端的第一PDU会话建立完成消息(即PDU Session Establishment Accept)中携带第一信息,指示是否允许第一终端建立组播组。
在一些实施例中,该方法还包括:
向第二终端发送第二PDU会话建立完成消息,第二PDU会话建立完成消息中包含第二信息,第二信息用于指示第二终端是否成功加入目标组播组。
具体地,会话管理功能接收到第二终端发起的PDU会话建立请求,并确定是否允许第二终端加入目标组播组之后,可以在发送给第二终端的第二PDU会话建立完成消息(即PDU Session Establishment Accept)中携带第二信息,指示第二终端是否成功加入目标组播组。
图5为本公开实施例提供的组播组建立方法的流程示意图之三,该方法应用于第二终端,如图5所示,该方法包括如下步骤:
步骤500、接收第一请求消息,第一请求消息用于请求第二终端加入目标组播组;目标组播组为第一终端发起建立的组播组,第一终端与第二终端属于同一虚拟网络VN组。
步骤510、根据第一请求消息,发送第二协议数据单元PDU会话建立请求消息或第一PDU会话修改请求消息,第二PDU会话建立请求消息或第一
PDU会话修改请求消息中包含第二终端的应用层标识和目标组播组的组播地址信息。
具体地,第一终端为发起建立组播组的任意终端,第二终端为第一终端邀请加入组播组的成员终端。第一终端和第二终端属于同一VN组。其中,第二终端可以包括一个或多个终端。
第一终端需要发起建立组播组的情况下,第一终端可以在其PDU会话建立请求消息(即PDU Session Establishment Request)中携带第一终端的应用层标识和第二终端的应用层标识。在一些实施例中,终端的应用层标识可以是GPSI。
第一终端可以向接入和移动性管理功能发送第一PDU会话建立请求消息,接入和移动性管理功能接收到该第一PDU会话建立请求消息后,可以将第一终端的应用层标识和第二终端的应用层标识携带在第一创建会话管理上下文请求消息(即Nsmf PDU Session CreateSMContext Request)中,发送给会话管理功能。会话管理功能接收到第一创建会话管理上下文请求消息之后,便可以根据该第一创建会话管理上下文请求消息,确定是否允许第一终端建立组播组。
会话管理功能判断允许第一终端建立组播组后,可以向第二终端发送第一请求消息,请求第二终端加入第一终端发起建立的组播组。
在一些实施例中,会话管理功能可以经由接入和移动性管理功能以及网络设备(例如基站),向第二终端发送第一请求消息。
在一些实施例中,第一请求消息中可以包含目标组播组的组播地址信息。
一种实施方式中,第二终端接收到第一请求消息时,若尚未建立PDU会话,则第二终端可以发起PDU会话建立请求(即PDU Session Establishment Request),PDU会话建立请求中携带第二终端的应用层标识和目标组播组的组播地址信息,用于请求加入目标组播组。
在一些实施例中,目标组播组的组播地址信息可以是会话管理功能发送给第二终端的,或者第二终端中预先配置的。
接入和移动性管理功能接收到第二终端发起的PDU会话建立请求后,可
以向会话管理功能发送第二创建会话管理上下文请求消息(即Nsmf PDU Session CreateSMContext Request),该第二创建会话管理上下文请求消息中包含第二终端的应用层标识和目标组播组的组播地址信息。
会话管理功能接收到第二创建会话管理上下文请求消息之后,便可以根据该第二创建会话管理上下文请求消息,确定是否允许第二终端加入目标组播组。
一种实施方式中,第二终端接收到第一请求消息时,若已经建立PDU会话,则第二终端可以发起PDU会话修改请求(即PDU Session Modification Request),PDU会话修改请求中携带第二终端的应用层标识和目标组播组的组播地址信息,用于请求加入目标组播组。
在一些实施例中,目标组播组的组播地址信息可以是会话管理功能发送给第二终端的,或者第二终端中预先配置的。
接入和移动性管理功能接收到第二终端发起的PDU会话建立请求后,可以向会话管理功能发送第一更新会话管理上下文请求消息(即Nsmf PDU Session_UpdateSMContext Request),该第一更新会话管理上下文请求消息中包含第二终端的应用层标识和目标组播组的组播地址信息。
会话管理功能接收到第一更新会话管理上下文请求消息之后,便可以根据该第一更新会话管理上下文请求消息,确定是否允许第二终端加入目标组播组。
本公开实施例提供的组播组建立方法,终端接收会话管理功能发送的加入组播组的请求后,通过新建或修改PDU会话请求加入组播组,实现了终端发起的组播组的建立过程,简化了组播组的建立方式,减少了信令交互。
在一些实施例中,发送第二PDU会话建立请求消息之后,该方法还包括:
接收第二PDU会话建立完成消息,第二PDU会话建立完成消息中包含第二信息,第二信息用于指示第二终端是否成功加入目标组播组。
具体地,会话管理功能接收到第二终端发起的PDU会话建立请求,并确定是否允许第二终端加入目标组播组之后,可以在发送给第二终端的第二PDU会话建立完成消息(即PDU Session Establishment Accept)中携带第二
信息,指示第二终端是否成功加入目标组播组。
本公开各实施例提供的方法是基于同一申请构思的,因此各方法的实施可以相互参见,重复之处不再赘述。
以下通过具体应用场景的实施例对本公开各上述实施例提供的方法进行举例说明。
实施例一:UE1建立PDU会话及组播组。
图6为本公开实施例提供的终端建立PDU会话及组播组的流程图。如图6所示,UE1在建立PDU会话的同时请求建立包含UE2及UE3的组播组,其主要过程包括:
1、应用功能AF配置相关VN组中可以发起组播组建立的UE信息。
2、UE1发送PDU会话建立请求,携带其自身的应用层标识和其想要建立组播组的同VN组成员的应用层标识,如GPSI。
3、接入与移动性管理功能AMF选择会话管理功能SMF。
4、AMF在会话建立过程中将UE1和其想要建立组播组的同VN组成员的应用层标识转发给SMF。
5、SMF与统一数据管理UDM交互,获取SM相关签约信息,以及AF配置的UE1是否可以发起组播组建立的配置信息,并订阅信息更新。
6、SMF向AMF发送创建会话管理上下文响应消息。
7、进行PDU会话身份验证/授权。
8a、SMF选择策略控制功能PCF。
8b、SMF发起会话管理策略关联建立或会话管理策略关联修改流程。
9、SMF选择用户面功能UPF。
10、SMF发起会话管理策略关联修改流程。
11、SMF与UPF交互(N4会话建立请求/响应)。
12、SMF根据步骤4和步骤5中的信息,判断是否允许当前UE1建立组播组。
若不允许:SMF继续执行其他会话建立相关的步骤13-14,并在PDU Session Establishment Accept消息中携带不允许建立组播组的标识。
若允许:SMF判断组播组目标成员UE2和UE3是否建立了PDU会话:
a、UE2或UE3尚未建立PDU会话,参考实施例二。
b、UE2或UE3已经建立了PDU会话,参考实施例三。
注:关于UE1发起建立的组播组的组播地址:
a、SMF可以在此步骤为该组播组分配组播地址。
b、此组播组的组播地址可以是基于AF配置的。
c、该组播组的组播地址可以是在UE1建立PDU会话之前或之后,配置在UE1中的。
13、继续执行PDU会话建立过程。
14、网络通过SMF向UE发送PDU Session Establishment Accept消息,携带是否允许UE1建立组播组的标识信息。
实施例二:UE2或UE3尚未建立PDU会话。
图7为本公开实施例提供的终端加入组播组的流程图之一。如图7所示,UE2或UE3在未建立PDU会话的情况下加入UE1建立的组播组,其主要过程包括:
1:参照实施例一中UE1发起PDU会话建立过程。
2-4、会话管理功能SMF通过接入与移动性管理功能AMF向UE2/UE3发送消息,携带UE1会话所建立的组播组的组播地址。
5-6、UE2/UE3发起PDU会话建立请求,携带其收到的组播地址。
注:UE2/UE3的组播地址还可以来自UE2/UE3会话建立前的配置。
7、SMF向统一数据管理UMD获取UE2/UE3是否加入组播组的配置信息。(可选)
8、SMF向AMF发送创建会话管理上下文响应消息。
9、进行PDU会话身份验证/授权。
10a、SMF选择策略控制功能PCF。
10b、SMF在向PCF获取SM相关策略信息时,SMF可以基于PCF有关此UE是否允许加入组播组进行判断。(可选)
11、SMF选择用户面功能UPF。
12、SMF发起会话管理策略关联修改。
13、SMF为此会话进行用户面匹配和转发规则下发时,携带有关组播组的匹配转发规则,如当收到目的地址为上述组播地址时,转发至UE2/UE3。
14、继续执行PDU会话建立过程。
15、网络通过SMF向UE2/UE3的PDU Session Establishment Accept的消息中增加是否成功加入上述组播组的标识。
实施例三:UE2或UE3已建立PDU会话。
图8为本公开实施例提供的终端加入组播组的流程图之二。如图8所示,UE2或UE3在已建立PDU会话的情况下加入UE1建立的组播组,其主要过程包括:
1、参照实施例一中UE1发起PDU会话建立过程。
2-4、会话管理功能SMF通过接入与移动性管理功能AMF向UE2/UE3发送消息,携带UE1所建立的组播组的组播地址。
5-6、UE2/UE3将收到的组播地址及其自身的应用层标识告知SMF。
7、执行PDU会话修改过程。
8、SMF与策略管理功能PCF/统一数据管理UDM交互,判断是否允许当前UE加入组播组。
9、SMF与UE2/UE3的PDU会话路径上的用户面功能UPF交互增加对组播组数据的匹配和转发规则。
10、执行PDU会话修改过程。
11、SMF通过组级N4会话修改请求向同组播组的UE1的PDU会话路径上的UPF下发有关组播组的数据匹配和转发规则。
本公开各实施例提供的方法和装置是基于同一申请构思的,由于方法和装置解决问题的原理相似,因此装置和方法的实施可以相互参见,重复之处不再赘述。
图9为本公开实施例提供的第一终端的结构示意图,如图9所示,该第一终端包括存储器920,收发机910和处理器900;其中,处理器900与存储器920也可以物理上分开布置。
存储器920,用于存储计算机程序;收发机910,用于在处理器900的控制下收发数据。
具体地,收发机910用于在处理器900的控制下接收和发送数据。
其中,在图9中,总线架构可以包括任意数量的互联的总线和桥,具体由处理器900代表的一个或多个处理器和存储器920代表的存储器的各种电路链接在一起。总线架构还可以将诸如***设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本公开不再对其进行进一步描述。总线接口提供接口。收发机910可以是多个元件,即包括发送机和接收机,提供用于在传输介质上与各种其他装置通信的单元,这些传输介质包括无线信道、有线信道、光缆等传输介质。针对不同的用户设备,用户接口930还可以是能够外接内接需要设备的接口,连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器900负责管理总线架构和通常的处理,存储器920可以存储处理器900在执行操作时所使用的数据。
处理器900可以是中央处理器(Central Processing Unit,CPU)、专用集成电路(Application Specific Integrated Circuit,ASIC)、现场可编程门阵列(Field-Programmable Gate Array,FPGA)或复杂可编程逻辑器件(Complex Programmable Logic Device,CPLD),处理器也可以采用多核架构。
处理器900通过调用存储器920存储的计算机程序,用于按照获得的可执行指令执行本公开实施例提供的任一所述方法,例如:发送第一协议数据单元PDU会话建立请求消息,第一PDU会话建立请求消息中包含第一终端的应用层标识和第二终端的应用层标识;
其中,第二终端与第一终端属于同一虚拟网络VN组。
在一些实施例中,发送第一PDU会话建立请求消息之后,该方法还包括:
接收第一PDU会话建立完成消息,第一PDU会话建立完成消息中包含第一信息,第一信息用于指示网络是否允许第一终端建立组播组。
图10为本公开实施例提供的会话管理功能的结构示意图,如图10所示,该会话管理功能包括存储器1020,收发机1010和处理器1000;其中,处理
器1000与存储器1020也可以物理上分开布置。
存储器1020,用于存储计算机程序;收发机1010,用于在处理器1000的控制下收发数据。
具体地,收发机1010用于在处理器1000的控制下接收和发送数据。
其中,在图10中,总线架构可以包括任意数量的互联的总线和桥,具体由处理器1000代表的一个或多个处理器和存储器1020代表的存储器的各种电路链接在一起。总线架构还可以将诸如***设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本公开不再对其进行进一步描述。总线接口提供接口。收发机1010可以是多个元件,即包括发送机和接收机,提供用于在传输介质上与各种其他装置通信的单元,这些传输介质包括无线信道、有线信道、光缆等传输介质。
处理器1000负责管理总线架构和通常的处理,存储器1020可以存储处理器1000在执行操作时所使用的数据。
处理器1000可以是CPU、ASIC、FPGA或CPLD,处理器也可以采用多核架构。
处理器1000通过调用存储器1020存储的计算机程序,用于按照获得的可执行指令执行本公开实施例提供的任一所述方法,例如:接收接入和移动性管理功能发送的第一创建会话管理上下文请求消息,第一创建会话管理上下文请求消息中包含第一终端的应用层标识和第二终端的应用层标识;其中,第一终端为发起建立组播组的终端,第二终端与第一终端属于同一虚拟网络VN组;
根据第一创建会话管理上下文请求消息,确定是否允许第一终端建立组播组。
在一些实施例中,根据第一创建会话管理上下文请求消息,确定是否允许第一终端建立组播组,包括:
根据第一终端的应用层标识,向统一数据管理功能查询第一终端是否被允许建立组播组。
在一些实施例中,在确定允许第一终端建立组播组的情况下,该方法还
包括:
向第二终端发送第一请求消息,第一请求消息用于请求第二终端加入目标组播组,目标组播组为第一终端发起建立的组播组。
在一些实施例中,第一请求消息中包含目标组播组的组播地址信息。
在一些实施例中,向第二终端发送第一请求消息之后,该方法还包括:
接收接入和移动性管理功能发送的第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息中包含第二终端的应用层标识和目标组播组的组播地址信息;
根据第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,确定是否允许第二终端加入目标组播组。
在一些实施例中,根据第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,确定是否允许第二终端加入目标组播组,包括:
根据第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,向统一数据管理功能和/或策略控制功能查询第二终端是否被允许加入目标组播组。
在一些实施例中,在确定允许第二终端加入目标组播组的情况下,该方法还包括:
向第二终端的协议数据单元PDU会话路径上的用户面功能发送目标组播组的数据匹配和转发规则。
在一些实施例中,该方法还包括:
向第一终端的PDU会话路径上的用户面功能发送组级会话修改请求消息,组级会话修改请求消息中包含目标组播组的数据匹配和转发规则。
在一些实施例中,该方法还包括:
向第一终端发送第一PDU会话建立完成消息,第一PDU会话建立完成消息中包含第一信息,第一信息用于指示网络是否允许第一终端建立组播组。
在一些实施例中,该方法还包括:
向第二终端发送第二PDU会话建立完成消息,第二PDU会话建立完成
消息中包含第二信息,第二信息用于指示第二终端是否成功加入目标组播组。
图11为本公开实施例提供的第二终端的结构示意图,如图11所示,该第二终端包括存储器1120,收发机1110和处理器1100;其中,处理器1100与存储器1120也可以物理上分开布置。
存储器1120,用于存储计算机程序;收发机1110,用于在处理器1100的控制下收发数据。
具体地,收发机1110用于在处理器1100的控制下接收和发送数据。
其中,在图11中,总线架构可以包括任意数量的互联的总线和桥,具体由处理器1100代表的一个或多个处理器和存储器1120代表的存储器的各种电路链接在一起。总线架构还可以将诸如***设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本公开不再对其进行进一步描述。总线接口提供接口。收发机1110可以是多个元件,即包括发送机和接收机,提供用于在传输介质上与各种其他装置通信的单元,这些传输介质包括无线信道、有线信道、光缆等传输介质。针对不同的用户设备,用户接口1130还可以是能够外接内接需要设备的接口,连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器1100负责管理总线架构和通常的处理,存储器1120可以存储处理器1100在执行操作时所使用的数据。
处理器1100可以是CPU、ASIC、FPGA或CPLD,处理器也可以采用多核架构。
处理器1100通过调用存储器1120存储的计算机程序,用于按照获得的可执行指令执行本公开实施例提供的任一所述方法,例如:接收第一请求消息,第一请求消息用于请求第二终端加入目标组播组;目标组播组为第一终端发起建立的组播组,第一终端与第二终端属于同一虚拟网络VN组;
根据第一请求消息,发送第二协议数据单元PDU会话建立请求消息或第一PDU会话修改请求消息,第二PDU会话建立请求消息或第一PDU会话修改请求消息中包含第二终端的应用层标识和目标组播组的组播地址信息。
在一些实施例中,第一请求消息中包含目标组播组的组播地址信息。
在一些实施例中,发送第二PDU会话建立请求消息之后,该方法还包括:
接收第二PDU会话建立完成消息,第二PDU会话建立完成消息中包含第二信息,第二信息用于指示第二终端是否成功加入目标组播组。
在此需要说明的是,本公开实施例提供的上述第一终端、会话管理功能和第二终端,能够实现上述方法实施例所实现的所有方法步骤,且能够达到相同的技术效果,在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
图12为本公开实施例提供的组播组建立装置的结构示意图之一,如图12所示,该装置包括:
第一发送单元1200,用于发送第一协议数据单元PDU会话建立请求消息,第一PDU会话建立请求消息中包含第一终端的应用层标识和第二终端的应用层标识;
其中,第二终端与第一终端属于同一虚拟网络VN组。
在一些实施例中,该装置还包括:
第一接收单元,用于接收第一PDU会话建立完成消息,第一PDU会话建立完成消息中包含第一信息,第一信息用于指示网络是否允许第一终端建立组播组。
图13为本公开实施例提供的组播组建立装置的结构示意图之二,如图13所示,该装置包括:
第二接收单元1300,用于接收接入和移动性管理功能发送的第一创建会话管理上下文请求消息,第一创建会话管理上下文请求消息中包含第一终端的应用层标识和第二终端的应用层标识;其中,第一终端为发起建立组播组的终端,第二终端与第一终端属于同一虚拟网络VN组;
确定单元1310,用于根据第一创建会话管理上下文请求消息,确定是否允许第一终端建立组播组。
在一些实施例中,根据第一创建会话管理上下文请求消息,确定是否允许第一终端建立组播组,包括:
根据第一终端的应用层标识,向统一数据管理功能查询第一终端是否被
允许建立组播组。
在一些实施例中,该装置还包括第二发送单元,用于:
在确定允许第一终端建立组播组的情况下,向第二终端发送第一请求消息,第一请求消息用于请求第二终端加入目标组播组,目标组播组为第一终端发起建立的组播组。
在一些实施例中,第一请求消息中包含目标组播组的组播地址信息。
在一些实施例中,第二接收单元1300还用于:
接收接入和移动性管理功能发送的第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息中包含第二终端的应用层标识和目标组播组的组播地址信息;
确定单元1310还用于:
根据第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,确定是否允许第二终端加入目标组播组。
在一些实施例中,根据第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,确定是否允许第二终端加入目标组播组,包括:
根据第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,向统一数据管理功能和/或策略控制功能查询第二终端是否被允许加入目标组播组。
在一些实施例中,第二发送单元还用于:
向第二终端的协议数据单元PDU会话路径上的用户面功能发送目标组播组的数据匹配和转发规则。
在一些实施例中,第二发送单元还用于:
向第一终端的PDU会话路径上的用户面功能发送组级会话修改请求消息,组级会话修改请求消息中包含目标组播组的数据匹配和转发规则。
在一些实施例中,第二发送单元还用于:
向第一终端发送第一PDU会话建立完成消息,第一PDU会话建立完成消息中包含第一信息,第一信息用于指示网络是否允许第一终端建立组播组。
在一些实施例中,第二发送单元还用于:
向第二终端发送第二PDU会话建立完成消息,第二PDU会话建立完成消息中包含第二信息,第二信息用于指示第二终端是否成功加入目标组播组。
图14为本公开实施例提供的组播组建立装置的结构示意图之三,如图14所示,该装置包括:
第三接收单元1400,用于接收第一请求消息,第一请求消息用于请求第二终端加入目标组播组;目标组播组为第一终端发起建立的组播组,第一终端与第二终端属于同一虚拟网络VN组;
第三发送单元1410,用于根据第一请求消息,发送第二协议数据单元PDU会话建立请求消息或第一PDU会话修改请求消息,第二PDU会话建立请求消息或第一PDU会话修改请求消息中包含第二终端的应用层标识和目标组播组的组播地址信息。
在一些实施例中,第一请求消息中包含目标组播组的组播地址信息。
在一些实施例中,第三接收单元1400还用于:
接收第二PDU会话建立完成消息,第二PDU会话建立完成消息中包含第二信息,第二信息用于指示第二终端是否成功加入目标组播组。
需要说明的是,本公开实施例中对单元的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。另外,在本公开各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个处理器可读取存储介质中。基于这样的理解,本公开的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)或处理器(processor)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读
存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
在此需要说明的是,本公开实施例提供的上述装置,能够实现上述方法实施例所实现的所有方法步骤,且能够达到相同的技术效果,在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
另一方面,本公开实施例还提供一种计算机可读存储介质,所述计算机可读存储介质存储有计算机程序,所述计算机程序用于使计算机执行上述各实施例提供的组播组建立方法。
在此需要说明的是,本公开实施例提供的计算机可读存储介质,能够实现上述方法实施例所实现的所有方法步骤,且能够达到相同的技术效果,在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
所述计算机可读存储介质可以是计算机能够存取的任何可用介质或数据存储设备,包括但不限于磁性存储器(例如软盘、硬盘、磁带、磁光盘(MO)等)、光学存储器(例如CD、DVD、BD、HVD等)、以及半导体存储器(例如ROM、EPROM、EEPROM、非易失性存储器(NAND FLASH)、固态硬盘(SSD))等。
本公开实施例提供的技术方案可以适用于多种***,尤其是5G***。例如适用的***可以是全球移动通讯(global system of mobile communication,GSM)***、码分多址(code division multiple access,CDMA)***、宽带码分多址(Wideband Code Division Multiple Access,WCDMA)通用分组无线业务(general packet radio service,GPRS)***、长期演进(long term evolution,LTE)***、LTE频分双工(frequency division duplex,FDD)***、LTE时分双工(time division duplex,TDD)***、高级长期演进(long term evolution advanced,LTE-A)***、通用移动***(universal mobile telecommunication system,UMTS)、全球互联微波接入(worldwide interoperability for microwave access,WiMAX)***、5G新空口(New Radio,NR)***等。这多种***中均包括终端设备和网络设备。***中还可以包括核心网部分,例如演进的分组***(Evloved Packet System,EPS)、5G***(5GS)等。
本公开实施例涉及的终端,可以是指向用户提供语音和/或数据连通性的设备,具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备等。在不同的***中,终端的名称可能也不相同,例如在5G***中,终端可以称为用户设备(User Equipment,UE)。无线终端设备可以经无线接入网(Radio Access Network,RAN)与一个或多个核心网(Core Network,CN)进行通信,无线终端设备可以是移动终端设备,如移动电话(或称为“蜂窝”电话)和具有移动终端设备的计算机,例如,可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置,它们与无线接入网交换语言和/或数据。例如,个人通信业务(Personal Communication Service,PCS)电话、无绳电话、会话发起协议(Session Initiated Protocol,SIP)话机、无线本地环路(Wireless Local Loop,WLL)站、个人数字助理(Personal Digital Assistant,PDA)等设备。无线终端设备也可以称为***、订户单元(subscriber unit)、订户站(subscriber station),移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点(access point)、远程终端设备(remote terminal)、接入终端设备(access terminal)、用户终端设备(user terminal)、用户代理(user agent)、用户装置(user device),本公开实施例中并不限定。
本公开实施例涉及的网络设备,可以是基站,该基站可以包括多个为终端提供服务的小区。根据具体应用场合不同,基站又可以称为接入点,或者可以是接入网中在空中接口上通过一个或多个扇区与无线终端设备通信的设备,或者其它名称。网络设备可用于将收到的空中帧与网际协议(Internet Protocol,IP)分组进行相互更换,作为无线终端设备与接入网的其余部分之间的路由器,其中接入网的其余部分可包括网际协议(IP)通信网络。网络设备还可协调对空中接口的属性管理。例如,本公开实施例涉及的网络设备可以是全球移动通信***(Global System for Mobile communications,GSM)或码分多址接入(Code Division Multiple Access,CDMA)中的网络设备(Base Transceiver Station,BTS),也可以是带宽码分多址接入(Wide-band Code Division Multiple Access,WCDMA)中的网络设备(NodeB),还可以是长期演进(long term evolution,LTE)***中的演进型网络设备(evolutional Node
B,eNB或e-NodeB)、5G网络架构(next generation system)中的5G基站(gNB),也可以是家庭演进基站(Home evolved Node B,HeNB)、中继节点(relay node)、家庭基站(femto)、微微基站(pico)等,本公开实施例中并不限定。在一些网络结构中,网络设备可以包括集中单元(centralized unit,CU)节点和分布单元(distributed unit,DU)节点,集中单元和分布单元也可以地理上分开布置。
网络设备与终端之间可以各自使用一或多根天线进行多输入多输出(Multi Input Multi Output,MIMO)传输,MIMO传输可以是单用户MIMO(Single User MIMO,SU-MIMO)或多用户MIMO(Multiple User MIMO,MU-MIMO)。根据根天线组合的形态和数量,MIMO传输可以是2D-MIMO、3D-MIMO、FD-MIMO或massive-MIMO,也可以是分集传输或预编码传输或波束赋形传输等。
本领域内的技术人员应明白,本公开的实施例可提供为方法、***、或计算机程序产品。因此,本公开可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本公开可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本公开是参照根据本公开实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机可执行指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机可执行指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些处理器可执行指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的处理器可读存储器中,使得存储在该处理器可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程
或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些处理器可执行指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然,本领域的技术人员可以对本公开进行各种改动和变型而不脱离本公开的精神和范围。这样,倘若本公开的这些修改和变型属于本公开权利要求及其等同技术的范围之内,则本公开也意图包含这些改动和变型在内。
Claims (46)
- 一种组播组建立方法,应用于第一终端,包括:发送第一协议数据单元PDU会话建立请求消息,所述第一PDU会话建立请求消息中包含所述第一终端的应用层标识和第二终端的应用层标识;其中,所述第二终端与所述第一终端属于同一虚拟网络VN组。
- 根据权利要求1所述的组播组建立方法,其中,所述发送第一PDU会话建立请求消息之后,所述方法还包括:接收第一PDU会话建立完成消息,所述第一PDU会话建立完成消息中包含第一信息,所述第一信息用于指示网络是否允许所述第一终端建立组播组。
- 一种组播组建立方法,应用于会话管理功能,包括:接收接入和移动性管理功能发送的第一创建会话管理上下文请求消息,所述第一创建会话管理上下文请求消息中包含第一终端的应用层标识和第二终端的应用层标识;其中,所述第一终端为发起建立组播组的终端,所述第二终端与所述第一终端属于同一虚拟网络VN组;根据所述第一创建会话管理上下文请求消息,确定是否允许所述第一终端建立组播组。
- 根据权利要求3所述的组播组建立方法,其中,所述根据所述第一创建会话管理上下文请求消息,确定是否允许所述第一终端建立组播组,包括:根据所述第一终端的应用层标识,向统一数据管理功能查询所述第一终端是否被允许建立组播组。
- 根据权利要求3或4所述的组播组建立方法,其中,在确定允许所述第一终端建立组播组的情况下,所述方法还包括:向所述第二终端发送第一请求消息,所述第一请求消息用于请求所述第二终端加入目标组播组,所述目标组播组为所述第一终端发起建立的组播组。
- 根据权利要求5所述的组播组建立方法,其中,所述第一请求消息中包含所述目标组播组的组播地址信息。
- 根据权利要求5或6所述的组播组建立方法,其中,所述向所述第二 终端发送第一请求消息之后,所述方法还包括:接收接入和移动性管理功能发送的第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息中包含所述第二终端的应用层标识和所述目标组播组的组播地址信息;根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,确定是否允许所述第二终端加入所述目标组播组。
- 根据权利要求7所述的组播组建立方法,其中,所述根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,确定是否允许所述第二终端加入所述目标组播组,包括:根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,向统一数据管理功能和/或策略控制功能查询所述第二终端是否被允许加入所述目标组播组。
- 根据权利要求7或8所述的组播组建立方法,其中,在确定允许所述第二终端加入所述目标组播组的情况下,所述方法还包括:向所述第二终端的协议数据单元PDU会话路径上的用户面功能发送所述目标组播组的数据匹配和转发规则。
- 根据权利要求9所述的组播组建立方法,其中,所述方法还包括:向所述第一终端的PDU会话路径上的用户面功能发送组级会话修改请求消息,所述组级会话修改请求消息中包含所述目标组播组的数据匹配和转发规则。
- 根据权利要求3所述的组播组建立方法,其中,所述方法还包括:向所述第一终端发送第一PDU会话建立完成消息,所述第一PDU会话建立完成消息中包含第一信息,所述第一信息用于指示网络是否允许所述第一终端建立组播组。
- 根据权利要求7所述的组播组建立方法,其中,所述方法还包括:向所述第二终端发送第二PDU会话建立完成消息,所述第二PDU会话建立完成消息中包含第二信息,所述第二信息用于指示所述第二终端是否成 功加入所述目标组播组。
- 一种组播组建立方法,应用于第二终端,包括:接收第一请求消息,所述第一请求消息用于请求所述第二终端加入目标组播组;所述目标组播组为第一终端发起建立的组播组,所述第一终端与所述第二终端属于同一虚拟网络VN组;根据所述第一请求消息,发送第二协议数据单元PDU会话建立请求消息或第一PDU会话修改请求消息,所述第二PDU会话建立请求消息或所述第一PDU会话修改请求消息中包含所述第二终端的应用层标识和所述目标组播组的组播地址信息。
- 根据权利要求13所述的组播组建立方法,其中,所述第一请求消息中包含所述目标组播组的组播地址信息。
- 根据权利要求13或14所述的组播组建立方法,其中,所述发送第二PDU会话建立请求消息之后,所述方法还包括:接收第二PDU会话建立完成消息,所述第二PDU会话建立完成消息中包含第二信息,所述第二信息用于指示所述第二终端是否成功加入所述目标组播组。
- 一种第一终端,包括存储器,收发机,处理器;存储器,用于存储计算机程序;收发机,用于在所述处理器的控制下收发数据;处理器,用于读取所述存储器中的计算机程序并执行以下操作:发送第一协议数据单元PDU会话建立请求消息,所述第一PDU会话建立请求消息中包含所述第一终端的应用层标识和第二终端的应用层标识;其中,所述第二终端与所述第一终端属于同一虚拟网络VN组。
- 根据权利要求16所述的第一终端,其中,所述发送第一PDU会话建立请求消息之后,所述操作还包括:接收第一PDU会话建立完成消息,所述第一PDU会话建立完成消息中包含第一信息,所述第一信息用于指示网络是否允许所述第一终端建立组播组。
- 一种会话管理功能,包括存储器,收发机,处理器;存储器,用于存储计算机程序;收发机,用于在所述处理器的控制下收发数据;处理器,用于读取所述存储器中的计算机程序并执行以下操作:接收接入和移动性管理功能发送的第一创建会话管理上下文请求消息,所述第一创建会话管理上下文请求消息中包含第一终端的应用层标识和第二终端的应用层标识;其中,所述第一终端为发起建立组播组的终端,所述第二终端与所述第一终端属于同一虚拟网络VN组;根据所述第一创建会话管理上下文请求消息,确定是否允许所述第一终端建立组播组。
- 根据权利要求18所述的会话管理功能,其中,所述根据所述第一创建会话管理上下文请求消息,确定是否允许所述第一终端建立组播组,包括:根据所述第一终端的应用层标识,向统一数据管理功能查询所述第一终端是否被允许建立组播组。
- 根据权利要求18所述的会话管理功能,其中,在确定允许所述第一终端建立组播组的情况下,所述操作还包括:向所述第二终端发送第一请求消息,所述第一请求消息用于请求所述第二终端加入目标组播组,所述目标组播组为所述第一终端发起建立的组播组。
- 根据权利要求20所述的会话管理功能,其中,所述第一请求消息中包含所述目标组播组的组播地址信息。
- 根据权利要求20或21所述的会话管理功能,其中,所述向所述第二终端发送第一请求消息之后,所述操作还包括:接收接入和移动性管理功能发送的第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息中包含所述第二终端的应用层标识和所述目标组播组的组播地址信息;根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,确定是否允许所述第二终端加入所述目标组播组。
- 根据权利要求22所述的会话管理功能,其中,所述根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,确定 是否允许所述第二终端加入所述目标组播组,包括:根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,向统一数据管理功能和/或策略控制功能查询所述第二终端是否被允许加入所述目标组播组。
- 根据权利要求22所述的会话管理功能,其中,在确定允许所述第二终端加入所述目标组播组的情况下,所述操作还包括:向所述第二终端的协议数据单元PDU会话路径上的用户面功能发送所述目标组播组的数据匹配和转发规则。
- 根据权利要求24所述的会话管理功能,其中,所述操作还包括:向所述第一终端的PDU会话路径上的用户面功能发送组级会话修改请求消息,所述组级会话修改请求消息中包含所述目标组播组的数据匹配和转发规则。
- 根据权利要求18所述的会话管理功能,其中,所述操作还包括:向所述第一终端发送第一PDU会话建立完成消息,所述第一PDU会话建立完成消息中包含第一信息,所述第一信息用于指示网络是否允许所述第一终端建立组播组。
- 根据权利要求22所述的会话管理功能,其中,所述操作还包括:向所述第二终端发送第二PDU会话建立完成消息,所述第二PDU会话建立完成消息中包含第二信息,所述第二信息用于指示所述第二终端是否成功加入所述目标组播组。
- 一种第二终端,包括存储器,收发机,处理器;存储器,用于存储计算机程序;收发机,用于在所述处理器的控制下收发数据;处理器,用于读取所述存储器中的计算机程序并执行以下操作:接收第一请求消息,所述第一请求消息用于请求所述第二终端加入目标组播组;所述目标组播组为第一终端发起建立的组播组,所述第一终端与所述第二终端属于同一虚拟网络VN组;根据所述第一请求消息,发送第二协议数据单元PDU会话建立请求消息或第一PDU会话修改请求消息,所述第二PDU会话建立请求消息或所述第 一PDU会话修改请求消息中包含所述第二终端的应用层标识和所述目标组播组的组播地址信息。
- 根据权利要求28所述的第二终端,其中,所述第一请求消息中包含所述目标组播组的组播地址信息。
- 根据权利要求28所述的第二终端,其中,所述发送第二PDU会话建立请求消息之后,所述操作还包括:接收第二PDU会话建立完成消息,所述第二PDU会话建立完成消息中包含第二信息,所述第二信息用于指示所述第二终端是否成功加入所述目标组播组。
- 一种组播组建立装置,包括:第一发送单元,用于发送第一协议数据单元PDU会话建立请求消息,所述第一PDU会话建立请求消息中包含第一终端的应用层标识和第二终端的应用层标识;其中,所述第二终端与所述第一终端属于同一虚拟网络VN组。
- 根据权利要求31所述的组播组建立装置,其中,所述装置还包括:第一接收单元,用于接收第一PDU会话建立完成消息,所述第一PDU会话建立完成消息中包含第一信息,所述第一信息用于指示网络是否允许所述第一终端建立组播组。
- 一种组播组建立装置,包括:第二接收单元,用于接收接入和移动性管理功能发送的第一创建会话管理上下文请求消息,所述第一创建会话管理上下文请求消息中包含第一终端的应用层标识和第二终端的应用层标识;其中,所述第一终端为发起建立组播组的终端,所述第二终端与所述第一终端属于同一虚拟网络VN组;确定单元,用于根据所述第一创建会话管理上下文请求消息,确定是否允许所述第一终端建立组播组。
- 根据权利要求33所述的组播组建立装置,其中,所述根据所述第一创建会话管理上下文请求消息,确定是否允许所述第一终端建立组播组,包括:根据所述第一终端的应用层标识,向统一数据管理功能查询所述第一终端是否被允许建立组播组。
- 根据权利要求33或34所述的组播组建立装置,其中,所述装置还包括第二发送单元,用于:在确定允许所述第一终端建立组播组的情况下,向所述第二终端发送第一请求消息,所述第一请求消息用于请求所述第二终端加入目标组播组,所述目标组播组为所述第一终端发起建立的组播组。
- 根据权利要求35所述的组播组建立装置,其中,所述第一请求消息中包含所述目标组播组的组播地址信息。
- 根据权利要求35或36所述的组播组建立装置,其中,所述第二接收单元还用于:接收接入和移动性管理功能发送的第二创建会话管理上下文请求消息或第一更新会话管理上下文请求消息,所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息中包含所述第二终端的应用层标识和所述目标组播组的组播地址信息;所述确定单元还用于:根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,确定是否允许所述第二终端加入所述目标组播组。
- 根据权利要求37所述的组播组建立装置,其中,所述根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,确定是否允许所述第二终端加入所述目标组播组,包括:根据所述第二创建会话管理上下文请求消息或所述第一更新会话管理上下文请求消息,向统一数据管理功能和/或策略控制功能查询所述第二终端是否被允许加入所述目标组播组。
- 根据权利要求37或38所述的组播组建立装置,其中,所述第二发送单元还用于:在确定允许所述第二终端加入所述目标组播组的情况下,向所述第二终端的协议数据单元PDU会话路径上的用户面功能发送所述目标组播组的数据匹配和转发规则。
- 根据权利要求39所述的组播组建立装置,其中,所述第二发送单元还用于:向所述第一终端的PDU会话路径上的用户面功能发送组级会话修改请求消息,所述组级会话修改请求消息中包含所述目标组播组的数据匹配和转发规则。
- 根据权利要求33所述的组播组建立装置,其中,所述第二发送单元还用于:向所述第一终端发送第一PDU会话建立完成消息,所述第一PDU会话建立完成消息中包含第一信息,所述第一信息用于指示网络是否允许所述第一终端建立组播组。
- 根据权利要求37所述的组播组建立装置,其中,所述第二发送单元还用于:向所述第二终端发送第二PDU会话建立完成消息,所述第二PDU会话建立完成消息中包含第二信息,所述第二信息用于指示所述第二终端是否成功加入所述目标组播组。
- 一种组播组建立装置,包括:第三接收单元,用于接收第一请求消息,所述第一请求消息用于请求第二终端加入目标组播组;所述目标组播组为第一终端发起建立的组播组,所述第一终端与所述第二终端属于同一虚拟网络VN组;第三发送单元,用于根据所述第一请求消息,发送第二协议数据单元PDU会话建立请求消息或第一PDU会话修改请求消息,所述第二PDU会话建立请求消息或所述第一PDU会话修改请求消息中包含所述第二终端的应用层标识和所述目标组播组的组播地址信息。
- 根据权利要求43所述的组播组建立装置,其中,所述第一请求消息中包含所述目标组播组的组播地址信息。
- 根据权利要求43或44所述的组播组建立装置,其中,所述第三接收单元还用于:接收第二PDU会话建立完成消息,所述第二PDU会话建立完成消息中 包含第二信息,所述第二信息用于指示所述第二终端是否成功加入所述目标组播组。
- 一种计算机可读存储介质,所述计算机可读存储介质存储有计算机程序,所述计算机程序用于使计算机执行权利要求1至2任一项所述的方法,或执行权利要求3至12任一项所述的方法,或执行权利要求12至15任一项所述的方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202211559733.XA CN118158623A (zh) | 2022-12-06 | 2022-12-06 | 组播组建立方法、设备、装置及存储介质 |
CN202211559733.X | 2022-12-06 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2024120132A1 true WO2024120132A1 (zh) | 2024-06-13 |
Family
ID=91284026
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2023/131504 WO2024120132A1 (zh) | 2022-12-06 | 2023-11-14 | 组播组建立方法、设备、装置及存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN118158623A (zh) |
WO (1) | WO2024120132A1 (zh) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112584328A (zh) * | 2019-09-30 | 2021-03-30 | 华为技术有限公司 | 组播通信方法及其装置 |
CN113660102A (zh) * | 2019-06-17 | 2021-11-16 | 腾讯科技(深圳)有限公司 | 虚拟网络群组的组播组的组播方法、装置、设备及*** |
WO2022035187A1 (en) * | 2020-08-12 | 2022-02-17 | Samsung Electronics Co., Ltd. | Apparatus and method for management of routing information and session control for unmanned aerial system (uas) communication |
CN114828165A (zh) * | 2021-01-18 | 2022-07-29 | 华为技术有限公司 | 一种通信方法及通信装置 |
-
2022
- 2022-12-06 CN CN202211559733.XA patent/CN118158623A/zh active Pending
-
2023
- 2023-11-14 WO PCT/CN2023/131504 patent/WO2024120132A1/zh unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113660102A (zh) * | 2019-06-17 | 2021-11-16 | 腾讯科技(深圳)有限公司 | 虚拟网络群组的组播组的组播方法、装置、设备及*** |
CN112584328A (zh) * | 2019-09-30 | 2021-03-30 | 华为技术有限公司 | 组播通信方法及其装置 |
WO2022035187A1 (en) * | 2020-08-12 | 2022-02-17 | Samsung Electronics Co., Ltd. | Apparatus and method for management of routing information and session control for unmanned aerial system (uas) communication |
CN114828165A (zh) * | 2021-01-18 | 2022-07-29 | 华为技术有限公司 | 一种通信方法及通信装置 |
Non-Patent Citations (1)
Title |
---|
HUAWEI, HISILICON: "Procedures for support of 5G VN group communication", 3GPP DRAFT; S2-1907698 TS23.502 CR1641_PROCEDURES FOR SUPPORT OF 5G VN GROUP COMMUNICATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Sapporo, Japan; 20190624 - 20190628, 18 June 2019 (2019-06-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051752665 * |
Also Published As
Publication number | Publication date |
---|---|
CN118158623A (zh) | 2024-06-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022028041A1 (zh) | 用户终端与网络进行通信的方法、终端、网络设备及装置 | |
WO2023000884A1 (zh) | 多播会话处理方法、网络功能实体、装置及存储介质 | |
WO2022171154A1 (zh) | 数据分析方法、装置、电子设备及存储介质 | |
WO2024120132A1 (zh) | 组播组建立方法、设备、装置及存储介质 | |
WO2022156439A1 (zh) | 信息传输方法、装置、基站及介质 | |
WO2024120268A1 (zh) | 一种信息处理方法、装置及设备 | |
CN114980305A (zh) | 定位参考信号的配置方法、装置及终端 | |
WO2024067398A1 (zh) | 紧急业务的处理方法及装置 | |
WO2023020276A1 (zh) | 组播广播业务数据传输方法、装置、设备以及存储介质 | |
WO2023284474A1 (zh) | Amf选择方法、设备、装置及存储介质 | |
WO2024082903A1 (zh) | 协议数据单元pdu会话的建立方法及装置 | |
WO2024078580A1 (zh) | 非紧急业务的处理方法及装置 | |
WO2024008181A1 (zh) | 同步传输组确定方法、终端及核心网网元 | |
WO2024082839A1 (zh) | 一种信息传输方法、装置及设备 | |
WO2023185573A1 (zh) | 一种信息处理方法、装置及设备 | |
WO2024067322A1 (zh) | 候选小区配置的变更方法、装置、终端和网络设备 | |
WO2024067332A1 (zh) | 路径选择方法、信息上报方法及装置 | |
WO2023125107A1 (zh) | 一种信息处理方法、装置及可读存储介质 | |
WO2024027584A1 (zh) | 多播业务的业务数据接收方法、设备、装置及存储介质 | |
WO2023029679A1 (zh) | 第一中继节点发现方法、装置及存储介质 | |
WO2024120194A1 (zh) | 算网融合方法、装置及存储介质 | |
WO2023077948A1 (zh) | 一种通信的方法和装置 | |
WO2023207595A1 (zh) | 一种资源调度方法、装置、网络设备及网元 | |
WO2024098879A1 (zh) | 信息传输方法、装置、终端及网络设备 | |
WO2023212930A1 (zh) | 通信方法、装置、设备以及存储介质 |