US20230070801A1 - Multicast downlink service notification method, terminal device and network device - Google Patents

Multicast downlink service notification method, terminal device and network device Download PDF

Info

Publication number
US20230070801A1
US20230070801A1 US17/984,830 US202217984830A US2023070801A1 US 20230070801 A1 US20230070801 A1 US 20230070801A1 US 202217984830 A US202217984830 A US 202217984830A US 2023070801 A1 US2023070801 A1 US 2023070801A1
Authority
US
United States
Prior art keywords
group
information
terminal device
network device
downlink data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
US17/984,830
Other languages
English (en)
Inventor
Jianhua Liu
Shukun Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Dongguan Oppo Mobile Telecommunications Corp Ltd
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Dongguan Oppo Mobile Telecommunications Corp Ltd
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Dongguan Oppo Mobile Telecommunications Corp Ltd, Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Dongguan Oppo Mobile Telecommunications Corp Ltd
Assigned to GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD. reassignment GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LIU, JIANHUA, WANG, SHUKUN
Publication of US20230070801A1 publication Critical patent/US20230070801A1/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This application relates to the field of communications, and more specifically, to a notification method for multicast downlink service, a terminal device, and a network device.
  • a point-to-multipoint transmission mechanism is to be introduced.
  • 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.
  • 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.
  • the terminal device when there is no downlink data, the terminal device will be in an idle state.
  • a notification mechanism is required to notify the terminal device of arrival of the downlink data.
  • Embodiments of the application provide a notification method for multicast downlink service, a terminal device, and a network device to solve the technical problem as mentioned above.
  • Some embodiments of the application propose a notification method for multicast downlink service, including:
  • Some embodiments of the application propose a notification method for multicast downlink service, including:
  • Some embodiments of the application propose a notification method for multicast downlink services, including:
  • Some embodiments of the application propose a notification method for multicast downlink services, including:
  • Some embodiments of the application propose a notification method for multicast downlink services, including:
  • Some embodiments of the application propose a terminal device, including:
  • Some embodiments of the application propose a network device, including:
  • Some embodiments of the application propose a network device, including:
  • Some embodiments of the application propose a network device, including:
  • Some embodiments of the application propose a network device, including:
  • Some embodiments of the application propose a terminal device, including: a processor and a memory, where the memory is configured to store a computer program, and the processor is configured to call and run the computer program stored in the memory, thereby implementing the method according to any embodiments of the notification method for multicast downlink services as described above.
  • Some embodiments of the application propose a network device, including: a processor and a memory, where the memory is configured to store a computer program, and the processor is configured to call and run the computer program stored in the memory, thereby implementing the method according to any embodiments of the notification method for multicast downlink services as described above.
  • Some embodiments of the application propose a chip including: a processor, configured to call and run a computer program from a memory, thereby causing a device installed with the chip to implement the method according to any embodiments of the notification method for multicast downlink services as described above.
  • Some embodiments of the application propose a chip including: a processor, configured to call and run a computer program from a memory, thereby causing a device installed with the chip to implement the method according to any embodiments of the notification method for multicast downlink services as described above.
  • Some embodiments of the application propose a computer-readable storage medium, storing a computer program that enables a computer to implement the method according to any embodiments of the notification method for multicast downlink services as described above.
  • Some embodiments of the application propose a computer-readable storage medium, storing a computer program that enables a computer to implement the method according to any embodiments of the notification method for multicast downlink services as described above.
  • Some embodiments of the application propose a computer program product, including computer program instructions that cause a computer to implement the method according to any embodiments of the notification method for multicast downlink services as described above.
  • Some embodiments of the application propose a computer program product, including computer program instructions that cause a computer to implement the method according to any embodiments of the notification method for multicast downlink services as described above.
  • Some embodiments of the application propose a computer program, causing a computer to implement the method according to any embodiments of the notification method for multicast downlink services as described above.
  • Some embodiments of the application propose a computer program, causing a computer to implement the method according to any embodiments of the notification method for multicast downlink services as described above.
  • 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.
  • FIG. 1 is a schematic diagram of an application scenario according to some embodiments of the application.
  • FIG. 2 is an implementation flowchart of a multicast downlink service notification method 200 according to some embodiments of the application.
  • FIG. 3 is an implementation flow chart according to the first embodiment of the application.
  • FIG. 4 is an implementation flow chart according to the second embodiment of the application.
  • FIG. 5 is an implementation flow chart according to the third embodiment of the application.
  • FIG. 6 is an implementation flow chart according to the fourth embodiment of the application.
  • FIG. 7 is an implementation flowchart of a multicast downlink service notification method 700 according to some embodiments of the application.
  • FIG. 8 is an implementation flowchart of a multicast downlink service notification method 800 according to some embodiments of the application.
  • FIG. 9 is an implementation flowchart of a multicast downlink service notification method 900 according to some embodiments of the application.
  • FIG. 10 is an implementation flowchart of a multicast downlink service notification method 1000 according to some embodiments of the application.
  • FIG. 11 is a block diagram of a terminal device 1100 according to some embodiments of the application.
  • FIG. 12 is a block diagram of a terminal device 1200 according to some embodiments of the application.
  • FIG. 13 is a block diagram of a network device 1300 according to some embodiments of the application.
  • FIG. 14 is a block diagram of a network device 1400 according to some embodiments of the application.
  • FIG. 15 is a block diagram of a network device 1500 according to some embodiments of the application.
  • FIG. 16 is a block diagram of a network device 1600 according to some embodiments of the application.
  • FIG. 17 is a block diagram of a network device 1700 according to some embodiments of the application.
  • FIG. 18 is a block diagram of a network device 1800 according to some embodiments of the application.
  • FIG. 19 is a block diagram of a network device 1900 according to some embodiments of the application.
  • FIG. 20 is a block diagram of a network device 2000 according to some embodiments of the application.
  • FIG. 21 is a block diagram of a communication device 2100 according to some embodiments of the application.
  • FIG. 22 is a block diagram of a chip 2200 according to some embodiments of the application.
  • GSM global system of mobile
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • LTE-A advanced long term evolution
  • NR new radio
  • 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 (5G) system or other communication systems.
  • UMTS universal mobile telecommunication system
  • WLAN wireless local area network
  • WiFi wireless fidelity
  • 5G 5th-generation
  • D2D device to device
  • M2M machine to machine
  • MTC machine type communication
  • V2V vehicle to vehicle
  • 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.
  • CA carrier aggregation
  • DC dual connectivity
  • SA standalone
  • Embodiments of the application do not limit the applied frequency spectrum.
  • some embodiments of this application can be applied to licensed spectrum or unlicensed spectrum.
  • 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.
  • UE user equipment
  • 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).
  • ST station
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • 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.
  • 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.
  • AP access point
  • BTS base transceiver station
  • NB NodeB
  • eNB evolutional Node B
  • gNB network device
  • gNB network device
  • the network device provides services for the cell
  • the terminal device communicates with the network device through transmission resources (e.g., frequency domain resources or spectrum resources) used by the cell
  • 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. 1 exemplarily shows one network device 110 and two terminal devices 120 .
  • the wireless communication system 100 may include multiple network devices 110 , and the coverage of each network device 110 may include other numbers of terminal device 120 , which are not limited in the embodiments of the application.
  • Some embodiments of the application may be applied between one terminal device 120 and one network device 110 , and may also be applied between one terminal device 120 and another terminal device 120 .
  • the wireless communication system 100 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.
  • MME mobility management entity
  • AMF access and mobility management function
  • 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.
  • the character “/” in this disclosure generally indicates that the associated objects before and after are in an “or” relationship.
  • FIG. 2 is an implementation flowchart of a multicast downlink service notification method 200 according to some embodiments of the application.
  • the method may optionally be applied to the system shown in FIG. 1 , for example, applied to the terminal device, but is not limited thereto.
  • the method includes at least part of the following content.
  • the terminal device receives a paging message, where the paging message is used for notifying presence of multicast downlink data.
  • the terminal device responds to the paging message.
  • 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.
  • SIB system information block
  • responding to the paging message includes: activating a relevant MBS session or initiating a radio resource control (RRC) resume procedure.
  • RRC radio resource control
  • activating the relevant MBS session includes:
  • the terminal device initiates the RRC resume procedure when it is in an inactive state.
  • the above method further includes:
  • the group-specific identity includes a radio network temporary identity (RNTI).
  • RNTI radio network temporary identity
  • the above method further includes:
  • the terminal device monitors the paging message on an MBS-specific PO.
  • the terminal device calculates the specific PO according to an MBS-specific identity and DRX.
  • 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.
  • the terminal device determines the group-specific PO by using following formulas:
  • i _ s floor(Group_ID/ N )mod N s;
  • the foregoing method further includes: receiving, by the terminal device, the multicast downlink data by means of the MBS session.
  • the foregoing method further includes: negotiating, by the terminal device, the group-specific DRX cycle with a network device.
  • 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 multicast downlink data arrives at a radio access network (RAN), and the RAN pages all terminal devices.
  • RAN radio access network
  • the impact on irrelevant terminal devices is reduced, and there is no storage requirement for group information on the RAN side.
  • FIG. 3 is a schematic diagram of specific steps of some embodiments, including the following steps:
  • the multicast downlink data arrives at the RAN, and the RAN paging the terminal device in the group.
  • the overhead of paging is reduced, and a new RAN side behavior or PO calculation manner is introduced.
  • FIG. 4 is a schematic diagram of specific steps of this embodiment, including the following steps:
  • the first one includes the following steps 3, 4, 5a, 5b:
  • the RAN side may start a timer, and after the timer expires, it starts to send downlink data through multicast.
  • 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.
  • 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 3′, 4′, 5a′, 5b′:
  • i _ s floor(Group_ID/ N )mod N s;
  • some embodiments of the application also propose a negotiation and configuration procedure for the group-specific DRX.
  • the terminal device negotiates the group-specific DRX with the network during the registration procedure of the terminal device.
  • the group-specific DRX is negotiated during the establishment of the MBS session.
  • 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.
  • the core network configures this information to the RAN.
  • the multicast downlink data arrives at the core network, and the core network pages all terminal devices.
  • FIG. 5 is a schematic diagram of specific steps of this embodiment, including the following steps:
  • multicast downlink data arrives at the core network, and the core network pages the terminal device in the group.
  • FIG. 6 is a schematic diagram of specific steps of this embodiment, including the following steps:
  • the first one includes the following steps 3, 4, and 5:
  • AMF determines the terminal device to be paged according to the terminal information in the group provided by SMF in step 3.
  • the second type includes the following steps 3′, 4′, 5′ :
  • This embodiment also proposes a negotiation and configuration method for Group DRX.
  • DRX is negotiated with the network during the registration process of the terminal device; or negotiated during establishment of the MBS session.
  • AMF or SMF configures a specific DRX to the terminal device according to the group that the terminal device is interested in or joins.
  • FIG. 7 is an implementation flowchart of a multicast downlink service notification method 700 according to some embodiments of the application, including a following step.
  • the first network device sends a paging message, where the paging message is used for notifying presence of multicast downlink data.
  • the first network device sends the paging message on all POs.
  • 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.
  • 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;
  • the first network device sends the paging message on an MBS-specific PO.
  • the first network device calculates the specific PO according to an MBS-specific identity and DRX.
  • 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.
  • the group-specific identity/MBS session identity includes an RNTI.
  • the first network device determines the group-specific PO by using following formulas:
  • i _ s floor(Group_ID/ N )mod N s;
  • 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.
  • the method further includes:
  • the method further includes:
  • the message is a paging request message.
  • the message is an N2 message for establishing a connection of the multicast/MBS session service.
  • the method further includes:
  • the method further includes:
  • the method further includes: receiving the timer configured by a core network upon establishing the MBS session.
  • FIG. 8 is an implementation flow chart of a multicast downlink service notification method 800 according to some embodiments of the application, including a following step.
  • 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.
  • the terminal device to be paged includes a terminal device registered in a registration area where the first network device is located.
  • the method further includes:
  • the method further includes:
  • the method further includes:
  • 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 MB S session establishment procedure.
  • the method further includes: configuring, by the second network device, the group-/MBS session-specific DRX cycle to the first network device.
  • the second network device configures the group-/MBS session-specific DRX cycle to the first network device during the MBS session establishment procedure.
  • FIG. 9 is an implementation flowchart of a multicast downlink service notification method 900 according to some embodiments of the application, including a following step.
  • 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.
  • the method further includes:
  • 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.
  • the method further includes: configuring, by the third network device, the group-/MBS session-specific DRX cycle to the first network device.
  • the third network device configures the group-/MBS session-specific DRX cycle to the first network device during the MBS session establishment procedure.
  • FIG. 10 is an implementation flowchart of a multicast downlink service notification method 1000 according to some embodiments of the application, including a following step.
  • 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.
  • the method further includes:
  • FIG. 11 is a block diagram of a terminal device 1100 according to some embodiments of the application, including a paging message receiving module 1101 and a responding module 1102 .
  • the paging message receiving module 1101 is configured to receive a paging message, where the paging message is used for notifying presence of multicast downlink data.
  • the responding module 1102 is configured to respond to the paging message.
  • 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 1102 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.
  • SIB system information block
  • responding to the paging message includes:
  • activating the related MBS session includes:
  • the terminal device initiates the RRC resume procedure in an inactive state.
  • the terminal device further includes:
  • the group-specific identity includes a radio network temporary identity (RNTI).
  • RNTI radio network temporary identity
  • the terminal device further includes:
  • the paging message receiving module 1101 is configured to monitor the paging message on an MBS-specific PO.
  • the paging message receiving module 1101 is configured to calculate the specific PO according to an MBS-specific identity and DRX.
  • 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.
  • the first determining module 1204 is configured to determine the group-specific PO by using following formulas:
  • i _ s floor(Group_ID/ N )mod N s;
  • the terminal device further includes:
  • the terminal device negotiates the group-specific DRX cycle with a network device.
  • the terminal device further includes:
  • FIG. 13 is a block diagram of a network device 1300 according to some embodiments of the application, including a paging message sending module 1301 .
  • the paging message sending module 1301 is configured to send a paging message, where the paging message is used for notifying presence of multicast downlink data.
  • the paging message sending module 1301 is configured to send the paging message on all POs.
  • 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.
  • 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 1301 is configured to send the paging message on the group-/MBS session-specific PO.
  • the paging message sending module 1301 is configured to send the paging message on an MBS-specific PO.
  • the network device calculates the specific PO according to an MBS-specific identity and DRX.
  • 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.
  • the group-specific identity/MBS session identity includes an RNTI.
  • the network device determines the group-specific PO by using following formulas:
  • i _ s floor(Group_ID/ N )mod N s;
  • i_s represents an identity of the group-specific PO
  • 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.
  • the network device further includes:
  • the network device further includes:
  • the message is a paging request message.
  • the message is an N2 message for establishing a connection of the multicast/MBS session service.
  • the network device further includes:
  • the network device further includes:
  • the network device further includes:
  • FIG. 15 is a block diagram of a network device 11500 according to some embodiments of the application, including a paging request message sending module 1501 .
  • the paging request message sending module 1501 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.
  • the terminal device to be paged includes a terminal device registered in a registration area where the first network device is located.
  • the network device further includes:
  • the third receiving module 1602 is further configured to receive information of the terminal device to be paged from a third network device.
  • the network device further includes:
  • the first configuring module 1603 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.
  • the first configuring module 1603 is further configured to configure the group-/MBS session-specific DRX cycle to the first network device.
  • the first configuring module 1603 is configured to configure the group-/MBS session-specific DRX cycle to the first network device during the MBS session establishment procedure.
  • FIG. 17 is a block diagram of a network device 1700 according to some embodiments of the application, including a first notifying module 1701 .
  • the first notifying module 1701 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.
  • the network device further includes:
  • the second configuring module 1802 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.
  • the second configuring module 1802 is further configured to configure the group-/MBS session-specific DRX cycle to the first network device.
  • the second configuring module 1802 is configured to configure the group-/MBS session-specific DRX cycle to the first network device during the MBS session establishment procedure.
  • FIG. 19 is a block diagram of a network device 1900 according to some embodiments of the application, including a second notifying module 1901 .
  • the second notifying module 1901 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.
  • the network device further includes:
  • FIG. 21 is a block diagram of a communication device 2100 according to some embodiments of the application.
  • the communication device 2100 shown in FIG. 21 includes a processor 2110 , and the processor 2110 may call and run a computer program from a memory to implement the method in some embodiments of the application.
  • the communication device 2100 may further include a memory 2120 .
  • the processor 2110 may call and run a computer program from the memory 2120 to implement the method in some embodiments of the application.
  • the memory 2120 may be a separate device independent of the processor 2110 , or may be integrated in the processor 2110 .
  • the communication device 2100 may further include a transceiver 2130 , and the processor 2110 may control the transceiver 2130 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.
  • the processor 2110 may control the transceiver 2130 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.
  • the transceiver 2130 may include a transmitter and a receiver.
  • the transceiver 2130 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 2100 may be the terminal device according to some embodiments of the application, and the communication device 2100 may implement the corresponding process implemented by the terminal device in each method according to some embodiments of the application.
  • the communication device 2100 may implement the corresponding process implemented by the terminal device in each method according to some embodiments of the application.
  • details are not repeated herein.
  • the communication device 2100 may be the network device according to some embodiments of the application, and the communication device 2100 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. 22 is a block diagram of a chip 2200 according to some embodiments of the application.
  • the chip 2200 shown in FIG. 22 includes a processor 2210 , and the processor 2210 may call and run a computer program from a memory to implement the method in some embodiments of the application.
  • the chip 2200 may further include a memory 2220 .
  • the processor 2210 may call and run a computer program from the memory 2220 to implement the method in some embodiments of the application.
  • the memory 2220 may be a separate device independent of the processor 2210 , or may be integrated in the processor 2210 .
  • the chip 2200 may further include an input interface 2230 .
  • the processor 2210 may control the input interface 2230 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
  • the chip 2200 may further include an output interface 2240 .
  • the processor 2210 may control the output interface 2240 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
  • 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.
  • 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.
  • 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.
  • DSP digital signal processors
  • FPGA field programmable gate arrays
  • ASIC application specific integrated circuits
  • 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.
  • the non-volatile memory may be read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM) or flash memory.
  • ROM read-only memory
  • PROM programmable ROM
  • EPROM erasable PROM
  • EEPROM electrically EPROM
  • flash memory volatile memory
  • RAM random access memory
  • 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.
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • SLDRAM synch link DRAM
  • DR RAM direct Rambus RAM
  • DR RAM direct Rambus RAM
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • 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.
  • 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.
  • 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)).
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
US17/984,830 2020-05-12 2022-11-10 Multicast downlink service notification method, terminal device and network device Pending US20230070801A1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/089884 WO2021226848A1 (zh) 2020-05-12 2020-05-12 组播下行业务通知方法、终端设备和网络设备

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/089884 Continuation WO2021226848A1 (zh) 2020-05-12 2020-05-12 组播下行业务通知方法、终端设备和网络设备

