WO2018089615A1

WO2018089615A1 - Radio access network (ran) node, mobile device and methods for configuration of a group-cast mode in a software defined network (sdn)

Info

Publication number: WO2018089615A1
Application number: PCT/US2017/060830
Authority: WO
Inventors: Ching-Yu Liao
Original assignee: Intel Corporation
Priority date: 2016-11-10
Filing date: 2017-11-09
Publication date: 2018-05-17

Abstract

Embodiments of a RAN node, mobile device and methods for communication are generally described herein. The RAN node may receive a quality of service (QoS) measurement from a mobile device for a group based service (GBS). The RAN node may determine, based at least partly on the QoS measurement, whether to switch the mobile device from a uni-cast mode to a group-cast mode for the GBS. The RAN node may transmit a group service response that indicates: whether the mobile device is to switch from the uni-cast mode to the group-cast mode for the GBS; and, if it is determined that the mobile device is to switch from the uni-cast mode to the group-cast mode, a channel allocated for transmission of packets for the GBS for the group-cast mode.

Description

RADIO ACCESS NETWORK (RAN) NODE, MOBILE DEVICE AND METHODS FOR CONFIGURATION OF A GROUP-CAST MODE IN A

SOFTWARE DEFINED NETWORK (SDN)

PRIORITY CLAIM

[0001] This application claims priority to United States Provisional Patent Application Serial No. 62/420,404, filed November 10, 2016, and to United States Provisional Patent Application Serial No. 62/436,912, filed December 20, 2016, both of which are incorporated herein by reference in their entirety. TECHNICAL FIELD

[0002] Embodiments pertain to wireless communications. Some embodiments relate to wireless networks including 3GPP (Third Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, and 3GPP LTE-A (LTE Advanced) networks. Some embodiments relate to Fifth Generation (5G) networks. Some embodiments relate to 5G New Radio (NR) networks. Some embodiments relate to wireless local area networks (WLANs). Some embodiments relate to software defined networks (SDNs). Some embodiments relate to group-cast operation.

BACKGROUND

[0003] Base stations and mobile devices operating in a cellular network may exchange data. In an example, services such as video and others may be delivered to mobile devices by a network using group-cast techniques. In some cases, the network may include multiple components. Some operations may be challenging in such cases, such as communication of control information between the multiple components. Accordingly, there is a general need for methods and systems to perform such operations in these and other scenarios.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] FIG. 1 is a functional diagram of an example network in accordance with some embodiments;

[0005] FIG. 2 illustrates a block diagram of an example machine in accordance with some embodiments;

[0006] FIG. 3 illustrates a mobile device in accordance with some aspects;

[0007] FIG. 4 illustrates a base station in accordance with some aspects;

[0008] FIG. 5 illustrates an exemplary communication circuitry according to some aspects;

[0009] FIG. 6 illustrates the operation of a method of communication in accordance with some embodiments;

[0010] FIG. 7 illustrates the operation of another method of communication in accordance with some embodiments;

[0011] FIG. 8 illustrates the operation of another method of communication in accordance with some embodiments;

[0012] FIG. 9 illustrates the operation of another method of communication in accordance with some embodiments;

[0013] FIG. 10 illustrates an outline of example methods in accordance with some embodiments;

[0014] FIG. 11 illustrates example operations and/or example messages in accordance with some embodiments;

[0015] FIG. 12 illustrates example operations and/or example messages in accordance with some embodiments;

[0016] FIG. 13 illustrates example operations and/or example messages in accordance with some embodiments;

[0017] FIG. 14 illustrates example operations and/or example messages in accordance with some embodiments; [0018] FIG. 15 illustrates example operations and/or example messa^ ;es in accordance with some embodiments;

[0019] FIG. 16 illustrates example operations and/or example messa^ ;es in accordance with some embodiments;

[0020] FIG. 17 illustrates example operations and/or example messa^ ;es in accordance with some embodiments;

[0021] FIG. 18 illustrates example operations and/or example messa^ ;es in accordance with some embodiments;

[0022] FIG. 19 illustrates example operations and/or example messa^ ;es in accordance with some embodiments; and

[0023] FIG. 20 illustrates example operations and/or example messa^ ;es in accordance with some embodiments.

DETAILED DESCRIPTION

[0024] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0025] FIG. 1 is a functional diagram of an example network in accordance with some embodiments. The network 100 is an example of an SDN-based system architecture. The radio access network (RAN) 120 may support any number of RAN nodes 115. FIG. 1 illustrates one RAN node 115, but embodiments are not limited to one RAN node 115, as multiple RAN nodes 115 may be supported, in some embodiments. In some embodiments, the RAN node 115 may be a base station. In some embodiments, the RAN node 115 may be a base station arranged to operate in accordance with one or more protocols and/or standards, such as Third Generation Partnership Project (3GPP), 3GPP Long Term Evolution (LTE), new radio (NR), fourth generation (4G), fifth generation (5G), wireless local area network (WLAN), Wi-Fi, IEEE 802.11 and/or other. Embodiments are not limited to these protocols and standards. In some embodiments, the RAN node 115 may be an Evolved Node-B (eNB) arranged to operate in accordance with a 3GPP LTE protocol and/or other 3GPP protocol(s). In some embodiments, the RAN node 115 may be a Generation Node-B (gNB) arranged to operate in accordance with an NR protocol and/or other protocol(s). In some embodiments, the RAN node 115 may be an access point (AP) arranged to operate in accordance with a WLAN protocol, Wi-Fi protocol and/or 802.11 protocol(s). These examples are not limiting, as any mobile device may be used, including mobile devices that may not necessarily be arranged to operate in accordance with a standard.

[0026] The mobile device 110 may communicate with the RAN node

115 over a wireless channel. The RAN node 115 may communicate with any number of mobile devices 110. FIG. 1 illustrates one mobile device 110, but embodiments are not limited to one mobile device 110, as multiple mobile devices 110 may be supported by the RAN node 115, in some embodiments. In some embodiments, the mobile device 110 may be arranged to operate in accordance with one or more protocols and/or standards, such as 3GPP, 3GPP LTE, NR, 4G, 5G, WLAN, Wi-Fi, IEEE 802.11 and/or other. Embodiments are not limited to these protocols and standards. In some embodiments, the mobile device 110 may be a User Equipment (UE) arranged to operate in accordance with a 3GPP LTE protocol, 3GPP protocol, NR protocol and/or other protocol(s). In some embodiments, the mobile device 110 may be a station (STA) arranged to operate in accordance with a WLAN protocol, Wi-Fi protocol and/or 802.11 protocol(s). These examples are not limiting, as any mobile device 110 may be used, including mobile devices 110 that may not necessarily be arranged to operate in accordance with a standard.

[0027] In some embodiments, the service portal function (SPF) 130 and/or CN-CPF 140 may allocate a temporary ID for identification of a group- cast requested by an application server 160 providing group based service. A group based service ID (GBS-ID) is a non-limiting example of such a temporary ID. In some embodiments, the mobile device 110 may use the group based service obtained GBS-ID, which is used to identify the group based service, from the application server 160 after the mobile device 110 registers with the application server 160 for the group base service. The RAN node 115 may have received the group-cast data for the group based service of the GBS-ID from the application server 160, but may use unicast or group-cast for the serving mobile devices 110. The SPF 130 and/or CN-CPF 140 may allocate the same or different GBS-ID for identifying one or more group-casts.

[0028] In some embodiments, the application server 160 may interface with devices over NG0 and may exchange information in an application layer. The devices may register to the SDN network 100 first and then to the application server 160.

[0029] In some embodiments, the subscription repository 170 may store one or more of the following: subscription(s) of mobile devices 110, application servers 160 and/or other components; security parameters of a mobile device 110 and/or application servers 160; corresponding subscription services information (such as service features, quality of services, traffic characteristics and/or other). In some embodiments, the CN-CPF 140 and the SPF 130 may have interfaces with the subscription repository 170 to authenticate and authorize the mobile device 110 and the application server 160, respectively.

[0030] In some embodiments, the core network control plane function

(CN-CPF) 140 may be responsible for managing local control plane function(s) for QoS provisioning and routing policies. In some embodiments, the CN-CPF 140 may interface with the SPF 130 in the northbound over interface NG5 to communicate with application servers 160 via NG7. In some embodiments, the CN-CPF 140 may interface with CN-UPF 150, which may deploy one or more data gateways (DGWs), in the southbound over NG4 interface, and may configure routing policies to one or more DGWs so as to provision QoS for a requested service of a mobile device 110. In some embodiments, the CN-CPF 140 may interface with one or more RAN nodes 115 to forward from the source node 115 to the target node 115 for uplink/downlink packet transmission. In some embodiments, the CN-CPF 140 may interface with subscription repository 170 over NG6a interface to retrieve/update the device 110, service related subscription information locally. In some embodiments, the CN-CPF 140 may allocate IP addresses of the requested services in the service domains within the SDN network 100, and may preserve the allocated IP addresses of the requested service for the device 110. In some embodiments, the CN-CPF 140 may perform one or more operations related to access. In some embodiments, the CN-CPF 140 may perform one or more operations related to mobility management. In some embodiments, the CN-CPF 140 may perform one or more operations related to session management.

[0031] In some embodiments, the core network user plane function (CN-

UPF) 150 may interface with CN-CPF 140, and may follow configured routing policies to forward/duplicate data packets received. In some embodiments, the CN-CUF 150 may deploy one or more data gateways (DGWs).

[0032] In some embodiments, the SPF 130 may be designed as a border gateway inside of a trust domain in an operator's network. In some

embodiments, the SPF 130 may authorize the application server and provide the requested service from the SMN. In some embodiments, the SPF 130 may handle the local service polices within the operator domain. In some embodiments, the SPF 130 may interface with the subscription repository 170 for obtaining the service subscriptions of the application servers 160, mobile devices 110 and/or service group parameters. In some embodiments, the SPF 130 may interface with the CN-CPF 140 for receiving session related information of the groups and devices 110. In some embodiments, the SPF 130 may interface with RAN node 115 directly for receiving radio resource information from the RAN node 115, and for enforcing policies in the RAN node 115 that may not necessarily require information/decision of the CN-CPFs 140. If there is no direct connection between the RAN node 115 and the SPF 130 and if the information/decision of the CN-CPF 140 is not necessarily required, the CN-CPF 140 may forward the information/policies between the RAN node 115 and the SPF 130.

[0033] In some cases, it may be assumed that devices 110 have default unicast PDU sessions setup for communicating with application server over NG0.

[0034] In some embodiments, the network 100 may be a software defined network (SDN). It should be noted that embodiments are not limited to usage of SDN networks, however, as other networks may be used in some embodiments. As an example, a Third Generation Partnership Project (3GPP) network may be used, in some cases. As another example, a Fifth Generation (5G) network may be used in some cases. As another example, a New Radio (NR) network may be used in some cases. As another example, a wireless local area network (WLAN) may be used in some cases. Embodiments are not limited to these example networks, however, as other networks may be used in some embodiments. In some embodiments, a network may include one or more components shown in FIG. 1. Some embodiments may not necessarily include all components shown in FIG. 1, and some embodiments may include one or more additional components not shown in FIG. 1. It should be noted that embodiments are not limited to the number of components shown in FIG. 1.

Embodiments are also not limited to the arrangement of the components shown in FIG. 1. Embodiments are also not limited to the connectivity between the components shown in FIG. 1.

[0035] It should be noted that references herein to a RAN node 115 are not limiting. In some embodiments, an Evolved Node-B (eNB), Generation Node-B (gNB), access point (AP) and/or other base station may be used. For instance, descriptions of one or more operations, techniques and/or methods practiced by the RAN node 115 are not limiting. In some embodiments, one or more of those operations, techniques and/or methods may be practiced by another base station component. In some embodiments, the base station component may be configured to operate in accordance with a New Radio (NR) protocol and/or NR standard, although the scope of embodiments is not limited in this respect. In some embodiments, the base station component may be configured to operate in accordance with a Fifth Generation (5G) protocol and/or 5G standard, although the scope of embodiments is not limited in this respect.

[0036] It should be noted that references herein to a mobile device 110 are not limiting. In some embodiments, a User Equipment (UE), station (STA) and/or other device may be used. For instance, descriptions of one or more operations, techniques and/or methods practiced by the mobile device 110 are not limiting. In some embodiments, one or more of those operations, techniques and/or methods may be practiced by a UE, STA and/or other device. In some embodiments, the mobile device 110 may be configured to operate in accordance with a New Radio (NR) protocol and/or NR standard, although the scope of embodiments is not limited in this respect. In some embodiments, the mobile device 110 may be configured to operate in accordance with a Fifth Generation (5G) protocol and/or 5G standard, although the scope of embodiments is not limited in this respect

[0037] In some embodiments, the mobile device 110 may transmit signals (data, control and/or other) to the RAN node 115, and may receive signals (data, control and/or other) from the RAN node 115. In some embodiments, the RAN node 115 may transmit signals (data, control and/or other) to the mobile device 110, and may receive signals (data, control and/or other) from the mobile device 110. These embodiments will be described in more detail below.

[0038] As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware. Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software.

