CN117296344A - Wireless communication method, user equipment and transmitting equipment - Google Patents

Abstract

A wireless communication method executable in a User Equipment (UE), the method comprising: receiving a group notification from a network, wherein the group notification is configured to instruct a UE to enter a Radio Resource Control (RRC) connected state; initiating an RRC connection with the network to enter an RRC connected state; a Multicast and Broadcast Service (MBS) session of delivery mode 1 (DM 1) is received in an RRC connected state.

Description

Wireless communication method, user equipment and transmitting equipment

Technical Field

The present application relates to the field of communication systems, and more particularly, to a wireless communication method, a user equipment, and a transmitting device.

Background

Wireless communication systems and networks have evolved towards broadband and mobile systems. In cellular wireless communication systems, user Equipment (UE) is connected to a Radio Access Network (RAN) via a radio link. The RAN includes a set of Base Stations (BSs) that provide radio links for UEs in a cell covered by the base stations and an interface to a Core Network (CN), which provides overall network control. It can be seen that both the RAN and CN perform functions related to the overall network. The third generation partnership project (3 GPP) has developed a so-called Long Term Evolution (LTE) system for an evolved universal mobile telecommunications system universal radio access network (E-UTRAN) in which one or more macro cells are supported by a base station called eNodeB or eNB (evolved NodeB). Recently, LTE is evolving further towards so-called 5G or NR (new radio) systems, in which one or more cells are supported by a base station called a gNB.

At the RAN #86 conference, new work items are approved for supporting NR multicast and broadcast. According to the related discussion of SA2 on 5G Multicast and Broadcast Services (MBS), there are two delivery methods for transmitting MBS packet streams over the air. One approach is the point-to-multipoint (PTM) transmission method, i.e., a RAN node transmits a single MBS packet over the air to a group of UEs. Another approach is the point-to-point (PTP) transmission method, i.e. the RAN node transmits a single MBS data packet over the radio to a single UE.

RAN2 operates in two MBS transport modes (DM 1 and DM 2). DM1 is used for multicast session transmission and is suitable for UEs in a Radio Resource Control (RRC) connected state. MBS configuration is provided for the UE. DM1 may use PTP and PTM transmissions and may take advantage of Uplink (UL) UE feedback (e.g., hybrid automatic repeat request (HARQ)) when the UE is in RRC connected state. DM2 is used for broadcast session delivery and is applicable to UEs in all RRC states.

Technical problem

Although DM1 and DM2 are introduced for multicast session delivery and broadcast session delivery, no configuration and notification in DM1 and DM2 for MBS service delivery is proposed.

Technical proposal

The purpose of the application is to provide a wireless communication method, user equipment and transmitting equipment.

A first aspect of the present application provides a wireless communication method executable in a User Equipment (UE), the method comprising: receiving a group notification from a network, wherein the group notification is configured to instruct the UE to enter a Radio Resource Control (RRC) connected state; initiating an RRC connection with the network to enter an RRC connection state; multicast and broadcast service MBS sessions of delivery mode 1 (DM 1) are received in the RRC connected state.

A second aspect of the present application provides a wireless communication method executable in a User Equipment (UE), the method comprising: receiving a Multicast and Broadcast Service (MBS) session of delivery mode 2 (DM 2) from a network; and receiving an indication from the network, wherein the indication is configured to indicate the MBS session start, stop or modification of DM 2.

A third aspect of the present application provides a wireless communication method executable in a transmitting apparatus, the method comprising: transmitting a group notification to a User Equipment (UE), wherein the group notification is configured to instruct the UE to enter a Radio Resource Control (RRC) connected state; and transmitting a Multicast and Broadcast Service (MBS) session of a delivery mode 1 (DM 1) to the UE in the RRC connected state.

A fourth aspect of the present application provides a wireless communication method executable in a transmitting device, the method comprising: transmitting a Multicast and Broadcast Service (MBS) session of a delivery mode 2 (DM 2) to a User Equipment (UE); and transmitting an indication to the UE, wherein the indication is configured to indicate the MBS session start, stop or modification of the DM 2.

A fifth aspect of the present application provides a user equipment, the user equipment comprising: a transceiver; and a processor coupled to the transceiver and configured to perform steps comprising: receiving a group notification from a network, wherein the group notification is configured to instruct the UE to enter a Radio Resource Control (RRC) connected state; initiating an RRC connection with the network to enter an RRC connection state; multicast and broadcast service MBS sessions of delivery mode 1 (DM 1) are received in the RRC connected state.

A sixth aspect of the present application provides a user equipment, the user equipment comprising: a transceiver; and a processor coupled to the transceiver and configured to perform steps comprising: receiving a Multicast and Broadcast Service (MBS) session of delivery mode 2 (DM 2) from a network; and receiving an indication from the network, wherein the indication is configured to indicate the MBS session start, stop or modification of DM 2.

A seventh aspect of the present application provides a base station, the base station comprising: a transceiver; and a processor coupled to the transceiver and configured to perform steps comprising: transmitting a group notification to a User Equipment (UE), wherein the group notification is configured to instruct the UE to enter a Radio Resource Control (RRC) connected state; and transmitting a Multicast and Broadcast Service (MBS) session of a delivery mode 1 (DM 1) in the RRC connected state.

An eighth aspect of the present application provides a base station, the base station comprising: a transceiver; and a processor coupled to the transceiver and configured to perform steps comprising: transmitting a Multicast and Broadcast Service (MBS) session of a delivery mode 2 (DM 2) to a User Equipment (UE); and transmitting an indication to the UE, wherein the indication is configured to indicate the MBS session start, stop or modification of the DM 2.

The disclosed methods may be implemented in a chip. The chip may include a processor configured to invoke and run a computer program stored in a memory to cause a device on which the chip is installed to perform the disclosed methods.

