Patent Description:
In the <NUM> system, a point-to-multipoint transmission mechanism is to be introduced. In the network architecture of this transmission mechanism, the network side sends downlink data within an area of the multicast/broadcast service by means of the point-to-multipoint transmission mechanism. Terminal devices in this area can receive data through multicast/broadcast channels.

In the data interface, that is N3 interface, between the core network and RAN, a UE-specific N3 channel may be used, and unicast data and multicast/broadcast data for a certain UE are all transmitted in this specific channel. It is also possible to use a shared transmission channel, which is shared by multiple terminal devices for data transmission, and the multiple terminal devices may belong to the same group.

In order to save the overhead of network resource, when there is no downlink data, the terminal device will be in an idle state. When a certain group of downlink multicast/broadcast data arrives, a notification mechanism is required to notify the terminal device of arrival of the downlink data. At present, there is no mechanism to notify a certain group of terminal devices of the arrival of downlink multicast/broadcast data.

<CIT> discloses RNC configuration of MBMS service paging to UEs in DRX mode by SGSN using PDP context activation indicating to RNC the MBMS service TMGI and corresponding DRX parameter, which is used by the RNC to calculate the paging occasion and perform paging procedure.

<CIT> discloses methods and systems for modifying or releasing a Multicast/Broadcast (MB) session for delivery of MB Data to a plurality of Electronic Devices (EDs) connected to a (Radio) Access Network (R) AN node is disclosed. The method includes receiving one or more triggers, and instructing the various network functions and (R) AN nodes to modify (or release) the MB session dependent on the received trigger. <CIT>, 3GPP Draft "New MBS architecture and procedures" XP051842423, and <CIT> represent further prior art in the field.

Embodiments of the application provide a notification method for multicast downlink service, a network device, and a computer-readable storage medium to solve the technical problem as mentioned above.

According to an aspect, there is provided a notification method as set out in claim <NUM>. Optional features are set out in claim <NUM>.

According to another aspect, there is provided a network device as set out in claim <NUM>. Optional features are set out in claim <NUM>.

According to another aspect, there is provided a computer-readable storage medium as set out in claim <NUM>.

According to the method proposed by some embodiments of the application, the network device sends a paging message to the terminal device, where the paging message is used for notifying the terminal device of presence of multicast downlink data, so as to notify a certain group of terminal devices of the arrival of downlink multicast/broadcast data.

The technical solutions according to some embodiments of the application will be described below in conjunction with the drawings according to some embodiments of the application.

It should be noted that the terms "first", "second" and the like in the claims and description according to some embodiments of the application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or order. Additionally, the objects described by "first" and "second" may be the same or different.

The technical solutions according to some embodiments of this application can be applied to various communication systems, such as global system of mobile (GSM) communication system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, advanced long term evolution (LTE-A) system, new radio (NR) system, evolution system of the NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, universal mobile telecommunication system (UMTS), wireless local area network (WLAN), wireless fidelity (WiFi), 5th-generation (<NUM>) system or other communication systems.

Generally speaking, traditional communication systems support a limited number of connections and are easy for implementation. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, device to device (D2D) communication, machine to machine (M2M) communication, machine type communication (MTC), vehicle to vehicle (V2V) communication, and the like. Embodiments of this application can also be applied to these communications system.

Optionally, the communication system in some embodiments of the application can be applied to a carrier aggregation (CA) scenario, can also be applied to a dual connectivity (DC) scenario, and can also be applied to a standalone (SA) network deployment scenario.

Embodiments of the application do not limit the applied frequency spectrum. For example, some embodiments of this application can be applied to licensed spectrum or unlicensed spectrum.

Some embodiments of this application describe various examples in combination with network device and terminal device. The terminal device may also be referred to as user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile site, remote station, remote terminal, mobile device, user terminal, terminal device, wireless communication device, user agent, user device, or the like. The terminal device may be a station (ST) in WLAN, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing devices connected to wireless modems, a vehicle-mounted device, a wearable device, or a terminal device in the next-generation communication system, such as the NR network or the future-evolved public land mobile network (PLMN).