[0039] FIG. 2 illustrates a block diagram of an example machine in accordance with some embodiments. The machine 200 is an example machine upon which any one or more of the techniques and/or methodologies discussed herein may be performed. In alternative embodiments, the machine 200 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 200 may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 200 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment. The machine 200 may be a mobile device 110, RAN node 115, UE, STA, eNB, AP, base station, user device, personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a smart phone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.

[0040] Examples as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[0041] Accordingly, the term "module" is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general -purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time. [0042] The machine (e.g., computer system) 200 may include a hardware processor 202 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. The machine 200 may further include a display unit 210, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In an example, the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display. The machine 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors 221, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The machine 200 may include an output controller 228, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[0043] The storage device 216 may include a machine readable medium

222 on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, or within the hardware processor 202 during execution thereof by the machine 200. In an example, one or any combination of the hardware processor 202, the main memory 204, the static memory 206, or the storage device 216 may constitute machine readable media. In some embodiments, the machine readable medium may be or may include a non-transitory computer-readable storage medium. In some embodiments, the machine readable medium may be or may include a computer-readable storage medium.

[0044] While the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224. The term "machine readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 200 and that cause the machine 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable

Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, machine readable media may include non-transitory machine readable media. In some examples, machine readable media may include machine readable media that is not a transitory propagating signal.

[0045] The instructions 224 may further be transmitted or received over a communications network 226 using a transmission medium via the network interface device 220 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, among others. In an example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 226. In an example, the network interface device 220 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. In some examples, the network interface device 220 may wirelessly communicate using Multiple User MIMO techniques. The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 200, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

[0046] FIG. 3 illustrates a mobile device in accordance with some aspects. In some embodiments, the mobile device 300 may be or may be configured to operate as a User Equipment (UE). In some embodiments, the mobile device 300 may be arranged to operate in accordance with a new radio (NR) protocol. In some embodiments, the mobile device 300 may be arranged to operate in accordance with a Third Generation Partnership Protocol (3GPP) protocol. The mobile device 300 may be suitable for use as a mobile device 110 as depicted in FIG. 1, in some embodiments. It should be noted that in some embodiments, a mobile device or an apparatus of a mobile device may include one or more of the components shown in one or more of FIGs. 2, 3, and 5. In some embodiments, such a mobile device and/or apparatus may include one or more additional components.

[0047] In some embodiments, the mobile device 300 may include an application processor 305, baseband processor 310 (also referred to as a baseband module), radio front end module (RFEM) 315, memory 320, connectivity module 325, near field communication (NFC) controller 330, audio driver 335, camera driver 340, touch screen 345, display driver 350, sensors 355, removable memory 360, power management integrated circuit (PMIC) 365 and smart battery 370. In some embodiments, the mobile device 300 may be a UE. In some aspects, the mobile device 300 may be an STA.

[0048] In some embodiments, application processor 305 may include, for example, one or more CPU cores and one or more of cache memory, low dropout voltage regulators (LDOs), interrupt controllers, serial interfaces such as serial peripheral interface (SPI), inter-integrated circuit (I²C) or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input-output (IO), memory card controllers such as secure digital / multi-media card (SD/MMC) or similar, universal serial bus (USB) interfaces, mobile industry processor interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports.

[0049] In some embodiments, baseband module 310 may be

implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, and/or a multi-chip module containing two or more integrated circuits.

[0050] FIG. 4 illustrates a base station in accordance with some embodiments. In some embodiments, the base station 400 may be or may be configured to operate as an Evolved Node-B (eNB). In some embodiments, the base station 400 may be or may be configured to operate as a Generation Node- B (gNB). In some embodiments, the base station 400 may be arranged to operate in accordance with a new radio (NR) protocol. In some embodiments, the base station 400 may be arranged to operate in accordance with a Third Generation Partnership Protocol (3 GPP) protocol. It should be noted that in some embodiments, the base station 400 may be a stationary non-mobile device. The base station 400 may be suitable for use as a RAN node 115 as depicted in FIG. 1, in some embodiments. It should be noted that in some embodiments, a RAN node, an apparatus of a RAN node, a base station and/or an apparatus of a base station may include one or more of the components shown in one or more of FIGs. 2, 4, and 5. In some embodiments, the RAN node, base station and/or apparatus may include one or more additional components.

[0051] The base station 400 may include one or more of application processor 405, baseband modules 410, one or more radio front end modules 415, memory 420, power management circuitry 425, power tee circuitry 430, network controller 435, network interface connector 440, satellite navigation receiver module 445, and user interface 450. In some embodiments, the base station 400 may be an Evolved Node-B (eNB), which may be arranged to operate in accordance with a 3GPP protocol, new radio (NR) protocol and/or Fifth Generation (5G) protocol. In some embodiments, the base station 400 may be a generation Node-B (gNB), which may be arranged to operate in accordance with a 3GPP protocol, new radio (NR) protocol and/or Fifth Generation (5G) protocol. [0052] In some embodiments, application processor 405 may include one or more CPU cores and one or more of cache memory, low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I²C or universal programmable serial interface module, real time clock (RTC), timer- counters including interval and watchdog timers, general purpose IO, memory card controllers such as SD/MMC or similar, USB interfaces, MIPI interfaces and Joint Test Access Group (JTAG) test access ports.

[0053] In some embodiments, baseband processor 410 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits.