The disclosed methods may be programmed as computer-executable instructions stored in a non-transitory computer-readable medium. The non-transitory computer readable medium, when loaded into a computer, directs the processor of the computer to perform the disclosed methods.

The non-transitory computer readable medium may include at least one of the group consisting of: hard disks, CD-ROMs, optical storage devices, magnetic storage devices, read-only memory, programmable read-only memory, erasable programmable read-only memory, EPROM, electrically erasable programmable read-only memory, and flash memory.

The disclosed methods may be programmed as a computer program product that causes a computer to perform the disclosed methods.

The disclosed methods may be programmed as a computer program that causes a computer to perform the disclosed methods.

Advantageous effects

Embodiments of the present application provide configuration and notification for MBS service delivery in DM1 and DM 2. In detail, the embodiments of the present application provide reception of the MBS session of DM1 and reception of the MBS session of DM2 in RRC idle state, RRC inactive state and connected state.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the related art, the drawings described in the embodiments will be briefly described below. It is evident that the figures are only some embodiments of the invention, from which a person skilled in the art can obtain other figures without the need for inventive effort.

Fig. 1 is a schematic diagram illustrating a telecommunications system.

Fig. 2 is a schematic diagram showing a CRAN with a baseband unit pool, a remote radio head, and a UE.

Fig. 3 is a schematic diagram illustrating a wireless communication method that may be performed in a user equipment according to an embodiment of the present application.

Fig. 4 is a schematic diagram illustrating a flow chart of group CN paging when a UE is in an RRC idle state according to an embodiment of the present application.

Fig. 5 is a schematic diagram illustrating a flow chart of group CN paging when a UE is in an RRC inactive state according to an embodiment of the present application.

Fig. 6 is a schematic diagram illustrating a flow chart of group RAN paging when a UE is in an RRC inactive state according to an embodiment of the present application.

Fig. 7 is a schematic diagram illustrating a flow chart of group MCCH notification when a UE is in an RRC idle state according to an embodiment of the present application.

Fig. 8 is a schematic diagram illustrating a flowchart of group MCCH notification when a UE is in an RRC inactive state according to an embodiment of the present application.

Fig. 9 is a schematic diagram illustrating a flow chart of group MCCH notification when a UE is in an RRC inactive state according to another embodiment of the present application.

Fig. 10 is a diagram illustrating a configuration in which a UE monitors at least one G-RNTI interested in at least one corresponding MBS session of DM1 to receive RRC dedicated signaling and an MBS session of DM1 in an RRC connected state.

Fig. 11 is a schematic diagram showing a flowchart of starting/stopping/modifying an MBS session of DM1 when a UE is in an RRC connected state according to an embodiment of the present application.

Fig. 12 is a schematic diagram showing a flowchart of start/stop/modification of at least one MBS session of DM1 when a UE is in an RRC connected state according to another embodiment of the present application.

Fig. 13 is a schematic diagram showing a flowchart of start/stop/modification of at least one MBS session of DM1 when a UE is in an RRC connected state according to still another embodiment of the present application.

Fig. 14 is a schematic diagram showing a flowchart of start/stop/modification of at least one MBS session of DM1 when a UE is in an RRC connected state according to still another embodiment of the present application.

Fig. 15 is a schematic diagram illustrating a wireless communication method that may be performed in a user equipment according to an embodiment of the present application.

Fig. 16 is a schematic diagram illustrating a flowchart of stopping/modifying at least one MBS session of DM2 when a UE is in an RRC idle state or an RRC inactive state according to an embodiment of the present application.

Fig. 17 is a schematic diagram showing a flowchart of start/stop/modification of at least one MBS session of DM2 when a UE is in an RRC connected state according to another embodiment of the present application.

Fig. 18 is a schematic diagram showing a flowchart of start/stop/modification of at least one MBS session of DM2 when a UE is in an RRC connected state according to still another embodiment of the present application.

Fig. 19 is a schematic diagram showing a flowchart of start/stop/modification of at least one MBS session of DM2 when a UE is in an RRC connected state according to still another embodiment of the present application.

Fig. 20 is a schematic diagram showing a flowchart of starting/stopping/modifying an MBS session of DM2 when a UE is in an RRC connected state according to an embodiment of the present application.

Fig. 21 is a schematic diagram illustrating a wireless communication method that can be performed in a transmitting apparatus according to an embodiment of the present application.

Fig. 22 is a schematic diagram illustrating a wireless communication method that may be performed in a User Equipment (UE) according to an embodiment of the present application.

Fig. 23 is a block diagram of a system for wireless communication according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be described in detail with reference to the following drawings, technical main body, structural features, achieved objects and effects. In particular, the terminology in the embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.

Referring to fig. 1, a telecommunication system including a group 100a having a plurality of UEs, a Base Station (BS) 200a and a network entity apparatus 300 performs a disclosed method according to an embodiment of the present application. The group of multiple UEs 100a may include UE 10a, UE 10b, and other UEs. Fig. 1 is shown for illustration and not limitation, and a system may include more UE, BS, and CN entities. The connections between the devices and the device components are shown as lines and arrows. The connection between the devices may be achieved by a wireless connection. The connections between the device components may be made through wires, buses, traces, cables or optical fibers. The UE 10a may include a processor 11a, a memory 12a, and a transceiver 13a. The UE 10b may include a processor 11b, a memory 12b, and a transceiver 13b. The base station 200a may include a baseband unit (BBU) 204a. The baseband unit 204a may include a processor 201a, a memory 202a, and a transceiver 203a. The network entity device 300 may include a processor 301, a memory 302, and a transceiver 303. Each of the processors 11a, 11b, 201a, and 301 may be configured to implement the proposed functions, processes, and/or methods described in the specification. Layers of the radio interface protocol may be implemented in the processors 11a, 11b, 201a and 301. Each of the memories 12a, 12b, 202a and 302 is operable to store various programs and information for operating the connected processors. Each of the transceivers 13a, 13b, 203a, and 303 is operatively coupled to, transmits, and/or receives wireless signals or wired signals with a connected processor. UE 10a may communicate with UE 10b via a side link. The base station 200a may be one of an eNB, a gNB, or other type of radio node.