As an example without limitation, in some embodiments of the application, the terminal device may also be a wearable device. The wearable device can also be called a wearable smart device, which is a general term for those wearable devices that are intelligently developed and design based on everyday wear using wearable technology, such as glasses, gloves, watches, clothing, shoes and the like. The wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. The wearable device is not only a kind of hardware device, but also able to realize powerful functions through software support, data interaction, and cloud interaction. In a broad sense, the wearable smart device is characterized in full feature, large size, provided with complete or partial functions that can be achieved without relying on smart phones, and includes, for example, smart watches or smart glasses. Also, the wearable smart device may focus on a certain type of application function, and need to cooperate with other devices such as smart phones for usage, and includes, for example, all kinds of smart bracelets and smart jewelry for physical sign monitoring.

The network device may be a device configured to communicate with mobile devices. The network device may be an access point (AP) in WLAN, a base transceiver station (BTS) in GSM or CDMA, or a NodeB (NB) in WCDMA, or an evolutional Node B (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, or a wearable device, or a network device (gNB) in the NR network, or a network device in the future-evolved PLMN.

In some embodiments of the application, the network device provides services for the cell, and the terminal device communicates with the network device through transmission resources (e.g., frequency domain resources or spectrum resources) used by the cell, and the cell may correspond to a network device (e.g., a base station). The cell may belong to a macro base station or a base station corresponding to a small cell. The small cell here may include a metro cell, a micro cell, a pico cell, a femto cells, and the like. These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.

<FIG> exemplarily shows one network device <NUM> and two terminal devices <NUM>. Optionally, the wireless communication system <NUM> may include multiple network devices <NUM>, and the coverage of each network device <NUM> may include other numbers of terminal device <NUM>, which are not limited in the embodiments of the application. Some embodiments of the application may be applied between one terminal device <NUM> and one network device <NUM>, and may also be applied between one terminal device <NUM> and another terminal device <NUM>.

Optionally, the wireless communication system <NUM> may also include other network entities such as a mobility management entity (MME), an access and mobility management function (AMF) and the like, which is not limited in the embodiments of the application.

It should be understood that the terms "system" and "network" in this disclosure are often used interchangeably in this disclosure. The term "and/or" in this disclosure indicates an association relationship describing the associated objects, which means that there may be three relationships. For example, A and/or B may mean three situations: A exists alone, both A and B exist, B exist alone. In addition, the character "/" in this disclosure generally indicates that the associated objects before and after are in an "or" relationship.

Some embodiments of the application propose a multicast downlink service notification method. <FIG> is an implementation flowchart of a multicast downlink service notification method <NUM> according to some embodiments of the application. The method may optionally be applied to the system shown in <FIG>, for example, applied to the terminal device, but is not limited thereto. The method includes at least part of the following content.

In S210, the terminal device receives a paging message, where the paging message is used for notifying presence of multicast downlink data.

In S220, the terminal device responds to the paging message.

Optionally, the above-mentioned paging message carries at least one of: group information of a group to which the multicast downlink data belongs, relevant multicast broadcast service (MBS, or broadcast can multicast service) session information, and indication information of MBS service updating.

The terminal device determines whether the paging message or a relevant system information block (SIB) of MBS service updating carries information of an interesting group of the terminal device, and if yes, responds to the paging message.

In some embodiments, responding to the paging message includes: activating a relevant MBS session or initiating a radio resource control (RRC) resume procedure.

In some embodiments, activating the relevant MBS session includes:
activating, by the terminal device, the relevant MBS session by entering a connected state from an idle state and sending a non-access stratum (NAS) message.

In some embodiments, the terminal device initiates the RRC resume procedure when it is in an inactive state.

In some embodiments, the above method further includes:
receiving, by the terminal device, a group-specific discontinuous reception (DRX) cycle and a group-specific identity.

Optionally, the group-specific identity includes a radio network temporary identity (RNTI).

In some embodiments, the above method further includes:.

Alternatively, in some embodiments, the terminal device monitors the paging message on an MBS-specific PO.

Optionally, the terminal device calculates the specific PO according to an MBS-specific identity and DRX.

In some embodiments, the MBS-specific identity and DRX are defined in a protocol, or broadcasted by an access network in system information, or configured for the terminal device by a core network through a NAS message.

In some embodiments, the terminal device determines the group-specific PO by using following formulas: <MAT> and <MAT>.

In some embodiments, the foregoing method further includes: receiving, by the terminal device, the multicast downlink data by means of the MBS session.

In some embodiments, the foregoing method further includes: negotiating, by the terminal device, the group-specific DRX cycle with a network device.

Optionally, the terminal device negotiates the group-specific DRX cycle with the network device during a registration procedure and/or an MBS session establishment procedure.

The main process of the multicast downlink service notification method applied to the terminal device according to embodiments of the application is described in detail below with reference to the drawings and some embodiments of the application.

In Embodiment <NUM>, the multicast downlink data arrives at a radio access network (RAN), and the RAN pages all terminal devices.

Key technical points are described as follows:.

According to the above-mentioned embodiments, the impact on irrelevant terminal devices is reduced, and there is no storage requirement for group information on the RAN side.

<FIG> is a schematic diagram of specific steps of some embodiments, including the following steps:.

In Embodiment <NUM>, the multicast downlink data arrives at the RAN, and the RAN paging the terminal device in the group.

Key technical points are described as follows.

According to this embodiment, the overhead of paging is reduced, and a new RAN side behavior or PO calculation manner is introduced.

<FIG> is a schematic diagram of specific steps of this embodiment, including the following steps:.

There are two ways to deal with the next steps.

The first one includes the following steps <NUM>, <NUM>, 5a, 5b:.

The RAN side may start a timer, and after the timer expires, it starts to send downlink data through multicast.

Optionally, the RAN node starts a timer upon sending the paging message to a first one terminal device, sending the paging message to a last one terminal device, or receiving a response to the paging message from the first one terminal device.

Optionally, the RAN node receives the above-mentioned timer configured by the core network when the MBS session is established.

The second way includes the following steps <NUM>', <NUM>', 5a', 5b':.

In addition, some embodiments of the application also propose a negotiation and configuration procedure for the group-specific DRX. Optionally, the terminal device negotiates the group-specific DRX with the network during the registration procedure of the terminal device. Alternatively, the group-specific DRX is negotiated during the establishment of the MBS session. For example, AMF or SMF configures a specific group-specific DRX to the terminal device according to the group that the terminal device is interested in or joins. When the MBS session is established, the core network configures this information to the RAN.

In Embodiment <NUM>, the multicast downlink data arrives at the core network, and the core network pages all terminal devices.

In Embodiment <NUM>, multicast downlink data arrives at the core network, and the core network pages the terminal device in the group.

The first one includes the following steps <NUM>, <NUM>, and <NUM>:.

The second type includes the following steps <NUM>', <NUM>', <NUM>':.

This embodiment also proposes a negotiation and configuration method for Group DRX. Optionally, DRX is negotiated with the network during the registration process of the terminal device; or negotiated during establishment of the MBS session. Specifically, AMF or SMF configures a specific DRX to the terminal device according to the group that the terminal device is interested in or joins.

Some embodiments of the application also propose a multicast downlink service notification method, which is applied to a first network device. Optionally, the first network device is an RAN device. <FIG> is an implementation flowchart of a multicast downlink service notification method <NUM> according to some embodiments of the application, including a following step.

In S710, the first network device sends a paging message, where the paging message is used for notifying presence of multicast downlink data.

In some embodiments, the first network device sends the paging message on all POs.

In some embodiments, the first network device determines a terminal device to be paged according to group information of a group to which the multicast downlink data belongs / relevant MBS session information, and a correspondence between the group / MBS session and the terminal device.

In some embodiments, the first network device determines a group-specific PO according to a group-/MBS session-specific DRX cycle and a group-specific identity/MBS session identity; and
sends the paging message on the group-/MBS session-specific PO.

Optionally, the first network device sends the paging message on an MBS-specific PO.

Optionally, the first network device calculates the specific PO according to an MBS-specific identity and DRX.

In some embodiments, the paging message carries at least one of: group information of a group to which the multicast downlink data belongs, relevant MBS session information, and indication information of MBS service updating.

Optionally, the group-specific identity/MBS session identity includes an RNTI.

In some embodiments, the first network device determines the group-specific PO by using following formulas: <MAT> and <MAT>.

In some embodiments, the first network device determines the group information of the group to which the multicast downlink data belongs or the relevant MBS session information according to information of N3 channel, and the N3 channel is a channel used for receiving the multicast downlink data or the MBS session.

Optionally, the method further includes:
receiving, by the first network device, a message from a second network device, where the message carries a group-/MBS session-specific DRX cycle and a group-/MBS session-specific identity.

Optionally, the message is a paging request message.

Optionally, the message is an N2 message for establishing a connection of the multicast/MBS session service.

In some embodiments, the method further includes:
receiving, by the first network device, a paging request message from a second network device, where the paging request message carries group information of a group to which the multicast downlink data belongs and/or relevant MBS session information.

In some embodiments, the method further includes:.

In some embodiments, the method further includes: receiving the timer configured by a core network upon establishing the MBS session.

Some embodiments of the application also propose a multicast downlink service notification method, which is applied to a second network device. Optionally, the second network device is an AMF. <FIG> is an implementation flow chart of a multicast downlink service notification method <NUM> according to some embodiments of the application, including a following step.

In S810, the second network device sends a paging request message to a first network device, where the paging request message carries at least one of: group information of a group to which multicast downlink data belongs, relevant MBS session information, identity information and DRX information of at least one terminal device to be paged, a group-specific DRX cycle, and a group-specific identity.

Optionally, the terminal device to be paged includes a terminal device registered in a registration area where the first network device is located.

In some embodiments, the method further includes:
receiving, by the second network device, information of the terminal device to be paged from a third network device.

In some embodiments, the method further includes:
configuring, by the second network device, a group-/MBS session-specific DRX cycle to a terminal device according to a group/MBS session that the terminal device joins.

Optionally, the second network device configures the group-specific DRX cycle to the terminal device during a registration procedure of the terminal device and/or an MBS session establishment procedure.

Optionally, the method further includes: configuring, by the second network device, the group-/MBS session-specific DRX cycle to the first network device.

Optionally, the second network device configures the group-/MBS session-specific DRX cycle to the first network device during the MBS session establishment procedure.

Some embodiments of the application also propose a multicast downlink service notification method, which is applied to a third network device. Optionally, the third network device is an SMF. <FIG> is an implementation flowchart of a multicast downlink service notification method <NUM> according to some embodiments of the application, including a following step.

In S910, the third network device sends to a second network device, a first arrival message related to multicast downlink data or an MBS session, or terminal information related to the multicast/MBS session, where the first arrival message carries group information of a group to which the multicast downlink data belongs and/or relevant MBS session information.

In some embodiments, the method further includes:
configuring, by the third network device, a group-/MBS session-specific DRX cycle to a terminal device according to a group/MBS session that the terminal device joins.

In some embodiments, the third network device configures the group-/MBS session-specific DRX cycle to the terminal device during a registration procedure of the terminal device and/or an MBS session establishment procedure.

Optionally, the method further includes: configuring, by the third network device, the group-/MBS session-specific DRX cycle to the first network device.

Optionally, the third network device configures the group-/MBS session-specific DRX cycle to the first network device during the MBS session establishment procedure.

Some embodiments of the application also proposes a multicast downlink service notification method, which is applied to a fourth network device. Optionally, the fourth network device is a UPF. <FIG> is an implementation flowchart of a multicast downlink service notification method <NUM> according to some embodiments of the application, including a following step.

In S1010, the fourth network device sends to a third network device a second arrival message of multicast/MBS session downlink data, where the second arrival message of the multicast/MBS session downlink data carries group information of a group to which the multicast downlink data belongs and/or MBS session information relevant to the group to which the multicast downlink data belongs.

In some embodiments, the method further includes:
determining, by the fourth network device, the group information of the group to which the multicast downlink data belongs and/or the MBS session information relevant to the group to which the multicast downlink data belongs according to at least one of a channel, IP information, and address information at which the multicast downlink data arrives.

Some embodiments of the application also propose a terminal device. <FIG> is a block diagram of a terminal device <NUM> according to some embodiments of the application, including a paging message receiving module <NUM> and a responding module <NUM>.

The paging message receiving module <NUM> is configured to receive a paging message, where the paging message is used for notifying presence of multicast downlink data.

The responding module <NUM> is configured to respond to the paging message.

Optionally, the paging message carries at least one of: group information of a group to which the multicast downlink data belongs, relevant multicast broadcast service (MBS) session information, and indication information of MBS service updating.

The responding module <NUM> is configured to determine whether the paging message or a relevant system information block (SIB) of MBS service updating carries information of an interesting group of the terminal device, and if yes, respond to the paging message.

Optionally, responding to the paging message includes:
activating a relevant MBS session or initiating a radio resource control (RRC) resume procedure.

Optionally, activating the related MBS session includes:
activating, by the terminal device, the related MBS session by entering a connected state from an idle state and sending a non-access stratum (NAS) message.

Optionally, the terminal device initiates the RRC resume procedure in an inactive state.

As shown in <FIG>, in some embodiments, the terminal device further includes:
a first receiving module <NUM>, configured to receive a group-specific discontinuous reception (DRX) cycle and a group-specific identity.

Optionally, the terminal device further includes:.

In some embodiments, the paging message receiving module <NUM> is configured to monitor the paging message on an MBS-specific PO.

Optionally, the paging message receiving module <NUM> is configured to calculate the specific PO according to an MBS-specific identity and DRX.

Optionally, the MBS-specific identity and DRX are defined in a protocol, or broadcasted by an access network in system information, or configured for the terminal device by a core network through a NAS message.

In some embodiments, the first determining module <NUM> is configured to determine the group-specific PO by using following formulas: <MAT> and <MAT>.

As shown in <FIG>, in some embodiments, the terminal device further includes:
a multicast receiving module <NUM>, configured to receive the multicast downlink data by means of the MBS session.

In some embodiments, the terminal device negotiates the group-specific DRX cycle with a network device.

As shown in <FIG>, in some embodiments, the terminal device further includes:
a negotiating module <NUM>, configured to negotiate the group-specific DRX cycle with the network device during a registration procedure and/or an MBS session establishment procedure.

It should be understood that the above-mentioned and other operations and/or functions of the modules in the terminal device according to some embodiments of the application are configured to implement the corresponding process of the terminal device in the method <NUM> of <FIG>, which will not be repeated here for brevity.

Some embodiments of the application also propose a network device. The network device may be the first network device as described above. Optionally, the network device is an RAN device. <FIG> is a block diagram of a network device <NUM> according to some embodiments of the application, including a paging message sending module <NUM>.

The paging message sending module <NUM> is configured to send a paging message, where the paging message is used for notifying presence of multicast downlink data.

In some embodiments, the paging message sending module <NUM> is configured to send the paging message on all POs.

Optionally, the network device determines a terminal device to be paged according to group information of a group to which the multicast downlink data belongs / relevant MBS session information, and a correspondence between the group / MBS session and the terminal device.

Optionally, the network device determines a group-specific PO according to a group-/MBS session-specific DRX cycle and a group-specific identity/MBS session identity.

The paging message sending module <NUM> is configured to send the paging message on the group-/MBS session-specific PO.

In some embodiments, the paging message sending module <NUM> is configured to send the paging message on an MBS-specific PO.

In some embodiments, the network device calculates the specific PO according to an MBS-specific identity and DRX.

In some embodiments, the network device determines the group-specific PO by using following formulas: <MAT> and <MAT>.

In some embodiments, the network device determines the group information of the group to which the multicast downlink data belongs or the relevant MBS session information according to information of N3 channel, and the N3 channel is a channel used for receiving the multicast downlink data or the MBS session.

As shown in <FIG>, in some embodiments, the network device further includes:.

In some embodiments, the network device further includes:
a second receiving module <NUM>, configured to receive a message from a second network device, where the message carries a group-/MBS session-specific DRX cycle and a group-/MBS session-specific identity.

In some embodiments, the message is an N2 message for establishing a connection of the multicast/MBS session service.

In some embodiments, the network device further includes:
a second paging request message receiving module <NUM>, configured to receive a paging request message from a second network device, where the paging request message carries group information of a group to which the multicast downlink data belongs and/or relevant MBS session information.

In some embodiments, the network device further includes:
a multicast sending module <NUM>, configured to start a timer upon sending the paging message to a first one terminal device, sending the paging message to a last one terminal device, or receiving a response to the paging message from the first one terminal device; and send the multicast downlink data when the timer expires.

In some embodiments, the network device further includes:
a timer module <NUM>, configured to receive the timer configured by a core network upon establishing the MBS session.

It should be understood that the above-mentioned and other operations and/or functions of the modules in the network device according to some embodiments of the application are configured to implement the corresponding process of the network device in the method <NUM> of <FIG>, which will not be repeated here for brevity.

Some embodiments of the application also propose a network device. The network device may be the second network device as described above. Optionally, the network device is an AMF. <FIG> is a block diagram of a network device <NUM> according to some embodiments of the application, including a paging request message sending module <NUM>.

The paging request message sending module <NUM> is configured to send a paging request message to a first network device, wherein the paging request message carries at least one of: group information of a group to which multicast downlink data belongs, relevant MBS session information, identity information and DRX information of at least one terminal device to be paged, a group-specific DRX cycle, and a group-specific identity.

In some embodiments, the terminal device to be paged includes a terminal device registered in a registration area where the first network device is located.

In some embodiments, the third receiving module <NUM> is further configured to receive information of the terminal device to be paged from a third network device.

In some embodiments, the network device further includes:
a first configuring module <NUM>, configured to configure a group-/MBS session-specific DRX cycle to a terminal device according to a group/MBS session that the terminal device joins.

Optionally, the first configuring module <NUM> is configured to configure the group-specific DRX cycle to the terminal device during a registration procedure of the terminal device and/or an MBS session establishment procedure.

Optionally, the first configuring module <NUM> is further configured to configure the group-/MBS session-specific DRX cycle to the first network device.

Optionally, the first configuring module <NUM> is configured to configure the group-/MBS session-specific DRX cycle to the first network device during the MBS session establishment procedure.

Some embodiments of the application also propose a network device. The network device may be the third network device as described above. Optionally, the network device is an SMF. <FIG> is a block diagram of a network device <NUM> according to some embodiments of the application, including a first notifying module <NUM>.

The first notifying module <NUM> is configured to send to a second network device a first arrival message related to multicast downlink data or an MBS session, or terminal information related to the multicast/MBS session, wherein the first arrival message carries group information of a group to which the multicast downlink data belongs and/or relevant MBS session information.

As shown in <FIG>, in some embodiments, the network device further includes:
a second configuring module <NUM>, configured to configure a group-/MBS session-specific DRX cycle to a terminal device according to a group/MBS session that the terminal device joins.

Optionally, the second configuring module <NUM> is configured to configure the group-/MBS session-specific DRX cycle to the terminal device during a registration procedure of the terminal device and/or an MBS session establishment procedure.

Optionally, the second configuring module <NUM> is further configured to configure the group-/MBS session-specific DRX cycle to the first network device.

In some embodiments, the second configuring module <NUM> is configured to configure the group-/MBS session-specific DRX cycle to the first network device during the MBS session establishment procedure.

Some embodiments of the application also propose a network device. The network device may be the fourth network device as described above. Optionally, the network device is a UPF. <FIG> is a block diagram of a network device <NUM> according to some embodiments of the application, including a second notifying module <NUM>.

The second notifying module <NUM> is configured to send to a third network device a second arrival message of multicast/MBS session downlink data, wherein the second arrival message of the multicast/MBS session downlink data carries group information of a group to which the multicast downlink data belongs and/or MBS session information relevant to the group to which the multicast downlink data belongs.

As shown in <FIG>, in some embodiments, the network device further includes:
a second determining module <NUM>, configured to determine the group information of the group to which the multicast downlink data belongs and/or the MBS session information relevant to the group to which the multicast downlink data belongs according to at least one of a channel, IP information, and address information at which the multicast downlink data arrives.

<FIG> is a block diagram of a communication device <NUM> according to some embodiments of the application. The communication device <NUM> shown in <FIG> includes a processor <NUM>, and the processor <NUM> may call and run a computer program from a memory to implement the method in some embodiments of the application.

Optionally, as shown in <FIG>, the communication device <NUM> may further include a memory <NUM>. The processor <NUM> may call and run a computer program from the memory <NUM> to implement the method in some embodiments of the application.

Optionally, as shown in <FIG>, the communication device <NUM> may further include a transceiver <NUM>, and the processor <NUM> may control the transceiver <NUM> to communicate with other devices, for example, to send information or data to other devices, or to receive information or data sent by other devices.

In some embodiments, the transceiver <NUM> may include a transmitter and a receiver. The transceiver <NUM> may further include an antenna, and the number of antennas may be one or more.

Optionally, the communication device <NUM> may be the terminal device according to some embodiments of the application, and the communication device <NUM> may implement the corresponding process implemented by the terminal device in each method according to some embodiments of the application. For brevity, details are not repeated herein.

Optionally, the communication device <NUM> may be the network device according to some embodiments of the application, and the communication device <NUM> may implement corresponding processes implemented by the network device in each method according to some embodiments of the application. For brevity, details are not repeated herein.

<FIG> is a block diagram of a chip <NUM> according to some embodiments of the application. The chip <NUM> shown in <FIG> includes a processor <NUM>, and the processor <NUM> may call and run a computer program from a memory to implement the method in some embodiments of the application.

Optionally, as shown in <FIG>, the chip <NUM> may further include a memory <NUM>. The processor <NUM> may call and run a computer program from the memory <NUM> to implement the method in some embodiments of the application.

Optionally, the chip <NUM> may further include an input interface <NUM>. The processor <NUM> may control the input interface <NUM> to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

Optionally, the chip may be applied to the terminal device in some embodiments of the application, and the chip may implement the corresponding process implemented by the terminal device in each method according to some embodiments of the application. For brevity, details are not repeated herein.

It should be understood that the chip mentioned in some embodiments of the application may also be referred to as a system-level chip, a system chip, a chip system, a system-on-chip, or the like.

The aforementioned processors may be general-purpose processors, digital signal processors (DSP), field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or other programmable logic devices, transistor logic devices, discrete hardware components, and the like. Herein, the aforementioned general-purpose processor may be a microprocessor or any conventional processor.

The above-mentioned memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. In some embodiments, the non-volatile memory may be read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM) or flash memory. The volatile memory may be random access memory (RAM).

It should be understood that the foregoing memory is exemplary but not restrictive. For example, the memory in some embodiments of the application may also be static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synch link DRAM (SLDRAM), direct Rambus RAM (DR RAM) and the like. In other words, the memory in the embodiments of the application is intended to include, but is not limited to, these and any other suitable types of memory.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it may be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instruction may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instruction may be transmitted from a website, computer, server, or data center through a wired manner (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or a wireless manner (e.g., infrared, radio, microwave) to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that may be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, and a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)).

It should be understood that in the various embodiments of the application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the application.

Those skilled in the art may clearly understand that, for the convenience and conciseness of description, the specific working process of the system, device and unit described above may refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

Claim 1:
A notification method for multicast downlink service comprising:
sending (S710), by a first network device, a paging message, wherein the paging message is used for notifying presence of multicast downlink data and carries relevant multicast broadcast service, MBS, session information;
receiving, by the first network device, a paging request message from a second network device, wherein the paging request message carries identity information of a terminal device to be paged and DRX information of the terminal device;
the identity information and the DRX information are used for determining a paging occasion, PO, corresponding to the terminal device to be paged.