[0054] In some embodiments, memory 420 may include one or more of volatile memory including dynamic random access memory (DRAM) and/or synchronous dynamic random access memory (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magneto-resistive random access memory (MRAM) and/or a three-dimensional cross-point memory. Memory 420 may be implemented as one or more of solder down packaged integrated circuits, socketed memory modules and plug-in memory cards.

[0055] In some embodiments, power management integrated circuitry

425 may include one or more of voltage regulators, surge protectors, power alarm detection circuitry and one or more backup power sources such as a battery or capacitor. Power alarm detection circuitry may detect one or more of brown out (under-voltage) and surge (over-voltage) conditions.

[0056] In some embodiments, power tee circuitry 430 may provide for electrical power drawn from a network cable to provide both power supply and data connectivity to the base station 400 using a single cable. In some embodiments, network controller 435 may provide connectivity to a network using a standard network interface protocol such as Ethernet. Network connectivity may be provided using a physical connection which is one of electrical (commonly referred to as copper interconnect), optical or wireless. [0057] In some embodiments, satellite navigation receiver module 445 may include circuitry to receive and decode signals transmitted by one or more navigation satellite constellations such as the global positioning system (GPS), Globalnaya Navigatsionnaya Sputnikovaya Sistema (GLONASS), Galileo and/or BeiDou. The receiver 445 may provide data to application processor 405 which may include one or more of position data or time data. Application processor 405 may use time data to synchronize operations with other radio base stations. In some embodiments, user interface 450 may include one or more of physical or virtual buttons, such as a reset button, one or more indicators such as light emitting diodes (LEDs) and a display screen.

[0058] FIG. 5 illustrates an exemplary communication circuitry according to some aspects. Circuitry 500 is alternatively grouped according to functions. Components as shown in 500 are shown here for illustrative purposes and may include other components not shown here in Fig. 5. In some aspects, the communication circuitry 500 may be used for millimeter wave

communication, although aspects are not limited to millimeter wave communication. Communication at any suitable frequency may be performed by the communication circuitry 500 in some aspects.

[0059] It should be noted that a device, such as the mobile device 110, mobile device 300, base station 115, base station 400, the machine 200 and/or other device may include one or more components of the communication circuitry 500, in some aspects.

[0060] The communication circuitry 500 may include protocol processing circuitry 505, which may implement one or more of medium access control (MAC), radio link control (RLC), packet data convergence protocol

(PDCP), radio resource control (RRC) and non-access stratum (NAS) functions. Protocol processing circuitry 505 may include one or more processing cores (not shown) to execute instructions and one or more memory structures (not shown) to store program and data information.

[0061] The communication circuitry 500 may further include digital baseband circuitry 510, which may implement physical layer (PHY) functions including one or more of hybrid automatic repeat request (HARQ) functions, scrambling and/or descrambling, coding and/or decoding, layer mapping and/or de-mapping, modulation symbol mapping, received symbol and/or bit metric determination, multi-antenna port pre -coding and/or decoding which may include one or more of space-time, space-frequency or spatial coding, reference signal generation and/or detection, preamble sequence generation and/or decoding, synchronization sequence generation and/or detection, control channel signal blind decoding, and other related functions.

[0062] The communication circuitry 500 may further include transmit circuitry 515, receive circuitry 520 and/or antenna array circuitry 530. The communication circuitry 500 may further include radio frequency (RF) circuitry 525. In an aspect of the disclosure, RF circuitry 525 may include multiple parallel RF chains for one or more of transmit or receive functions, each connected to one or more antennas of the antenna array 530.

[0063] In some embodiments, protocol processing circuitry 505 may include one or more instances of control circuitry (not shown) to provide control functions for one or more of digital baseband circuitry 510, transmit circuitry 515, receive circuitry 520, and/or radio frequency circuitry 525

[0064] In some embodiments, processing circuitry may perform one or more operations described herein and/or other operation(s). In a non-limiting example, the processing circuitry may include one or more components such as the processor 202, application processor 305, baseband module 310, application processor 405, baseband module 410, protocol processing circuitry 505, digital baseband circuitry 510, similar component(s) and/or other component(s).

[0065] In some embodiments, a transceiver may transmit one or more elements (including but not limited to those described herein) and/or receive one or more elements (including but not limited to those described herein). In a non- limiting example, the transceiver may include one or more components such as the radio front end module 315, radio front end module 415, transmit circuitry 515, receive circuitry 520, radio frequency circuitry 525, similar component(s) and/or other component(s).

[0066] One or more antennas (such as 230, 312, 412, 530 and/or others) may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some multiple -input multiple-output (MIMO) embodiments, one or more of the antennas (such as 230, 312, 412, 530 and/or others) may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.

[0067] In some embodiments, the mobile device 1 10, RAN node 1 15, mobile device 300, base station 400, machine 200 and/or other device described herein may be a mobile device and/or portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a wearable device such as a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or other device that may receive and/or transmit information wirelessly. In some embodiments, the mobile device 1 10, RAN node 1 15, mobile device 300, base station 400, machine 200 and/or other device described herein may be configured to operate in accordance with 3GPP standards, although the scope of the embodiments is not limited in this respect. In some embodiments, the mobile device 1 10, RAN node 1 15, mobile device 300, base station 400, machine 200 and/or other device described herein may be configured to operate in accordance with new radio (NR) standards, although the scope of the embodiments is not limited in this respect. In some embodiments, the mobile device 1 10, RAN node 1 15, mobile device 300, base station 400, machine 200 and/or other device described herein may be configured to operate according to other protocols or standards, including IEEE 802.1 1 or other IEEE standards. In some embodiments, the mobile device 1 10, RAN node 1 15, mobile device 300, base station 400, machine 200 and/or other device described herein may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.

[0068] Although the mobile device 1 10, RAN node 1 15, mobile device

300, base station 400, machine 200 and/or other device described herein may each be illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements.

[0069] Embodiments may be implemented in one or a combination of hardware, firmware and software. Embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include readonly memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. Some embodiments may include one or more processors and may be configured with instructions stored on a computer-readable storage device.

[0070] It should be noted that in some embodiments, an apparatus used by the mobile device 110, RAN node 115, mobile device 300, base station 400, machine 200 and/or other device described herein may include various components shown in FIGs. 2-5. Accordingly, techniques and operations described herein that refer to the mobile device 110 may be applicable to an apparatus of a mobile device. In addition, techniques and operations described herein that refer to the RAN node 115 may be applicable to an apparatus of a RAN node.

[0071] In accordance with some embodiments, the RAN node 115 may transmit control signaling that indicates a request for a quality of service (QoS) measurement from a mobile device 110 for a group based service (GBS). The

RAN node 115 may receive a group service report from the mobile device 110 that includes the QoS measurement. The RAN node 115 may determine, based at least partly on the QoS measurement, whether to switch the mobile device 110 from a uni-cast mode to a group-cast mode for the GBS. The RAN node 115 may transmit a group service response that indicates: whether the mobile device 110 is to switch from the uni-cast mode to the group-cast mode for the GBS; and, if it is determined that the mobile device 110 is to switch from the uni-cast mode to the group-cast mode, a channel allocated for transmission of packets for the GBS for the group-cast mode. These embodiments are described in more detail below.

[0072] FIG. 6 illustrates the operation of a method of communication in accordance with some embodiments. FIG. 7 illustrates the operation of another method of communication in accordance with some embodiments. FIG. 8 illustrates the operation of another method of communication in accordance with some embodiments. FIG. 9 illustrates the operation of another method of communication in accordance with some embodiments.

[0073] It is important to note that embodiments of the methods 600-900 may include additional or even fewer operations or processes in comparison to what is illustrated in FIGs. 6-9. In addition, embodiments of the methods 600- 900 are not necessarily limited to the chronological order that is shown in FIGs. 6-9. In describing the methods 600-900, reference may be made to FIGs. 1-20, although it is understood that the method 600 may be practiced with any other suitable systems, interfaces and components.

[0074] In addition, while the methods 600-900 and other methods described herein may refer to mobile devices 110 and/or RAN nodes 115, one or more operations of the methods may also be practiced by other devices, such as a base station, eNB, AP, UE, STA and/or other device. In addition, the methods 600-900 and other methods described herein may be practiced by wireless devices configured to operate in other suitable types of wireless communication systems, including systems configured to operate according to various IEEE standards such as IEEE 802.11. The methods 600-900 may also be applicable to an apparatus of a RAN node 115, an apparatus of a mobile device, an apparatus of an SPF node and/or an apparatus of another device described above.

[0075] In addition, discussion herein of various techniques, operations, methods and/or concepts related to a method (including but not limited to methods 600-900) may be applicable to one or more other methods described herein, in some cases.

[0076] It should also be noted that embodiments are not limited by references herein (such as in descriptions of the methods 600-900 and/or other descriptions herein) to transmission, reception and/or exchanging of elements such as frames, messages, requests, indicators, signals or other elements. In some embodiments, such an element may be generated, encoded or otherwise processed by processing circuitry (such as by a baseband processor included in the processing circuitry) for transmission. The transmission may be performed by a transceiver or other component, in some cases. In some embodiments, such an element may be decoded, detected or otherwise processed by the processing circuitry (such as by the baseband processor). The element may be received by a transceiver or other component, in some cases. In some embodiments, the processing circuitry and the transceiver may be included in a same apparatus. The scope of embodiments is not limited in this respect, however, as the transceiver may be separate from the apparatus that comprises the processing circuitry, in some embodiments.

[0077] In some embodiments, a RAN node 1 15 may perform one or more operations of the method 600, but embodiments are not limited to performance of the method 600 and/or operations of it by the RAN node 1 15. Although references may be made to performance of one or more operations of the method 600 by the RAN node 1 15 in descriptions herein, another component may perform the same operation(s), similar operation(s) and/or reciprocal operation(s), in some embodiments.

[0078] At operation 605, the RAN node 1 15 may receive a group service request for a group based service (GBS) from a mobile device 1 10. In some embodiments, the group service request may indicate whether the mobile device 1 10 supports operation in the group-cast mode for the GBS. It should be noted that embodiments are not limited to usage of the group service request to communicate such information. One or more other control messages may be used, in some embodiments.

[0079] In some embodiments, a uni-cast mode may be based on per- packet transmissions per mobile device 1 10 as part of the GBS. The group-cast mode may be based on per-packet transmissions to multiple mobile devices 110 as part of the GBS.

[0080] In some embodiments, the control signaling may indicate a maximum time delay for transmission of the group service request by the mobile device 110. Accordingly, the mobile device 110 may determine a random delay in accordance with the maximum time delay and may transmit the group service request in accordance with the determined random delay. In some embodiments, the control signaling may indicate a valid reporting duration for transmission of the group service request by the mobile device 110. Accordingly, the mobile device 110 may determine a random delay in accordance with the valid reporting duration and may transmit the group service request in accordance with the determined random delay.

[0081] In some embodiments, the control signaling may include a broadcast message. In some embodiments, the control signaling may include a uni-cast message .

[0082] In some embodiments, the control signaling may indicate a group based service identifier (GBS-ID) of the GBS. In some embodiments, the control signaling may indicate a report type parameter that indicates whether the mobile device 110 is to transmit an aperiodic group service report or periodic group service reports. In some embodiments, the control signaling may indicate a report time parameter that indicates: a report time if the report type parameter indicates that the mobile device 110 is transmit an aperiodic group service report, or a report period if the report type parameter indicates that the mobile device 110 is transmit periodic group service reports. In some embodiments, the control signaling may indicate other information.

[0083] At operation 610, the RAN node 115 may transmit control signaling that indicates a request for one or more QoS measurements from the mobile device 110 for the GBS. At operation 615, the RAN node 115 may receive a group service report that includes the one or more QoS measurements. At operation 620, the RAN node 115 may determine, based at least partly on the QoS measurement, whether to switch the mobile device 110 from a uni-cast mode to a group-cast mode for the GBS. At operation 625, the RAN node 115 may transmit a group service response. [0084] Non-limiting example QoS measurements include, but are not limited to, a signal quality measurement, a packet error rate, a reference signal received power (RSRP), reference signal received quality (RSRQ), received signal power, signal-to-noise ratio (SNR) and/or other. In some embodiments, the QoS measurement(s) may be based on signals received at the mobile device 110 from the RAN node 1 15. The signals may be transmitted as part of the GBS, although the scope of embodiments is not limited in this respect.

[0085] In some embodiments, the RAN node 115 may determine that the mobile device 110 is to switch from the uni-cast mode to the group-cast mode for the GBS if the signal quality measurement is above a first predetermined threshold. In some embodiments, the RAN node 115 may determine that the mobile device 110 is to switch from the uni-cast mode to the group-cast mode for the GBS if the packet error rate is below a second predetermined threshold.

[0086] In some embodiments, the group service response may indicate whether the mobile device 110 is to switch from the uni-cast mode to the group- cast mode for the GBS. If it is determined that the mobile device 110 is to switch from the uni-cast mode to the group-cast mode, the group service response may further indicate a channel allocated for transmission of packets for the GBS for the group-cast mode.

[0087] In some embodiments, the RAN node 115 may determine that the mobile device 110 is to switch from the group-cast mode to the uni-cast mode for the GBS. Various techniques may be used, including but not limited to techniques similar to those described above for determination of whether the mobile device 110 is to switch to the group-cast mode for the GBS. For instance, the determination may be based on the signal quality measurement, the packet error rate and/or other. In some embodiments, the group service response may indicate whether the mobile device 110 is to switch from the group-cast mode to the uni-cast mode for the GBS.

[0088] At operation 630, the RAN node 115 may receive packets for the GBS from an application server 160. At operation 635, the RAN node 115 may transmit packets for the GBS to one or more mobile devices 110.

[0089] In some embodiments, the RAN node may receive packets for the

GBS from the core network. For instance, the RAN node 115 may comprise an interface. The interface may be configurable to receive packets from the core network. In some embodiments, the core network may process control plane and user plane messages sent by the application server 160 for the GBS. In some embodiments, the interface may be configurable to receive packets from a core network component that operates as a relay to forward core plane messages and user plane messages from the application server 160 to the RAN node 115. In some embodiments, the RAN node 115 may receive packets indirectly from the application server 160. For instance, a path between the RAN node 115 and the application server 160 may include one or more components.

[0090] In some embodiments, an apparatus of a RAN device 115 may comprise memory. The memory may be configurable to store one or more QoS measurements. The memory may store one or more other elements and the apparatus may use them for performance of one or more operations. The apparatus may include processing circuitry, which may perform one or more operations (including but not limited to operation(s) of the method 600 and/or other methods described herein). The processing circuitry may include a baseband processor. The baseband circuitry and/or the processing circuitry may perform one or more operations described herein, including but not limited to determination of whether to switch the mobile device 110 from the uni-cast mode to the group-cast mode for the GBS. The apparatus of the RAN node 115 may include a transceiver to receive the control signaling. The transceiver may transmit and/or receive other blocks, messages and/or other elements.

[0091] In some embodiments, a mobile device 110 may perform one or more operations of the method 700, but embodiments are not limited to performance of the method 700 and/or operations of it by the mobile device 110. Although references may be made to performance of one or more operations of the method 700 by the mobile device 110 in descriptions herein, another component may perform the same operation(s), similar operation(s) and/or reciprocal operation(s), in some embodiments.

[0092] At operation 705, the mobile device 110 may receive one or more packets from a source RAN node 115 as part of a group based service (GBS). In some embodiments, the packet(s) may be received from the source RAN node

115 in a group-cast mode as part of the GBS. The packet(s) may include a first GBS identifier (GBS-ID) reserved to indicate packets from the source RAN node 115 for the GBS in the group-cast mode.

[0093] It should be noted that references to a "source RAN node" and a

"target RAN node" may be used for clarity, but such references are not limiting.

[0094] At operation 710, the mobile device 110 may receive a handover command message from the source RAN node 115 that indicates a second GBS- ID reserved to indicate packets from a target RAN node 115 for the GBS in the group-cast mode. In some embodiments, additional information may be indicated and/or included. It should be noted that embodiments are not limited to usage of the handover command message to communicate the information described above. One or more other control message(s) may be used to communicate the information, in some embodiments.

[0095] At operation 715, the mobile device 110 may transmit, to the target RAN node 115, a handover request message that indicates a request for a handover to the target RAN node 115. In some embodiments, the handover request message may indicate a request for a handover to the target RAN node 115 for the GBS, although the scope of embodiments is not limited in this respect. In some embodiments, additional information may be indicated and/or included. It should be noted that embodiments are not limited to usage of the handover request message to communicate the information described above. One or more other control message(s) may be used to communicate the information, in some embodiments.

[0096] At operation 720, the mobile device 110 may receive a handover response message from the target RAN 115 that indicates whether the request for the handover is accepted. In some embodiments, additional information may be indicated and/or included. It should be noted that embodiments are not limited to usage of the handover response message to communicate the information described above. One or more other control message(s) may be used to communicate the information, in some embodiments. In some embodiments, the handover response message may include a third GBS-ID. In a non-limiting example, the third GBS-ID may be the same as the second GBS-ID. In another non-limiting example, the third GBS-ID may be different from the second GBS- ID. In some cases, the GBS-ID may not necessarily be the same between the source RAN node 115 and the target RAN node 115.

[0097] At operation 725, the mobile device 110 may transmit, to the source RAN node 115, a handover complete message indicates: that the handover to the target RAN node has been performed, a device ID of the mobile device 110 and/or the third GBS-ID. In some embodiments, additional information may be indicated and/or included. It should be noted that embodiments are not limited to usage of the handover complete message to communicate the information described above. One or more other control message(s) may be used to communicate the information, in some embodiments.

[0098] At operation 730, if the handover is accepted, the mobile device

110 may receive one or more packets from the target RAN node 115 in the group-cast mode as part of the GBS. In some embodiments, the packets may include the second GBS-ID. In some embodiments, the packets may include the third GBS-ID.

[0099] In some embodiments, a RAN node 115 may perform one or more operations of the method 800, but embodiments are not limited to performance of the method 800 and/or operations of it by the RAN node 115. Although references may be made to performance of one or more operations of the method 800 by the RAN node 115 in descriptions herein, another component may perform the same operation(s), similar operation(s) and/or reciprocal operation(s), in some embodiments.

[00100] At operation 805, the RAN node 115 may receive a monitoring report request message from a service portal function (SPF) node 130 that indicates a request for usage information for a group based service (GBS). At operation 810, the RAN node 115 may determine the usage information. At operation 815, the RAN node 115 may transmit a report message that includes the usage information. In some embodiments, the usage information may include a number of mobile devices supported by the RAN node 115 for the GBS. In some embodiments, the usage information may further include maximum transmission rates of mobile devices 110 that operate in the uni-cast mode for the GBS. Other information may be included, in some embodiments. [00101] At operation 820, the RAN node 115 may receive control signaling from the SPF node 130 that indicates whether the RAN node 115 is to switch one or more mobile devices from a uni-cast mode to a group-cast mode for the GBS.

[00102] At operation 825, the RAN node 115 may transmit a message that indicates that the mobile device 110 is to switch to the group-cast mode for the GBS. In some embodiments, the RAN node 115 may transmit the message that indicates that the mobile device 110 is to switch to the group-cast mode for the GBS if the control signaling received at operation 820 indicates that the mobile device 110 is to switch to the group-cast mode for the GBS.

[00103] In some embodiments, if the control signaling from the SPF node

130 indicates that a plurality of mobile devices 110 are to switch to the group- cast mode for the GBS, the RAN node 115 may transmit, to one of the mobile devices 110 of the plurality, a paging message that indicates that the mobile device 110 is to switch to the group-cast mode for the GBS. The RAN node 115 may transmit multiple paging messages. For instance, the RAN node 115 may transmit a paging message to each of the mobile devices 110 that are to switch to the group-cast mode for the GBS, in some embodiments.

[00104] In some embodiments, if the control signaling from the SPF node indicates that a plurality of mobile devices are to switch to the group-cast mode for the GBS, the RAN node may transmit a broadcast control message that indicates that the mobile devices 110 of the plurality are to switch to the group- cast mode for the GBS.

[00105] At operation 830, the RAN node 115 may transmit a packet on a channel allocated for transmission of packets for the GBS for the group-cast mode. In some embodiments, if the control signaling from the SPF node 130 indicates that a plurality of mobile devices 110 are to switch to the group-cast mode for the GBS, the RAN node 115 may transmit a packet to the plurality of mobile devices 110 on a channel allocated for transmission of packets for the GBS for the group-cast mode. It should be noted that the RAN node 115 may transmit one or more packets in the group-cast mode for the GBS and may also transmit one or more packets in the uni-cast mode for the GBS. For instance, the

RAN node 115 may simultaneously support usage of a uni-cast mode for one or more mobile devices 110 for the GBS and usage of a group-cast mode for one or more mobile devices 110 for the GBS.

[00106] In some embodiments, an SPF node 130 may perform one or more operations of the method 900, but embodiments are not limited to performance of the method 900 and/or operations of it by the SPF node 130. Although references may be made to performance of one or more operations of the method 900 by the SPF node 130 in descriptions herein, another component may perform the same operation(s), similar operation(s) and/or reciprocal operation(s), in some embodiments.

[00107] At operation 905, the SPF node 130 may transmit, to a RAN node

115, a monitoring report request message that indicates a request for usage information for a GBS supported by the RAN node 115. In some embodiments, additional information may be indicated and/or included. It should be noted that embodiments are not limited to usage of the monitoring report request message to communicate the information described above. One or more other control message(s) may be used to communicate the information, in some embodiments.

[00108] In some embodiments, the usage information may include a number of mobile devices supported by the RAN node 115 for the GBS, maximum transmission rates of the mobile devices 110 for the GBS and/or other information.

[00109] At operation 910, the SPF node 130 may receive a report message from the RAN node that includes the usage information.

[00110] At operation 915, the SPF node 130 may determine, based on the usage information, whether to initiate a request for the RAN node 115 to operate in a group-cast mode for the GBS. In a non-limiting example, the SPF node 130 may determine to initiate the request for the RAN node 115 to operate in the group-cast mode for the GBS if the number of mobile devices 110 supported by the RAN node 115 for the GBS is greater than a first predetermined threshold. In another non-limiting example, the SPF node 130 may determine to initiate the request for the RAN node 115 to operate in the group-cast mode for the GBS if the maximum transmission rates of the mobile devices 110 for the GBS are greater than a second predetermined threshold. These examples are not limiting, however. In some embodiments, technique(s) may use other information and/or comparisons to determine whether to initiate the request described above.

[00111] At operation 920, the SPF node 130 may transmit a GBS service request to an application server 160 that supports the GBS. In some embodiments, additional information may be indicated and/or included. It should be noted that embodiments are not limited to usage of the GBS service request to communicate the information described above. One or more other control message(s) may be used to communicate the information, in some embodiments.

[00112] In some embodiments, the SPF node 130 may transmit the GBS service request if it is determined that the request for the RAN node 115 to operate in the group-cast mode for the GBS is to be initiated, although the scope of embodiments is not limited in this respect.

[00113] At operation 925, the SPF node 130 may receive a GBS service response message from the application server 160 that indicates whether the RAN node 115 is to operate in the group-cast mode for the GBS. In some embodiments, additional information may be indicated and/or included. It should be noted that embodiments are not limited to usage of the GBS service resopnse to communicate the information described above. One or more other control message(s) may be used to communicate the information, in some embodiments.

[00114] At operation 930, the SPF node 130 may transmit, to the RAN node 115, control signaling that indicates that the RAN node 115 is to operate in the group-cast mode for the GBS.

[00115] FIG. 10 illustrates an outline of example methods in accordance with some embodiments. FIG. 11 illustrates example operations and/or example messages in accordance with some embodiments. FIG. 12 illustrates example operations and/or example messages in accordance with some embodiments. FIG. 13 illustrates example operations and/or example messages in accordance with some embodiments. FIG. 14 illustrates example operations and/or example messages in accordance with some embodiments. FIG. 15 illustrates example operations and/or example messages in accordance with some embodiments.

FIG. 16 illustrates example operations and/or example messages in accordance with some embodiments. FIG. 17 illustrates example operations and/or example messages in accordance with some embodiments. FIG. 18 illustrates example operations and/or example messages in accordance with some embodiments; FIG. 19 illustrates example operations and/or example messages in accordance with some embodiments. FIG. 20 illustrates example operations and/or example messages in accordance with some embodiments.

[00116] It should be noted that the examples shown in FIGs. 10-20 may illustrate some or all of the concepts and techniques described herein in some cases, but embodiments are not limited by the examples. For instance, embodiments are not limited by the name, number, type, size, ordering, arrangement and/or other aspects of the operations, components and other elements as shown in FIGs. 10-20. Although some of the elements shown in the examples of FIGs. 10-20 may be included in a 3GPP LTE standard, 5G standard, NR standard and/or other standard, embodiments are not limited to usage of such elements that are included in standards.

[00117] In some embodiments, methods to provision local group based service(s) with RAN assisted information may be used. With RAN assisted information, the group based service may be enabled to reflect real time radio resource usage and the traffic activities of mobile devices.

[00118] In some embodiments, a RAN node 115 may assist in activation of a group-cast transmission for a group based service by providing local information to application servers. For clarity and organizational purposes, descriptions below may refer to "solutions" (such as Solution 1, Solution 2, Solution 3, Solution 4, and Solution 5), but such references are not limiting. In some embodiments, a method may include one or more operations from one or more of the solutions described below. For instance, a method may include one or more operations from a first solution described below and may further include one or more operations from a second solution described below. In some embodiments, the method may include one or more additional operations, which may or may not be described in one of the solutions below. In some

embodiments, a method may include operations from multiple solutions described herein. [00119] Solution 1 includes methods for the RAN node to provide assistance information via SPF/CN-CPF to the application server for setting a GBS triggering threshold. Solution 2 and Solution 4 include methods for monitoring the radio resource usage as assistance information at the RAN node. Solution 3 includes methods for the RAN node/SPF/CN-CPF/Application server to initiate a GBS service in group-cast mode. Solution 5 includes methods for a RAN node to inform the mobile devices using GBS in unicast mode. Such methods may further enable the GBS in group-cast mode for the mobile devices. In some cases, the mobile devices may switch from usage of unicast mode to usage of group-cast mode. It should be noted that methods described herein may be applicable to an SDN based infrastructure, although the scope of

embodiments is not limited in this respect. In some embodiments, one or more of the operations, techniques and/or methods described herein may be applicable to scenarios in which provisioning of a group based service is performed using V2X, group based message delivery, MBMS in EPS and/or other.

[00120] Referring to FIG. 10, in some embodiments, initiation of a GBS service by the RAN node 1020 or by SPF 1030 or by the Application server 1040 may be performed based on assistance information from the RAN node 1020. The boxes indicate 1050-1056 indicate information related to Solution 1, Solution 2, Solution 3, Solution 4, and Solution 5.

[00121] In Solution 1, two options (referred to as option 1A and option

IB) are described below, but embodiments are not limited to these two options. Other options are possible, in some embodiments. The application server may provide information to the SMN for registration of GBS service and/or activation of monitoring/reporting procedure toward RAN nodes before initiation of GBS service using group-cast.

[00122] Referring to FIG. 11, option 1A is illustrated. The application server 1120 may send a service registration message 1125 for the GBS service to

SPF 1115. The service registration message 1 125 may indicate one or more of the following information: a Service ID, a GBS indication, an application server

ID, service area information and/or other information. The service ID may be provided to indicate that the service ID/GBS-ID is associated to a GBS service.

The GBS indication may be provided to indicate that the Service ID/GBS-ID is associated to a GBS service. The service area ID may be provided to the SPF 1115 as location information to determine the impacted RAN nodes. The application server ID may be provided for authorization.

[00123] In some embodiments, the SPF 1115 may return an allocated temporary GBS-ID in response to the service registration request message 1125 or when the group-cast is activated. The RAN node 1110 may return an allocated temporary RAN node ID to identify the instance of the service information notification for the GBS service associated to the service ID/GBS- ID. As indicated by 1130, the SPF 1115 may determine whether service information notification (including but not limited to a service ID and/or GBS- ID) is to be sent to one or more RAN nodes in the service information notification message 1135.

[00124] In some embodiments, a monitoring/reporting procedure between the SPF 1115 and one or more RANs 1110 may be activated by the SPF 1115 or by the RAN nodes 1110. If activation is performed by the SPF 1115, the notification message 1155 may additionally include one or more of the following for activation of the monitoring/reporting procedure: monitoring information (including but not limited to a number of mobile devices, maximum transmission rates used by the mobile devices using the GBS service in unicast mode which is associated to a service ID and/or GBS-ID if provided), a reporting type parameter (such as a periodic report with indicated criteria, a one-time report and/or other), an action type (such as GBS triggering, monitoring report and/or other), and/or other information. If activation is performed by the RAN node 1110, the RAN node 1110 may send a status update to the SPF 1115.

[00125] In the report message 1160, the reporting info may include one or more of the following information: a triggering threshold, a number of mobile devices, maximum transmission rates for serving mobile devices in unicast mode, and/or other information.

[00126] Referring to FIG. 12, option IB is illustrated. The application server 1220 may activate a monitoring/reporting procedure by sending a monitoring/reporting request message 1225 for the GBS service to SPF 1215.

The monitoring/reporting request message 1225 may indicate one or more of the following information: a service ID of the GBS service, a GBS indication, a service area ID, an application server ID, service area information and/or other information. The service ID may be provided to indicate that the service ID/GBS-ID is associated to a GBS service. The GBS indication may be provided to indicate that the service ID/GBS-ID is associated to a GBS service. The service area ID may be provided to the SPF 1215 as location information to determine the impacted RAN nodes. The application server ID may be provided for authorization.

[00127] The SPF 1215 may initiate the monitoring/reporting procedure towards the RAN node 1210 for the GBS identified by a GBS-ID. In a response message to the application server 1220, the SPF 1215 may return an allocated temporary GBS-ID associated to the service ID if no GBS-ID is associated to the service ID of the GBS. The monitoring/reporting request message 1235 may include one or more of the following information: monitoring information (including but not limited to a number of mobile devices, maximum transmission rates used by the mobile devices using the GBS service in unicast mode which is associated to a service ID and/or GBS-ID if provided, and/or other), a reporting type (such as a periodic report with indicated criteria, a one-time report and/or other), an action type (such as GBS triggering, monitoring report and/or other), and/or other information. It should be noted that one or more elements described regarding option 2 of solution 1 may be used in solution 3, in some

embodiments.

[00128] The report message 1240 may include one or more of the following information: a triggering threshold, a number of mobile devices, maximum transmission rates for serving mobile devices in unicast mode, and/or other information. In some embodiments, the report message 1245 may include at least some of the information included in the report message 1240. In some embodiments, the report message 1245 may be based on at least some of the information included in the report message 1240. The RAN node 1210 may return an allocated temporary RAN node ID to identify the instance of the service information notification for the GBS service associated to the service ID/GBS-ID.

[00129] In Solution 2, when the RAN node receives the service availability information in Solution 1 -Option A or the monitoring request message in Solution 1 -Option B from the SPF, the RAN node may start to collect radio resource usage information of the GBS service associated to a service ID/GBS-ID. The RAN nodes may collect radio resource usage information associated to the service ID, wherein the service ID may be indicated when a mobile device sends a service request message which includes the configured service ID for the GBS service. The radio resource usage information may include one or more of: a number of mobile devices using the GBS associated with the service ID/GBS-ID; maximum transmission rates used by the mobile devices using the GBS service in unicast mode which is associated to a service ID and/or GBS-ID if provided; and/or other information. If GBS-ID is provided at the service request message, the mobile device may get the GBS- ID information from the broadcast information which provides the mapping of the preconfigured Service ID and the GBS-ID.

[00130] In Solution 3, three options (referred to as option 3A, option 3B and option 3C) are described below, but embodiments are not limited to these three options. Other options are possible, in some embodiments. Solution 3 provides different techniques for initiation of GBS service using group-cast.

[00131] Referring to FIG. 13, option 3A is illustrated. With service availability information received from the SPF in solution 1 or the reporting information from the RAN node 1315, the RAN node 1315 may provide information to application server 1325 about triggering threshold for a GBS service identified by a service ID/GBS-ID. For a congested RAN node 1315, the RAN node 1315 may want to join GBS service using group-cast with a lower threshold. The application server 1325 may determine to initiate GBS service request to SPF 1320 when a triggering threshold is met. In some embodiments, the triggering threshold may be a number of mobile devices, maximum transmission rates for serving mobile devices in unicast mode and/or other.

[00132] Referring to FIG. 14, option 3B is illustrated. The RAN node

1415 may monitor activities on mobile devices 1410 using group based service in terms of radio resource scheduling and may update the radio resources information to the SPF/CN-CPF 1420. The SPF/CN-CPF 1420 may determine to initiate GBS service request to the application server 1425 for triggering group- cast of a GBS-ID from the application server 1425. [00133] Referring to FIG. 15, option 3C is illustrated. The RAN node

1515 may monitor activities on mobile devices using group based service in terms of radio resource scheduling. The RAN node 1515 may initiate a GBS service request to the SPF 1520 and the application server 1525 for triggering group-cast of a GBS-ID from the application server 1525.

[00134] An example of provisioning local group based service will be described below. This example may be applicable to vehicular communication, although the scope of embodiments is not limited in this respect. Operations described as part of this example may be included in other scenarios, in some cases. In some embodiments, a method may include one or more of those operations. In some embodiments, the method may include one or more additional operations.

[00135] For a group of vehicles, a unicast mode may be used to obtain GBS service from a RAN node. Depending on a traffic situation, the RAN node may determine to use group-cast mode for sharing the information among the vehicles by a local group based service. In order to initiate the GBS in group- cast mode and to trigger the switching from the unicast mode to group-cast mode for vehicles using a GBS with GBS-ID(s), the RAN node may initiate a GBS request message to the application server based on measurements of the radio resource usage for the GBS. As such, the GBS service may be provided in a more responsive and dynamic manner and may reflect real-time radio resource usage and/or traffic activities. In some embodiments, one or more of the operations, techniques and/or concepts described for one or more of Solutions 1- 5 may be used in this example.

[00136] An example method described below includes 7 operations

(referred to as Operations 1-7). It should be noted that some embodiments may not necessarily include all of Operations 1-7. Some embodiments may include one or more additional operations. Embodiments are not limited to performance of Operations 1-7 in chronological order.

[00137] In some embodiments, Solution 1 (or a portion of it) may be used for Operations 1-4. In Operation 1, the application server may send a service registration request message to the SPF. In Operation 2, after finishing the service registration procedure, the application server may serve the mobile devices for a GBS service in unicast mode. In Operation 3, the SPF/CN-CPF may inform one or more RAN nodes about available services of the GBS service with the service ID. In Operation 4, the SPF may initiate monitoring/reporting procedures towards selected RAN nodes for the GBS service associated to the service ID.

[00138] In some embodiments, one or more of Solution 2, Solution 4, a portion of Solution 2, and a portion of Solution 4 may be used for Operation 5. Operation 5 will be described below, without limitation, as Operation 5A and 5B. In Operation 5A, Solution 2 (or a portion of it) may be used. The RAN node may count a number of the vehicles with group-cast capability or may measure maximum transmission rates of the vehicles with group-cast capability. In Operation 5B, Solution 4 (or a portion of it) may be used. The RAN node may trigger measurement reporting from the mobile devices.

[00139] In some embodiments, Solution 3 (or a portion of it) may be used for Operation 6. In Operation 6, based on the monitoring results, the RAN node may determine to initiate GBS with GBS -ID in group-cast mode to the application server by sending a GBS request message to the application server.

[00140] In some embodiments, Solution 5 (or a portion of it) may be used for Operation 7. When the group-cast mode is enabled, the RAN node may use one or more of the following two options to notify the mobile devices to switch from the unicast mode to the group-cast mode. In a first option, a paging procedure may be used for switching individual mobile device from unicast mode to the group-cast mode. In a second option, a broadcast mechanism may use System information Block to bring a group of mobile devices from unicast mode to the group-cast mode.

[00141] Referring to FIG. 16, Solution 4 is illustrated. In Solution 4, the

RAN node 1615 may obtain unicast information from the mobile devices 1610 using one or more group based services. Two options are presented for Solution 4, but embodiments are not limited to these two options.

[00142] In a first option (indicated by 1620), a broadcast mode may be used. In a first operation in the first option of Solution 4, the RAN node 1615 with active group-casts received from the application server may broadcast (as indicated by 1622) one or more of the following group based service information. A group based service ID (GBS-ID) may be an identification of the group service to identify a particular group based service within the operator domain. A response duration for a responding service report message from the mobile devices may indicate a window of time in which the message is to be received. Radio channel information for receiving the group-cast data may be included. With the radio channel information, the mobile device 1610 currently not operating in group-cast mode may measure quality of service parameters such as received signal quality, packet error rates, packet delays, delay jitters and/or other. A report indication may include requested information, which may include a report type (such as one-time report or periodical report or other), a reporting time for scheduled one-time report time, a period of the reporting, a corresponding valid reporting duration, requested report content for operation mode (such as unicast and/or group-cast), quality of service parameters (such as received signal quality, packet error rates, packet delays, delay jitters and/or other) in one or more operation modes.

[00143] In a second operation in the first option of Solution 4, when receiving the broadcast information about the group based service of GBS-ID, the mobile device may send a service reporting message 1624 to the RAN node 1615 indicating the GBS-ID and requested quality of service parameters (such as received signal quality, packet error rates, packet delays, delay jitters and/or other) of the requested operation mode(s). In some embodiments, the service reporting message 1624 may be sent with a random duration after receiving the broadcast information. This technique may be used to avoid a large amount of signaling generated by multiple mobile devices using the same group based service ID, in some cases.

[00144] In a second option for Solution 4 (indicated by 1630), a broadcast mode may be used. In a first operation in the second option of Solution 4, the RAN node 1615 may send a message 1632 to request information in the measurement report from a mobile device 1610 using the group based service of GBS-ID. The information may include one or more of the following: a GBS-ID, the radio channel information for receiving the group-cast data, wherein with this information, a mobile device 1610 not currently operating in group-cast mode may measure quality of service parameters (such as received signal quality, packet error rates, packet delays, delay jitters and/or other); a report indication that may include requested information; a report type (such as onetime report or periodic report); a reporting time for a scheduled one-time report time or a period of the reporting and a corresponding valid reporting duration; requested report content for operation mode (unicast and/or group-cast), requested quality of service parameters (such as received signal quality, packet error rates, packet delays, delay jitters and/or other) in one or more operation modes. Additionally, the RAN 1615 node may request more report information to assist the decision on using unicast/group-cast for the mobile device. The information may be mobile device location information and/or user activity information (which may indicate active/inactive mode of the application for the group based service, a mobility level of the mobile device and/or other). If the mobile device has more than one active group based service, the RAN node 1615 may indicate information for each GBS-ID.

[00145] In a second operation of the second option for Solution 4, in response to the group service report request message for the group based service of GBS-ID, the mobile device 1610 may send a service reporting message 1634 to the RAN node 1615 indicating the GBS-ID, requested quality of service parameters (such as received signal quality, packet error rates, packet delays, delay jitters and/or other) of the requested operation mode(s). A mobile device 1610 may return one or more measurement reports as requested in the first operation of the second option of Solution 4 to the RAN node 1615. If the mobile device 1610 has more than one active group based services, it may report as instructed by the RAN node 1615.

[00146] Referring to FIG. 17, Solution 5 is illustrated. When the RAN node 1715 receives a request to enable the group-cast for the GBS from the SPF/CN-CPF, the RAN node 1715 may inform the mobile device to switch between the unicast and group-cast for the group based service. In some cases, operations may depend on a first message sent from the RAN node 1715 to trigger the mobile device 1710 for the switch from the unicast operation mode to the group-cast operation mode. In a non-limiting example, in an individual switch mode: the first message may be a paging message or a service notification message depending on the status of the activeness of the mobile device 1710. In another non-limiting example, in a group switch model, the first message may be a broadcast message indicating the GBS-ID that is provided from the application server or the RAN node 1715.

[00147] In some embodiments, a method may include one or more operations described below (referred to as Operations 1-6 without limitation). Embodiments are not limited to the chronological order described below. In some embodiments, the method may include one or more additional operations.

[00148] In Operation 1, the RAN node 1710 may send a first message

1720 indicating the GBS-ID of the group based service and/or an operation mode to trigger the switching between unicast mode and the group-cast mode. The first message 1720 may be a paging message or a service notification message depending on the status of the activeness of the mobile device. For example, if the mobile device 1710 is in an idle mode, the RAN node 1715 may send a paging message to bring the mobile device 1710 back to the connected mode for the specified group based service with GBS-ID. In this case, the mobile device ID may be added and may be used as a paging target for a mobile device 1710 while the GBS-ID is used to identify the service for the paging. For example, if the mobile device 1710 is in a connected mode, the RAN node 1715 may send a service notification for notifying the mobile device 1710 to change status of the group based service with GBS-ID.

[00149] In Operation 2, the if the mobile device 1710 is capable of using the indicated operation mode, the mobile device 1710 may send a group based service request message 1725 to request service with a desired operation mode by indicating the GBS-ID and the desired operation mode to the RAN node 1715 for the group based service. Otherwise, the mobile device 1710 may reject to the service notification with a particular cause value indicated in the service request message 1725.

[00150] In Operation 3, the RAN node 1715 may respond to the group based service request message 1725 with message 1730, which may indicate the switching commands for the GBS-ID and provides radio resource information for the operation mode. If the operation mode is for group-cast, the radio resource information may indicate radio channel information for the group-cast of the GBS-ID. If the operation mode is for unicast, the radio resource information may indicate the scheduled time/radio resource to start the unicast. In another non-limiting example, Operations 1-3 may be implemented with two messages between the RAN node 1715 and the mobile device 1710, such as a first message that includes switching information for the mobile device 1710 and a response message from the mobile device 1710 to confirm the notification.

[00151] In Operation 4, the mobile device 1710 and the RAN node 1715 may switch to the requested operation mode (as indicated by 1740). In

Operation 5, the mobile device 1710 may switch to the desired operation mode as follows. As indicated by 1745, if the operation mode is for group-cast, the mobile device 1710 may start to receive the broadcast information for the GBS- ID and may switch to group-cast operation mode for the group based service with GBS-ID. As indicated by 1750, if the operation mode is for unicast, the mobile device 1710 may use the unicast mode to receive the group based service of the GBS-ID and may use radio resources scheduled by the RAN node 1715. In some embodiments, a technique similar to usage of a PDSCH in an LTE network may be used, although the scope of embodiments is not limited in this respect. In Operation 6, the mobile device 1710 may start to receive the data of the group based service of the GBS-ID, as indicated by 1755.

[00152] In some embodiments, in a method of provisioning a group based service in a mobile network, an application server 160 may initiate a group based service identified by a service ID based on assistance information of an SPF 130. The application server 160 may send a first message to the SPF 130, wherein the first message is for group service request that includes at least one of the following: service ID, GBS-ID, application server ID and/or other. The application server 160 may send the first message when it receives a second message from the SPF 130, wherein the second message includes at least one of the following: service ID, GBS-ID, application server ID, action type (which may indicate GBS initiation in group-cast mode, in some cases) and/or other. The SPF 130 may determine to initiate GBS in group-cast mode when it receives a third message from a RAN node 115. The third message may include at least one of the following: service ID, action type (which may indicate the GBS initiation in group-cast mode. [00153] In some embodiments, the application server 160 may determine to initiate the GBS identified by an GBS -ID/service ID when a triggering threshold is met. The triggering threshold may be received from the RAN node 115 via the SPF 130. In some embodiments, the triggering threshold may be a number of mobile devices 110 using GBS identified by the service ID or maximum transmission rates of mobile devices 110 using GBS in unicast mode.

[00154] In some embodiments, in a method of provisioning a group based service in a mobile network, an application server 160 may send a first message to an SPF 130, wherein the first message may include at least one of the following: service ID, GBS indication, application server ID, service area information, message type and/or other. In some embodiments, the message type in the first message may be indicated as a GBS service registration message. The SPF 130 may send a second message to a RAN node 115 that indicates available GBS service information. The second message may be a service information notification message and may include at least one of the following: service ID, GBS indication and/or other. In some embodiments, the RAN node 115 may send, to the SPF 130, a third message that includes at least one of the following information: service ID, RAN node temporary ID (which may be used to identify the monitoring/reporting instant at the RAN node 115) and/or other.

[00155] In some embodiments, the message type in the first message may be indicated as a monitoring/reporting request message, which may be used to initiate monitoring/reporting procedure in one or more RAN nodes 115 by sending a second message from the SPF 130 to one or more RAN nodes 115. The second message may include at least one of the following: monitoring information and report type including one time report or periodic report with an indicated period. In some embodiments, the RAN node 115 may send, to the SPF 130, a third message that includes at least one of the following: service ID, RAN node temporary ID (which may be used to identify the

monitoring/reporting instant at the RAN node 115, in some cases), reporting information and/or other.

[00156] In clarity and organizational purposes, descriptions below may refer to "solutions" (such as Solution 6, Solution 7, and Solution 8), but such references are not limiting. In some embodiments, a method may include one or more operations from one or more of the solutions described below. For instance, a method may include one or more operations from a first solution described below and may further include one or more operations from a second solution described below. In some embodiments, the method may include one or more additional operations, which may or may not be described in one of the solutions below. In some embodiments, a method may include operations from multiple solutions described herein.

[00157] Referring to FIG. 18, Solution 6 is described. In Solution 6, a RAN node 1815 may receive unicast/group-cast information from mobile devices using one or more group based services. Two options (referred to as Option 1 and Option 2 without limitation) are described below, but embodiments are not limited to these two options. In Option 1 of Solution 6 (indicated by 1820), in a first operation, the RAN node 1815 with active group-casts received from the application server may broadcast the following group based service information (as indicated by 1822): a group based service ID (GBS-ID), wherein the GBS-ID is the identification of the group service to identify a particular group based service within the operator domain; a response duration related to a window of time for a responding service report message from the mobile devices 1810; radio channel information for receiving the group-cast data, wherein with this information, a mobile device 1810 currently not operating in group-cast mode may measure one or more quality of service parameters (such as received signal quality, packet error rates, packet delays, delay jitters and/or other); a report indication; and/or other information. The report indication may include requested information, which may include a report type for one-time report or periodical report, a reporting time for scheduled one-time report time or period of the reporting and the corresponding valid reporting duration, requested report content for operation mode (unicast and/or group-cast), quality of service parameters (such as received signal quality, packet error rates, packet delays, delay jitters and/or other) in one or more operation modes. In a second operation in Option 1 of Solution 6, when receiving the broadcast information about the group based service of GBS-ID, the mobile device may send a service reporting message (as indicated by 1824) to the RAN node 1815 indicating the GBS-ID and requested quality of service parameters (e.g. received signal quality, packet error rates, packet delays, delay jitters and/or other) of the requested operation mode(s). In some embodiments, the service reporting message may be sent with a random duration after receiving the broadcast information. This may mitigate relatively large amounts of signaling generated by mobile devices 1810 using the same group based service ID, in some cases.

[00158] In Option 2 of Solution 6 (indicated by 1830), the RAN node

1815 may send a message 1832 to request information in the measurement report from a mobile device 1810 using the group based service of GBS-ID, wherein the information may include at least one of the following: a GBS-ID; radio channel information for receiving the group-cast data, wherein with this information, a mobile device 1810 currently not operating in group-cast mode may measure requested quality of service parameters (such as received signal quality, packet error rates, packet delays, delay jitters and/or other); a report indication; and/or other information. In some embodiments, the report indication may include the requested information, which may include a report type for one-time report or periodical report, a reporting time for scheduled onetime report time or period of the reporting and the corresponding valid reporting duration, requested report content for operation mode (unicast and/or group- cast), requested quality of service parameters (such as received signal quality, packet error rates, packet delays, delay jitters and/or other) in one or more operation modes. Additionally, the RAN node 1815 may request more report information to assist the decision on using unicast/group-cast for the mobile device 1810, wherein the information may include mobile device location information, user activity information (which may indicate the active/inactive mode of the application for the group based service, the mobility level of the mobile device and/or other), and/or other information. If the mobile device 1810 has more than one active group based services, the RAN node 1815 indicates required information for each GBS-ID. In a second operation in Option 2 of Solution 6, in response to the group service report request message 1832 for the group based service of GBS-ID, the mobile device 1810 may send a service reporting message 1834 to the RAN node 1815 indicating the GBS-ID, requested quality of service parameters (such as received signal quality, packet error rates, packet delays, delay jitters and/or other) of the requested operation mode(s). The mobile device 1810 may return one or more measurement reports as requested in Operation 1 of Option 2 to the RAN node 1815. If the mobile device 1810 has more than one active group based services, it may report as instructed by the RAN node 1815.

[00159] Referring to FIG. 19, Solution 7 is illustrated. Based on measurement reports sent from the mobile device 1910, the RAN node 1915 may decide to trigger the mobile device 1910 to switch between unicast and group- cast for a group based service. In Solution 7, a mobile device 1910 is triggered for the switch between the unicast operation mode and the group-cast operation mode.

[00160] In some embodiments, a method may include one or more operations described below (referred to as Operations 1-6 without limitation). Embodiments are not limited to the chronological order described below. In some embodiments, the method may include one or more additional operations.

[00161] In Operation 1 of Solution 7, the RAN node 1915 may send a first message 1920 that indicates the GBS-ID of the group based service and/or the operation mode to trigger the switching between unicast mode and the group- cast mode. In some embodiments, the first message may be a paging message or a service notification message, which may depend on a status of the activeness of the mobile device 1910. In a non-limiting example, if the mobile device 1910 is in idle mode, the RAN node 1915 may send a paging message to bring the mobile device 1910 back to the connected mode for the specified group based service with GBS-ID. In this case, the mobile device ID may be added and may be used as a paging target for a mobile device 1910 while the GBS-ID is used to identify the service for the paging. In another non-limiting example, if the mobile device 1910 is in connected mode, the RAN node 1915 may send a service notification for notifying the mobile device 1910 to change status of the group based service with GBS-ID.

[00162] In Operation 2 of Solution 7, if the mobile device 1910 is capable of using the indicated operation mode, the mobile device 1910 may send a group based service request message 1925 for requesting service with desired operation mode by indicating the GBS-ID and the desired operation mode to the RAN node 1915 for the group based service. Otherwise, the mobile device 1910 may reject to the service notification with a particular cause value indicated in the service request message 1925.

[00163] In Operation 3 of Solution 7, the RAN node 1915 may respond (as indicated by 1930) to the group based service request message 1925 indicating the switching commands for the GBS-ID and provides radio resource information for the operation mode. If the operation mode is for group-cast, the radio resource information may indicate radio channel information for the group- cast of the GBS-ID. If the operation mode is for unicast, the radio resource information may indicate the scheduled time/radio resource to start the unicast.

[00164] In some embodiments, Operations 1-3 may be implemented with two messages between the RAN node 1915 and the mobile device 1910, such as a first message that includes switching information for the mobile device 1910 and a response message from the mobile device 1910 to confirm the notification.

[00165] In Operation 4 of Solution 7, the mobile device 1910 and the RAN node 1915 may switch to the requested operation mode, as indicated by 1935 and 1940. In Operation 5 of Solution 7, the mobile device 1910 may switch to the desired operation mode as follows. As indicated by 1945, if the operation mode is for group-cast, the mobile device 1910 may start to receive the broadcast information for the GBS-ID and may switch to group-cast operation mode for the group based service with GBS-ID. As indicated by 1950, if the operation mode is for unicast, the mobile device 1910 may use the unicast mode to receive the group based service of the GBS-ID and may use the radio resources scheduled by the RAN node. In a non-limiting example, a technique similar to usage of a PDSCH in an LTE network may be used. In Operation 6 of Solution 7, the mobile device 1910 may start to receive the data of the group based service of the GBS-ID, as indicated by 1955.

[00166] Referring to FIG. 20, Solution 8 is illustrated. Based on measurement reports sent from the mobile device 2010, the RAN node 2015 may decide to trigger a handover for the mobile device 2010 to the target RAN node

2020. In some cases, this solution provides a method for the RAN node to guarantee service continuity for the mobile device 2010 using the group based service of a GBS-ID. In this solution, it may be assumed that the target RAN node 2020 has received the group based service of the GBS-ID from the application server and may use unicast or group-cast for the serving mobile devices for the group based service of a GBS-ID, although the scope of embodiments is not limited in this respect.

[00167] In some embodiments, a method may include one or more operations described below (referred to as Operations 1-8 without limitation). Embodiments are not limited to the chronological order described below. In some embodiments, the method may include one or more additional operations.

[00168] In Operation 1 of Solution 8, the RAN node 2015 may determine to enforce handover to the mobile device 2010, as indicated by 1230. In

Operation 2 of Solution 8, if information about the group based service for the target RAN node 2020 is unknown or if such information is expired, the RAN node 2015 may send a query message to another network node so as to obtain the group based service information of the target RAN node 2020. Different options are possible. As indicated by 2035, the message may be sent via interface to the CN-CPF and/or SPF (as indicated by 2025). As indicated by 2040, the message may be sent via interface to the target RAN node 2020. The message may include at least one of the following: a target RAN node ID, a GBS-ID and/or other information. If the GBS-ID used at the target RAN node 2020 is different for the same group based service, the response message may provide a target GBS-ID used at the target RAN node 2020.

[00169] In Operation 3 of Solution 8, the RAN node 2015 may send a handover preparation message 2045 to the target RAN node 2020 to notify the upcoming handover request from the mobile device 2010. The handover preparation message 2045 may include the GBS-ID for the group based service used in target RAN node 2020, a device ID of the mobile device 2010, a current operation mode of the group based service of GBS-ID and/or other information. In response, the target RAN node 2020 may return agreed operation mode for the group based service of GBS-ID, the device ID. Additionally, the target RAN node 2020 may send a service notification message 2047 to the CN-CPF/SPF

2025 which may include (and/or may be based on) some or all of the information described for 2045, although the scope of embodiments is not limited in this respect. [00170] In Operation 4 of Solution 8, the RAN node 2015 may send a handover command message 2050 to the mobile device 2010, which may include one or more of the following: the RAN node ID, the GBS-ID, the target GBS-ID, the operation mode and/or other information. In Operation 5 of Solution 8, the mobile device 2010 may suspend the group based service of GBS-ID, as indicated by 2055. In Operation 6 of Solution 8, the mobile device 2010 may send a handover request message 2060 to the target RAN node 2020, wherein the message may include one or more of the following: a device ID, a target GBS-ID, an operation mode and/or other information. In Operation 7 of Solution 8, the target RAN node 2020 may send a handover response message 2065, which may include one or more of the following: a target GBS-ID, an operation mode, radio resource information and/or other information. If the agreed operation mode is group-cast, the radio resource information may include the radio channel of the group-cast. If the agreed operation mode is unicast, the radio resource information may include scheduled radio resource(s) to be used.

[00171] In Operation 8 of Solution 8, the mobile device 2010 may send a handover complete message 2070 to the source RAN node 2015 to confirm the handover procedure. The message 2070 may include one or more of the following: a device ID, an original GBS-ID and/or other information. In Operation 9 of Solution 8 (as indicated by 2075), the mobile device 2010 may resume group based service of the target GBS-ID according to the operation mode indicated in Operation 4 of Solution 8. If the operation mode is for group- cast, the mobile device 2010 may start to receive the broadcast information for the target GBS-ID and may use the group-cast operation mode for the group based service with target GBS-ID. If the operation mode is for unicast, the mobile device 2010 may start to receive the group based service of the target GBS-ID via unicast by using the radio resources scheduled by the target RAN node 2020. In a non-limiting example, a technique similar to usage of a PDSCH in an LTE network may be used.

[00172] In some embodiments, a method may be performed. The method may be for reporting in a mobile network by a RAN node 115 with active group- casts received from the application server, in some cases, although the scope of embodiments is not limited in this respect. The RAN node 115 may send the following group based service information: group based service ID (GBS-ID), valid duration for responding service report message, and/or other information. The group based service ID (GBS-ID) may be an identification of the group service to identify a particular group based service within the operator domain. The valid duration may be used for responding service report message from the mobile devices 110. In some embodiments, the first message may be a broadcast message. In some embodiments, the first message may be for a mobile device 110. In some embodiments, the first message may additionally indicate a report indication, wherein the report indication may include one or more of the following: a report type for one-time report or periodical report, a reporting time for scheduled one-time report time or period of the reporting and the corresponding valid reporting duration, requested report content for operation mode (unicast and/or group-cast), requested quality of service parameters (such as received signal quality, packet error rates, packet delays, delay jitters and/or other) in one or more operation modes, and/or other information.

[00173] In some embodiments, the information may include a response duration related to a request for responding service report message from the mobile devices 110. In some embodiments, the information may include radio channel information for receiving the group-cast data, wherein with this information, a mobile device 110 not currently operating in group-cast mode may measure requested quality of service parameters (such as received signal quality, packet error rates, packet delays, delay jitters and/or other).

[00174] In some embodiments, in response to the received broadcast information, the mobile device 110 may wait a random time within the indicated response duration and may send a service reporting message to the RAN node 115 indicating the GBS-ID and its reports. The report may include requested quality of service parameters (such as received signal quality, packet error rates, packet delays, delay jitters and/or other) of the requested one or more operation modes

[00175] In some embodiments, a method may be performed. The method may be performed to switch an operation mode in a mobile network, in some cases, although the scope of embodiments is not limited in this respect. A RAN node 115 may send a first message that indicates an identity of a mobile device 110 and the GBS-ID of the group based service to trigger the switching between unicast mode and group-cast mode. In some embodiments, in response to the first message, a mobile device 110 may send a second message for service request that indicates the GBS-ID and a desired operation mode to the RAN node 115 for the group based service. In some embodiments, the RAN node 115 may, in response to the second message for service request, indicate switching commands for the GBS-ID and provide radio resource information for the operation mode. In some embodiments, if the operation mode is for group-cast, the radio resource information may indicate radio channel information for the group-cast of the GBS-ID. In some embodiments, if the operation mode is for unicast, the radio resource information may indicate scheduled time/radio resource(s) to start the unicast. In some embodiments, the first message may be a paging message or a service notification message, which may depend on a status of the idle/connected mode of the mobile device 110. In some

embodiments, the mobile device 110 may switch to the desired operation mode. If the operation mode is for group-cast, the mobile device 110 may start to receive the broadcast information for the GBS-ID and may switch to group-cast operation mode for the group based service with GBS-ID. If the operation mode is for unicast, the mobile device 110 may use the unicast mode to receive the group based service of the GBS-ID and may use the radio resources scheduled by the RAN node 115.

[00176] In some embodiments, a method may be performed. The method may be performed to provide service continuity for a first RAN node 115, in some cases, although the scope of embodiments is not limited in this respect. The first RAN node 115 may, based on measurement report(s) sent from the mobile device 110, decide whether to trigger a handover procedure for a mobile device 110 to a second RAN node 115 in order to provide service continuity for the mobile device 110 using the group based service of a first GBS-ID used at the first RAN node 115 and a second GBS-ID used at the second RAN node 115. In some embodiments, the first RAN node 115 may send a handover command message to the mobile device 110. The message may include one or more of the following: a first RAN node ID, a first GBS-ID, a second GBS-ID, an operation mode and/or other information. In some embodiments, the mobile device 110 may suspend the group based service of GBS-ID and may send a handover request message to the second RAN node 115. The message may include one or more of the following: a device ID, the second GBS-ID, the operation mode and/or other information. In some embodiments the RAN node 115 may return a handover response message that includes one or more of the following: the second GBS-ID, the operation mode, radio resource information used at the second RAN node 115 and/or other information. In some embodiments, the mobile device 110 may send a handover complete message to the source RAN node 115 to confirm the handover procedure. The message may include the device ID, the first GBS-ID and/or other information.

[00177] In some embodiments, the mobile device 110 may resume group based service of the target GBS-ID according to the operation mode. If the operation mode is for group-cast, the mobile device 110 may start to receive the broadcast information for the target GBS-ID and may use the group-cast operation mode for the group based service with target GBS-ID. If the operation mode is for uni-cast, the mobile device 110 may start to receive the group based service of the target GBS-ID via uni-cast by usage of the radio resources scheduled by the target RAN node 115. In a non-limiting example, a technique similar to usage of a PDSCH in an LTE network may be used.

[00178] In some embodiments, a method of provisioning a group based service in a mobile network for an SPF node 130 may include one or more of: determination of a policy of session management; allocation of a temporary ID to identify an authorized group based service (GBS); and sending a first message to a CN-CNF 120 after the SPF node 130 receives a second message indicating a service request from an application server 160. The first message may include at least one of the following information: the temporary ID, security parameters, group service area information, information related to the policy of session management and/or other information.

[00179] In some embodiments, the second message may include at least one of the following information: a group service ID, an application server ID, a service area (which may be indicated by a service area ID, in some cases) or geographical areas, a service request type (which may be indicated as group, in some cases); and a service profile. The service profile may include one or more of: a service time, a traffic load, a priority, maximum/average/minimum transmission rate(s), latency, group size (such as a number of device in the group).

[00180] In some embodiments, the policy of session management may include an IP multicast capability of the SPF node 130, the service profile and/or other information. In some embodiments, the group service area information may include a service area ID (SAI) and/or a mapped SAI. The mapped SAI may be provided by the application server 160 or may be calculated by the SPF 130. In some embodiments, the first message may be sent after receiving a third message from a subscription repository 170. The third message may indicate at least one of the following information: group service policies according to the service subscription, security parameters for IP packets encryption/integrity, group service ID, subscribed service area information of the group based service (such as a geographical area or the SAI) and/or other information.

[00181] In some embodiments, the CN-CPF 140 may inform the CN-UPF

150 and impacted RAN nodes 115 with routing policies identified by the TGSID. In addition, the CN-CPF 140 may determine the port number and the IP address of the boundary DGW for the group service identified by the TGSID. The RAN node 115 receiving the group service request indicating the enabling of the IP multicast may perform an IP multicast join procedure towards the CN- CPF 140. The CN-CPF 140 may then organize the IP multicast group and may configure the routing policies accordingly.

[00182] In addition, the CN-CPF 140 may store the security parameters in the group service context for security protection over user plane traffic transmission. In one embodiment, the CN-CPF 140 checks packets

encryption/integrity if requested by the CN-UPF 150. In another embodiment, the CN-UPF 150 checks packets encryption/integrity which security parameters are configured or provided by CN-UPF 150. Further, the CN-CPF 140 may forward the security parameters to the RAN nodes 115 for decrypting the IP packets identified by the TGSID. That is, the IP packets sent from the application server 160 to the impacted RAN nodes 115 may be secured by the encryption mechanism. [00183] In some embodiments, the CN-CPF 140 may send a response message to the SPF 130 and the SPF 130 may forward the information to the application server 160. The response message may include the information of the boundary DGW IP address and port number, security parameters, TGSID and/or other information. There may be more than one boundary DGW information, in some cases. For instance, the application server 160 may transmit the same data traffic via more than one boundary DGW with different IP address and/or port number.

[00184] In some embodiments, the application server 160 may encrypt the content of the IP traffic packets, may mark TGSID in IP packet header, and may start Group Service Downlink Transmission via the assigned DGW IP address/Port number. The DGWs receiving the IP packets marked with TGSID may enforce the routing rules to duplicates and may forward the IP packets accordingly. The RAN node 115 may use the stored security parameters to decrypt the packet identified by the TGSID.

[00185] In some embodiments, one or more of the above operations may be used to establish a PDU group-cast session. Within the service areas, the impacted nodes may need to support IP multicast capability. Depending on the IP multicast capability in the impacted RAN nodes 115/CN-CPF 140/CN-UPF 150, and network load conditions, the CN-CPF 140 may determine which type of the PDU group-cast session is used for provisioning group-based service requested by the application server 160.

[00186] In some embodiments, the CN-CPF 140 may have one or more of the following options (and/or other options) to configure routing polices on the DGWs in CN-UPF 150 with or without using IP multicast. In a first option, the routing policies may be configured with IP multi-cast. A PDU multicast session may be created for the joined RAN nodes 115 with IP multicast capability. The CN-CPF 140 may configure a routing policy for the IP multicast session on one or more DGWs in CN-UPF 150. The DGWs may check the IP multicast address and may determine how to forward the group service packets. When there is a change of the joined RAN node 115, the routing policies may need to be reconfigured for the impacted DGWs. The IP multicast group may be managed by SPF 130 or CN-CPF 140. [00187] In a second option, the routing policies may be configured without IP multi-cast. The CN-CPF 140 may configure routing policies on one or more DGWs in CN-UPF 150. In the routing policies, some of the DGWs may be configured to forward the same received traffic flow towards different targets, e.g. destined to different DGWs or RAN nodes 115. That is, the packet flow may be split by replicating the received packets from the source input and forwarding to two or more target outputs, which may be towards different RAN node(s) 115. The PDU group-cast session may be setup with one or more flows between the boundary DGW and the destined RAN nodes 115. For example, the traffic flow may be split at the boundary DGW or any intermediate DGWs.

[00188] In Example 1, an apparatus of a radio access network (RAN) node may comprise memory. The apparatus may further comprise processing circuitry. The processing circuitry may be configured to encode, for transmission, control signaling that indicates a request for a quality of service (QoS) measurement from a mobile device for a group based service (GBS). The processing circuitry may be further configured to decode a group service report from the mobile device that includes the QoS measurement. The processing circuitry may be further configured to store the QoS measurement in the memory. The processing circuitry may be further configured to determine, based at least partly on the QoS measurement, whether to switch the mobile device from a uni-cast mode to a group-cast mode for the GBS. The processing circuitry may be further configured to encode, for transmission, a group service response that indicates: whether the mobile device is to switch from the uni-cast mode to the group-cast mode for the GBS; and, if it is determined that the mobile device is to switch from the uni-cast mode to the group-cast mode, a channel allocated for transmission of packets for the GBS for the group-cast mode.

[00189] In Example 2, the subject matter of Example 1, wherein the uni- cast mode may be based on per-packet transmissions per mobile device as part of the GBS. The group-cast mode may be based on per-packet transmissions to multiple mobile devices as part of the GBS.

[00190] In Example 3, the subject matter of one or any combination of

Examples 1-2, wherein the QoS measurement may be a signal quality measurement or a packet error rate. The processing circuitry may be further configured to determine that the mobile device is to switch from the uni-cast mode to the group-cast mode for the GBS if: the signal quality measurement is above a first predetermined threshold, or the packet error rate is below a second predetermined threshold.

[00191] In Example 4, the subject matter of one or any combination of

Examples 1-3, wherein the processing circuitry may be further configured to decode, from the mobile device, a group service request that indicates whether the mobile device supports operation in the group-cast mode for the GBS.

[00192] In Example 5, the subject matter of one or any combination of

Examples 1-4, wherein the control signaling may indicate a maximum time delay for transmission of the group service request by the mobile device.

[00193] In Example 6, the subject matter of one or any combination of

Examples 1-5, wherein the control signaling may include a broadcast message.

[00194] In Example 7, the subject matter of one or any combination of

Examples 1-6, wherein the control signaling may indicate one or more of: a group based service identifier (GBS-ID) of the GBS; a report type parameter that indicates whether the mobile device is to transmit an aperiodic group service report or periodic group service reports; and a report time parameter. The report time parameter may indicate: a report time if the report type parameter indicates that the mobile device is transmit an aperiodic group service report; or a report period if the report type parameter indicates that the mobile device is transmit periodic group service reports.

[00195] In Example 8, the subject matter of one or any combination of Examples 1-7, wherein the RAN node may be arranged to operate in a software defined network (SDN) that supports an application server. The RAN node may further comprise an interface. The interface may be configurable to receive packets from a core network component that operates as a relay to forward core plane messages and user plane messages from the application server to the RAN node.

[00196] In Example 9, the subject matter of one or any combination of

Examples 1-8, wherein the processing circuitry may be further configured to determine, based at least partly on the QoS measurement, whether to switch the mobile device from the group-cast mode to the uni-cast mode for the GBS.

[00197] In Example 10, the subject matter of one or any combination of

Examples 1-9, wherein the RAN node may be an Evolved Node-B (eNB) arranged to operate in accordance with a Third Generation Partnership Protocol (3GPP) protocol or a Generation Node-B (gNB) arranged to operate in accordance with a new radio (NR) protocol.

[00198] In Example 11, the subject matter of one or any combination of

Examples 1-10, wherein the RAN node may be an access point (AP) arranged to operate in accordance with a wireless local area network (WLAN) protocol.

[00199] In Example 12, the subject matter of one or any combination of

Examples 1-11, wherein the apparatus may further include a transceiver to transmit the control signaling, to receive the group service report and to transmit the group service response.

[00200] In Example 13, the subject matter of one or any combination of

Examples 1-12, wherein the processing circuitry may include a baseband processor to determine whether to switch the mobile device from the uni-cast mode to the group-cast mode for the GBS.

[00201] In Example 14, a computer-readable storage medium may store instructions for execution by one or more processors to perform operations for communication by a mobile device. The operations may configure the one or more processors to decode a packet received from a source radio access network

(RAN) node in a group-cast mode as part of a group based service (GBS). The packet may include a first GBS identifier (GBS-ID) reserved to indicate packets from the source RAN node for the GBS in the group-cast mode. The operations may further configure the one or more processors to decode a handover command message from the source RAN node that includes a second GBS-ID reserved to indicate packets to a target RAN node for the GBS in the group-cast mode. The handover command message may further include the first GBS-ID. The operations may further configure the one or more processors to encode, for transmission to the target RAN node, a handover request message that indicates a request for a handover to the target RAN node. The handover request message may include the second GBS-ID. The operations may further configure the one or more processors to decode a handover response message from the target RAN that indicates whether the request for the handover is accepted. The operations may further configure the one or more processors to, if the handover is accepted, decode a packet received from the target RAN node in the group-cast mode as part of the GBS.

[00202] In Example 15, the subject matter of Example 14, wherein the handover response message may include a third GBS-ID.

[00203] In Example 16, the subject matter of one or any combination of

Examples 14-15, wherein the operations may further configure the one or more processors to encode, for transmission to the source RAN node, a handover complete message that indicates: that the handover to the target RAN node has been performed, a device ID of the mobile device, and the third GBS-ID.

[00204] In Example 17, an apparatus of a radio access network (RAN) node may comprise memory. The apparatus may further comprise processing circuitry. The processing circuitry may be configured to decode a monitoring report request message from a service portal function (SPF) node or an application server. The monitoring report request message may indicate a request for usage information for a group based service (GBS). The usage information may include a number of mobile devices supported by the RAN node for the GBS. The processing circuitry may be further configured to determine the usage information. The processing circuitry may be further configured to encode, for transmission to the SPF node or the application server, a report message that includes the usage information. The processing circuitry may be further configured to decode control signaling from the SPF node or the application server. The control signaling may indicate whether the RAN node is to switch one or more mobile devices from a uni-cast mode to a group-cast mode for the GBS.

[00205] In Example 18, the subject matter of Example 17, wherein the processing circuitry may be further configured to, if the control signaling from the SPF node indicates that a plurality of mobile devices are to switch to the group-cast mode for the GBS: encode, for transmission to one of the mobile devices of the plurality, a paging message that indicates that the mobile device is to switch to the group-cast mode for the GBS. [00206] In Example 19, the subject matter of one or any combination of

Examples 17-18, wherein the processing circuitry may be further configured to, if the control signaling from the SPF node indicates that a plurality of mobile devices are to switch to the group-cast mode for the GBS: encode, for broadcast transmission, a broadcast control message that indicates that the mobile devices of the plurality are to switch to the group-cast mode for the GBS.

[00207] In Example 20, the subject matter of one or any combination of

Examples 17-19, wherein the processing circuitry may be further configured to, if the control signaling from the SPF node indicates that a plurality of mobile devices are to switch to the group-cast mode for the GBS: encode a packet for transmission to the plurality of mobile devices on a channel allocated for transmission of packets for the GBS for the group-cast mode.

[00208] In Example 21, the subject matter of one or any combination of

Examples 17-20, wherein the usage information may further include maximum transmission rates of mobile devices that operate in the uni-cast mode for the GBS.

[00209] In Example 22, an apparatus of a service portal function (SPF) node may comprise memory. The apparatus may further comprise processing circuitry. The processing circuitry may be configured to encode, for transmission to a radio access network (RAN) node, a monitoring report request message that indicates a request for usage information for a group based service (GBS) supported by the RAN node. The usage information may include a number of mobile devices supported by the RAN node for the GBS or maximum transmission rates of the mobile devices for the GBS. The processing circuitry may be further configured to decode a report message from the RAN node that includes the usage information. The processing circuitry may be further configured to determine, based on the usage information, whether to initiate a request for the RAN to operate in a group-cast mode for the GBS. The group- cast mode may be based on per-packet transmissions to multiple mobile devices. The processing circuitry may be further configured to, if it is determined that the request for the RAN node to operate in the group-cast mode for the GBS is to be performed, encode a GBS service request for transmission to an application server that supports the GBS. [00210] In Example 23, the subject matter of Example 22, wherein the processing circuitry may be further configured to decode a GBS service response message from the application server that indicates whether the RAN node is to operate in the group-cast mode for the GBS. The processing circuitry may be further configured to encode, for transmission to the RAN node, control signaling that indicates that the RAN node is to operate in the group-cast mode for the GBS.

[00211] In Example 24, the subject matter of one or any combination of

Examples 22-23, wherein the processing circuitry may be further configured to determine to initiate the request for the RAN node to operate in the group-cast mode for the GBS if the number of mobile devices supported by the RAN node for the GBS is greater than a predetermined threshold.

[00212] In Example 25, the subject matter of one or any combination of

Examples 22-24, wherein the processing circuitry may be further configured to determine to initiate the request for the RAN node to operate in the group-cast mode for the GBS if the maximum transmission rates of the mobile devices for the GBS are greater than a predetermined threshold.

[00213] In Example 26, an apparatus of a service portal function (SPF) node may comprise memory. The apparatus may further comprise processing circuitry. The processing circuitry may be configured to determine a session management policy for a group based service (GBS). The processing circuitry may be further configured to allocate a temporary identifier (ID) for the GBS. The processing circuitry may be further configured to decode a service request message for the GBS received from an application server. The processing circuitry may be further configured to encode, for transmission to a core network control plane function (CN-CPF) node, a control message that includes the temporary ID for the GBS and one or more parameters of the session management policy.

[00214] In Example 27, the subject matter of Example 26, wherein the service request message for the GBS may include a service profile that includes one or more of: a traffic load of the GBS, a latency of the GBS, a transmission rate for the GBS, and a number of devices in a group configured for the GBS. [00215] In Example 28, the subject matter of one or any combination of

Examples 26-27, wherein the session management policy may include one or more of: a multi-cast capability of the SPF node and a service profile. The service profile may include one or more of: a traffic load of the GBS, a latency of the GBS, a transmission rate for the GBS, and a number of devices in a group configured for the GBS.

[00216] In Example 29, the subject matter of one or any combination of

Examples 26-28, wherein the control message may further include one or more of: a service area ID (SAI) of the GBS, a mapped SAI received from the application server, and a mapped SAI determined by SPF node.

[00217] In Example 30, the subject matter of one or any combination of

Examples 26-29, wherein the control message is a first control message. The processing circuitry may be further configured to decode, from a subscription repository, a second control message that indicates one or more of: a group service policy of the GBS based on a service subscription, and subscribed service area information of the GBS that indicates a geographical area or a service area ID (SAI).

[00218] In Example 31, an apparatus of a mobile device may comprise means for decoding a packet received from a source radio access network (RAN) node in a group-cast mode as part of a group based service (GBS). The packet may include a first GBS identifier (GBS-ID) reserved to indicate packets from the source RAN node for the GBS in the group-cast mode. The apparatus may further comprise means for decoding a handover command message from the source RAN node that includes a second GBS-ID reserved to indicate packets to a target RAN node for the GBS in the group-cast mode, wherein the handover command message further includes the first GBS-ID. The apparatus may further comprise means for encoding, for transmission to the target RAN node, a handover request message that indicates a request for a handover to the target RAN node. The handover request message may include the second GBS-ID. The apparatus may further comprise means for decoding a handover response message from the target RAN that indicates whether the request for the handover is accepted. The apparatus may further comprise means for, if the handover is accepted, decoding a packet received from the target RAN node in the group- cast mode as part of the GBS.

[00219] In Example 32, the subject matter of Example 31, wherein the handover response message may include a third GBS-ID.

[00220] In Example 33, the subject matter of one or any combination of

Examples 31-32, wherein the apparatus may further comprise means for encoding, for transmission to the source RAN node, a handover complete message that indicates: that the handover to the target RAN node has been performed, a device ID of the mobile device, and the third GBS-ID.

[00221] The Abstract is provided to comply with 37 C.F.R. Section

1.72(b) requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims

What is claimed is: 1. An apparatus of a radio access network (RAN) node, the apparatus comprising: memory; and processing circuitry, configured to:

encode, for transmission, control signaling that indicates a request for a quality of service (QoS) measurement from a mobile device for a group based service (GBS);

decode a group service report from the mobile device that includes the

QoS measurement;

store the QoS measurement in the memory;

determine, based at least partly on the QoS measurement, whether to switch the mobile device from a uni-cast mode to a group-cast mode for the GBS; and

encode, for transmission, a group service response that indicates:

whether the mobile device is to switch from the uni-cast mode to the group-cast mode for the GBS, and

if it is determined that the mobile device is to switch from the uni-cast mode to the group-cast mode, a channel allocated for transmission of packets for the GBS for the group-cast mode.

2. The apparatus according to claim 1, wherein:

the uni-cast mode is based on per-packet transmissions per mobile device as part of the GBS, and

the group-cast mode is based on per-packet transmissions to multiple mobile devices as part of the GBS.

3. The apparatus according to claim 1, wherein:

the QoS measurement is a signal quality measurement or a packet error rate, and the processing circuitry is further configured to determine that the mobile device is to switch from the uni-cast mode to the group-cast mode for the GBS if:

the signal quality measurement is above a first predetermined threshold, or

the packet error rate is below a second predetermined threshold.

4. The apparatus according to claim 1, the processing circuitry further configured to:

decode, from the mobile device, a group service request that indicates whether the mobile device supports operation in the group-cast mode for the GBS.

5. The apparatus according to any of claims 1-4, wherein the control signaling indicates a maximum time delay for transmission of the group service request by the mobile device.

6. The apparatus according to claim 1, wherein the control signaling includes a broadcast message.

7. The apparatus according to claim 1, wherein the control signaling indicates one or more of:

a group based service identifier (GBS-ID) of the GBS,

a report type parameter that indicates whether the mobile device is to transmit an aperiodic group service report or periodic group service reports, and a report time parameter that indicates:

a report time if the report type parameter indicates that the mobile device is transmit an aperiodic group service report, or

a report period if the report type parameter indicates that the mobile device is transmit periodic group service reports.

8. The apparatus according to any of claims 1, 6, and 7, wherein: the RAN node is arranged to operate in a software defined network (SDN) that supports an application server,

the RAN node further comprises an interface,

the interface is configurable to receive packets from a core network component that operates as a relay to forward core plane messages and user plane messages from the application server to the RAN node.

9. The apparatus according to claim 1, the processing circuitry further configured to:

determine, based at least partly on the QoS measurement, whether to switch the mobile device from the group-cast mode to the uni-cast mode for the GBS.

10. The apparatus according to claim 1 or 9, wherein the RAN node is an Evolved Node-B (eNB) arranged to operate in accordance with a Third

Generation Partnership Protocol (3GPP) protocol or a Generation Node-B (gNB) arranged to operate in accordance with a new radio (NR) protocol.

11. The apparatus according to claim 1, wherein the RAN node is an access point (AP) arranged to operate in accordance with a wireless local area network (WLAN) protocol.

12. The apparatus according to claim 1, wherein the apparatus further includes a transceiver to transmit the control signaling, to receive the group service report and to transmit the group service response.

13. The apparatus according to claim 1, wherein the processing circuitry includes a baseband processor to determine whether to switch the mobile device from the uni-cast mode to the group-cast mode for the GBS.

14. A computer-readable storage medium that stores instructions for execution by one or more processors to perform operations for communication by a mobile device, the operations to configure the one or more processors to: decode a packet received from a source radio access network (RAN) node in a group-cast mode as part of a group based service (GBS), wherein the packet includes a first GBS identifier (GBS-ID) reserved to indicate packets from the source RAN node for the GBS in the group-cast mode;

decode a handover command message from the source RAN node that includes a second GBS-ID reserved to indicate packets to a target RAN node for the GBS in the group-cast mode, wherein the handover command message further includes the first GBS-ID;

encode, for transmission to the target RAN node, a handover request message that indicates a request for a handover to the target RAN node, wherein the handover request message includes the second GBS-ID;

decode a handover response message from the target RAN that indicates whether the request for the handover is accepted; and

if the handover is accepted, decode a packet received from the target RAN node in the group-cast mode as part of the GBS.

15. The computer-readable storage medium according to claim 14, wherein the handover response message includes a third GBS-ID.

16. The computer-readable storage medium according to claim 15, the operations to configure the one or more processors to encode, for transmission to the source RAN node, a handover complete message that indicates:

that the handover to the target RAN node has been performed, a device ID of the mobile device, and

the third GBS-ID.

17. An apparatus of a radio access network (RAN) node, the apparatus comprising: memory; and processing circuitry, configured to:

decode a monitoring report request message from a service portal function (SPF) node or an application server, wherein the monitoring report request message indicates a request for usage information for a group based service (GBS), wherein the usage information includes a number of mobile devices supported by the RAN node for the GBS; determine the usage information;

encode, for transmission to the SPF node or the application server, a report message that includes the usage information; and

decode control signaling from the SPF node or the application server, wherein the control signaling indicates whether the RAN node is to switch one or more mobile devices from a uni-cast mode to a group-cast mode for the GBS.

18. The apparatus according to claim 17, the processing circuitry further configured to:

if the control signaling from the SPF node indicates that a plurality of mobile devices are to switch to the group-cast mode for the GBS:

encode, for transmission to one of the mobile devices of the plurality, a paging message that indicates that the mobile device is to switch to the group-cast mode for the GBS.

19. The apparatus according to claim 17, the processing circuitry further configured to:

encode, for broadcast transmission, a broadcast control message that indicates that the mobile devices of the plurality are to switch to the group- cast mode for the GBS.

20. The apparatus according to claim 17, the processing circuitry further configured to:

if the control signaling from the SPF node indicates that a plurality of mobile devices are to switch to the group-cast mode for the GBS, encode a packet for transmission to the plurality of mobile devices on a channel allocated for transmission of packets for the GBS for the group-cast mode.

21. The apparatus according to any of claims 17-20, wherein the usage information further includes maximum transmission rates of mobile devices that operate in the uni-cast mode for the GBS.

22. An apparatus of a service portal function (SPF) node, the apparatus comprising: memory; and processing circuitry, configured to:

encode, for transmission to a radio access network (RAN) node, a monitoring report request message that indicates a request for usage information for a group based service (GBS) supported by the RAN node,

wherein the usage information includes a number of mobile devices supported by the RAN node for the GBS or maximum transmission rates of the mobile devices for the GBS;

decode a report message from the RAN node that includes the usage information;

determine, based on the usage information, whether to initiate a request for the RAN to operate in a group-cast mode for the GBS, wherein the group- cast mode is based on per-packet transmissions to multiple mobile devices; and if it is determined that the request for the RAN node to operate in the group-cast mode for the GBS is to be performed, encode a GBS service request for transmission to an application server that supports the GBS.

23. The apparatus according to claim 22, the processing circuitry further configured to:

decode a GBS service response message from the application server that indicates whether the RAN node is to operate in the group-cast mode for the GBS; and

encode, for transmission to the RAN node, control signaling that indicates that the RAN node is to operate in the group-cast mode for the GBS.

24. The apparatus according to claim 22, the processing circuitry further configured to:

determine to initiate the request for the RAN node to operate in the group-cast mode for the GBS if the number of mobile devices supported by the RAN node for the GBS is greater than a predetermined threshold.

25. The apparatus according to claim 22, the processing circuitry further configured to:

determine to initiate the request for the RAN node to operate in the group-cast mode for the GBS if the maximum transmission rates of the mobile devices for the GBS are greater than a predetermined threshold.

26. An apparatus of a service portal function (SPF) node, the apparatus comprising: memory; and processing circuitry, configured to:

determine a session management policy for a group based service (GBS); allocate a temporary identifier (ID) for the GBS;

decode a service request message for the GBS received from an application server; and

encode, for transmission to a core network control plane function (CN- CPF) node, a control message that includes the temporary ID for the GBS and one or more parameters of the session management policy.

27. The apparatus according to claim 26, wherein the service request message for the GBS includes a service profile that includes one or more of: a traffic load of the GBS, a latency of the GBS, a transmission rate for the GBS, and a number of devices in a group configured for the GBS.

28. The apparatus according to claim 26, wherein the session

management policy includes one or more of:

a multi-cast capability of the SPF node, and

a service profile that includes one or more of: a traffic load of the GBS, a latency of the GBS, a transmission rate for the GBS, and a number of devices in a group configured for the GBS.

29. The apparatus according to claim 26, wherein the control message further includes one or more of:

a service area ID (SAI) of the GBS,

a mapped SAI received from the application server, and

a mapped SAI determined by SPF node.

30. The apparatus according to claim 26, wherein:

the control message is a first control message,

the processing circuitry is further configured to decode, from a subscription repository, a second control message that indicates one or more of:

a group service policy of the GBS based on a service subscription, and

subscribed service area information of the GBS that indicates a geographical area or a service area ID (SAI).