Each of the processors 11a, 11b, 201a, and 301 may include a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), other chipset, logic circuit, and/or data processing device. Each of the memories 12a, 12b, 202a, and 302 may include Read Only Memory (ROM), random Access Memory (RAM), flash memory, memory cards, storage media, and/or other storage devices. Each of the transceivers 13a, 13b, 203a, and 303 may include baseband circuitry and Radio Frequency (RF) circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein may be implemented with modules, units, processes, functions, entities, etc. that perform the functions described herein. The modules may be stored in memory and executed by a processor. The memory may be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.

The network entity device 300 may be a node in the CN. The CN may include an LTE CN or a 5G core (5 GC), the 5GC including a User Plane Function (UPF), a Session Management Function (SMF), a mobility management function (AMF), a Unified Data Management (UDM), a Policy Control Function (PCF), a Control Plane (CP)/User Plane (UP) split (cup), an authentication server (AUSF), a Network Slice Selection Function (NSSF), and a network opening function (NEF).

Referring to fig. 2, a base station 200b is an embodiment of a base station 200a and includes a Central Controller (CC) 210, access points 211-1, 211-2, … …, and 211-M. M is a positive integer. The central controller 210 may be implemented as a Central Unit (CU) and may include BBUs (such as BBU 204 a) associated with Access Points (APs) 211-1, 211-2, … …, and 211-M. Each access point 211-1, 211-2, … …, and 211-M may be implemented as a wireless node and the Remote Unit (RU) or remote radio head (Remote Radio Head, RRH) may include a transmit-receive point (TRP). The access points 211-1, 211-2, … …, and 211-M may be located in different locations.

The central controller 210 receives wireless signals from the group 100b having V User Equipments (UEs) through the group of M distributed radio nodes. V is a positive integer. The group of V user equipments includes UE 10-1, UE 10-2, UE 10-3, … … and UE 10-V. The UE 10-1, UE 10-2, UE 10-3, … …, and UE 10-V may be located in different locations.

The technical problem considered belongs to the field of high-density connections and non-orthogonal multiple access (NOMA) in CRAN systems. In an example, the CRAN network operates in a Time Division Duplex (TDD) mode in which channel estimation is performed through uplink pilot transmission.

Each coherent time slot is divided between two instances of uplink training using orthogonal uplink pilots, uplink data transmissions, and downlink data transmissions. Embodiments of the present application handle uplinks from V UEs to M single antenna Access Points (APs). At each slot, each AP independently performs uplink channel estimation.

The APs 211-1, 211-2, … …, and 211-M are distributed within the coverage area and managed by a central controller 210, which central controller 210 contains a centralized Base Band Unit (BBU) pool and handles operations of the physical layer and Medium Access Control (MAC) layers such as data decoding and encoding, scheduling, and power allocation. The AP 211-1, the AP 211-2, … …, and the AP 211-M are linked to the central controller 210 through a high-performance transmission link called a front-end (frontau). The forwarding may be accomplished through an optical cable or a high bandwidth wireless channel. The system in FIG. 2 includes base station 200b and UE 10-1, UE 10-2, UE 10-3, … … and UE 10-V. UE 10-1, UE 10-2, UE 10-3, … …, and UE 10-V are simplified examples of CRANs. The APs 211-1, 211-2, … … and 211-M perform channel estimation and link-level transmission chains until equalized. The central controller 210 performs signal decoding, signal encoding, signal modulation, signal demodulation, signal scheduling, and MAC layer operations.

The Uplink (UL) transmission of control signals or data may be a transmission operation from the UE to the base station. The Downlink (DL) transmission of the control signal or data may be a transmission operation from the base station to the UE.

Referring to fig. 3, fig. 3 is a schematic diagram illustrating a wireless communication method that may be performed in a User Equipment (UE) according to an embodiment of the present application. The wireless communication method is used for receiving the MBS session of DM 1. DM1 is used for multicast session delivery. In this embodiment, the UE is in an RRC idle state or an RRC inactive state. Only when the UE is in the RRC connected state, the UE can receive the MBS session of DM 1.

In step S30, a group notification is received from the network, wherein the group notification is configured to instruct the UE to enter an RRC connected state.

The group notification is sent by the network to a group of UEs based on an MBS session Identifier (ID) or a 5G system architecture evolution-temporary mobile station identifier (5G-S-TMSI). The group notification is included in the RRC message.

In step S32, an RRC connection with the network is initiated to enter an RRC connected state.

When the UE is in an RRC idle state, the UE initiates an RRC connection setup to connect with the network in response to receiving the group notification. When the UE is in the RRC inactive state, the UE initiates an RRC connection recovery procedure to connect with the network in response to receiving the group notification. Optionally, when the UE is in an RRC inactive state, the UE enters an RRC idle state and then initiates an RRC connection setup procedure to connect with the network in response to receiving the group notification. Then, the UE enters an RRC connected state.

In step S34, the MBS session of DM1 is received in the RRC connected state.

After the UE enters a connected state, the MBS session of DM1 is received from the network.

The present application provides two methods for providing group notifications to UEs. One method is group paging and the other is group Multicast Control Channel (MCCH) notification.

In the group paging provided herein, a page is sent to a plurality of UEs, and the UE is one of the plurality of UEs.

In the group paging provided in the present application, a group notification identity (UE-identity) is newly established (added) in the paging message. The group announcement identity is configured as a group core network identity (CN ID) or a group radio access network identity (RAN ID) to allocate each MBS session of DM 1. When the UE receives the paging message including the group notification identifier, the UE may determine whether the UE belongs to the MBS session of DM1 through the group notification identifier.