Publications (1)

Publication Number Publication Date
US20230070801A1 true US20230070801A1 (en) 2023-03-09

Family

ID=78526139

Family Applications (1)

Application Number Title Priority Date Filing Date
US17/984,830 Pending US20230070801A1 (en) 2020-05-12 2022-11-10 Multicast downlink service notification method, terminal device and network device

Country Status (6)

Country Link
US (1) US20230070801A1 (de)
EP (1) EP4138422A4 (de)
JP (1) JP2023530582A (de)
KR (1) KR20230008758A (de)
CN (2) CN115486100A (de)
WO (1) WO2021226848A1 (de)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023128618A1 (en) * 2021-12-29 2023-07-06 Lg Electronics Inc. Method and apparatus for handling connection based on a multicast type in a wireless communication system
CN117135578A (zh) * 2022-05-20 2023-11-28 中国移动通信有限公司研究院 通信处理方法、装置、通信设备及可读存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101483811B (zh) * 2008-01-08 2010-12-08 大唐移动通信设备有限公司 一种多媒体广播组播业务的寻呼方法和系统
KR101682956B1 (ko) * 2010-10-14 2016-12-07 삼성전자주식회사 기기 간 통신 시스템에서 페이징된 기기에서의 억세스 오버헤드를 감소하기 위한 방법 및 장치
WO2017126621A1 (ja) * 2016-01-21 2017-07-27 京セラ株式会社 無線端末及びネットワーク装置
CN109429185B (zh) * 2017-08-30 2021-08-03 成都鼎桥通信技术有限公司 Mbsfn群组信令发送方法及装置
US11013052B2 (en) * 2018-01-15 2021-05-18 Huawei Technologies Co., Ltd. Methods and systems for multicast-broadcast session release and modification

