ABSTRACT
Abstract
An apparatus in a network function comprising at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to: determine that a protocol data unit session for a user equipment is to be updated to add or modify multicast information; and provide multicast context information associated with said user equipment which causes said user equipment to receive multicast data associated with said multicast context information.
Description
This application is a national phase entry of Patent Cooperation Treaty Application No. PCT/EP2017/082480 filed Dec. 12, 2017, entitled âMETHOD, SYSTEM AND APPARATUS FOR MULTICAST SESSION MANAGEMENT IN 5G COMMUNICATION NETWORK,â the disclosure of which is incorporated herein by reference in its entirety.
FIELD
The present application relates to a method, apparatus, system and computer program and in particular but not exclusively to a method and apparatus for multicast session management in a 5G or New Radio (NR) communications network.
BACKGROUND
A communication system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, base stations/access points and/or other nodes by providing carriers between the various entities involved in the communications path. A communication system can be provided for example by means of a communication network and one or more compatible communication devices. The communication sessions may comprise, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and/or content data and so on. Non-limiting examples of services provided comprise two-way or multi-way calls, data communication or multimedia services and access to a data network system, such as the Internet.
In a wireless communication system at least a part of a communication session between at least two stations occurs over a wireless link.
A user can access the communication system by means of an appropriate communication device or terminal. A communication device of a user is often referred to as user equipment (UE). A communication device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly with other users. The communication device may access a carrier provided by a station or access point, and transmit and/or receive communications on the carrier.
The communication system and associated devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved. Communication protocols and/or parameters which shall be used for the connection are also typically defined. One example of a communications system is UTRAN (3G radio), long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS), and now 5G New Radio (NR) radio-access technology with 5G Core Network (5GC). 5G NR is being standardized by the 3rd Generation Partnership Project (3GPP).
Multicast and broadcast in cellular networks is an area of discussion. Multicast session definition and management architecture for delivering content using multicast/broadcast in LTE-Advanced networks are known. Here wide-area delivery of content using multicast/broadcast is implemented using multicast broadcast single frequency networks (MBSFN) areas where the same content is delivered over the air using synchronized time-frequency physical resources. For delivery of such content to a smaller area, single cell-point-to-multipoint (SC-PTM) technology was developed.
SUMMARY
According to an aspect, there is provided a an apparatus comprising at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to: determine that a protocol data unit session for a user equipment is to be updated to add or modify multicast information; and provide multicast context information associated with said user equipment.
The apparatus may be configured to receive a request caused by the user equipment, said request initiating the updating of the protocol data unit session of that user equipment.
The request may comprise information about an interest of said user equipment to receive data from a multicast group.
The request may comprise a protocol data unit session update request.
The apparatus may be configured to initiate the updating of the protocol data unit session of the user equipment.
The apparatus may be configured to initiate the updating of the protocol data unit session in response to a policy and control function.
The apparatus may be configured to initiate the updating of the protocol data unit session in response to modification of a policy.
The apparatus may be configured to initiate the updating of the protocol data unit session in response to an update of subscription data.
The apparatus may be configured to initiate the updating of the protocol data unit session in response to a trigger event.
The trigger event may comprise a quality of service related event.
The apparatus may be configured to determine that the protocol data unit session for the user equipment is to be updated n in response to an access node initiated modification.
The apparatus may be configured to receive information about a user plane event and in response to receiving said event determining that said protocol data session is to be updated.
The user plane event may comprise reception of a multicast listener report.
The apparatus may be configured to determine if a multicast context for an identified multicast group exists.
When said apparatus determines that the multicast context for the identified multicast group does not exist in the network, the apparatus may be configured to create a multicast context for the identified multicast group.
The apparatus may be configured to determine if the apparatus has multicast context for an identified multicast group.
The apparatus may be configured to fetch at least one of multicast subscription data and multicast context data.
The apparatus may be configured to cause a multicast context to be created.
The apparatus may be configured to transmit a session management update message with multicast context information comprising at least of: session management information for at least one radio access node and at least one user equipment.
The session management information may comprise at least one of: a multicast packet data unit identifier, a session identifier, at least one quality of service profile, core network tunnel information, a single network slice selection assistance information, session-AMBR information; a multicast packet data unit identifier, a session identifier, at least one quality of service profile, session-AMBR information and at least one of a multicast group identifier.
The session management information may comprise at least one of: a protocol data unit session identifier, a multicast identifier associated with a multicast group, at least one quality of service profile, core network tunnel information, a single network slice selection assistance information, and session-AMBR information.
The session management information may comprise in a first container at least one of: a protocol data unit session identifier, a multicast identifier associated with a multicast group, at least one quality of service profile, core network tunnel information, a single network slice selection assistance information, and session-AMBR information.
The multicast context identifier may be associated with a multicast context of multicast group.
The session management information may comprise in a second container at least one of: a protocol data unit session identifier, a multicast identifier of a multicast group, at least one quality of service profile, and session-AMBR information.
The apparatus may be provided in a session management function.
According to another aspect, there is provided an apparatus comprising at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to: provide information about a user plane event for a user equipment when a protocol data session is to be updated for the user equipment to add or modify multicast information; and receive a session establishment or modification request associated with the multicast information.
The user plane event may comprise reception of a multicast listener report.
The apparatus may be provided in a user plane function.
According to another aspect, there is provided an apparatus in an access node comprising at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to: receive a session establishment or modification request associated with multicast information for a at least one user equipment; establish a tunnel with a user plane function using the said multicast information; receive from a user plane function data for multicasting/broadcasting; and transmit using a set of radio bearers the data for multicasting/broadcasting to the at least one user equipment, the at least one user equipment identified in the session establishment or modification request as being interested in receiving data from a multicasting/broadcasting group associated with the data for multicasting/broadcasting.
The apparatus may be configured to cause a message to be transmitted comprising session management information when a least one quality of service target cannot be fulfilled.
According to another aspect, there is provided an apparatus in a user equipment comprising at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to: cause a request to be sent indicating at least an interest to receive multicast data; and receive a session management update message with multicast information comprising at least an indication that a multicast context has been one of added and created.
The request may be at least one of: a protocol data unit session modification request; and a user plane packet comprising at least an indication of at least an interest to receive multicast data.
The apparatus may be configured to cause the protocol data unit session modification request to be sent in response to a multicast listener report for which said user equipment does not have the associated multicast context.
The apparatus may be configured to receive a multicast listener report after a multicast context has been one of added and created and then to discard the multicast listener report.
According to another aspect there is provided an apparatus in a user equipment comprising at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to: receive a session management update message with multicast information comprising at least an indication that a multicast context has been one of added and created; receive a multicast listener report after a multicast context has been one of added and created; and discard the multicast listener report.
According to another aspect, there is provided a method comprising: determining that a protocol data unit session for a user equipment is to be updated to add or modify multicast information; and providing multicast context information associated with said user equipment.
The method may comprise receiving a request caused by the user equipment, said request initiating the updating of the protocol data unit session of that user equipment.
The request may comprise information about an interest of said user equipment to receive data from a multicast group.
The request may comprise a protocol data unit session update request.
The method may comprise initiating the updating of the protocol data unit session the user equipment.
The method may comprise initiating the updating of the protocol data unit session in response to a policy and control function.
The method may comprise initiating the updating of the protocol data unit session in response to modification of a policy.
The method may comprise initiating the updating of the protocol data unit session in response to an update of subscription data.
The method may comprise initiating the updating of the protocol data unit session in response to a trigger event.
The trigger event may comprise a quality of service related event.
The method may comprise determining that the protocol data unit session for the user equipment is to be updated in response to an access node initiated modification.
The method may comprise receiving information about a user plane event and in response to receiving said event determining that said protocol data session is to be updated.
The user plane event may comprise reception of a multicast listener report.
The method may comprise determining if the apparatus has multicast context for an identified multicast group.
The method may comprise determining if a multicast context for an identified multicast group exists.
When it is determined that the multicast context for the identified multicast group does not exist in the network, the method may comprise creating a multicast context for the identified multicast group.
The method may comprise fetching at least one of multicast subscription data and multicast context data.
The method may comprise causing a multicast context to be created.
The method may comprise transmitting a session management update message with multicast context information comprising at least of: session management information for at least one radio access node and at least one user equipment.
The session management information may comprise at least one of: a multicast packet data unit identifier, a session identifier, at least one quality of service profile, core network tunnel information, a single network slice selection assistance information, session-AMBR information; a multicast packet data unit identifier, a session identifier, at least one quality of service profile, session-AMBR information and at least one of a multicast group identifier.
The session management information may comprise at least one of: a protocol data unit session identifier, a multicast identifier associated with a multicast group, at least one quality of service profile, core network tunnel information, a single network slice selection assistance info
This application is a national phase entry of Patent Cooperation Treaty Application No. PCT/EP2017/082480 filed Dec. 12, 2017, entitled âMETHOD, SYSTEM AND APPARATUS FOR MULTICAST SESSION MANAGEMENT IN 5G COMMUNICATION NETWORK,â the disclosure of which is incorporated herein by reference in its entirety.
FIELD
The present application relates to a method, apparatus, system and computer program and in particular but not exclusively to a method and apparatus for multicast session management in a 5G or New Radio (NR) communications network.
BACKGROUND
A communication system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, base stations/access points and/or other nodes by providing carriers between the various entities involved in the communications path. A communication system can be provided for example by means of a communication network and one or more compatible communication devices. The communication sessions may comprise, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and/or content data and so on. Non-limiting examples of services provided comprise two-way or multi-way calls, data communication or multimedia services and access to a data network system, such as the Internet.
In a wireless communication system at least a part of a communication session between at least two stations occurs over a wireless link.
A user can access the communication system by means of an appropriate communication device or terminal. A communication device of a user is often referred to as user equipment (UE). A communication device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly with other users. The communication device may access a carrier provided by a station or access point, and transmit and/or receive communications on the carrier.
The communication system and associated devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved. Communication protocols and/or parameters which shall be used for the connection are also typically defined. One example of a communications system is UTRAN (3G radio), long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS), and now 5G New Radio (NR) radio-access technology with 5G Core Network (5GC). 5G NR is being standardized by the 3rd Generation Partnership Project (3GPP).
Multicast and broadcast in cellular networks is an area of discussion. Multicast session definition and management architecture for delivering content using multicast/broadcast in LTE-Advanced networks are known. Here wide-area delivery of content using multicast/broadcast is implemented using multicast broadcast single frequency networks (MBSFN) areas where the same content is delivered over the air using synchronized time-frequency physical resources. For delivery of such content to a smaller area, single cell-point-to-multipoint (SC-PTM) technology was developed.
SUMMARY
According to an aspect, there is provided a an apparatus comprising at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to: determine that a protocol data unit session for a user equipment is to be updated to add or modify multicast information; and provide multicast context information associated with said user equipment.
The apparatus may be configured to receive a request caused by the user equipment, said request initiating the updating of the protocol data unit session of that user equipment.
The request may comprise information about an interest of said user equipment to receive data from a multicast group.
The request may comprise a protocol data unit session update request.
The apparatus may be configured to initiate the updating of the protocol data unit session of the user equipment.
The apparatus may be configured to initiate the updating of the protocol data unit session in response to a policy and control function.
The apparatus may be configured to initiate the updating of the protocol data unit session in response to modification of a policy.
The apparatus may be configured to initiate the updating of the protocol data unit session in response to an update of subscription data.
The apparatus may be configured to initiate the updating of the protocol data unit session in response to a trigger event.
The trigger event may comprise a quality of service related event.
The apparatus may be configured to determine that the protocol data unit session for the user equipment is to be updated n in response to an access node initiated modification.
The apparatus may be configured to receive information about a user plane event and in response to receiving said event determining that said protocol data session is to be updated.
The user plane event may comprise reception of a multicast listener report.
The apparatus may be configured to determine if a multicast context for an identified multicast group exists.
When said apparatus determines that the multicast context for the identified multicast group does not exist in the network, the apparatus may be configured to create a multicast context for the identified multicast group.
The apparatus may be configured to determine if the apparatus has multicast context for an identified multicast group.
The apparatus may be configured to fetch at least one of multicast subscription data and multicast context data.
The apparatus may be configured to cause a multicast context to be created.
The apparatus may be configured to transmit a session management update message with multicast context information comprising at least of: session management information for at least one radio access node and at least one user equipment.
The session management information may comprise at least one of: a multicast packet data unit identifier, a session identifier, at least one quality of service profile, core network tunnel information, a single network slice selection assistance information, session-AMBR information; a multicast packet data unit identifier, a session identifier, at least one quality of service profile, session-AMBR information and at least one of a multicast group identifier.
The session management information may comprise at least one of: a protocol data unit session identifier, a multicast identifier associated with a multicast group, at least one quality of service profile, core network tunnel information, a single network slice selection assistance information, and session-AMBR information.
The session management information may comprise in a first container at least one of: a protocol data unit session identifier, a multicast identifier associated with a multicast group, at least one quality of service profile, core network tunnel information, a single network slice selection assistance information, and session-AMBR information.
The multicast context identifier may be associated with a multicast context of multicast group.
The session management information may comprise in a second container at least one of: a protocol data unit session identifier, a multicast identifier of a multicast group, at least one quality of service profile, and session-AMBR information.
The apparatus may be provided in a session management function.
According to another aspect, there is provided an apparatus comprising at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to: provide information about a user plane event for a user equipment when a protocol data session is to be updated for the user equipment to add or modify multicast information; and receive a session establishment or modification request associated with the multicast information.
The user plane event may comprise reception of a multicast listener report.
The apparatus may be provided in a user plane function.
According to another aspect, there is provided an apparatus in an access node comprising at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to: receive a session establishment or modification request associated with multicast information for a at least one user equipment; establish a tunnel with a user plane function using the said multicast information; receive from a user plane function data for multicasting/broadcasting; and transmit using a set of radio bearers the data for multicasting/broadcasting to the at least one user equipment, the at least one user equipment identified in the session establishment or modification request as being interested in receiving data from a multicasting/broadcasting group associated with the data for multicasting/broadcasting.
The apparatus may be configured to cause a message to be transmitted comprising session management information when a least one quality of service target cannot be fulfilled.
According to another aspect, there is provided an apparatus in a user equipment comprising at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to: cause a request to be sent indicating at least an interest to receive multicast data; and receive a session management update message with multicast information comprising at least an indication that a multicast context has been one of added and created.
The request may be at least one of: a protocol data unit session modification request; and a user plane packet comprising at least an indication of at least an interest to receive multicast data.
The apparatus may be configured to cause the protocol data unit session modification request to be sent in response to a multicast listener report for which said user equipment does not have the associated multicast context.
The apparatus may be configured to receive a multicast listener report after a multicast context has been one of added and created and then to discard the multicast listener report.
According to another aspect there is provided an apparatus in a user equipment comprising at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to: receive a session management update message with multicast information comprising at least an indication that a multicast context has been one of added and created; receive a multicast listener report after a multicast context has been one of added and created; and discard the multicast listener report.
According to another aspect, there is provided a method comprising: determining that a protocol data unit session for a user equipment is to be updated to add or modify multicast information; and providing multicast context information associated with said user equipment.
The method may comprise receiving a request caused by the user equipment, said request initiating the updating of the protocol data unit session of that user equipment.
The request may comprise information about an interest of said user equipment to receive data from a multicast group.
The request may comprise a protocol data unit session update request.
The method may comprise initiating the updating of the protocol data unit session the user equipment.
The method may comprise initiating the updating of the protocol data unit session in response to a policy and control function.
The method may comprise initiating the updating of the protocol data unit session in response to modification of a policy.
The method may comprise initiating the updating of the protocol data unit session in response to an update of subscription data.
The method may comprise initiating the updating of the protocol data unit session in response to a trigger event.
The trigger event may comprise a quality of service related event.
The method may comprise determining that the protocol data unit session for the user equipment is to be updated in response to an access node initiated modification.
The method may comprise receiving information about a user plane event and in response to receiving said event determining that said protocol data session is to be updated.
The user plane event may comprise reception of a multicast listener report.
The method may comprise determining if the apparatus has multicast context for an identified multicast group.
The method may comprise determining if a multicast context for an identified multicast group exists.
When it is determined that the multicast context for the identified multicast group does not exist in the network, the method may comprise creating a multicast context for the identified multicast group.
The method may comprise fetching at least one of multicast subscription data and multicast context data.
The method may comprise causing a multicast context to be created.
The method may comprise transmitting a session management update message with multicast context information comprising at least of: session management information for at least one radio access node and at least one user equipment.
The session management information may comprise at least one of: a multicast packet data unit identifier, a session identifier, at least one quality of service profile, core network tunnel information, a single network slice selection assistance information, session-AMBR information; a multicast packet data unit identifier, a session identifier, at least one quality of service profile, session-AMBR information and at least one of a multicast group identifier.
The session management information may comprise at least one of: a protocol data unit session identifier, a multicast identifier associated with a multicast group, at least one quality of service profile, core network tunnel information, a single network slice selection assistance information, and session-AMBR information.
The session management information may comprise in a first container at least one of: a protocol data unit session identifier, a multicast identifier associated with a multicast group, at least one quality of service profile, core network tunnel information, a single network slice selection assistance information, and session-AMBR information.
The multicast context identifier may be associated with a multicast context of multicast group.
The session management information may comprise in a second container at least one of: a protocol data unit session identifier, a multicast identifier of a multicast group, at least one quality of service profile, and session-AMBR information.
The method may be performed in a session management function.
According to another aspect, there is provided a method comprising: providing information about a user plane event for a user equipment when a protocol data session is to be updated for the user equipment to add or modify multicast information; and receiving a session establishment or modification request associated with the multicast information.
The user plane event may comprise reception of a multicast listener report.
The method may be performed in a user plane function.
According to another aspect, there is provided a method comprising: receiving a session establishment or modification request associated with multicast information for a at least one user equipment; establishing a tunnel with a user plane function using the said multicast information; receiving from a user plane function data for multicasting/broadcasting; and transmitting using a set of radio bearers the data for multicasting/broadcasting to the at least one user equipment, the at least one user equipment identified in the session establishment or modification request as being interested in receiving data from a multicasting/broadcasting group associated with the data for multicasting/broadcasting.
The method may comprise causing a message to be transmitted comprising session management information when a least one quality of service target cannot be fulfilled.
According to another aspect, there is provided a method comprising: causing a request to be sent indicating at least an interest to receive multicast data; and receiving a session management update message with multicast information comprising at least an indication that a multicast context has been one of added and created.
The request may be at least one of: a protocol data unit session modification request; and a user plane packet comprising at least an indication of at least an interest to receive multicast data.
The method may comprise causing the protocol data unit session modification request to be sent in response to a multicast listener report for which said user equipment does not have the associated multicast context.
The method may comprise receiving a multicast listener report after a multicast context has been one of added and created and then to discard the multicast listener report.
According to another aspect there is provided a method comprising: receiving a session management update message with multicast information comprising at least an indication that a multicast context has been one of added and created; receiving a multicast listener report after a multicast context has been one of added and created; and discarding the multicast listener report.
According to another aspect, there is provided an apparatus comprising: means for determining that a protocol data unit session for a user equipment is to be updated to add or modify multicast information; and means for providing multicast context information associated with said user equipment.
The apparatus may comprise means for receiving a request caused by the user equipment, said request initiating the updating of the protocol data unit session of that user equipment.
The request may comprise information about an interest of said user equipment to receive data from a multicast group.
The request may comprise a protocol data unit session update request.
The apparatus may comprise means for initiating the updating of the protocol data unit session of the user equipment.
The apparatus may comprise means for initiating the updating of the protocol data unit session in response to a policy and control function.
The apparatus may comprise means for initiating the updating of the protocol data unit session in response to modification of a policy.
The apparatus may comprise means for initiating the updating of the protocol data unit session in response to an update of subscription data.
The apparatus may comprise means for initiating the updating of the protocol data unit session in response to a trigger event.
The trigger event may comprise a quality of service related event.
The apparatus may comprise means for determining that the protocol data unit session for the user equipment is to be updated in response to an access node initiated modification.
The apparatus may comprise means for receiving information about a user plane event and in response to receiving said event determining that said protocol data session is to be updated.
The user plane event may comprise reception of a multicast listener report.
The apparatus may comprise means for determining if a multicast context for an identified multicast group exists.
When it is determined that the multicast context for the identified multicast group does not exist in the network, the apparatus may comprise means for creating a multicast context for the identified multicast group.
The apparatus may comprise means for determining if the apparatus has multicast context for an identified multicast group.
The apparatus may comprise means for fetching at least one of multicast subscription data and multicast context data.
The apparatus may comprise means for causing a multicast context to be created.
The apparatus may comprise means for transmitting a session management update message with multicast context information comprising at least of: session management information for at least one radio access node and at least one user equipment.
The session management information may comprise at least one of: a multicast packet data unit identifier, a session identifier, at least one quality of service profile, core network tunnel information, a single network slice selection assistance information, session-AMBR information; a multicast packet data unit identifier, a session identifier, at least one quality of service profile, session-AMBR information and at least one of a multicast group identifier.
The session management information may comprise at least one of: a protocol data unit session identifier, a multicast identifier associated with a multicast group, at least one quality of service profile, core network tunnel information, a single network slice selection assistance information, and session-AMBR information.
The session management information may comprise in a first container at least one of: a protocol data unit session identifier, a multicast identifier associated with a multicast group, at least one quality of service profile, core network tunnel information, a single network slice selection assistance information, and session-AMBR information.
The multicast context identifier may be associated with a multicast context of multicast group.
The session management information may comprise in a second container at least one of: a protocol data unit session identifier, a multicast identifier of a multicast group, at least one quality of service profile, and session-AMBR information.
The apparatus may be provided in a session management function.
According to another aspect, there is provided an apparatus comprising: means for providing information about a user plane event for a user equipment when a protocol data session is to be updated for the user equipment to add or modify multicast information; and means for receiving a session establishment or modification request associated with the multicast information.
The user plane event may comprise reception of a multicast listener report.
The apparatus may be provided in a user plane function.
According to another aspect, there is provided an apparatus comprising: means for receiving a session establishment or modification request associated with multicast information for a at least one user equipment; means for establishing a tunnel with a user plane function using the said multicast information; means for receiving from a user plane function data for multicasting/broadcasting; and means for transmitting using a set of radio bearers the data for multicasting/broadcasting to the at least one user equipment, the at least one user equipment identified in the session establishment or modification request as being interested in receiving data from a multicasting/broadcasting group associated with the data for multicasting/broadcasting.
The apparatus may comprise means for causing a message to be transmitted comprising session management information when a least one quality of service target cannot be fulfilled.
According to another aspect, there is provided an apparatus comprising: means for causing a request to be sent indicating at least an interest to receive multicast data; and means for receiving a session management update message with multicast information comprising at least an indication that a multicast context has been one of added and created.
The request may be at least one of protocol data unit session modification request and a user plane packet comprising at least an indication of at least an interest to receive multicast data.
The apparatus may comprise means for causing the protocol data unit session modification request to be sent in response to a multicast listener report for which said user equipment does not have the associated multicast context.
The apparatus may comprise means for receiving a multicast listener report after a multicast context has been one of added and created and then to discard the multicast listener report.
According to another aspect there is provided an apparatus comprising: means for receiving a session management update message with multicast information comprising at least an indication that a multicast context has been one of added and created; means for receiving a multicast listener report after a multicast context has been one of added and created; and means for discarding the multicast listener report.
In another aspect there is provided a computer program embodied on a non-transitory computer-readable storage medium, the computer program comprising program code for providing any of the above methods.
In another aspect there is provided a computer program product for a computer, comprising software code portions for performing the steps of any of the previous methods, when said product is run.
A computer program comprising program code means adapted to perform the method(s) may be provided. The computer program may be stored and/or otherwise embodied by means of a carrier medium.
In the above, many different embodiments have been described. It should be appreciated that further embodiments may be provided by the combination of any two or more of the embodiments described above.
DESCRIPTION OF FIGURES
Embodiments will now be described, by way of example only, with reference to the accompanying Figures in which:
FIG. 1 shows a schematic diagram of an example communication system comprising a plurality of base stations and a plurality of communication devices;
FIG. 2 shows a schematic diagram of an example mobile communication device;
FIG. 3 shows a schematic diagram of an example control apparatus;
FIG. 4 shows example known multicast/broadcast architecture;
FIG. 5 shows an example 5G NR architecture suitable for implementing some embodiments;
FIG. 6 shows a modification to the architecture of FIG. 5 ;
FIG. 7 shows a modification to the architecture of FIG. 6 ; and
FIGS. 8 a to 8 c shows a flowchart of an example method for supporting multicast/broadcast in a 5G NR architecture according to some embodiments.
DETAILED DESCRIPTION
Some embodiments as discussed in further detail may be in the context of multicast session definition and management in for example 3GPP 5G architecture.
Before explaining in detail the examples, certain general principles of a wireless communication system and mobile communication devices are briefly explained with reference to FIGS. 1 to 2 to assist in understanding the technology underlying the described examples.
In a wireless communication system 100 , such as that shown in FIG. 1 , mobile communication devices or user equipment (UE) 102 , 104 , 105 are provided wireless access via at least one access point or similar wireless transmitting and/or receiving node or point. An access point or base station is referred to as a Node B or generally NB (for example an eNB in LTE and gNB in 5G NR). Base stations are typically controlled by at least one appropriate controller apparatus, so as to enable operation thereof and management of mobile communication devices in communication with the base stations. The controller apparatus may be located in a radio access network (e.g. wireless communication system 100 ) or in a core network (CN) (not shown) and may be implemented as one central apparatus or its functionality may be distributed over several apparatus. The controller apparatus may be part of the base station and/or provided by a separate entity such as a Radio Network Controller. In FIG. 1
control apparatus
108 and 109 are shown to control the respective macro level base stations
106 and 107 . In some systems, the control apparatus may additionally or alternatively be provided in a radio network controller.
LTE (and 5G) systems may however be considered to have a so-called âflatâ architecture, without the provision of RNCs; rather the NB is in communication with a system architecture evolution gateway (SAE-GW) and a mobility management entity (MME), which entities may also be pooled meaning that a plurality of these nodes may serve a plurality (set) of NBs. Each UE is served by only one MME and/or S-GW at a time and the NB keeps track of current association. SAE-GW is a âhigh-levelâ user plane core network element in LTE, which may consist of the S-GW and the P-GW (serving gateway and packet data network gateway, respectively). The functionalities of the S-GW and P-GW are separated and they are not required to be co-located.
In FIG. 1
base stations
106 and 107 are shown as connected to a wider communications network 113 via gateway 112 . A further gateway function may be provided to connect to another network.
The smaller base stations (or relay nodes or RN) 116 , 118 and 120 may also be connected to the network 113 , for example by a separate gateway function and/or via the controllers of the macro level stations. The
base stations
116 , 118 and 120 may be pico or femto level base stations or the like. In the example, station 118 is connected via a gateway 111 whilst station 120 connects via the controller apparatus 108 . The station 116 may be connected via station 107 as will be explained in further detail hereafter. In some embodiments, the smaller stations may not be provided.
A possible mobile communication device will now be described in more detail with reference to FIG. 2 showing a schematic, partially sectioned view of a communication device 200 . Such a communication device is often referred to as user equipment (UE) or terminal. An appropriate mobile communication device may be provided by any device capable of sending and receiving radio signals. Non-limiting examples comprise a mobile station (MS) or mobile device such as a mobile phone or what is known as a âsmart phoneâ, a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), personal data assistant (PDA) or a tablet provided with wireless communication capabilities, or any combinations of these or the like. A mobile communication device may provide, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and so on. Users may thus be offered and provided numerous services via their communication devices. Non-limiting examples of these services comprise two-way or multi-way calls, data communication or multimedia services or simply an access to a data communications network system, such as the Internet. Users may also be provided broadcast or multicast data. Non-limiting examples of the content comprise downloads, television and radio programs, videos, advertisements, various alerts and other information.
The mobile device 200 may receive signals over an air or radio interface 207 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals. In FIG. 2 transceiver apparatus is designated schematically by block 206 . The transceiver apparatus 206 may be provided for example by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.
A mobile device is typically provided with at least one data processing entity 201 , at least one memory 202 and other possible components 203 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices. The data processing, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference 204 . The user may control the operation of the mobile device by means of a suitable user interface such as key pad 205 , voice commands, touch sensitive screen or pad, combinations thereof or the like. A display 208 , a speaker and a microphone can be also provided. Furthermore, a mobile communication device may comprise appropriate connectors (either wired or wireless) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto. The
communication devices
102 , 104 , 105 may access the communication system based on various access techniques.
An example control apparatus (and/or base station) is shown in FIG. 3 . FIG. 3 shows an example of a control apparatus provided in any of the various functions discussed later in relation to FIGS. 5 , 6 and 7 . The control apparatus 300 comprises at least one memory 301 , at least one data processing unit
302 , 303 and an input/ output interface 304 . The control apparatus 300 or processor 302 / 303 can be configured to execute an appropriate software code to provide the control functions.
An example of wireless communication systems are architectures standardized by the 3rd Generation Partnership Project (3GPP). The currently being developed 3GPP based development, release 15, is often referred to as the 5G or NR standards part of long term evolution (LTE) or LTE Advanced Pro of the Universal Mobile Telecommunications System (UMTS) radio-access technology. Other examples of radio access system comprise those provided by base stations of systems that are based on technologies such as wireless local area network (WLAN) and/or WiMax (Worldwide Interoperability for Microwave Access).
As discussed earlier one of the aspects of these wireless communications systems is multicast/broadcast operations over cellular networks. With respect to FIG. 4 an architecture proposed for delivering content using multicast/broadcast in LTE-Advanced networks is shown.
The architecture shows a content provider 401 generating suitable multicast/broadcast content which is forwarded to a broadcast multicast service centre (BMSC) 403 for broadcast/multicast output and to a packet data gateway (P-GW) 405 for unicast output.
The packet data gateway (P-GW) 405 is the link between the mobile device and the services that reside in an external packet network such as the content provider 401 . The P- GW 405 may communicate with a serving gateway (S-GW) 407 .
The S- GW 407 is the gateway which terminates the interface towards E-UTARN. For each UE at given point of time, there is a single S-GW. The S-GW is further in communication with the eNB 409 .
The eNB 409 can receive the content from the S- GW 407 and forward it to the UE 410 over a unicast 402 path.
The architecture further shows a broadcast multicast service centre (BMSC) 403 which is in communication with a multimedia broadcast multicast services-gateway (MBMS-GW) 411 .
The MBMS- GW 411 may be in further communication with an eNB 413 for providing a single cell point to multipoint (SC-PTM) link 404 to an UE 420 or a multicast-broadcast single-frequency network (MBSFN) link in MBSFN area when all cells of MBSFN area are controlled by a single eNB.
The MBMS- GW 411 may also be in communication with a series of eNBs 419 1 , 419 2 , 419 3 which form a multicast-broadcast single-frequency network (MBSFN) area 421 and which communicate to UEs 406 within the MBSFN area the content provided by the content provider.
Also the MBMS- GW 411 may also be in communication with a mobility management entity (MME) 415 . The MME deals with the control plane and handles the signalling related to mobility and security for E-UTRAN access. The MME is in communication with a multi-cell/multicast coordination entity (MCE) 417 .
The MCE 417 is a functional entity providing functions for admission control and allocation of radio resources by the E-UTRAN and for MBMS session control and is configured to control the eNBs 419 1 , 419 2 , 419 3 which form a multicast-broadcast single-frequency network (MBSFN) area 421 .
In other words FIG. 4 shows an architecture for the wide-area delivery of content using multicast/broadcast using multicast broadcast single frequency networks (MBSFN) areas where the same content is delivered over the air using synchronized time-frequency physical resources. For delivery of such content to a smaller area, single cell-point-to-multipoint (SC-PTM) technology was developed.
One aim of content delivery in 5G may be for the simple and/or efficient reuse of unicast architecture. This may reduce infrastructure for the delivery of multicast/broadcast content.
Some of the embodiments described hereafter may improve the traditional MBMS architecture which was designed for the delivery of conventional broadcast content. Linear TV content consumption has been declining and the implementations described hereafter may natively support dynamic delivery of popular content using unicast and multicast capabilities efficiently. This may be without significant additional infrastructure requirements from the network operators' perspective.
The MBMS architecture in 3GPP has been an add-on feature which requires new network entities and interfaces and has a terrestrial broadcast of linear TV approach in mind. As discussed above some embodiments may aim to better fit new service models such as âover-the-topâ media and internet-of-things (IoT) services. Some embodiments may be able to implement and service the consumption of linear TV. An example use case for these embodiments may be the consumption of multimedia feeds during live events by large population of users. With dynamic provisioning of live content through various social media applications, there are emerging trends of ânew media contentâ that is being increasingly consumed in a linear manner (for e.g., Facebook/Twitter/YouTube Live feature). Some embodiments as discussed in further detail later may be configured to provide network capability for delivering multicast content efficiently for such use cases.
Some embodiments may enable support for multicast/broadcast in 5G with a minimal footprint over the unicast architecture. Some embodiments may make multicast/broadcast support an integral part of the 5G system. Some embodiments may provide an efficient transport of multicast traffic.
Some embodiments as discussed herein, in contrast to eMBMS and its MBMS operation on demand (MooD) architecture, which is used to setup MBMS session based on UEs demand, may enhance a UE's context with information about network functions serving multicast traffic for this UE and multicast group. Some embodiments may use a PDU (protocol data unit) session modification procedure to manage the UE context update, and to manage control and user plane network functions for multicast traffic delivery.
In some embodiments either a UE or a UPF (user plane function) triggers a PDU session modification procedure. This may be in response to a user plane event such as a request to transmit a multicast listener's report (MLR) with a multicast address for which UE does not yet have a context by higher layers in the UE or in response to the reception of the MLR by an existing UPF.
It should be noted that there may be network functions in the network used to serve UE's unicast traffic, i.e. SMF (session management function), UPF, AMF (access and mobility function) etc. These functions may be referred to as unicast network functions. During the PDU session modification procedure, the unicast SMF serving the UE may check whether a context for the multicast group exists in the network. If the context does not exist, then the context is created. The network may decide whether what unicast network function i
CLAIMS
Claims ( 14 )
The invention claimed is:
1. An apparatus of a core network, the apparatus comprising at least one processor and at least one memory including computer code for one or more network functions, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to:
receive a protocol data unit session modification request sent by a user equipment, the protocol data unit session modification request comprising information of a multicast group the user equipment has an interest in receiving multicast data from;
determine, based on the information of the multicast group, that a protocol data unit session for a user equipment is to be updated to add or modify a multicast context for the multicast group;
determine that the multicast context for the multicast group does not exist in the core network;
obtain the multicast context for the multicast group; and
provide the multicast context for the multicast group to the user equipment which causes the user equipment to receive multicast data associated with the multicast group.
2. An apparatus as claimed in claim 1 , wherein the at least one memory and the computer code are further configured, with the at least one processor, to cause the apparatus at least to receive the protocol data unit session modification request from the user equipment, the protocol data unit session modification request initiating updating of the protocol data unit session of the user equipment to add or modify multicast context for the multicast group.
3. An apparatus as claimed in claim 1 , wherein the at least one memory and the computer code are further configured, with the at least one processor, to cause the apparatus to initiate updating of the protocol data unit session of the user equipment to add or modify multicast context for the multicast group.
4. An apparatus as claimed in claim 1 , wherein the at least one memory and the computer code are further configured, with the at least one processor, to cause the apparatus to initiate updating of the protocol data unit session to add or modify multicast context for the multicast group in response to a trigger event.
5. An apparatus as claimed in claim 1 , wherein the multicast context includes information about the user equipment's interest in receiving data from the multicast group and further includes associations to a context of at least one other user equipment receiving or having an interest in receiving data from the multicast group.
6. An apparatus as claimed in claim 4 , wherein the triggering event is a user plane event comprising reception of a multicast listener report.
7. An apparatus as claimed in claim 1 , wherein the at least one memory and the computer code are further configured, with the at least one processor, to cause the apparatus to fetch multicast subscription data.
8. An apparatus as claimed in claim 1 , wherein the at least one memory and the computer code are further configured, with the at least one processor, to cause the apparatus to transmit a session management update message with the multicast context for the multicast group, the multicast context for the multicast group comprising at least of: session management information for at least one radio access node and at least the user equipment.
9. An apparatus as claimed in claim 8 , wherein the session management information comprises at least one of: a protocol data unit session identifier for the protocol data unit session, a multicast group identifier associated with the multicast group, at least one quality of service profile, core network tunnel information, a single network slice selection assistance information, and session-aggregate maximum bit rate information.
10. A user equipment comprising at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the user equipment at least to:
send, towards an access and mobility management function of a core network, a protocol data unit modification request to update a protocol data session for the user equipment, the protocol data unit modification request comprising information of a multicast group the user equipment has an interest in receiving multicast data from; and
receive a message comprising at least an indication that a multicast context has been one of added to and created for the protocol data session for the user equipment; and
receive multicast data from the multicast group.
11. The user equipment as claimed in claim 10 , wherein said protocol data unit modification request comprises a user plane packet comprising at least an indication of at least the interest.
12. The user equipment as claimed in claim 10 , wherein the at least one memory and the computer code are further configured, with the at least one processor, to cause the user equipment to cause the protocol data unit modification request to be sent in response to a multicast listener report for which the user equipment does not have the multicast context.
13. The user equipment as claimed in claim 10 , wherein the at least one memory and the computer code are further configured, with the at least one processor, to cause the user equipment to receive a multicast listener report after the multicast context has been one of added to and created for a protocol data unit session for the user equipment and then to discard the multicast listener report.
14. A method comprising:
receiving a protocol data unit session modification request sent by a user equipment, the protocol data unit session modification request comprising information of a multicast group the user equipment has an interest in receiving multicast data from;
determining, based on the information of the multicast group, that a protocol data unit session for a user equipment is to be updated to add or modify multicast context for the multicast group;
determine that the multicast context for the multicast group does not exist in a core network;
obtain the multicast context for the multicast group; and
provide the multicast context for the multicast group to the user equipment which causes the user equipment to receive multicast data associated with the multicast group.
US16/772,092
2017-12-12
2017-12-12
Method, system and apparatus for multicast session management in 5G communication network
Active
US11825385B2
( en )
Applications Claiming Priority (1)
Application Number
Priority Date
Filing Date
Title
PCT/EP2017/082480
WO2019114939A1
( en )
2017-12-12
2017-12-12
Method, system & apparatus for multicast session management in a 5g communication network
Publications (2)
Publication Number
Publication Date
US20210076164A1
US20210076164A1 ( en )
2021-03-11
US11825385B2
true
US11825385B2 ( en )
2023-11-21
Family
ID=60957257
Family Applications (1)
Application Number
Title
Priority Date
Filing Date
US16/772,092
Active
US11825385B2
( en )
2017-12-12
2017-12-12
Method, system and apparatus for multicast session management in 5G communication network
Country Status (3)
Country
Link
US
( 1 )
US11825385B2
( en )
EP
( 1 )
EP3725035B1
( en )
WO
( 1 )
WO2019114939A1
( en )
Families Citing this family (34)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
WO2019034005A1
( en )
*
2017-08-14
2019-02-21
å为ææ¯æéå ¬å¸
Multicast method and device
US11700508B2
( en )
*
2018-01-03
2023-07-11
Interdigital Patent Holdings, Inc.
Multicast and broadcast services in 5G networks for IoT applications
WO2019158218A1
( en )
*
2018-02-19
2019-08-22
Huawei Technologies Co., Ltd.
Apparatus for supporting and influencing qos levels
CN110519172B
( en )
*
2018-05-21
2022-05-13
å为ææ¯æéå ¬å¸
Wireless communication method and apparatus
US11418926B2
( en )
2018-08-14
2022-08-16
Nokia Technologies Oy
Method of multicast data delivery in 5G supporting cloud architecture
WO2020101639A1
( en )
2018-11-12
2020-05-22
Nokia Technologies Oy
Method and apparatus for efficient delivery of source and forward error correction streams in systems supporting mixed unicast multicast transmission
WO2020145031A1
( en )
*
2019-01-09
2020-07-16
Nec Corporation
An access network node
CN110474969B
( en )
*
2019-07-29
2021-07-16
å为ææ¯æéå ¬å¸
Session management method and device
CN114424498B
( en )
*
2019-09-30
2023-06-16
å为ææ¯æéå ¬å¸
Data transmission method, device, system and storage medium
CN112584328B
( en )
*
2019-09-30
2023-03-24
å为ææ¯æéå ¬å¸
Multicast communication method and device
CN112637785B
( en )
*
2019-10-08
2022-04-29
å为ææ¯æéå ¬å¸
Method and apparatus for multicast transmission
CN112788543B
( en )
*
2019-11-07
2023-04-07
å为ææ¯æéå ¬å¸
Communication method, device and equipment
WO2021120072A1
( en )
*
2019-12-18
2021-06-24
å为ææ¯æéå ¬å¸
Multicast communication method and device thereof
EP4087363A4
( en )
*
2020-01-02
2023-01-11
Guangdong Oppo Mobile Telecommunications Corp., Ltd.
TRANSMISSION MODE SWITCHING METHOD, ELECTRONIC DEVICE AND STORAGE MEDIA
WO2021136655A1
( en )
*
2020-01-03
2021-07-08
Telefonaktiebolaget Lm Ericsson (Publ)
Methods for network node awareness of multicast or broadcast service in telecommunication network and related apparatus
CN114868407A
( en )
*
2020-01-07
2022-08-05
Oppo广ä¸ç§»å¨éä¿¡æéå ¬å¸
Broadcast service establishing method and network equipment
US20230081145A1
( en )
*
2020-02-07
2023-03-16
Nokia Technologies Oy
Optimization of 5g mbms/5mbs data delivery over an n3 interface
WO2021159229A1
( en )
*
2020-02-10
2021-08-19
Mediatek Singapore Pte. Ltd.
Methods and apparatus of multicast radio bearer establishment for nr multicast and broadcast services
US12538185B2
( en )
2020-02-13
2026-01-27
Interdigital Patent Holdings, Inc.
Methods of delivery mode switch for multicast and broadcast service in a 5G network
US20230082017A1
( en )
*
2020-02-14
2023-03-16
Kt Corporation
Method and device for processing mbs data
EP4114046A4
( en )
*
2020-03-24
2023-04-12
Huawei Technologies Co., Ltd.
MULTICAST COMMUNICATION METHOD AND COMMUNICATION APPARATUS
CN113660616B
( en )
*
2020-04-10
2022-11-11
å为ææ¯æéå ¬å¸
Communication method and device for multicast/broadcast service
CN113573248B
( en )
*
2020-04-28
2023-06-20
å为ææ¯æéå ¬å¸
Method and device for transmitting data
CN113709677B
( en )
*
2020-05-22
2023-04-11
大å移å¨é信设å¤æéå ¬å¸
Method and device for joining multicast broadcast service MBS session
EP4154469A1
( en )
*
2020-05-22
2023-03-29
Nokia Technologies OY
Apparatus, methods, and computer programs for multicast session management in 5g networks
WO2021233556A1
( en )
*
2020-05-22
2021-11-25
Nokia Technologies Oy
Apparatus, method, and computer program for multicast sessions in location areas in 5g networks
CN120018317A
( en )
*
2020-05-27
2025-05-16
å为ææ¯æéå ¬å¸
A communication method, device and system
CN116491177B
( en )
2020-08-03
2025-01-28
诺åºäºéä¿¡å ¬å¸
Method and apparatus for radio communication
CN114071367B
( en )
*
2020-08-04
2022-09-09
大å移å¨é信设å¤æéå ¬å¸
Unicast-to-multicast conversion method, device, and processor-readable storage medium
JP2023127004A
( en )
*
2020-08-07
2023-09-13
ã·ã£ã¼ãæ ªå¼ä¼ç¤¾
UAV (Unmanned Aerial Vehicle)
CN114126082B
( en )
*
2020-08-31
2025-08-29
å为ææ¯æéå ¬å¸
Communication method and communication device
CN112243199B
( en )
2020-09-30
2023-05-12
è ¾è®¯ç§æï¼æ·±å³ï¼æéå ¬å¸
MBS service switching method, device, computer readable medium and electronic equipment
US12507040B2
( en )
2021-04-06
2025-12-23
Nokia Technologies Oy
Distributing multicast packets in individual protocol data unit (PDU) sessions
CN115942400A
( en )
*
2021-09-15
2023-04-07
ç»´æ²è½¯ä»¶ææ¯æéå ¬å¸
Multicast control, switching configuration method, device and equipment
Citations (12)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US20040185837A1
( en )
*
2003-02-12
2004-09-23
Samsung Electronics Co., Ltd.
Method for managing service context for paging user equipment in a multimedia broadcast/multicast service
US20060109812A1
( en )
*
2002-08-13
2006-05-25
Soeng-Hun Kim
Temporary mobile group identifier generation and distribution method
US20070136762A1
( en )
*
2004-07-23
2007-06-14
Huawei Technologies Co., Ltd.
Method for activating multimedia broadcast/multicast service
US20070232308A1
( en )
*
2004-01-09
2007-10-04
Bergstrom Joachim K O
Method for Multimedia Broadcast Multicast Service Linking for Pmm Idle Mobiles
US20090113487A1
( en )
*
2007-10-30
2009-04-30
General Instrument Corporation
Method and Apparatus for Broadcasting/Multicasting Content from Mobile User Equipment over an MBMS Network
US20120178457A1
( en )
*
2011-01-12
2012-07-12
Liao Ching-Yu
Apparatuses and methods for handling mobility management (mm) back-off timers
US20130279395A1
( en )
*
2010-11-08
2013-10-24
Sharp Kabushiki Kaisha
Mobile communication system, mobile station device, base station device, sgsn, ggsn, mme, mbms gw and mobile communication method
US20150304118A1
( en )
*
2012-03-07
2015-10-22
Commissariat A L'energie Atomique Et Aux Ene Alt
Method for preselecting a router in an rpl network
US20180092133A1
( en )
*
2015-04-02
2018-03-29
Convida Wireless, Llc
Managing mbms membership at the service capability exposure function
US20180242387A1
( en )
*
2014-10-24
2018-08-23
Telefonaktiebolaget Lm Ericsson (Publ)
Maintaining User Plane Session and Restoring Control Plane Session In Case of Control Plane Module Failure of Gateway for Multicast Transmissions
US20190158408A1
( en )
*
2017-11-17
2019-05-23
Huawei Technologies Co., Ltd.
Method and apparatus for traffic routing and path optimization for peer-to-peer communications
US20200267513A1
( en )
*
2017-11-09
2020-08-20
Huawei Technologies Co., Ltd.
Multicast service transmission method and device
2017
2017-12-12
WO
PCT/EP2017/082480
patent/WO2019114939A1/en
not_active
Ceased
2017-12-12
EP
EP17828864.3A
patent/EP3725035B1/en
active
Active
2017-12-12
US
US16/772,092
patent/US11825385B2/en
active
Active
Patent Citations (12)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US20060109812A1
( en )
*
2002-08-13
2006-05-25
Soeng-Hun Kim
Temporary mobile group identifier generation and distribution method
US20040185837A1
( en )
*
2003-02-12
2004-09-23
Samsung Electronics Co., Ltd.
Method for managing service context for paging user equipment in a multimedia broadcast/multicast service
US20070232308A1
( en )
*
2004-01-09
2007-10-04
Bergstrom Joachim K O
Method for Multimedia Broadcast Multicast Service Linking for Pmm Idle Mobiles
US20070136762A1
( en )
*
2004-07-23
2007-06-14
Huawei Technologies Co., Ltd.
Method for activating multimedia broadcast/multicast service
US20090113487A1
( en )
*
2007-10-30
2009-04-30
General Instrument Corporation
Method and Apparatus for Broadcasting/Multicasting Content from Mobile User Equipment over an MBMS Network
US20130279395A1
( en )
*
2010-11-08
2013-10-24
Sharp Kabushiki Kaisha
Mobile communication system, mobile station device, base station device, sgsn, ggsn, mme, mbms gw and mobile communication method
US20120178457A1
( en )
*
2011-01-12
2012-07-12
Liao Ching-Yu
Apparatuses and methods for handling mobility management (mm) back-off timers
US20150304118A1
( en )
*
2012-03-07
2015-10-22
Commissariat A L'energie Atomique Et Aux Ene Alt
Method for preselecting a router in an rpl network
US20180242387A1
( en )
*
2014-10-24
2018-08-23
Telefonaktiebolaget Lm Ericsson (Publ)
Maintaining User Plane Session and Restoring Control Plane Session In Case of Control Plane Module Failure of Gateway for Multicast Transmissions
US20180092133A1
( en )
*
2015-04-02
2018-03-29
Convida Wireless, Llc
Managing mbms membership at the service capability exposure function
US20200267513A1
( en )
*
2017-11-09
2020-08-20
Huawei Technologies Co., Ltd.
Multicast service transmission method and device
US20190158408A1
( en )
*
2017-11-17
2019-05-23
Huawei Technologies Co., Ltd.
Method and apparatus for traffic routing and path optimization for peer-to-peer communications
Non-Patent Citations (6)
* Cited by examiner, â Cited by third party
Title
" 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on the security aspects of the next generation system (Release 14) ", 3GPP Standard; Technical Report; 3GPP TR 33.899, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, vol. SA WG3, No. V1.3.0, Aug. 21, 2017 (Aug. 21, 2017), pp. 1-605, XP051450230, the whole document.
3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; GPRS Tunnelling Protocol (GTP) specification for Gateway Location Register (GLR); (Release 14), 3GPP TS 29.119 v14.0.0 (Mar. 2017). (11 pages).
3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3; (Release 15), 3GPP TS 29.468 v15.1.0 (Sep. 2017). (38 pages).
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multimedia Broadcast/Multicast Service (MBMS); (Release 14), 3GPP TS 23.246 V14.2.0 (Sep. 2017). (76 pages).
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2; (Release 15), 3GPP TS 23.502 v1.2.0 (Sep. 2017). (165 pages).
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2; (Release 15), 3GPP TS 23.501 v1.4.0 (Sep. 2017). (151 pages).
Also Published As
Publication number
Publication date
EP3725035B1
( en )
2024-10-02
EP3725035C0
( en )
2024-10-02
EP3725035A1
( en )
2020-10-21
US20210076164A1
( en )
2021-03-11
WO2019114939A1
( en )
2019-06-20
Similar Documents
Publication
Publication Date
Title
EP3725035B1
( en )
2024-10-02
Method, system & apparatus for multicast session management in a 5g communication network
US12015967B2
( en )
2024-06-18
Method, system and apparatus for multicast session management in 5G communication network
US20240365178A1
( en )
2024-10-31
Methods of delivery mode switch for multicast and broadcast service in a 5g network
EP2928220B1
( en )
2019-05-15
Method, system, base station and cluster epc for establishing group call context
CN110463231A
( en )
2019-11-15
System and method for group-based service provisioning
EP3758312B1
( en )
2023-03-29
Method and system for the creation of a multicast group
US11870601B2
( en )
2024-01-09
Policy control function fallback
WO2021097858A1
( en )
2021-05-27
Communication method and apparatus
WO2023185328A1
( en )
2023-10-05
Communication method and apparatus
CN113746649B
( en )
2022-12-06
Network slice control method and communication device
KR20240004483A
( en )
2024-01-11
MBS session handover method, and systems and devices therefor
CN113573248B
( en )
2023-06-20
Method and device for transmitting data
KR20250028278A
( en )
2025-02-28
Methods and devices for supporting receiving multicast services in an inactive state
WO2022242409A1
( en )
2022-11-24
Service data transmission method and communication apparatus
JP5894279B2
( en )
2016-03-23
Method and apparatus for improving MBMS count in LTE
US20250227599A1
( en )
2025-07-10
Apparatuses, Methods, and Computer Programs for Temporarily Unavailable Network Slices
WO2024033833A1
( en )
2024-02-15
Apparatus, method, and computer program
CN114342422A
( en )
2022-04-12
MBMS support over IOPS
EP4197159A1
( en )
2023-06-21
Support of multicast for terminal endpoint devices
US20230319677A1
( en )
2023-10-05
Shared cu up address management
CN116569607B
( en )
2025-04-25
Network slice local switching at distributed units
WO2022161815A1
( en )
2022-08-04
Ran control for local mbs and location-dependent mbs service
WO2023103575A1
( en )
2023-06-15
Multicast/broadcast communication method and related apparatus
CN119318205A
( en )
2025-01-14
Device, method and computer program
CN117998436A
( en )
2024-05-07
A communication method and device
Legal Events
Date
Code
Title
Description
2020-06-11
AS
Assignment
Owner name : NOKIA SOLUTIONS AND NETWORKS OY, FINLAND
Free format text : ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NAVRATIL, DAVID;KORJA, PEKKA;PRASAD, ATHUL;AND OTHERS;SIGNING DATES FROM 20190725 TO 20190805;REEL/FRAME:052913/0788
2020-06-11
FEPP
Fee payment procedure
Free format text : ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY
2020-12-10
STPP
Information on status: patent application and granting procedure in general
Free format text : APPLICATION DISPATCHED FROM PREEXAM, NOT YET DOCKETED
2021-08-20
STPP
Information on status: patent application and granting procedure in general
Free format text : DOCKETED NEW CASE - READY FOR EXAMINATION
2021-09-20
STPP
Information on status: patent application and granting procedure in general
Free format text : NON FINAL ACTION MAILED
2022-02-28
STPP
Information on status: patent application and granting procedure in general
Free format text : RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER
2022-06-14
STPP
Information on status: patent application and granting procedure in general
Free format text : FINAL REJECTION MAILED
2022-09-20
STPP
Information on status: patent application and granting procedure in general
Free format text : RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER
2022-10-18
STPP
Information on status: patent application and granting procedure in general
Free format text : ADVISORY ACTION MAILED
2022-11-23
STPP
Information on status: patent application and granting procedure in general
Free format text : DOCKETED NEW CASE - READY FOR EXAMINATION
2022-12-09
STPP
Information on status: patent application and granting procedure in general
Free format text : NON FINAL ACTION MAILED
2023-04-03
STPP
Information on status: patent application and granting procedure in general
Free format text : RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER
2023-07-05
STPP
Information on status: patent application and granting procedure in general
Free format text : NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS
2023-10-11
STPP
Information on status: patent application and granting procedure in general
Free format text : AWAITING TC RESP, ISSUE FEE PAYMENT VERIFIED
2023-10-12
STPP
Information on status: patent application and granting procedure in general
Free format text : PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED
2023-11-01
STCF
Information on status: patent grant
Free format text : PATENTED CASE