The group paging includes a group Core Network (CN) paging and a group Radio Access Network (RAN) paging.

The group CN page of the present application is issued by the CN. The UE may recognize the correspondence of the Identity (ID) of DM1 and the MBS session via a non-access stratum (NAS). The UE may determine whether to enter the RRC connected state according to the CN ID. The UE monitors group CN paging via at least one of MBS session ID (e.g., temporary mobile group identity), 5G system architecture evolution-temporary mobile station identity (5G-S-TMSI), or UE receiving MBS session of DM 1.

The group RAN page of the present application is sent by the base station. The UE may determine whether to enter the RRC connected state according to the RAN ID. The UE monitors group RAN paging via at least one of an MBS session ID (e.g., temporary mobile group identity), a 5G full radio network temporary identity (5G-full-RNTI), or a UE receiving an MBS session of DM 1.

In the embodiments of the present application, group CN paging is required when the UE is in RRC idle state. Referring to fig. 4, fig. 4 is a schematic diagram illustrating a flow chart of group CN paging when a UE is in an RRC idle state according to an embodiment of the present application.

In step S40, the network, i.e., the next generation radio access network (NG-RAN), initiates a paging procedure at the beginning of the MBS session of DM 1.

In step S42, the UE monitors a paging radio network temporary identity (P-RNTI). In detail, the UE monitors a Physical Downlink Control Channel (PDCCH) scrambled by the P-RNTI to check whether a paging message is received. Upon receiving the paging message, the group CN page proceeds to step S44. When no paging message is received, the group CN paging ends.

In step S44, it is determined whether the group notification identity is a group CN ID and whether the UE is interested in the MBS session of DM 1. When it is determined that the group notification identification is the group CN ID and the UE is interested in the MBS session of DM1, the group CN paging proceeds to step S46. When it is determined that the group notification identity is not the group CN ID or that the UE is not interested in the MBS session of DM1, the UE ignores the paging message.

In step S46, the UE initiates an RRC connection setup procedure.

After the UE initiates the RRC connection setup procedure, the UE enters an RRC connection state.

In another embodiment of the present application, a group CN page or a group RAN page is required when the UE is in RRC inactive state. Referring to fig. 5, fig. 5 is a schematic diagram illustrating a flow chart of group CN paging when a UE is in an RRC inactive state according to an embodiment of the present application.

In step S50, the network (next generation radio access network (NG-RAN)) initiates a paging procedure at the beginning of the MBS session of DM 1.

In step S52, the UE monitors the P-RNTI. In detail, the UE monitors the PDCCH scrambled by the P-RNTI to check whether a paging message is received. Upon receiving the paging message, the group CN page proceeds to step S54. When no paging message is received, the group CN paging ends.

In step S54, it is determined whether the group notification identity is a group CN ID and whether the UE is interested in the MBS session of DM 1. When it is determined that the group notification identification is the group CN ID and the UE is interested in the MBS session of DM1, CN paging proceeds to step S56. When it is determined that the group notification identity is not the group CN ID or that the UE is not interested in the MBS session of DM1, the UE ignores the paging message.

In step S56, the UE enters an RRC idle state and initiates an RRC connection setup procedure.

After the UE initiates the RRC connection setup procedure, the UE enters an RRC connection state.

Referring to fig. 6, fig. 6 is a schematic diagram illustrating a flow chart of group RAN paging when a UE is in an RRC inactive state according to an embodiment of the present application.

In step S60, the network (next generation radio access network (NG-RAN)) initiates a paging procedure at the beginning of the MBS session of DM 1.

In step S62, the UE monitors the P-RNTI. In detail, the UE monitors the PDCCH scrambled by the P-RNTI to check whether a paging message is received. Upon receiving the paging message, the group RAN paging proceeds to step S64. When no paging message is received, the group RAN paging ends.

In step S64, it is determined whether the group notification identity is a group RAN ID and whether the UE is interested in the MBS session of DM 1. When it is determined that the group notification identification is the group RAN ID and the UE is interested in the MBS session of DM1, the group RAN paging proceeds to step S66. When it is determined that the group advertisement identification is not the group RANID or that the UE is not interested in the MBS session of DM1, the UE ignores the paging message.

In step S66, the UE initiates an RRC resume setup procedure.

After the UE initiates the RRC connection recovery procedure, the UE enters an RRC connected state.

Another method for providing group notification to UEs is group MCCH notification. The group MCCH notification is a newly defined RRC message provided by the present application.

The group MCCH notification provided by the present application is transmitted to the UE via the MCCH. In the group paging provided in the present application, a group notification identity (UE-identity) is newly established (added) in the group MCCH notification. The group announcement identity is configured as a group core network identity (CN ID) or a group radio access network identity (RAN ID) to allocate each MBS session of DM 1. When the UE receives the paging message including the group notification identifier, the UE may determine whether the MBS session of DM1 belongs to the UE through the group notification identifier.

For a UE in an RRC inactive state, when it is determined that the group notification identity is a group CN ID and the UE is interested in an MBS session of DM1, the UE initiates an RRC connection setup procedure. When the group notification identity is not the group CN ID or the MBS session of DM1 is not of interest to the UE, the UE ignores the paging message.

For a UE in an RRC inactive state, when the group notification identity is a group CN ID and the UE is interested in an MBS session of DM1, the UE enters an RRC idle state and initiates an RRC connection setup procedure.

For a UE in an RRC inactive state, when the group notification identity is a group RAN ID and the UE is interested in an MBS session of DM1, the UE enters an RRC idle state and initiates an RRC connection restoration procedure. When the group advertisement identification is not the group RANID or the UE is not interested in the MBS session of DM1, the UE ignores the paging message.

In addition, a new RNTI (hereinafter referred to as "MBS-RNTI") may be defined for the PDCCH of the schedule of the RRC message provided in the present application.