Also Published As

Publication number Publication date
JP2023530582A (ja) 2023-07-19
EP4138422A4 (de) 2023-06-14
CN116321429A (zh) 2023-06-23
WO2021226848A1 (zh) 2021-11-18
KR20230008758A (ko) 2023-01-16
EP4138422A1 (de) 2023-02-22
CN115486100A (zh) 2022-12-16

Similar Documents

Publication Publication Date Title
US20230070801A1 (en) Multicast downlink service notification method, terminal device and network device
CN112586039A (zh) 无线通信方法、终端设备和网络设备
US20230209416A1 (en) Wireless communication method, terminal device, and network device
WO2021189461A1 (zh) 确定寻呼分组的方法、终端设备和网络设备
CN114982298B (zh) 寻呼时间位置的确定方法、发送寻呼的方法、用户终端和网络设备
CN114762408B (zh) 监听寻呼方法、寻呼方法、终端设备和网络设备
WO2021174427A1 (zh) 测量方法和终端设备
WO2022183356A1 (zh) 一种定时器运行方法、终端设备和网络设备
WO2021237623A1 (zh) 切片选择的方法和终端设备
CN116438828A (zh) 测量配置方法、终端设备、网络设备、芯片和存储介质
WO2021163978A1 (zh) 控制辅小区组状态的方法和终端设备
US20230262656A1 (en) Communications Method and Apparatus
WO2021203439A1 (zh) 数据传输方法、终端设备和网络设备
US20230379882A1 (en) Paging method and terminal device
WO2022016544A1 (zh) 无线通信方法、终端设备和网络设备
CN114424637B (zh) 寻呼的方法和装置
WO2022036509A1 (zh) 请求多播控制信道信令的方法、终端设备和通信设备
WO2021217513A1 (zh) 工作带宽部分的切换方法、终端设备和网络设备
WO2022147729A1 (zh) 功率控制的方法、终端设备和网络设备
WO2022141053A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022147673A1 (zh) 信令发送方法、终端设备的上下文迁移方法和网络设备
WO2021232256A1 (zh) 终端辅助信息上报方法、终端设备和网络设备
WO2022061493A1 (zh) 资源确定方法、终端设备和网络设备
WO2023024006A1 (zh) 一种确定节能信号监听时机的方法及装置、终端设备
CN116648941A (zh) 参数配置方法、终端设备和网络设备

Legal Events

Date Code Title Description
AS Assignment

Owner name: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD., CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LIU, JIANHUA;WANG, SHUKUN;SIGNING DATES FROM 20220801 TO 20220808;REEL/FRAME:061723/0202

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION