Patent Application
20240040339
The present application generally relates to wireless communication technology. More particularly, the present application relates to a method and an apparatus for providing Multicast Broadcast (MB) service in a local service area. The present application also relates to computer program product adapted for the same purpose. The present application also relates to a terminal device adapted to cooperate with the apparatus for providing MB service in a local service area.
3GPP has developed MBMS (Multicast/Broadcast Multimedia Subsystem) for 3G networks for video multicast/broadcasting and streaming services. For details, see 3GPP TS 23.246 16.1.0, which is incorporated herein by reference in its entirety. Moreover, eMBMS (evolved MBMS) for EPS has been introduced. In Rel-13 and Rel-14, the MBMS system has been updated to support new services such as Public Safety, Cellular Internet of Things (CIoT) and Vehicle to Everything (V2X).
The scope of a new Release-17 study in 3GPP SA2 working group covers both multicast requirements and use cases for CIoT, Public Safety, V2X etc., and dedicated broadcasting requirements and use cases. The study targets the 5G Release 17 and New Radio (NR) radio access. The development so far has been documented in 3GPP TR 23.757 V0.4.0, which is incorporated herein by reference in its entirety.
Multicast/Broadcast services are not supported on 5G NR until now. With the enhanced characteristics of the 5G NR, e.g. short delays, higher bandwidth etc., it is believed Mission Critical Services, e.g., Mission Critical Push To Talk, MCPTT, Mission Critical Data, MCData, and Mission Critical Video, MCVideo, as well as VTX services, will exhibit an enhanced and much better performance on 5G NR.
Due to the mobility of the terminal devices and the complexity in terms of signaling, it is a great challenge to deliver the local MB service in a resource efficient and user-friendly manner, especially In an IoT scenario where there are a large number of terminal devices. However, until now, there is no solution for solving the above problems in the art.
One of the objects is to provide methods and apparatus for providing MB service in a local service area, which allows an optimal usage of network resources and better user experience.
According to one aspect of the present disclosure, a method for providing Multicast Broadcast (MB) service in a local service area comprises the following steps carried out by a node configured to manage access and mobility:
According to another aspect of the present disclosure, an apparatus for providing Multicast Broadcast (MB) service in a local service area comprises:
According to another aspect of the present disclosure, a method for providing Multicast Broadcast (MB) service in a local service area comprises the following steps carried out by a RAN node:
According to another aspect of the present disclosure, a method for providing Multicast Broadcast (MB) service in a local service area comprises the following steps carried out by a RAN node:
According to another aspect of the present disclosure, an apparatus for providing Multicast Broadcast (MB) service in a local service area comprises:
According to another aspect of the present disclosure, a terminal device comprises:
According to another aspect of the present disclosure, a computer program product for providing Multicast Broadcast (MB) service in a local service area, the computer program product being embodied in a computer readable storage medium and comprising computer instructions for performing anyone of the methods as described above.
The foregoing and other objects, features, and advantages would be apparent from the following more particular description of preferred embodiments as illustrated in the accompanying drawings in which:
The invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term “processor” refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
Also, use of ordinal terms such as “first,” “second,” “third,” etc., in the claims to modify a claim element does not by itself connote any priority, precedence, or order of one claim element over another or the temporal order in which acts of a method are performed, but are used merely as labels to distinguish one claim element having a certain name from another element having a same name (but for use of the ordinal term) to distinguish the claim elements.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
As used herein, the term “terminal device” may be referred to as, for example, device, access terminal, user equipment (UE), mobile station, mobile unit, subscriber station, or the like. It may refer to any end device that can access a wireless communication network and receive services therefrom. By way of example and not limitation, the terminal device may include a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback appliance, a mobile phone, a cellular phone, a smart phone, a tablet, a wearable device, a personal digital assistant (PDA), or the like.
In an Internet of things (IoT) scenario, a terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another terminal device and/or a network equipment. In this case, the terminal device may be a machine-to-machine (M2M) device, which may, in a 3rd generation partnership project (3GPP) context, be referred to as a machine-type communication (MTC) device. Particular examples of such machines or devices may include sensors, metering devices such as power meters, industrial machineries, bikes, vehicles, or home or personal appliances, e.g. refrigerators, televisions, personal wearables such as watches, and so on.
A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.
To support multicast/broadcast MBS user service delivery in 5G system, new functional nodes or components and necessary enhancement to the existing entities are deployed. Note that the new functional nodes can be standalone or co-locate with existing network function nodes.
It shall be noted that a node or a functional node can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure, or as any combination thereof.
As shown in
In the architecture as shown in
User Equipment (UE), New Generation Radio Access Network (NG-RAN), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Network Exposure Function (NEF) and Policy Control Function (PCF) are enhanced to support MBS.
UE is enhanced to support 5G MBS services.
NG-RAN is enhanced to support Point-to-Multipoint (PTM) and Point-to-Point (PTP) delivery of MBS media. NG-RAN independently controls switching between PTM and PTP for best service quality and resource efficiency.
AMF is enhanced to select MB-SMF and be part of the signaling distribution tree.
MB-SMF is an SMF enhanced to control MB Sessions, signaling with AF (via NEF/MBSF), QoS control using PCF, and provision of MB Session information on request from AMF. The PDU session(s) the UE(s) maintain for individual delivery of an MBS service may be associated with the MB Session managed by the MB-SMF.
MB-UPF is a UPF enhanced with an MBS user plane function.
MBSF (Multicast/Broadcast Service Function) is a function which may be part of NEF or be deployed independently. The MBSF may support TMGI allocation or other MBS signaling for the service level management. The MBSF also provides an interface to the Application Function or content provider and it has an interface to the MBSU. MBSF may perform authorization of the UE to join the MB session.
MBSU (Multicast/Broadcast Service User plane) is a new entity to handle the payload part to cater for the service level functions and management.
NEF is an existing NF, which provides interface to the AF.
PCF is enhanced to handle QoS for MB Sessions, e.g. to authorize the QoS profiles for shared delivery.
Generally, local MB service is required to be delivered in a local service area for a specific period. All the relevant UEs in the local service area can receive the MBS service. When starting a local MB service, an application function needs to be able to notify 5G core network (CN) and NG-RAN of the coverage where the local MB service can be delivered, and thus those UEs outside the area are prevented from being served.
To offer local MBS service, the backhaul delay between 5GC and NG-RAN needs to be minimized. To this end, it is essential to have localized user plane deployment to work together with localized application function. For example, in the architecture as shown in
However, due to the mobility of the UEs and the complexity in terms of signaling, it is a great challenge to deliver the local MB service in a resource efficient manner. For example, in some cases, a UE successfully joining a MB session may move out from a local service area associated with the MB session. Since this event may occur randomly and may be detected by a number of nodes, it is desirable to have a mechanism for dealing with the occurrence in an efficient and user-friendly manner.
In the present disclosure, an AMF node may determine whether a terminal device, e.g., UE joining a MB session associated with a local service area is out of the local service area, and in response to the occurrence, the AMF node may remove the terminal device from the MB session and send a message, e.g., NAS message MB Session Remove to the terminal device. To this end, the AMF node may detect the event that the terminal device moves out from the local service area, e.g., by comparing a location of the terminal device with location-related criteria for the local service area. Alternatively, the determining may be based on judgement made by other node(s). For example, a RAN node or another AMF node may send to the AMF node a message indicating that the terminal device is out of the local service area or shall be removed from the MB session, on the basis of which the AMF node determines the terminal device is out of the local service area. Preferably, when the AMF node detects that the terminal device moves out from the local service area, it may notify the RAN node that the terminal device is out of the local service area or the terminal device shall be removed from the MB session, e.g., by sending a N2 message MB Session Remove, so that the terminal device will be removed from MB Session in both of 5GC and NG-RAN.
The term “location-related criteria” used herein refers to any standard which the location of a terminal device may be compared with or judged by. The examples of the location-related criteria include but are not limited to Location Criteria specificed in 3GPP TS 23.503 or a service area list.
The following embodiments will be described in connection with the 5G system as shown in
The flowchart as shown in
Step 201: The AMF node determines whether a terminal device joining a MB session associated with the local service area is out of the local service area.
In an illustrative example, the AMF node may compare a location of the terminal device with location-related criteria for the local service area to determine whether the terminal device is out of the local service area. For a handover scenario, e.g., during a handover from a source RAN node to a target RAN node, the AMF node may respond to a MB Session Command from the target RAN node by comparing a location of the terminal device with location-related criteria for the local service area so as to determine whether the terminal device is out of the local service area.
In another illustrative example, if receiving from a RAN node a message that the terminal device is out of the local service area or the terminal device shall be removed from the MB session, the AMF node will make a judgement that the terminal device is out of the local service area. For example, the AMF node may send to the RAN node a request for setting up MB session resource, which includes the location-related criteria for the local service area so that the RAN node may judge whether the terminal device is out of the local service area or the terminal device shall be removed from the MB session.
In another illustrative example, the location-related criteria is derived from local service area information included in an MB Session announcement or an Allocate Temporary Mobile Group Identity (TMGI) Request sent from an AF node to a NEF/MBSF node.
In another illustrative example, the local service area information is represented as one of the following lists or the combination thereof: a cellId list, a gnodeBId list, a tracking area list, a geographic area list, a civic address list and a service area list.
Step 202: The AMF node removes the terminal device from the MB session if the terminal device is determined to be out of the local service area. In an illustrative example, the removal may be performed by removing an association between the terminal device and MB Session Context. Alternatively, for a handover scenario, the removal may be performed by not sending a MB Session Join message to the target RAN node.
Step 203: The AMF node notifies the terminal device that the MB session is unavailable. Preferably but not necessarily, upon receiving a message or notification that the MB session is unavailable, the terminal device may terminate or interrupt an execution of a procedure relating to the MB service in the local service area.
As described above, the occurrence of moving out from the local service area may be detected by the AMF node. In this case, to remove the terminal device from MB Session in both of 5GC and NG-RAN, the AMF node may notify the RAN node that the terminal device is out of the local service area or the terminal device shall be removed from the MB session. This notifying operation may be performed along with the operation of removing the terminal device at step 202 or the operation of notifying the terminal device at step 203. Moreover, at step 202, it may be performed before, in synchronization with, or after the operation of removing the terminal device, and at step 203, it may be performed before in synchronization with, or after the operation of notifying the terminal device. In an illustrative example, For a handover scenario, e.g., during a handover from a source RAN node to a target RAN node, the AMF node may request a target AMF node to notify the terminal device after the handover or during the handover.
With reference to
The flowchart as shown in
Step 401: The RAN node detects whether a terminal device joining a MB session associated with the local service area is out of the local service area.
In an illustrative example, the RAN node may compare a location of the terminal device with location-related criteria for the local service area to determine whether the terminal device is out of the local service area. The location-related criteria may be included in a request for setting up MB session resource from the AMF node. For a handover scenario, e.g., during a handover from a source RAN node to a target RAN node, the source RAN node may perform the determining before the handover.
As described above, the location-related criteria may be derived from local service area information included in an MB Session announcement or an Allocate Temporary Mobile Group Identity (TMGI) Request sent from an AF node to a NEF/MBSF node, and the local service area information is represented as one of the following lists or the combination thereof: a cellId list, a gnodeBId list, a tracking area list, a geographic area list, a civic address list and a service area list.
Step 402: The RAN node removes the terminal device from the MB session if the terminal device is determined to be out of the local service area.
Step 403: The RAN node notifies the AMF that the MB session is out of the local service area or shall be removed from the MB session.
The flowchart as shown in
Step 501: The RAN node receives from an AMF node a message that the terminal device is out of the local service area or the terminal device shall be removed from the MB session.
Step 502: The RAN node removes the terminal device from the MB session in response to the even that the terminal device is determined to be out of the local service area.
With reference to
With reference to
Optionally, the processor may be further configured to carry out the step of notifying a user that the procedure is terminated or interrupted.
The Session Join procedure may be used by UEs to inform the 3GPP network of the UE interest in an MB Session.
As shown in
Step 800: The UE registers and a PDU Session is established. The UE and the AF uses the PDU Session e.g. to signal and establish a group on application level. For details, see 3GPP TS 23.468, which is incorporated herein by reference in its entirety.
Step 801: AF sends Allocate TMGI Request ( ) message to NEF/MBSF to request allocation of a TMGI to identify a new group. In particular, local service area information is additionally included in the Allocate TMGI Request to NEF/MBSF. In an illustrative example, the local service area information can be cellId list, gnodeBId list, tracking area list, geographic area list, civic address list, service area list or the combination thereof. Among them, cellId list, gnodeBId list and tracking area list shall only be used by AFs which reside in trust domain and are aware of such information.
Step 802: NEF/MBSF selects based on local configuration an MB-SMF (if there are multiple) to handle the group and sends an Allocate TMGI Request ( ) message to the MB-SMF. In particular, NEF/MBSF translates the local service area information into Location Criteria, e.g., specified in 3GPP TS 23.503, which is incorporated herein by reference in its entirety. Furthermore, the Location Criteria is included in Allocate TMGI Request to MB-SMF.
Optionally, the MBSF makes the TMGI allocation, stores in the MB Session Context and includes the allocated TMGI in the message to the MB-SMF. The MBSF may have a pre-configured TMGI range for each MB-SMF. The TMGI range should also be configured/registered in the NRF to allow AMFs to discover which MB-SMF is controlling an MB Session identified by a TMGI.
Step 803: MB-SMF allocates a TMGI (optionally pre-allocated TMGI may be used), a Lower Layer Multicast IP Address (LL MC address) for N3, and N6 tunnel information and stores the information in a new MB Session Context set to ‘inactive’ state. MB-SMF returns the TMGI and the N6 tunnel information to the NEF/MBSF. If MB-SMF makes the TMGI allocation, it may e.g. allocate a TMGI from a pre-configured TMGI range.
Step 804: The NEF/MBSF establishes a new MB Session Context set to ‘inactive’ state, stores received information and responds to the AF by sending a Allocate TMGI Response (TMGI) message.
Step 805: MB Session Announcement (see e.g., 3GPP TS 23.468, which is incorporated herein by reference in its entirety). The AF informs the members in the group of various group info e.g. TMGI, HL MC Address. In particular, the local service area information is also included in the MB Session announcement. The HL MC address may be allocated by the AF for the group/TMGI.
Step 806: UE indicates its interest to join an MB Session by sending an UL NAS MB Session Join Request (TMGI) message. NG-RAN forwards the NAS message to the AMF. The AMF stores the TMGI in its UE Context. In an illustrative example, if UE determines that it is outside the local service area, it is prohibited from sending MB Session Join Request to AMF.
Step 807: If the AMF does not already have a MB Session Context for the received TMGI, the AMF selects an MB SMF for the TMGI by querying the NRF. A MB Session Request (TMGI, AMF ID) message is sent to the MB SMF to announce the AMF's interest in the MB Session. When the MB-SMF has returned a MB Session Response ( ) message, the AMF creates a MB Session Context in ‘inactive’ state for the TMGI. In particular, in MB Session Response from MB-SMF to AMF, the Location Criteria should be included for local MBS service.
If AMF detects UE is inside the local service area, the Session Join procedure proceeds to Step 808, otherwise, it proceeds to Step 809.
Step 808: AMF sends MB Session Join Accept to UE, along with a N2 message MB Session Join to NG-RAN.
Step 809: AMF send MB Session Reject to UE to indicate the MB Session Join Request is rejected, with the indication of the reason, e.g., outside the local service area.
As shown in
Step 901: To activate a local MBS Bearer, AF includes additionally the local service area information in the Activate MBS Bearer Request to NEF.
Step 902: NEF/MBSF translates the local service area information into Location Criteria, e.g., specified in 3GPP TS 23.503, which is incorporated herein by reference in its entirety, and includes the Location Criteria in MB Session Start Request to MB-SMF.
Step 903: MB-SMF sends the TMGI for the MB Session and the Service Requirement to the PCF. The PCF returns a 5G QoS Profile, which the MB-SMF uses as the 5G Authorized QoS Profile for the MB Session.
Step 904: The MB-SMF selects the localized MB-UPF based on the Location Criteria to set up the resources.
Step 905: MB-SMF sends MB Session Start messages to all AMFs that has earlier joined the MB Session with the Location Criteria information.
Step 905a: After receiving MB Session Start request from MB-SMF, AMF check whether the joined UEs are within the local service area. For those UEs which are out of the local service area, AMF removes associations between those UEs and MB Session Context. Furthermore, AMF sends NAS MB Session Remove message to those UEs, along with a N2 message MB Session Remove (NGAP ID, TMGI) to inform NG-RAN. As an example, it assumes that AMF detects that UE2 is outside the local service area.
Step 906: AMF shall only send MB Session Resource Setup Request to the relevant RAN nodes in the local service area which have received N2 MB Session Join message from the AMF. The Location Criteria shall be included in the MB Session Resource Setup Request.
Steps 907-910: RAN nodes follow the Location Criteria of the local MB service to establish the downlink resource to deliver contents to the joined UEs within the local service area.
Step 911: AMF sends MB Session Start Ack (TMGI) to the MB-SMF.
Steps 912-913. MB-SMF sends the MB Session Start Ack (TMGI) message to the NEF/MBSF. N6 Tunnel info is included in the response if not already provided to the AF. The NEF/MBSF sends an Activate MBS Bearer Response including the N6 Tunnel Info to the AF.
Step 913a: If RAN detects some joined UEs outside the local service area based on the Location Criteria it received from AMF, it removes those UEs from the MB Session. To remove those UEs, RAN sends N2 message MB Session Remove to AMF with NGAP ID list and TMGI. AMF removes associations between those UEs and MB Session Context.
Step 913b: AMF send NAS MB Session Remove message to those UEs separately. For example, in this procedure, RAN detects UE3 is outside the local service area, AMF send MB Session Remove to UE3.
Steps 914-915: The MB Session is now active. AF starts transmitting the DL media stream using the N6 Tunnel Info, or optionally un-tunneled i.e. as an IP multicast stream using the HL MC address.
Step 916: NG-RAN transmits the received DL media stream using DL PTM or PTP resources.
Steps 917-918. Another UE (e.g., UE4) requests to join the MBS session. AMF checks whether UE 4 is located in the local service area. If UE4 is in the area, AMF accepts the request and inform NG-RAN of the newly joined UE, otherwise if UE4 is not within the area, AMF will reject the MB Session Join from UE4.
For details on the procedure as shown in
In this case, it assumes that before sending Handover Request to Target NG-RAN (i.e., step 1 of
In Case 2, it assumes that AMF detects an event that UE will not be in the local MBS service area after handover. Upon detecting the event, the following optional procedures are available:
AMF may send N2 message: MB Session Remove to Target NG-RAN after step 2a of
AMF will not trigger send MB Session Join to Target NG-RAN in step 10a of
In Case 3, it assumes that both of Source NG-RAN and AMF fail to detect that UE is moving out from the local service area until the completion of the handover. Therefore, at step 2b and step 10b of
Target NG-RAN sends N2 message: MB Session Remove to AMF after step 2b of
Target NG-RAN sends N2 message: MB Session Remove to AMF after step 10b of
For details on the procedure as shown in
In this case, it assumes that before sending Handover Request to Source AMF (i.e., step 1 of
In this case, it assumes that upon receiving Handover Request after step 1 of
In this case, it assumes that Target AMF detects an event that UE will not be in the local MBS service area after handover. Upon detecting the event, Target AMF should get the Location Criteria in step 7c of
In this case, it assumes that Target NG-RAN detects that UE will not be in the local MBS service area after handover. Upon detecting the event, Target NG-RAN should get the Location Criteria in step 7d of
It should be noted that the aforesaid embodiments are illustrative instead of restricting, substitute embodiments may be designed by those skilled in the art without departing from the scope of the claims enclosed. The wordings such as “include”, “including”, “comprise” and “comprising” do not exclude elements or steps which are present but not listed in the description and the claims. It also shall be noted that as used herein and in the appended claims, the singular forms “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise. Embodiments can be achieved by means of hardware including several different elements or by means of a suitably programmed computer. In the unit claims that list several means, several ones among these means can be specifically embodied in the same hardware item. The use of such words as first, second, third does not represent any order, which can be simply explained as names.
| Number | Date | Country | Kind |
|---|---|---|---|
| 9CT/CN2020/109010 | Aug 2020 | CN | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/EP2021/069444 | 7/13/2021 | WO |