Referring to fig. 7, fig. 7 is a schematic diagram illustrating a flowchart of group MCCH notification when a UE is in an RRC idle state according to an embodiment of the present application.

In step S70, the network, i.e., the next generation radio access network (NG-RAN), transmits an RRC message including the group notification identity at the beginning of the MBS session of DM 1.

In step S72, the UE monitors MBS-RNTI and receives RRC message.

In step S74, it is determined whether the group notification identity is a group CN ID and whether the UE is interested in the MBS session of DM 1. When it is determined that the group notification identity is the group CN ID and the UE is interested in the MBS session of DM1, the group notification identity proceeds to step S76. When it is determined that the group notification identity is not the group CN ID or that the UE is not interested in the MBS session of DM1, the UE ignores the paging message.

In step S76, the UE initiates an RRC connection setup procedure.

After the UE initiates the RRC connection setup procedure, the UE enters an RRC connection state.

Referring to fig. 8, fig. 8 is a schematic diagram illustrating a flowchart of group MCCH notification when a UE is in an RRC inactive state according to an embodiment of the present application.

In step S80, the network (next generation radio access network (NG-RAN)) transmits an RRC message including a group notification identity at the beginning of the MBS session of DM 1.

In step S82, the UE monitors MBS-RNTI and receives RRC message.

In step S84, it is determined whether the group notification identity is a group CN ID and whether the UE is interested in the MBS session of DM 1. When it is determined that the group notification identity is the group CN ID and the UE is interested in the MBS session of DM1, the group notification identity proceeds to step S86. When it is determined that the group notification identity is not the group CN ID or that the UE is not interested in the MBS session of DM1, the UE ignores the paging message.

In step S86, the UE enters an RRC idle state and initiates an RRC connection setup procedure.

After the UE initiates the RRC connection setup procedure, the UE enters an RRC connection state.

Referring to fig. 9, fig. 9 is a schematic diagram illustrating a flowchart of group MCCH notification when a UE is in an RRC inactive state according to another embodiment of the present application.

In step S90, the network (next generation radio access network (NG-RAN)) transmits an RRC message including a group notification identity at the beginning of the MBS session of DM 1.

In step S92, the UE monitors MBS-RNTI and receives RRC message.

In step S94, it is determined whether the group notification identity is a group RAN ID and whether the UE is interested in the MBS session of DM 1. When it is determined that the group advertisement identification is the group RAN ID and the UE is interested in the MBS session of DM1, the group advertisement identification proceeds to step S96. When it is determined that the group advertisement identification is not the group RANID or that the UE is not interested in the MBS session of DM1, the UE ignores the paging message.

In step S96, the UE initiates an RRC connection recovery procedure.

After the UE initiates the RRC connection recovery procedure, the UE enters the RRC connected state from the RRC inactive state.

After the UE enters the RRC connected state, the UE may receive the MBS session of DM 1. In the present application, RRC dedicated signaling is used to send configuration of MBS session of DM1 to UE. A new RRC message may be defined by adding a configuration Information Element (IE) or a legacy RRC connection reconfiguration message may be reused.

The group-RNTI (G-RNTI) is used for the RRC message. The UE may acquire the corresponding MBS session of DM1 via MCCH or via Msg2 or Msg4 of a Random Access Channel (RACH) procedure. In addition, the mapping relationship between the G-RNTI and the MBS session of DM1 is a one-to-one relationship, a one-to-many relationship or a many-to-one relationship.

Referring to fig. 10, fig. 10 is a diagram illustrating a configuration in which a UE monitors at least one G-RNTI interested in at least one corresponding MBS session of DM1 in an RRC connected state to receive RRC dedicated signaling and an MBS session of DM 1.

In step S1000, the network transmits at least one G-RNTI and at least one corresponding MBS session of DM1 to the UE via MCCH or via Msg2 or Msg4 of a Random Access Channel (RACH) procedure.

In step S1002, the UE monitors PDCCH scrambled by at least one G-RNTI of at least one MBS session of DM1 of interest to the UE.

In step S1004, the network transmits a PDCCH for scheduling of at least one MBS session and/or at least one MCCH of DM1 scrambled by at least one G-RNTI.

In step S1006, the network transmits an RRC message to the UE.

Referring to fig. 11, fig. 11 is a schematic diagram illustrating a flowchart of starting/stopping/modifying an MBS session of DM1 when a UE is in an RRC connected state according to an embodiment of the present application.

In step S1100, the network transmits at least one G-RNTI and at least one corresponding MBS session of DM1 to the UE via MCCH or via Msg2 or Msg4 of a Random Access Channel (RACH) procedure.

In step S1102, the UE monitors PDCCH scrambled by at least one G-RNTI of at least one MBS session of DM1 of interest to the UE.

In step S1104, the network transmits a PDCCH for scheduling of at least one MCCH and/or at least one MBS session of DM1 scrambled by at least one G-RNTI.

In step S1106, the network transmits RRC signaling to the UE to instruct at least one MBS session start, stop or modification of DM 1. That is, the UE receives RRC signaling from the network.

Referring to fig. 12, fig. 12 is a schematic diagram showing a flowchart of start/stop/modification of at least one MBS session of DM1 when a UE is in an RRC connected state according to another embodiment of the present application.

In step S1200, the network transmits the configuration of at least one MBS session including DM1 and the MBS configuration of the MCCH modification period to the UE via a Broadcast Control Channel (BCCH) and the MCCH.

In step S1202, the UE starts receiving at least one MBS session of DM 1.

In step S1204, the UE reads the MCCH for each MCCH modification period.

In step S1206, the network transmits an indication to the UE via the MCCH to indicate at least one MBS session start, stop or modification of DM 1. That is, the UE receives an indication from the network.

Referring to fig. 13, fig. 13 is a schematic diagram showing a flowchart of start/stop/modification of at least one MBS session of DM1 when a UE is in an RRC connected state according to still another embodiment of the present application. In the present embodiment, a Downlink Control Information (DCI) format is newly defined and used for scheduling of MCCH. The DCI format includes start/stop/modify bits of at least one MBS session of DM 1.

In step S1300, the network transmits MBS configurations including configurations of at least one MBS session of DM1 to the UE via the MCCH.

In step S1302, the UE starts receiving at least one MBS session of DM 1.

In step S1304, the UE monitors MBS-RNTI for scheduling by MCCH.

In step S1306, at least one MBS session of DM1 starts, stops, or is modified.

In step S1308, the network informs the UE of the start/stop/modification of at least one MBS session of DM1 through a DCI format scrambled by the MBS-RNTI. That is, the UE receives DCI signaling from the network. The DCI format is configured to instruct MBS session start, stop or modification of DM 1.

In step S1310, the network transmits an indication to the UE to indicate at least one MBS session start, stop or modification of DM 1.

In the embodiment of fig. 13, the network informs the UE that start/stop/modification occurs in step S1308, and then the network transmits an indication to indicate which MBS session of DM1 starts/stops or modifies in step S1310. In another embodiment, the network sends a DCI format to the UE, the DCI format carrying information of which MBS session of DM2 to start, stop or modify. That is, the network may inform the UE of the occurrence of start/stop/modification and which MBS session of DM2 is started, stopped or modified via the DCI format.

Referring to fig. 14, fig. 14 is a schematic diagram showing a flowchart of start/stop/modification of at least one MBS session of DM1 when a UE is in an RRC connected state according to still another embodiment of the present application.

In step S1400, the network transmits to the UE via the BCCH and the MCCH the MBS configuration of the corresponding MBS session including at least one G-RNTI, DM1 and MBS-N-RNTI. The MBS-N-RNTI is used for scheduling of MCCH change notification.

In step S1402, the UE monitors PDCCH scrambled by MBS-N-RNTI.

In step S1404, the network transmits a scheduled PDCCH for MCCH change notification scrambled by MBS-N-RNTI to the UE.

In step S1406, the network transmits the updated MCCH configuration to the UE to instruct at least one MBS session of DM1 to start, stop or modify. That is, the UE receives an updated MCCH configuration from the network.

Alternatively, the UE may send a Multicast Interest Indication (MII) to the network to indicate which MBS session of DM1 the UE is interested in. MII may be supported in RRC idle/inactive state and RRC connected state. Alternatively, MII is not supported in the RRC idle/inactive state, and is supported in the RRC connected state. Optionally, MII is not supported in RRC idle/inactive state and in RRC connected state.

Referring to fig. 15, fig. 15 is a schematic diagram illustrating a wireless communication method that may be performed in a User Equipment (UE) according to an embodiment of the present application. The wireless communication method is used for receiving the MBS session of DM 2. DM2 is used for broadcast session delivery or any other delivery and is applicable to UEs in all RRC states. That is, the UE may receive the MBS session of DM2 when the UE is in an RRC idle state, an RRC inactive state, or an RRC connected state.

In step S150, a Multicast and Broadcast Service (MBS) session of DM2 is received.

In step S152, an indication is received from the network, wherein the indication is configured to indicate MBS session start, stop or modification of DM 2.

Referring to fig. 16, fig. 16 is a schematic diagram illustrating a flowchart of stopping/modifying at least one MBS session of DM2 when a UE is in an RRC idle state or an RRC inactive state according to an embodiment of the present application. In the present embodiment, a Downlink Control Information (DCI) format is newly defined and used for scheduling of MCCH. The DCI format includes start/stop/modify bits of at least one MBS session of DM 2.

In step S1600, the network transmits the MBS configuration including the configuration of at least one MBS session of DM2 to the UE via the MCCH.

In step S1602, the UE starts receiving at least one MBS session of DM 2.

In step S1604, the UE monitors MBS-RNTI to schedule MCCH.

In step S1606, at least one MBS session of DM2 starts, stops, or is modified.

In step S1608, the network informs the UE of the start/stop/modification of at least one MBS session of the DM2 through a DCI format scrambled by the MBS-RNTI.

In step S1610, the network transmits an indication to the UE via the MCCH to indicate which MBS session of DM2 is stopped or modified. That is, the UE receives the indication.

In the embodiment of fig. 16, the network informs the UE that the stop/modify occurs in step S1608, and then the network transmits an indication to indicate which MBS session of DM2 is stopped or modified in step S1610. In another embodiment, the network sends a DCI format to the UE, the DCI format carrying information of which MBS session of DM2 is stopped or modified. That is, the network may inform the UE of the occurrence of the stop/modification and which MBS session stop or modification of DM2 via the DCI format.

Referring to fig. 17, fig. 17 is a schematic diagram showing a flowchart of start/stop/modification of at least one MBS session of DM2 when a UE is in an RRC connected state according to another embodiment of the present application.

In step S1700, the network transmits MBS configurations including at least one MBS session of DM2 and configuration of an MCCH modification period to the UE via the MCCH.

In step S1702, the UE starts receiving at least one MBS session of DM 2.

In step S1704, the UE reads the MCCH for each MCCH modification period. Note that the MCCH content is only allowed to be modified at each MCCH modification period boundary.

In step S1706, the network transmits an indication to the UE via the MCCH to indicate at least one MBS session start, stop or modification of DM 2. That is, the UE receives the indication.

Referring to fig. 18, fig. 18 is a schematic diagram illustrating a flowchart of start/stop/modification of at least one MBS session of DM2 when a UE is in an RRC connected state according to an embodiment of the present application. In the present embodiment, a Downlink Control Information (DCI) format is newly defined and used for scheduling of MCCH. The DCI format includes start/stop/modify bits of at least one MBS session of DM 2.

In step S1800, the network transmits MBS configurations including configurations of at least one MBS session of DM2 to the UE via the MCCH.

In step S1802, the UE starts to receive at least one MBS session of DM 2.

In step S1804, the UE monitors MBS-RNTI to schedule MCCH.

In step S1806, at least one MBS session of DM1 starts, stops, or is modified.

In step S1808, the network informs the UE of the start/stop/modification of at least one MBS session of the DM2 through a DCI format scrambled by the MBS-RNTI.

In step S1810, the network transmits an indication to the UE via the MCCH to indicate one MBS session start, stop or modification of DM 1.

In the embodiment of fig. 18, the network informs the UE that start/stop/modification occurs in step S1808, and then the network transmits an indication to indicate which MBS session of DM2 is started, stopped or modified in step S1810. In another embodiment, the network sends a DCI format to the UE, the DCI format carrying information of which MBS session of DM2 to start, stop or modify. That is, the network may inform the UE of the occurrence of start/stop/modification and which MBS session of DM2 is started, stopped or modified via the DCI format.

Referring to fig. 19, fig. 19 is a schematic diagram showing a flowchart of start/stop/modification of at least one MBS session of DM2 when a UE is in an RRC connected state according to still another embodiment of the present application.

In step S1900, the network transmits to the UE, via the BCCH and the MCCH, MBS configuration including at least one G-RNTI, a corresponding MBS session of DM2, and MBS-N-RNTI. The MBS-N-RNTI is used for scheduling of MCCH change notification.

In step S1902, the UE monitors PDCCH scrambled by MBS-N-RNTI.

In step S1904, the network transmits a scheduled PDCCH for MCCH change notification scrambled by the MBS-N-RNTI to the UE.

The network transmits the updated MCCH configuration to the UE to instruct at least one MBS session start, stop or modification of DM2 at step S1906.

Referring to fig. 20, fig. 20 is a schematic diagram showing a flowchart of starting/stopping/modifying an MBS session of DM2 when a UE is in an RRC connected state according to an embodiment of the present application.

In step S2000, the network transmits MBS configuration of the corresponding MBS session including at least one G-RNTI and DM2 to the UE via the BCCH and MCCH.

In step S2002, the UE monitors PDCCH scrambled by at least one G-RNTI of at least one MBS session of DM2 of interest to the UE.

In step S2004, the network transmits a PDCCH for scheduling of at least one MBS session and/or at least one MCCH of DM1 scrambled by at least one G-RNTI.

In step S2006, the network transmits RRC signaling to the UE to instruct at least one MBS session start, stop or modification of DM 1.

Referring to fig. 21, fig. 21 is a schematic diagram illustrating a wireless communication method that can be performed in a transmitting apparatus according to an embodiment of the present application.

In step S210, a group notification is sent to a User Equipment (UE), wherein the group notification is configured to instruct the UE to enter a Radio Resource Control (RRC) connected state.

In step S212, a Multicast and Broadcast Service (MBS) session of the delivery mode 1 (DM 1) is transmitted to the UE in the RRC connected state.

Referring to fig. 22, fig. 22 is a schematic diagram illustrating a wireless communication method executable in a User Equipment (UE) according to an embodiment of the present application.

In step S220, a Multicast and Broadcast Service (MBS) session of delivery mode 2 (DM 2) is transmitted to a User Equipment (UE).

In step S222, an indication is transmitted to the UE, wherein the indication is configured to indicate MBS session start, stop or modification of DM 2.

Embodiments of the present application provide configuration and notification for MBS service delivery in DM1 and DM 2. In detail, the embodiments of the present application provide for reception of MBS sessions of DM1 and reception of MBS sessions of DM2 in RRC idle state, RRC inactive state and connected state.

Note that the transmitting device of the present application may be a core network or a base station.

Fig. 23 is a block diagram of a system 700 for wireless communication according to an embodiment of the present application. The embodiments described herein may be implemented into a system using any suitably configured hardware and/or software. Fig. 23 shows a system 700, the system 700 comprising Radio Frequency (RF) circuitry 710, baseband circuitry 720, processing unit 730, memory/storage 740, display 750, camera 760, sensor 770, and input/output (I/O) interface 780 coupled to each other as shown.

The processing unit 730 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Processors may include any combination of general-purpose processors and special-purpose processors, such as graphics processors and application processors. The processor may be coupled with the memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems running on the system. RF circuitry 710, baseband circuitry 720, processing unit 730, memory/storage 740, display 750, camera 760, sensor 770, and I/O interface 780 are well known elements in system 700 (such as, but not limited to, laptop computing devices, tablet computing devices, netbooks, superbooks, smartphones, etc.). Furthermore, instructions as a software product may be stored in a readable storage medium in a computer. The software product in the computer is stored in a storage medium that includes a plurality of commands for a computing device (such as a personal computer, server, or network device) to perform all or some of the steps disclosed in the embodiments of the present application. The storage medium includes a USB disk, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM), a floppy disk, or other type of medium capable of storing program code.

Embodiments of the present application are a combination of techniques/procedures that may be employed in the 3GPP specifications to create the end product.

While the present application has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the present application is not limited to the disclosed embodiment, but is intended to cover various arrangements made without departing from the scope of the appended claims.

Claims (35)

1. A wireless communication method executable in a User Equipment (UE), the method comprising:

receiving a group notification from a network, wherein the group notification is configured to instruct the UE to enter a radio resource control, RRC, connected state;

initiating an RRC connection with the network to enter the RRC connected state;

a Multicast and Broadcast Service (MBS) session of delivery mode 1 (DM 1) is received in the RRC connected state.

2. The wireless communication method of claim 1, wherein the group notification is a group page that sends pages to a plurality of UEs, the UE being one of the plurality of UEs.

3. The wireless communication method of claim 2, wherein in the group paging, a group notification identity is established in a paging message.

4. The wireless communication method of claim 1, wherein the group page comprises a group Core Network (CN) page, and the group CN page is issued by a CN.

5. The wireless communication method of claim 1, wherein the group page comprises a group Radio Access Network (RAN) page, the group RAN page being issued by a base station.

6. The wireless communication method of claim 1, wherein the group notification is a group Multicast Control Channel (MCCH) notification, the group MCCH notification is an RRC message, the group MCCH notification is sent to the UE via an MCCH.

7. The wireless communication method of claim 1, wherein the UE receives an RRC dedicated signaling configuration of the MBS session of the DM1 in the RRC connected state.

8. The wireless communication method of claim 1, wherein the UE receives RRC signaling in the RRC connected state, the RRC signaling configured to instruct the MBS session of the DM1 to start, stop, or modify.

9. The wireless communication method of claim 1, wherein the UE receives an indication in the RRC connected state, the indication configured to indicate the MBS session start, stop or modification of the DM 1.

10. The wireless communication method of claim 9, wherein the UE receives a Downlink Control Information (DCI) format in the RRC connected state, the DCI format configured to indicate the MBS session start, stop or modification of the DM 1.

11. The wireless communication method of claim 1, wherein the UE receives an updated Multicast Control Channel (MCCH) configuration in the RRC connected state, the MCCH configuration configured to instruct the MBS session of the DM1 to start, stop or modify.

12. A method of wireless communication executable in a User Equipment (UE), the method comprising:

receiving a Multicast and Broadcast Service (MBS) session of delivery mode 2 (DM 2) from a network; and

an indication is received from the network, wherein the indication is configured to indicate the MBS session start, stop or modification of the DM 2.

13. The wireless communication method of claim 12, wherein receiving the indication from the network comprises:

the indication is received from the network when the UE is in a Radio Resource Control (RRC) idle state or an RRC inactive state, wherein the indication is a Downlink Control Information (DCI) format and is configured to indicate the MBS session stop or modification of the DM 2.

14. The wireless communication method of claim 12, wherein receiving the indication from the network comprises:

the indication is received from the network when the UE is in a Radio Resource Control (RRC) connected state, wherein the indication is configured to indicate the MBS session of the DM2 to start, stop or modify.

15. The wireless communication method of claim 12, wherein receiving the indication from the network comprises:

the indication is received from the network when the UE is in a Radio Resource Control (RRC) connected state, wherein the indication is RRC signaling and is configured to indicate the MBS session start, stop or modify of the DM 2.

16. The wireless communication method of claim 12, wherein receiving the indication from the network comprises:

the indication is received from the network when the UE is in a Radio Resource Control (RRC) connected state, wherein the indication is a Downlink Control Information (DCI) format and is configured to indicate the MBS session start, stop or modification of the DM 2.

17. The wireless communication method of claim 12, wherein the step of receiving the indication from the network comprises:

The indication is received from the network when the UE is in a Radio Resource Control (RRC) connected state, wherein the indication is an update Multicast Control Channel (MCCH) configuration and is configured to indicate the MBS session start, stop or modification of the DM 2.

18. A wireless communication method executable in a transmitting device, the method comprising:

transmitting a group notification to a User Equipment (UE), wherein the group notification is configured to instruct the UE to enter a Radio Resource Control (RRC) connected state; and

a Multicast and Broadcast Service (MBS) session of delivery mode 1 (DM 1) is transmitted to the UE in the RRC connected state.

19. A wireless communication method executable in a transmitting device, the method comprising:

transmitting a Multicast and Broadcast Service (MBS) session of a delivery mode 2 (DM 2) to a User Equipment (UE); and

an indication is sent to the UE, wherein the indication is configured to indicate the MBS session start, stop or modification of the DM 2.

20. A user equipment, the user equipment comprising:

a transceiver; and

a processor connected to the transceiver and configured to perform the method according to any one of claims 1 to 11.

21. A user equipment, the user equipment comprising:

a transceiver; and

a processor connected to the transceiver and configured to perform the method of any one of claims 12 to 17.

22. A base station, the base station comprising:

a transceiver; and

a processor connected to the transceiver and configured to perform the method of claim 18.

23. A base station, the base station comprising:

a transceiver; and

a processor connected to the transceiver and configured to perform the method of claim 19.

24. A chip, the chip comprising:

a processor configured to invoke and run a computer program stored in a memory to cause a device on which the chip is mounted to perform the wireless communication method according to any of claims 1 to 11.

25. A chip, the chip comprising:

a processor configured to invoke and run a computer program stored in a memory to cause a device on which the chip is mounted to perform the wireless communication method according to any of claims 12 to 17.

26. A chip, the chip comprising:

a processor configured to invoke and run a computer program stored in a memory to cause a device on which the chip is mounted to perform the wireless communication method of claim 18.

27. A chip, the chip comprising:

a processor configured to invoke and run a computer program stored in a memory to cause a device on which the chip is mounted to perform the wireless communication method of claim 19.

28. A computer-readable storage medium, in which a computer program is stored, wherein the computer program causes a computer to execute the wireless communication method according to any one of claims 1 to 11.

29. A computer-readable storage medium, in which a computer program is stored, wherein the computer program causes a computer to execute the wireless communication method according to any one of claims 12 to 17.

30. A computer-readable storage medium, in which a computer program is stored, wherein the computer program causes a computer to execute the wireless communication method according to claim 18.

31. A computer-readable storage medium, in which a computer program is stored, wherein the computer program causes a computer to execute the wireless communication method according to claim 19.

32. A computer program product comprising a computer program, wherein the computer program causes a computer to perform the wireless communication method of any of claims 1 to 11.

33. A computer program product comprising a computer program, wherein the computer program causes a computer to perform the wireless communication method of any of claims 12 to 17.

34. A computer program product comprising a computer program, wherein the computer program causes a computer to perform the wireless communication method of claim 18.

35. A computer program product comprising a computer program, wherein the computer program causes a computer to perform the wireless communication method of claim 19.