[go: up one dir, main page]

WO2024066858A1 - Procédé et appareil de communication - Google Patents

Procédé et appareil de communication Download PDF

Info

Publication number
WO2024066858A1
WO2024066858A1 PCT/CN2023/115378 CN2023115378W WO2024066858A1 WO 2024066858 A1 WO2024066858 A1 WO 2024066858A1 CN 2023115378 W CN2023115378 W CN 2023115378W WO 2024066858 A1 WO2024066858 A1 WO 2024066858A1
Authority
WO
WIPO (PCT)
Prior art keywords
mcch
information
area
identifier
configuration
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.)
Ceased
Application number
PCT/CN2023/115378
Other languages
English (en)
Chinese (zh)
Inventor
科齐奥尔戴维德
李秉肇
许斌
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2024066858A1 publication Critical patent/WO2024066858A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/021—Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • 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

Definitions

  • the embodiments of the present application relate to the field of communications, and more specifically, to a communication method and device.
  • Multicast and broadcast service can provide data to a large number of users with the same needs at the same time with fewer resources, so that network resources can be shared.
  • 3GPP 3rd generation partnership project
  • terminal devices can only receive MBS in the connected state.
  • the network device can first send an MBS control channel (MCCH) configuration to the terminal device.
  • MCCH MBS control channel
  • the MCCH configuration includes the configuration information of the MCCH.
  • the terminal device can obtain the MBS configuration in the MCCH. Further, the terminal device can receive the MBS in the connected state according to the MBS configuration.
  • R18 proposes to support terminal devices to receive MBS in the RRC inactive state. For example, when the terminal device has no unicast service and only has MBS, the network can release the terminal device to the RRC inactive state, and the terminal device can receive MBS in the RRC inactive state. In this way, the number of terminal devices in the RRC connected state in the network can be reduced, which is conducive to alleviating network congestion and energy saving of terminal devices.
  • the protocol does not define how the terminal device obtains the MCCH configuration before receiving the MBS.
  • the present application provides a communication method and apparatus, which enables a terminal device to obtain MCCH configuration. In addition, it can also prevent a terminal device that has not joined a multicast session from obtaining MCCH configuration, thereby ensuring the security of MCCH.
  • a communication method is provided.
  • the method may be executed by a terminal device, or may be executed by a component of the terminal device (eg, a chip or a circuit), which is not limited in the present application.
  • the method may include: a terminal device receives first information from a first network device, the first information includes at least one MCCH configuration and an effective area of at least one MCCH configuration; the terminal device receives second information from a second network device, the second information is used to indicate a first area identifier or a cell identifier; if the first area identifier or the cell identifier belongs to the effective area, the terminal device receives MCCH information from the second network device in an idle state or an inactive state according to the first MCCH configuration, and the at least one MCCH configuration includes the first MCCH configuration; if the first area identifier or the cell identifier does not belong to the effective area, the terminal device sends a radio resource control RRC recovery request message to the second network device.
  • the effective area of MCCH configuration can be pre-configured to the terminal device through dedicated signaling.
  • the terminal device can determine the first area through public signaling.
  • the terminal device can use the pre-configured MCCH configuration in the dedicated signaling to receive MCCH information.
  • the terminal device can receive the MCCH configuration in further dedicated signaling through the RRC reply process. In this way, the terminal device can obtain the MCCH configuration.
  • it can also prevent terminal devices that have not joined the multicast session from obtaining the MCCH configuration, thereby ensuring the security of the MCCH.
  • the terminal device can also determine the corresponding MCCH configuration according to the first area. In this way, the terminal can obtain the MCCH configuration more quickly, thereby improving communication efficiency.
  • the first MCCH configuration is determined according to the first area identifier or the cell identifier. For example, there is a corresponding relationship between the first area identifier or the cell identifier and the first MCCH configuration.
  • the first information is carried in an RRC release message or an RRC reconfiguration message.
  • the second information is carried in a paging message or a system message.
  • the first area identifier is any one of the following: a tracking area identifier, a radio access network area identifier, or an MCCH area identifier.
  • the effective area includes: at least one cell, at least one TA, at least one RNA, or at least one MCCH area.
  • the first area used to make a judgment may be a cell, a tracking area or an RNA.
  • the second information may be information that has been defined by the standard.
  • the second information is an identifier of a serving cell of a user equipment (UE). In this way, there is no need to add additional signaling to indicate the second information, thereby reducing signaling overhead.
  • the first area identifier or the cell identifier belongs to the effective area, including: the identifier of the first area is one of the identifiers corresponding to the effective area.
  • the RRC recovery request message includes a cause value of MCCH configuration acquisition or multicast reception.
  • the method also includes: the terminal device receives a second MCCH configuration from a second network device; the terminal device receives MCCH information from the second network device in an idle state or an inactive state according to the second MCCH configuration.
  • the UE can still obtain the MCCH configuration parameters of the serving cell, which helps to ensure the continuity of the multicast session.
  • the second MCCH configuration is carried in the RRC release message.
  • the first information further includes an identifier of a multicast broadcast service MBS corresponding to each MCCH configuration in at least one MCCH configuration.
  • the MCCH configuration can be associated with the MBS, so that a different MCCH configuration can be determined for each MBS, which has greater flexibility.
  • the first MCCH configuration includes one or more of the following: MCCH window information, MCCH modification period, MCCH frequency domain resources, and MCCH wireless network temporary identifier.
  • a communication method is provided.
  • the method may be executed by a first network device, or may be executed by a component (such as a chip or a circuit) of the first network device, and the present application does not limit this.
  • the method includes: a first network device sends first information to a terminal device, the first information includes at least one MCCH configuration and an effective area of at least one MCCH configuration, and the at least one MCCH configuration includes a first MCCH configuration; the first network device sends an MCCH message on a first MCCH channel, and the first MCCH channel uses the first MCCH configuration.
  • the method also includes: the first network device sends second information to the terminal device, the second information is used to indicate a first area identifier or a cell identifier, and the first area identifier or the cell identifier is used to determine a first MCCH configuration.
  • the second information is carried in a paging message or a system message.
  • the first information is carried in an RRC release message or an RRC reconfiguration message.
  • the method also includes: the first network device receives third information from a third network device, the third information includes N MCCH configurations and effective areas of the N MCCH configurations, at least one multicast configuration information includes N MCCH configurations, and the effective area of at least one MCCH configuration includes effective areas of the N MCCH configurations, the at least one MCCH configuration information and the effective area are determined based on the third information, and N is a positive integer.
  • the method also includes: the first network device determines fourth information, the fourth information includes R MCCH configurations and effective areas of the R MCCH configurations, at least one multicast configuration information includes R MCCH configurations, and the effective area of at least one MCCH configuration includes an effective area of R MCCH configurations, where R is a positive integer; the first network device sends the fourth information to the third network device.
  • the first network device and the third network device can coordinate to determine the MCC configuration, which can ensure the synchronization of the MCCH configuration between the network devices and has stronger feasibility.
  • the method further includes: the first network device receives an RRC recovery message from the terminal device; and the first network device sends a second MCCH configuration to the terminal device.
  • the RRC recovery request message includes a cause value of MCCH configuration acquisition or multicast reception.
  • the second MCCH configuration is carried in the RRC release message.
  • the first area is any one of the following: a tracking area identifier, a radio access network area identifier, or an MCCH area identifier.
  • the effective area includes: at least one cell, at least one TA, at least one RNA, or at least one MCCH area.
  • the first information further includes an identifier of a multicast broadcast service MBS corresponding to each MCCH configuration in at least one MCCH configuration.
  • the first MCCH configuration includes one or more of the following: MCCH window information, MCCH modification period, MCCH frequency domain resources, and MCCH wireless network temporary identifier.
  • a communication device which may be a terminal device, or a component of a terminal device (such as a chip or a circuit), etc., which is not limited in the present application.
  • the device may include: a transceiver unit and a processing unit, the transceiver unit is used to receive first information from a first network device, the first information includes at least one MCCH configuration and at least one effective area of the MCCH configuration; the transceiver unit is also used to: receive second information from a second network device, the second information is used to indicate a first area identifier or a cell identifier.
  • the processing unit is used to: if the first area identifier or the cell identifier belongs to the effective area, then receive MCCH information from the second network device in an idle state or an inactive state according to the first MCCH configuration, the at least one MCCH configuration includes the first MCCH configuration; if the first area identifier or the cell identifier does not belong to the effective area, then send a radio resource control RRC recovery request message to the second network device.
  • the first MCCH configuration is determined according to the first area identifier or the cell identifier. For example, there is a corresponding relationship between the first area identifier or the cell identifier and the first MCCH configuration.
  • the first information is carried in an RRC release message or an RRC reconfiguration message.
  • the second information is carried in a paging message or a system message.
  • the first area is any one of the following: a tracking area identifier, a radio access network area identifier, or an MCCH area identifier.
  • the effective area includes: at least one cell, at least one tracking area TA, at least one RNA, or at least one MCCH area.
  • the first area identifier or the cell identifier belongs to the effective area, including: the identifier of the first area is one of the identifiers corresponding to the effective area.
  • the RRC recovery request message includes a cause value of MCCH configuration acquisition or multicast reception.
  • the transceiver unit is further used to: receive a second MCCH configuration from a second network device; and receive MCCH information from the second network device in an idle state or an inactive state according to the second MCCH configuration.
  • the second MCCH configuration is carried in the RRC release message.
  • the first information further includes an identifier of a multicast broadcast service MBS corresponding to each MCCH configuration in at least one MCCH configuration.
  • the first MCCH configuration includes one or more of the following: MCCH window information, MCCH modification period, MCCH frequency domain resources, and MCCH wireless network temporary identifier.
  • a communication device which may be a first network device, or may be a component (such as a chip or circuit) of the first network device, which is not limited in the present application.
  • the device includes: a transceiver unit, used to send first information to a terminal device, the first information includes at least one MCCH configuration and at least one effective area of the MCCH configuration, and the at least one MCCH configuration includes a first MCCH configuration; the transceiver unit is also used to: send an MCCH message on a first MCCH channel, and the first MCCH channel uses the first MCCH configuration.
  • the transceiver unit is further used to: send second information to the terminal device, the second information is used to indicate a first area identifier or a cell identifier, and the first area identifier or the cell identifier is used to determine a first MCCH configuration.
  • the second information is carried in a paging message or a system message.
  • the first information is carried in an RRC release message or an RRC reconfiguration message.
  • the transceiver unit is further used to: receive third information from a third network device, the third information including N MCCH configurations and N MCCH configuration effective areas, at least one multicast configuration information including There are N MCCH configurations, and the effective area of at least one MCCH configuration includes the effective areas of N MCCH configurations.
  • the at least one MCCH configuration information and the effective area are determined according to the third information, and N is a positive integer.
  • the transceiver unit is also used to: determine fourth information, the fourth information includes R MCCH configurations and effective areas of the R MCCH configurations, at least one multicast configuration information includes R MCCH configurations, and the effective area of at least one MCCH configuration includes the effective area of R MCCH configurations, where R is a positive integer; and send the fourth information to a third network device.
  • the transceiver unit is further used to: receive an RRC recovery message from a terminal device; and send a second MCCH configuration to the terminal device.
  • the RRC recovery request message includes a cause value of MCCH configuration acquisition or multicast reception.
  • the second MCCH configuration is carried in the RRC release message.
  • the first area is any one of the following: a tracking area identifier, a radio access network area identifier, or an MCCH area identifier.
  • the effective area includes: at least one cell, at least one tracking area TA, at least one RNA, or at least one MCCH area.
  • the first information further includes an identifier of a multicast broadcast service MBS corresponding to each MCCH configuration in at least one MCCH configuration.
  • the first MCCH configuration includes one or more of the following: MCCH window information, MCCH modification period, MCCH frequency domain resources, and MCCH wireless network temporary identifier.
  • a communication device comprising: at least one processor, configured to execute a computer program or instruction stored in a memory, so as to execute the method in any possible implementation of the first aspect to the second aspect.
  • the device further comprises a memory, configured to store a computer program or instruction.
  • the device further comprises a communication interface, and the processor reads the computer program or instruction stored in the memory through the communication interface.
  • the apparatus is a terminal device or a first network device.
  • the apparatus is a chip, a chip system or a circuit for a terminal device or a first network device.
  • the present application provides a processor for executing the methods provided in the first to second aspects above.
  • a computer-readable storage medium which stores a program code for execution by a device, wherein the program code includes a method for executing any possible implementation of the first to second aspects above.
  • a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute a method in any possible implementation of the first to second aspects.
  • FIG1 shows a schematic diagram of a wireless communication system applicable to an embodiment of the present application.
  • FIG. 2 is a flow chart of a multicast broadcast session.
  • FIG. 3 is a flow chart of a multicast broadcast session and a protocol stack chart.
  • FIG. 4 is a schematic diagram of transmission resources for information of a multicast broadcast session.
  • FIG5 shows a schematic diagram of switching of the RRC state of the UE.
  • FIG. 6 is an example of terminal device connection recovery.
  • FIG. 7 is another example of terminal device connection recovery.
  • FIG8 is a schematic diagram of a communication method 400 provided in accordance with an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a communication method 500 provided in an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a communication device 2800 provided in an embodiment of the present application.
  • FIG. 11 is a schematic diagram of another communication device 2900 provided in an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a chip system 3000 provided in an embodiment of the present application.
  • the technical solution provided in this application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) or new radio (new radio, NR) system, long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, etc.
  • the technical solution provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • the technical solution provided in this application can also be applied to device to device (D2D) communication, vehicle to everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of things (IoT) communication system or other communication systems.
  • D2D device to device
  • V2X vehicle to everything
  • M2M machine to machine
  • MTC machine type communication
  • IoT Internet of things
  • V2X may include vehicle-to-vehicle (V2V), vehicle-to-pedestrian (V2P), and vehicle-to-infrastructure (V2I), where the infrastructure is, for example, a road side unit (RSU) or a network device.
  • V2V vehicle-to-vehicle
  • V2P vehicle-to-pedestrian
  • V2I vehicle-to-infrastructure
  • RSU road side unit
  • network device for example, a network device.
  • the terminal devices in the embodiments of the present application include various devices with wireless communication functions, which can be used to connect people, objects, machines, etc.
  • the terminal devices can be widely used in various scenarios, such as: cellular communication, D2D, V2X, peer to peer (P2P), M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc.
  • the terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc.
  • the terminal device can be a user equipment (UE), terminal, fixed device, mobile station device or mobile device of the third generation partnership project (3GPP) standard, a subscriber unit, a handheld device, a vehicle-mounted device, a wearable device, a cellular phone, a smart phone, a SIP phone, a wireless data card, a personal digital assistant (PDA), a computer, a tablet computer, a notebook computer, a wireless modem, a handheld device (handset), a laptop computer, a computer with wireless transceiver function, a smart book, a vehicle, a satellite, a global positioning system (GPS) device, a target tracking device, an aircraft (such as a drone, a helicopter, a multi-copter, a quadcopter, or an airplane), a ship, a remote control device, a smart home device, an industrial device, or a device built into the above device (for example, a communication module, a modem or a chip in the above device), or other processing devices connected to the wireless
  • the UE can also be used to act as a base station.
  • the UE can act as a scheduling entity that provides sidelink signals between UEs in scenarios such as V2X, D2D or P2P.
  • the device for realizing the function of the terminal device can be the terminal device, or a device that can support the terminal device to realize the function, such as a chip system or a chip, which can be installed in the terminal device.
  • the chip system can be composed of a chip, or it can include a chip and other discrete devices.
  • the network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may also be referred to as an access network device or a wireless access network device, such as a base station.
  • the network device in the embodiment of the present application may refer to a wireless access network (RAN) node (or device) that connects a terminal device to a wireless network.
  • RAN wireless access network
  • Base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting point (TRP), transmitting point (TP), master station, auxiliary station, multi-standard wireless (motor slide retainer, MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc.
  • NodeB evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting point (TRP), transmitting point (TP), master station, auxiliary station, multi-standard wireless (motor slide retainer, MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node,
  • the base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof.
  • the base station may also refer to a communication module, modem or chip used to be set in the aforementioned equipment or device.
  • the base station may also be a mobile switching center and a device that performs the base station function in D2D, V2X, and M2M communications, a network-side device in a 6G network, and a device that performs the base station function in a future communication system.
  • the base station may support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form used by the network equipment.
  • Base stations can be fixed or mobile.
  • a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station.
  • a helicopter or drone can be configured to act as a device that communicates with another base station.
  • the network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons and satellites in the air.
  • the embodiments of the present application do not limit the scenarios in which the network equipment and terminal equipment are located.
  • FIG1 shows a schematic diagram of a wireless communication system applicable to an embodiment of the present application.
  • the wireless communication system 100 may include at least one network device, such as the network device 110 shown in FIG1 , and the wireless communication system may also include at least one terminal device, such as the terminal device 120 and the terminal device 130 shown in FIG1 .
  • Both the network device and the terminal device may be configured with multiple antennas, and the network device and the terminal device may communicate using multi-antenna technology.
  • the terminal device 120 and the terminal device 130 may communicate directly or through the network device 110.
  • the network device can manage one or more cells, and one cell can have one or more terminal devices.
  • the network device and the terminal device form a single-cell communication system, and without loss of generality, the cell is referred to as cell #1.
  • the network device 110 in FIG. 1 can be a network device in cell #1, or the network device 110 can serve a terminal device (such as terminal device 120) in cell #1.
  • a cell can be understood as an area within the coverage of wireless signals of network equipment.
  • Wireless communication between communication devices may include: wireless communication between network devices and terminals, wireless communication between network devices and network devices, and wireless communication between terminal devices and terminal devices.
  • wireless communication can also be referred to as “communication”
  • communication can also be described as "data transmission”, “information transmission” or “transmission”.
  • terminal equipment is also referred to as “terminal device”, “terminal”, etc.
  • network equipment is also referred to as “network device”, “network side”, etc.
  • core network equipment is also referred to as “core network device”, “core network”, etc.
  • Multicast and broadcast service It is a service for multiple terminal devices, such as live broadcast service, public safety service, batch software update service, etc. As shown in Figure 2, the MBS service comes from the data server. First, the data server sends the MBS data to the core network device, then the core network device sends the MBS data to the base station, and finally the base station sends the MBS data to at least one UE that receives the MBS service.
  • the MBS service When sending from the core network to the base station, the MBS service is transmitted through a common transmission channel MBS session. Each MBS session can contain at least one MBS quality of service (QoS) flow.
  • QoS quality of service
  • the data packet When sending from the base station to the UE, the data packet is transmitted through the MBS radio bearer.
  • PTM point to multi-point
  • PTP point to point
  • Multicast service is designed for services with high QoS requirements. It can provide the same QoS level as unicast service. Group management is required for multicast service. Specifically, as shown in Figure 3, for multicast service, the core network needs to manage the joining and exiting of UE. The transmission between the core network and the base station relies on the protocol data unit session (PDU session), and the MBS QoS flow is introduced.
  • the radio access network (RAN) supports PTP and PTM transmission modes to send data to the UE, and supports dynamic switching between PTP and PTM controlled by the RAN. Among them, for the PTM transmission mode, multiple UEs can use the same group radio network temporary identifier (g-RNTI) for descrambling. For the PTP transmission mode, each UE uses its own cell radio network temporary identifier (C-RNTI) for monitoring.
  • g-RNTI group radio network temporary identifier
  • C-RNTI cell radio network temporary identifier
  • Multicast broadcast control channel and multicast broadcast service channel Two logical channels are introduced in the broadcast technology of NR MBS, namely, multicast broadcast control channel (MBS control channel, MCCH) and multicast broadcast service channel (MBS traffic channel, MTCH).
  • MCCH is used to transmit control information, including MTCH configuration information, such as g-RNTI and DRX parameters corresponding to MTCH.
  • MCCH is sent in a periodic manner.
  • MTCH logical channel is used to carry user data of broadcast services.
  • MTCH is scheduled through MCCH.
  • MTCH is configured at the level of per g-RNTI, or per MBS service. Among them, the base station schedules service data to multiple UEs at the same time through g-RNTI, and each g-RNTI can be associated with at least one broadcast service.
  • the above channels may correspond to different names.
  • the multicast broadcast service control channel may be a single cell multicast broadcast service control channel (single cell MCCH, SC-MCCH).
  • the multicast broadcast service control channel may be MC-MCCH.
  • channels with similar functions to the multicast broadcast service control channel may have other names, or channels with the same functions may have different names in different communication environments, communication scenarios or communication technologies.
  • different names for channels with similar or identical functions in different systems do not limit the channel content and function.
  • the multicast broadcast control channel in this application can be used to transmit control information, multicast broadcast service control channel, and multicast broadcast service control channel.
  • the broadcast service channel can be used to transmit user data.
  • MCCH is used in this application to represent a multicast broadcast service control channel
  • MTCH is used to represent a multicast broadcast service channel
  • Multicast broadcast control channel modification notification As shown in Figure 4, MCCH is repeatedly sent in each modification period (MP), including the repetition period (RP) in the figure. In one MP, the content of MCCH is the same.
  • MP modification period
  • the network device sends a PDCCH containing a modification notification, and the modification notification is MCCH change notification.
  • the UE detects the field corresponding to MCCH change Notification on the PDCCH, for example, 2 bits, it is considered that the modification notification is detected, and the UE re-acquires the MCCH.
  • the UE When acquiring the MCCH, the UE needs to detect the PDCCH scrambled by MCCH-RNTI to obtain the scheduling information of the MCCH.
  • the first bit in the MCCH modification notification indicates that the reason for the MCCH modification is the start of the session
  • the second bit in the MCCH modification notification indicates that the reason for the MCCH modification is the session modification, session stop or neighbor cell list update.
  • RRC state There are three RRC states in NR: RRC idle state (RRC_IDLE), RRC inactive state (RRC_INACTIVE), and RRC connected state (RRC_CONNECTED). The following is a brief introduction to the three RRC states.
  • RRC_CONNECTED RAN has the context of UE, and UE and RAN have signaling connection. UE can receive messages and system messages sent by RAN to control UE data transmission, handover, and notify UE of relevant scheduling information, and RAN can receive channel quality information fed back by UE.
  • RRC connection state can be referred to as connection state.
  • RRC_INACTIVE RRC inactive state: The RAN and the core network are connected, and no resources are allocated to the air interface, which can enable rapid service recovery and improve the experience of delay-sensitive applications.
  • the power saving effect of users in the inactive state can be close to that of the idle state, extending the battery life of the mobile phone.
  • the RRC inactive state can be referred to as the inactive state.
  • RRC_IDLE RAN has no context for the UE, and the UE and RAN have no signaling connection. In this state, the UE can receive system messages and paging messages, and perform cell selection and reselection.
  • the RRC connection establishment is triggered. After the RRC connection is established, the UE enters the RRC connected state.
  • the RRC idle state can be referred to as the idle state.
  • FIG5 shows a schematic diagram of the switching of the RRC state of the UE.
  • the transition of the UE from the RRC_connected state to the RRC inactive state can be achieved through the RRC release message.
  • the base station When the UE is released from the RRC connected state to the RRC inactive state, the base station will allocate an inactive radio network temporary identifier (I-RNTI) to the UE and store the UE context with this identifier.
  • I-RNTI inactive radio network temporary identifier
  • This base station is also called the last serving gNB of the UE, or the anchor gNB.
  • the connection between the UE and the core network will be stored in the anchor gNB.
  • the anchor gNB controls the UE to enter the RRC inactive state and allocates the UE context identifier and RNA management area information (e.g., RNA) to the UE.
  • RNA management area information e.g., RNA
  • the anchor gNB does not need to notify the RAN node corresponding to the RNA (except for periodic RNA).
  • the anchor area will notify the RAN node corresponding to the RNA node.
  • the UE when the UE requests to resume a previously suspended RRC connection or to update the RAN notification area (RNA), the UE sends an RRC resume request message to the serving base station, and the serving base station and the anchor base station restore the UE to the connected state. This is shown in Figure 6.
  • Fig. 6 is an example of terminal device connection recovery. As shown in Fig. 6, the method includes the following steps.
  • RRC resume request RRC resume request
  • the UE in the RRC inactive state may send an RRC recovery request message to the serving base station.
  • the serving base station initiates a retrieve UE context request message to the anchor base station.
  • the anchor base station replies with a retrieve UE context response message to the serving base station.
  • the obtain UE context response message includes the context of the UE connection state.
  • the serving base station sends an RRC recovery message to the UE.
  • the serving base station triggers RRC connection recovery according to the context of the UE connection state, and sends an RRC recovery message to the UE.
  • the UE recovers the RRC connection according to the RRC recovery message, thereby entering the connection state.
  • the UE After entering the connected state, the UE sends an RRC resume complete message.
  • the serving base station initiates a path switching process to the core network, switches the connection between the UE and the core network from the anchor base station to the current serving base station, that is, performs context migration, and completes the UE connection recovery process, which specifically includes S206-S209.
  • the serving base station initiates an Xn-U address indication process to the anchor base station.
  • the serving base station sends a signal to the access and mobility management function (AMF) network element Send a path switch request message.
  • AMF access and mobility management function
  • AMF sends a path switch response message to the serving base station.
  • the serving base station sends a UE context release (UE context release) message to the anchor base station.
  • UE context release UE context release
  • the standard also supports the connection recovery process without entering the connected state. For example, when the UE triggers a connection recovery request for RNA update, the UE has no data to transmit.
  • the anchor base station may choose to continue to release the UE to the RRC inactive state. At this time, no context migration or state transition is required, as shown in Figure 7.
  • Fig. 7 is another example of terminal device connection recovery. As shown in Fig. 6, the method includes the following steps.
  • RRC resume request RRC resume request
  • the UE in the RRC inactive state may send an RRC recovery request message to the serving base station, and the RRC recovery request message may include that the reason for the request is RNA update.
  • the serving base station initiates a retrieve UE context request message to the anchor base station.
  • the anchor base station replies to the serving base station with a retrieve UE context failure message.
  • the serving base station sends an RRC release message to the UE, instructing the UE to suspend the RRC connection.
  • the UE is still in the RRC inactive state.
  • MBS broadcast configuration adopts a two-step configuration method.
  • the network device indicates the MCCH configuration for MBS broadcast in the system message, such as system information block (SIB) 20, including the repetition period and offset of MCCH, the duration of MCCH window, the starting time slot of MCCH window, and the MCCH change period.
  • SIB system information block
  • MCCH can be received.
  • MCCH (or the information sent through the MCCH channel) is transmitted periodically, with a configured repetition period, and within the configured MCCH transmission window.
  • MCCH includes the configuration information of the broadcast session and the MTCH scheduling information.
  • the configuration information of the broadcast session includes the identifier of the broadcast session, the MBS radio bearer (MRB) configuration, G-RNTI, etc.
  • MBS radio bearer (MRB) configuration After reading the configuration information and MTCH scheduling information of the broadcast session, the terminal device can correctly receive the MBS broadcast session.
  • MBS radio bearer (MRB) configuration After reading the configuration information and MTCH scheduling information of the broadcast session, the terminal device can correctly receive the MBS broadcast session.
  • a terminal device When a terminal device is interested in receiving MBS broadcast services, it should perform the MCCH message acquisition process.
  • a terminal device that is interested in receiving MBS broadcast services should perform the MCCH message acquisition process when entering a cell that provides SIB20. For example, when a terminal device that is receiving or interested in receiving MBS broadcast services receives a change notification, it will re-acquire SIB 20 to obtain a new MCCH. Before the terminal device acquires a new MCCH message, the terminal device will apply the previously acquired MCCH message. For another example, since MCCH is configured per cell, the MBS configuration carried by the MCCH of each cell may be different.
  • MBS broadcast supports the use of MCCH change notifications to notify the UE of the start of a broadcast session, as well as MCCH message changes for ongoing broadcast sessions, including MBS session stop.
  • terminal devices can only receive data of multicast sessions in RRC connected state.
  • the network device sends MBS multicast configuration to the terminal device through dedicated signaling, such as RRC reconfiguration message (RRCReconfiguration message), including multicast MRB configuration, multicast common frequency resource (CFR) configuration, physical layer configuration (also called layer 1/L1 configuration), multicast G-RNTI, etc.
  • RRCReconfiguration message RRC reconfiguration message
  • CFR multicast common frequency resource
  • the network device can switch the terminal device to RRC idle or RRC inactive state.
  • the group notification mechanism is used to notify the terminal device in RRC idle or RRC inactive state that there is multicast session data to be sent. For example, after CN paging, for example, CN can notify RAN of multicast activation to trigger RAN paging, and for example, RAN paging is triggered after multicast session data arrives at RAN. After receiving the group notification, the terminal device re-establishes the RRC connection with the network device. The group notification is sent to the terminal device via a paging message.
  • the paging message used for group notification contains the MBS session ID (ie TMGI), which is used to page all terminal devices in the RRC idle and RRC inactive states that are associated with a certain MBS multicast session.
  • TMGI MBS session ID
  • the terminal device After receiving the paging message, the terminal device determines that the paging message contains the TMGI of the multicast session that the terminal device has joined. The terminal device then triggers RRC connection establishment or RRC connection recovery. After entering the connected state, the terminal device can receive data from the multicast session.
  • R18 supports terminal devices receiving multicast in the RRC inactive state. For example, when the terminal device has no unicast service but only multicast service, the network can release the terminal device to the RRC inactive state to receive multicast. In this way, the number of terminal devices in the RRC connected state in the network can be reduced, which is beneficial to alleviate network congestion and energy saving of terminal devices.
  • the protocol does not define how a terminal device receives MBS in an RRC inactive state.
  • the terminal device needs to obtain a multicast configuration so that it can receive the data of the multicast session according to the multicast configuration.
  • One possible way is to provide the multicast configuration to the terminal device by broadcasting the system message broadcast by the cell. For example, a method similar to the above-mentioned broadcast session is adopted to send the multicast configuration to the terminal device in MCCH, and the MCCH configuration can still indicate MCCH in SIB. However, through the broadcast method, the terminal device that has not joined the multicast session can also receive the MCCH configuration, so that the multicast configuration can be obtained, which has potential security risks.
  • the present application provides a solution, which enables only UEs that join the multicast service to obtain the multicast configuration, thereby improving the security of MCCH.
  • indication can include direct indication, indirect indication, explicit indication, implicit indication.
  • indication information can include direct indication, indirect indication, explicit indication, implicit indication.
  • the information indicated by the indication information is referred to as the information to be indicated.
  • the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated.
  • the information to be indicated can also be indirectly indicated by indicating other information, wherein there is an association relationship between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance.
  • the indication of specific information can also be achieved with the help of the arrangement order of each information agreed in advance (such as specified by the protocol), thereby reducing the indication overhead to a certain extent.
  • Fig. 8 is a schematic diagram of a communication method 400 provided in an embodiment of the present application.
  • the method 400 may include the following steps.
  • a first network device sends first information to a terminal device, and correspondingly, the terminal device receives the first information.
  • the first information includes at least one MCCH configuration and a valid area of the at least one MCCH configuration.
  • MCCH configuration can also be called MCCH configuration parameters or MCCH reception parameters, which are used by the terminal device to determine the time domain resources, frequency domain resources, descrambling codes, etc. for receiving MCCH.
  • MCCH configuration can include at least one of the following: MCCH window information, MCCH modification period, MCCH frequency domain resources, MCCH radio network temporary identifier (MCCH-RNTI), and one MCCH configuration consists of at least one of the above items.
  • the effective area is also called an available area, an applicable area or a valid area.
  • the effective area of the MCCH configuration means that within the effective area, the terminal device can use the corresponding MCCH configuration to receive the MCCH.
  • the effective area may be a cell list, a tracking area (TA) list, a radio access network notification area (RNA) list, or a combination of at least two lists. Any of the above lists may also include only one element, that is, the effective area may be a cell, a TA, or an RNA.
  • the cell list may be a list of cell identifiers (IDs), such as a physical cell identifier (PCI) list, a cell global identifier (CGI) list, etc.
  • the tracking area (TA) list may be a list composed of tracking area identifiers.
  • the RNA (RAN-Notification Area) list may be a list composed of RAN area codes (RAN-Area Code).
  • the effective area corresponding to MCCH configuration #1 is cell 1, cell 2, and cell 3, and the effective area corresponding to MCCH configuration 2 is cell 4, cell 5, or cell 6.
  • the effective area corresponding to MCCH configuration #1 is cell 1
  • the effective area corresponding to MCCH configuration #2 is cell 2.
  • the effective area may also be an MCCH area defined by the protocol, denoted as MCCH-area, and each MCCH area may be indicated by a first identifier, which may also be referred to as an MCCH area identifier, i.e., MCCH-area ID.
  • MCCH-area-1, MCCH-area-2, MCCH-area-3, etc. are configured.
  • Each MCCH area includes at least one cell. For example, if MCCH configuration #1 corresponds to an MCCH area identifier of MCCH-area-1, then all cells belonging to MCCH-area-1 are considered to be the effective area of MCCH configuration #1.
  • each cell may broadcast the MCCH area identifier corresponding to the MCCH area to which it belongs in a system message.
  • the MCCH configuration may include multiple MCCH configurations, each applicable to a different session or service.
  • one MBS multicast or a group of MBS multicast services corresponds to one MCCH configuration.
  • some parameters of the MCCH configurations of all services are the same, and some parameters are the same.
  • the numbers are different.
  • the MCCH window parameters, modification period and other parameters in the MCCH configuration may be the same, but the MCCH-RNTIs corresponding to different services are different.
  • the first information includes an identifier of a multicast broadcast service MBS corresponding to each MCCH configuration in at least one MCCH configuration.
  • different MCCH configurations can be configured for different MBS services.
  • terminal 1 can receive MBS service 1 through MCCH channel 1
  • terminal 2 can receive MBS service 2 through MCCH channel 2, thereby preventing the terminal receiving MBS service 2 from knowing the MCCH channel configuration of MBS service 1, thereby further enhancing security.
  • the terminal device may be in a connected state when receiving the first information.
  • the first information may be carried in dedicated signaling, such as an RRC release message or an RRC reconfiguration message.
  • the terminal device may save the first information for subsequent determination of the MCCH configuration.
  • the second network device sends second information to the terminal device, and correspondingly, the terminal device receives the second information.
  • the second information is used by the terminal to determine whether the service cell belongs to the effective area of at least one MCCH configuration.
  • the second information may be an identifier of the first area or an identifier of a cell.
  • the second information may be a cell identifier, such as PCI or CGI, and the terminal may determine whether the serving cell belongs to the cell list corresponding to the MCCH effective area according to the cell identifier.
  • a cell identifier such as PCI or CGI
  • the second information may be a TA identifier
  • the terminal may determine whether the serving cell belongs to the TA list corresponding to the MCCH effective area according to the TA identifier.
  • the second information may be an MCCH area identifier
  • the terminal may determine whether the serving cell belongs to the MCCH area identifier list corresponding to the MCCH effective area according to the MCCH area identifier.
  • the second network device and the first network device may be the same network device, for example, the terminal device does not reselect a cell after receiving the first information, or the cell after the terminal device reselects is still managed by the first network device.
  • the second network device and the first network device may be different network devices, for example, the terminal device reselects a cell after receiving the first information, and the cell after the terminal device reselects is managed by the second network device.
  • the second network device may be a base station to which the current serving cell of the terminal device belongs, and the first network device may be an anchor base station of the terminal device. If the second network device and the first network device are the same network device, the second network device may be a base station to which the current serving cell of the terminal device belongs, and also an anchor base station of the terminal device.
  • the terminal device may be in an inactive state or an idle state when receiving information from the first area.
  • the second information may be carried in public signaling, such as a paging message or a system message, or a synchronization channel, or a master information block (MIB).
  • the system message for sending the second information may be a system information block (SIB), such as SIB 1, SIB20, etc.
  • the terminal device can obtain the identifier of the first area or the identifier of the cell sent by the second network device. Based on the identifier of the first area or the identifier of the cell, the terminal device can determine the corresponding MCCH configuration, and then receive the MCCH information based on the corresponding MCCH configuration.
  • the second network device may send a group paging message to the UE when the MBS service is activated, and carry the MCCH area identifier in the group paging message, so that when the terminal receives the group paging, the MCCH configuration information to be used is determined according to the MCCH area identifier, and the MCCH message is received according to the MCCH configuration information, so that the terminal can obtain the MCCH configuration information in time when the service is activated.
  • the terminal device can obtain a system message broadcast by a network device (for example, a second network device) of the reselected target cell.
  • the system message includes an identifier of the cell or an identifier of the effective area to which the cell belongs.
  • the cell is also the service cell of the terminal device.
  • the terminal device can receive the MCCH according to the MCCH configuration configured by the dedicated signaling. If the reselected target cell is not within the effective area, the terminal device can initiate a connection recovery process, and the network device can send the MCCH configuration to the terminal device via dedicated signaling.
  • the MCCH information may also be referred to as an MCCH message, which refers to a message sent via the MCCH.
  • the MCCH information may include MBS configuration information, such as broadcast configuration information and/or multicast configuration information, according to which the terminal device may receive a multicast session.
  • the second network device sends an MCCH message on the first MCCH channel, the first MCCH channel uses the first MCCH configuration, and correspondingly, if the first area identifier or the cell identifier belongs to the effective area, the terminal device is in the idle state according to the first MCCH configuration. Or receive the MCCH message from the second network device in an inactive state; if the identifier of the first area or the identifier of the cell does not belong to the effective area, the terminal device sends a wireless resource control RRC recovery request message to the second network device, and then the second network device sends a second MCCH configuration to the terminal device, and the terminal device can use the second MCCH configuration to receive the MCCH message.
  • the terminal device can receive MCCH information in an idle state or an inactive state according to the first MCCH configuration corresponding to the identifier of the first area or the identifier of the cell.
  • the identifier of the first area or the identifier of the cell has a corresponding relationship with the first MCCH configuration, or in other words, the first MCCH configuration can be determined according to the identifier of the first area or the identifier of the cell.
  • the first information includes the first MCCH configuration and the identifier of the first area or the identifier of the cell, and the effective area corresponding to the first MCCH includes the identifier of the first area or the identifier of the cell.
  • the effective areas of MCCH configuration #1 are cell 1, cell 2, and cell 3. If the reselected cell is cell 1, cell 2, or cell 3, the terminal device determines that MCCH configuration #1 can be used to continue receiving MCCH information.
  • the effective area of MCCH configuration #1 is MCCH-area-1
  • the system message of the current cell indicates that the current cell belongs to MCCH-area-1
  • the terminal device determines that it can receive MCCH information according to MCCH configuration #1.
  • the area identifier of the MCCH configuration carried in the paging message is area #1, and the UE determines whether the MCCH configuration can be obtained according to the area identifier in the paging message and the effective area in the first information saved by itself. For example, it is determined whether the first information includes the area identifier in the paging message, and if so, the MCCH configuration in the first information is used to receive the MCCH information, and if the MCCH configuration cannot be obtained, the RRC connection recovery process is triggered.
  • the terminal device can initiate an RRC recovery message to the second network device. Further, the second network device can send a second MCCH configuration to the terminal device, and the terminal device can receive MCCH information according to the second MCCH.
  • the second MCCH configuration and the first MCCH can be the same or different.
  • the effective area of MCCH configuration can be pre-configured to the terminal device.
  • the terminal device can obtain the identifier of the first area or the identifier of the cell through public signaling.
  • the terminal device can use the MCCH configuration in the dedicated signaling to receive MCCH information.
  • the terminal device can receive the MCCH configuration in further dedicated signaling through the RRC reply process. In this way, the terminal device can obtain the MCCH configuration.
  • it can also prevent terminal devices that have not joined the multicast session from obtaining the MCCH configuration, thereby ensuring the security of the MCCH.
  • the terminal device can also determine a corresponding MCCH configuration according to the identifier of the first area or the identifier of the cell. In this way, the terminal can obtain the MCCH configuration more quickly, thereby improving communication efficiency.
  • the method further includes: the first network device receives third information from the third network device, the third information includes N MCCH configurations and their corresponding effective areas of the MCCH configurations, N is a positive integer, and the first network generates the first information according to the third information.
  • the first network device can combine the third information sent by multiple second network devices to determine a total area corresponding to the MCCH configuration information, and then send the total area to the third network device.
  • the first network device may also determine fourth information, and the fourth information is determined according to the MCCH configuration information used by the first network device.
  • the fourth information includes R MCCH configurations used by the first network device and their corresponding effective areas, where R is a positive integer.
  • the first network device uses MCCH channel 1 in cell 1 and MCCH channel 2 in cell 2, then the fourth information includes the configuration parameters of MCCH channel 1 and the effective area (cell 1) and the configuration parameters of MCCH channel 2 and the effective area (cell 2).
  • the first network device may send the fourth information to the third network device.
  • the first network device may integrate the third information sent by multiple second network devices and the R MCCH configurations used and their corresponding effective areas determined by it, determine a total area corresponding to the MCCH configuration information, and then send the total area to the third network device.
  • the third network device may be a neighboring base station of the first network device.
  • the network devices in the effective area can coordinate and synchronize the MCCH configuration.
  • the MCCH configuration in the effective area is the same through coordinated configuration.
  • base station #1 an example of the first network device
  • the base station can generate the MCCH configuration and The corresponding index is sent to other base stations around the MCCH configuration and index.
  • the base stations exchange MCCH configuration, the identifier of the cell managed by the base station can be carried.
  • the base station may also notify other base stations to stop sending MCCH, carrying the MCCH configuration index and the indication of turning off.
  • the RRC recovery request may include a cause value of MCCH configuration acquisition or multicast reception.
  • the terminal device can receive MCCH information according to the first MCCH configuration, the terminal device can obtain the multicast service reception configuration parameters corresponding to the multicast session joined by the terminal device according to the MCCH information, and receive the multicast service according to the multicast service reception configuration parameters.
  • the terminal device can initiate a connection recovery process, and the cause value can be set as multicast reception in the RRC recovery request message.
  • the second network device can send an RRC release message to the terminal device, carrying the MCCH configuration of the current cell, for example, the second MCCH configuration.
  • not detecting MCCH information according to the MCCH configuration includes: detecting the MCCH window, and not detecting the downlink control information (DCI) sent by the MCCH-RNTI in M consecutive MCCH windows, where M is greater than or equal to 1.
  • DCI downlink control information
  • the second network device may directly send the second MCCH configuration to the terminal device.
  • the second network device may coordinate with the anchor base station (e.g., the first network device) to send the second MCCH configuration to the terminal device.
  • the second network device may send a request to obtain a UE context to the anchor base station, the request including a reason value of MCCH configuration acquisition or multicast reception, and the anchor base station sends the second MCC configuration to the second network device.
  • Method 1 includes the following steps:
  • the terminal device triggers the connection recovery process.
  • the first cause value is set in the RRC recovery request message, and the specific first cause value may be obtaining MCCH configuration or multicast connection.
  • the serving base station After receiving the RRC recovery request message, the serving base station determines that it is necessary to provide the terminal device with the MCCH configuration according to the first cause value.
  • the serving base station may send the MCCH configuration of the cell currently accessed by the terminal device to the anchor base station.
  • the serving base station can judge based on the terminal device identifier carried in the RRC recovery request message that the current serving base station is not the anchor base station of the UE and does not have the UE's secret key information, so it cannot generate an encrypted RRC message, nor can it send the MCCH configuration to the UE through an encrypted RRC message. Therefore, the serving base station can send the MCCH configuration information of the cell currently accessed by the UE to the anchor base station, and the anchor base station generates an encrypted RRC message and sends it to the UE through the serving base station.
  • the MCCH configuration information may be carried in the context acquisition request.
  • the serving base station also carries the first cause value in the context acquisition message.
  • the serving base station carries indication information, which is used to instruct the anchor base station to carry the MCCH message in the RRC release message, and the RRC release message is an encrypted RRC message.
  • the anchor base station carries the MCCH configuration information in the RRC release message and sends it to the serving base station.
  • the RRC release message may be carried in the context acquisition failure message.
  • the serving base station sends an RRC release message to the UE so that the UE obtains the MCCH configuration.
  • the UE obtains the MCCH configuration according to the RRC release message, and continues to remain in the RRC inactive state, and reads the MCCH message according to the MCCH configuration to obtain the multicast service reception configuration parameters.
  • Method 2 includes the following steps:
  • the serving base station After receiving the RRC recovery request message, the serving base station determines that it is necessary to provide MCCH configuration to the terminal device according to the first cause value, and sends a context acquisition message to the anchor base station.
  • the serving base station can judge based on the UE identifier carried in the RRC recovery request message that the current serving base station is not the anchor base station of the UE and does not have the secret key information of the UE, so it cannot generate an RRC message, nor can it send the MCCH configuration to the UE through an encrypted RRC message.
  • the serving base station can send a context acquisition request to the anchor base station, thereby migrating the UE context to the serving base station, so that the serving base station becomes the new anchor base station of the UE, so that the serving base station can send an RRC message to the UE to notify the MCCH configuration information to the UE, and the RRC message is an encrypted RRC message.
  • the anchor base station sends the UE context to the serving base station.
  • the anchor base station sends the UE context to the serving base station through up and down acquisition response messages.
  • the serving base station can obtain the UE's secret key, and the serving base station initiates a path switching process to the core network, migrating the connection between the UE and the core network to the current serving base station, so that the serving base station becomes the UE's new anchor base station.
  • the serving base station sends an RRC release message to the UE, carrying the MCCH configuration information, so that the UE obtains the MCCH configuration.
  • the UE obtains the MCCH configuration according to the RRC release message and continues to remain in the RRC inactive state. It reads the MCCH message according to the MCCH configuration and then obtains the multicast service reception configuration parameters.
  • the RRC release message is an encrypted RRC message.
  • Fig. 9 is a schematic flow chart of a communication method 500 provided in an embodiment of the present application.
  • the method 500 can be regarded as a specific implementation of the method 400. As shown in Fig. 9, the method 500 includes the following steps.
  • a UE an example of a terminal device
  • the UE can initiate an RRC connection establishment process or an RRC connection recovery process to a network device, depending on the state of the UE.
  • the UE can use the RRC connection to send a request to join multicast session #1, which includes an identifier of the multicast session to be joined to the core network, for example, the identifier of the multicast session is TMGI.
  • the core network After the core network authenticates that the UE can join multicast session #1, the core network sends an indication to the access network, indicating the access network information about the multicast session that the UE has joined, wherein the information about the multicast session includes the identifier of multicast session #1 and the QoS information corresponding to the multicast session.
  • the core network can carry the above indication through a protocol data unit (PDU) session establishment or modification message.
  • PDU protocol data unit
  • the access network sends the multicast service reception configuration parameters of multicast session #1 to the UE according to the information of the multicast session joined by the UE.
  • the multicast service reception configuration parameters include: 1) multicast common frequency resource (CFR), 2) G-RNTI used by the multicast service, 3) search space of the multicast service, control resource set (CORESET) information of the multicast service, etc., 4) physical downlink shared channel (PDSCH) parameters of the multicast service, including scrambling code and rate matching parameters, 5) MRB of the multicast service, including MRB ID, corresponding packet data convergence protocol (PDCP) parameters, etc. 6) multicast radio link control (RLC) channel configuration, including MRB ID associated with RLC, length of sequence number (SN) of RLC, RLC mode and other information.
  • CFR multicast common frequency resource
  • G-RNTI used by the multicast service
  • CORESET control resource set
  • PDSCH physical downlink shared channel
  • MRB including MRB ID, corresponding packet data convergence protocol (PDCP) parameters
  • step S501 may be executed; otherwise, this step may be skipped.
  • the UE may receive the data of the multicast session #1 in the connected state according to the multicast service reception configuration parameters configured by the access network.
  • cell #1 determines to let the UE enter an inactive state to receive multicast session #1.
  • Cell #1 may switch the UE to an inactive state for data reception based on certain factors, for example, there are too many connected users in the current cell and no more connected UEs can be accommodated, or the UE expects to receive multicast services in a more power-saving mode.
  • cell #1 sends an RRC release message to the UE.
  • the RRC release message may include information #1 (an example of the first information), where information #1 includes MCCH configuration #1 and an effective area of MCCH configuration #1, for example, the effective areas are MCA 1 and MCA 2, and MCCH configuration #1 is used for the UE to receive configuration parameters for multicast services from the MCCH channel.
  • MCA is MCCH area.
  • Information #1 may be sent simultaneously with the RRC release message, or may be sent before the RRC release message, without limitation.
  • the UE After S503, the UE enters an inactive state.
  • Cell #1 may include the MCCH area to which cell #1 belongs, namely, MCA ID 1, in SIB 1. After the UE obtains SIB 1, it determines that MCCH configuration #1 can be used based on the fact that MCA ID 1 in SIB1 belongs to the effective area.
  • the UE receives the MCCH message according to MCCH configuration #1 and obtains the multicast service reception configuration parameters.
  • the UE receives data of the multicast session #1 in an inactive state.
  • the UE receives the data of the multicast session #1 in an inactive state according to the multicast service reception configuration parameters.
  • Cell #1 may include the MCCH area to which cell #2 belongs in SIB 1, assuming that cell #2 also belongs to MCA ID 1. After the UE obtains SIB1, it determines that it can continue to use MCCH configuration #1 based on the fact that MCA ID 1 in SIB 1 belongs to the effective area.
  • cell #1 broadcasts MCCH.
  • the UE receives the MCCH message according to MCCH configuration #1 and obtains the multicast service reception configuration parameters.
  • the UE receives data of multicast session #1 in an inactive state.
  • the UE receives the data of the multicast session #1 in an inactive state according to the multicast service reception configuration parameters.
  • cell #1 and cell #2 may belong to the same network device, for example, both belong to the first network device.
  • Cell #1 and cell #2 may also belong to different network devices, for example, cell #1 belongs to the first network device, and cell #2 belongs to the second network device.
  • the effective area of MCCH configuration can be pre-configured to the terminal device.
  • the terminal device can determine the identifier of the first area or the identifier of the cell through public signaling.
  • the terminal device can use the MCCH configuration in the dedicated signaling to receive MCCH information.
  • the terminal device can receive the MCCH configuration in further dedicated signaling through the RRC reply process. In this way, terminal devices that have not joined the multicast session can be prevented from obtaining the MCCH configuration, thereby ensuring the security of the MCCH.
  • the terminal device can also determine a corresponding MCCH configuration according to the identifier of the first area or the identifier of the cell. In this way, the terminal can obtain the MCCH configuration more quickly, thereby improving communication efficiency.
  • the methods and operations implemented by the terminal device can also be implemented by components that can be formed by the terminal device (such as chips or circuits); in addition, the methods and operations implemented by the network device can also be implemented by components that can be formed by the network device (such as chips or circuits), without limitation.
  • the embodiments of the present application also provide corresponding devices, which include modules for executing the corresponding methods in the above-mentioned method embodiments.
  • the module can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the above-mentioned method embodiments are also applicable to the following device embodiments.
  • Fig. 10 is a schematic diagram of a communication device 2800 provided in an embodiment of the present application.
  • the device 2800 includes a transceiver unit 2810, which can be used to implement corresponding communication functions.
  • the transceiver unit 2810 can also be called a communication interface or a communication unit.
  • the device 2800 may further include a processing unit 2820, which may be used for performing data processing.
  • a processing unit 2820 which may be used for performing data processing.
  • the device 2800 also includes a storage unit, which can be used to store instructions and/or data, and the processing unit 2820 can read the instructions and/or data in the storage unit so that the device implements the actions performed by the terminal device or network device in the aforementioned method embodiments.
  • a storage unit which can be used to store instructions and/or data
  • the processing unit 2820 can read the instructions and/or data in the storage unit so that the device implements the actions performed by the terminal device or network device in the aforementioned method embodiments.
  • the device 2800 may be the terminal device in the aforementioned embodiment, or may be a component (such as a chip) of the terminal device.
  • the device 2800 may implement the steps or processes executed by the terminal device in the above method embodiment, wherein the transceiver unit 2810 may be used to perform the transceiver-related operations of the terminal device in the above method embodiment, and the processing unit 2820 may be used to perform the processing-related operations of the terminal device in the above method embodiment.
  • the apparatus 2800 is used to implement the functions of the terminal device in the method embodiment shown in the method 400 or 500 .
  • the transceiver unit 2810 is used to receive first information from a first network device, the first information including at least one MCCH configuration and at least one effective area of the MCCH configuration; the transceiver unit 2810 is also used to: receive second information from a second network device, the second information is used to indicate a first area identifier or a cell identifier.
  • the processing unit 2820 is used to: if the first area identifier or the cell identifier belongs to the effective area, then receive MCCH information from the second network device in an idle state or an inactive state according to the first MCCH configuration, the at least one MCCH configuration including the first MCCH configuration; if the first area identifier or the cell identifier does not belong to the effective area, then send a radio resource control RRC recovery request message to the second network device.
  • the device 2800 can also implement other steps, actions or methods related to the terminal device in the above method 400 or 500, which will not be repeated here.
  • the device 2800 may be the first network device in the aforementioned embodiment, or may be a component (such as a chip) of the first network device.
  • the device 2800 may implement the steps or processes corresponding to those performed by the first network device in the above method embodiment, wherein the transceiver unit 2810 may be used to perform the transceiver-related operations of the first network device in the above method embodiment, and the processing unit 2820 may be used to perform the processing-related operations of the first network device in the above method embodiment.
  • the apparatus 2800 is used to implement the function of the first network device in the method embodiment shown in 400 or 500 .
  • the transceiver unit 2810 is used to send first information to the terminal device, the first information includes at least one MCCH configuration and at least one effective area of the MCCH configuration, and the at least one MCCH configuration includes the first MCCH configuration.
  • the transceiver unit 2810 is also used to send an MCCH message using the first MCCH configuration on the first MCCH channel.
  • the device 2800 can also implement other steps, actions or methods related to the first network device in the above method 400 or 500, which will not be repeated here.
  • the device 2800 here is embodied in the form of a functional unit.
  • the term "unit” here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and/or other suitable components that support the described functions.
  • ASIC application specific integrated circuit
  • processor such as a shared processor, a dedicated processor or a group processor, etc.
  • memory for executing one or more software or firmware programs, a merged logic circuit and/or other suitable components that support the described functions.
  • the device 2800 can be specifically the terminal device in the above-mentioned embodiment, and can be used to execute the various processes and/or steps corresponding to the terminal device in the above-mentioned method embodiments, or the device 2800 can be specifically the first network device in the above-mentioned embodiment, and can be used to execute the various processes and/or steps corresponding to the first network device in the above-mentioned method embodiments. To avoid repetition, it will not be repeated here.
  • the device 2800 of each of the above schemes has the function of implementing the corresponding steps performed by the terminal device in the above method, or the device 2800 of each of the above schemes has the function of implementing the corresponding steps performed by the first network device in the above method.
  • the function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the transceiver operations and related processing operations in each method embodiment.
  • the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the transceiver operations and related processing operations in each method embodiment.
  • transceiver unit 2810 can also be a transceiver circuit (for example, can include a receiving circuit and a sending circuit), and the processing unit can be a processing circuit.
  • the device in FIG. 10 may be a network element or device in the aforementioned embodiment, or may be a chip or a chip system, such as a system on chip (SoC).
  • the transceiver unit may be an input and output circuit or a communication interface; the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip. This is not limited here.
  • the device 2900 includes a processor 2910, the processor 2910 is coupled to a memory 2920, the memory 2920 is used to store computer programs or instructions and/or data, and the processor 2910 is used to execute the computer program or instructions stored in the memory 2920, or read the data stored in the memory 2920, so as to execute the methods in the above method embodiments.
  • processors 2910 there are one or more processors 2910 .
  • memory 2920 is one or more.
  • the memory 2920 is integrated with the processor 2910 or provided separately.
  • the device 2900 further includes an interface circuit 2930.
  • the interface circuit 2930 is used for receiving and/or sending signals.
  • the processor 2910 and the interface circuit 2930 are coupled to each other.
  • the processor 2910 is used to control the interface circuit 2930 to receive and/or send signals.
  • the interface circuit 2930 may be a transceiver or an input/output interface.
  • the processor 2910 is used to implement the function of the processing unit 920
  • the interface circuit 2930 is used to implement the function of the transceiver unit 910 .
  • the device 2900 is used to implement the operations performed by the terminal device in the above method embodiments.
  • the processor 2910 is used to execute the computer program or instructions stored in the memory 2920 to implement the relevant operations of the terminal device in the above various method embodiments.
  • the apparatus 2900 is used to implement the operations performed by the first network device in each of the above method embodiments.
  • the processor 2910 is used to execute the computer program or instructions stored in the memory 2920 to implement the relevant operations of the first network device in each method embodiment above.
  • the terminal chip When the above communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiment.
  • the terminal chip receives information from other modules in the terminal (such as a radio frequency module or an antenna), and the information is sent by the base station to the terminal; or the terminal chip sends information to other modules in the terminal (such as a radio frequency module or an antenna), and the information is sent by the terminal to the base station.
  • processors mentioned in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASICs), or a processor.
  • the general purpose processor may be a microprocessor or any conventional processor.
  • the memory mentioned in the embodiments of the present application may be a volatile memory and/or a non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory may be a random access memory (RAM).
  • a RAM may be used as an external cache.
  • RAM includes the following forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • SLDRAM synchronous link DRAM
  • DR RAM direct rambus RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.
  • memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.
  • FIG12 is a schematic diagram of a chip system 3000 provided in an embodiment of the present application.
  • the chip system 3000 (or also referred to as a processing system) includes a logic circuit 3010 and an input/output interface 3020.
  • the logic circuit 3010 can be a processing circuit in the chip system 3000.
  • the logic circuit 3010 can be coupled to the storage unit and call the instructions in the storage unit so that the chip system 3000 can implement the methods and functions of each embodiment of the present application.
  • the input/output interface 3020 can be an input/output circuit in the chip system 3000, outputting information processed by the chip system 3000, or inputting data or signaling information to be processed into the chip system 3000 for processing.
  • the chip system 3000 is used to implement the operations performed by the terminal device in the above method embodiments.
  • the logic circuit 3010 is used to implement the processing-related operations performed by the terminal device in the above method embodiments, such as the processing-related operations performed by the terminal device in the embodiments shown in Figures 8 or 9;
  • the input/output interface 3020 is used to implement the sending and/or receiving-related operations performed by the terminal device in the above method embodiments, such as the sending and/or receiving-related operations performed by the terminal device in the embodiments shown in Figures 8 or 9.
  • the chip system 3000 is used to implement the operations performed by the first network device in each of the above method embodiments.
  • the logic circuit 3010 is used to implement the processing-related operations performed by the first network device in the above method embodiments, such as the processing-related operations performed by the first network device in the embodiments shown in Figures 8 or 9;
  • the input/output interface 3020 is used to implement the sending and/or receiving-related operations performed by the first network device in the above method embodiments, such as the sending and/or receiving-related operations performed by the first network device in the embodiments shown in Figures 8 or 9.
  • An embodiment of the present application also provides a computer-readable storage medium on which computer instructions for implementing the methods executed by the terminal device or the first network device in the above-mentioned method embodiments are stored.
  • the computer when the computer program is executed by a computer, the computer can implement the method executed by the terminal device or the first network device in each embodiment of the above method.
  • An embodiment of the present application also provides a computer program product, comprising instructions, which, when executed by a computer, implement the methods performed by the terminal device or the first network device in the above-mentioned method embodiments.
  • the embodiment of the present application further provides a communication system, which includes the terminal device and the first network device in the above embodiments.
  • the system includes the terminal device and the first network device in the embodiment shown in Figure 8 or Figure 9.
  • the disclosed devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
  • all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. At present, it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer can be a personal computer, a server, or a network device, etc.
  • the computer instructions can 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 instructions can be transmitted from a website site, a computer, a server, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server, or data center.
  • the computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that contains one or more available media integrated.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD), etc.
  • the aforementioned available medium includes, but is not limited to, various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente demande concernent un procédé de communication et un appareil de communication. Le procédé peut comprendre les étapes suivantes : un dispositif terminal reçoit des premières informations et des secondes informations, les premières informations comprenant au moins une configuration MCCH et une zone efficace de l'au moins une configuration MCCH, et les secondes informations étant utilisées pour indiquer un premier identifiant de zone ou un identifiant de cellule ; si le premier identifiant de zone ou l'identifiant de cellule appartient à la zone efficace, le dispositif terminal reçoit un message MCCH en provenance d'un second dispositif de réseau dans un état de veille ou un état inactif selon une première configuration MCCH, la première configuration MCCH étant déterminée selon le premier identifiant de zone ou l'identifiant de cellule ; et si le premier identifiant de zone ou l'identifiant de cellule n'appartient pas à la zone efficace, le dispositif terminal envoie un message de demande de rétablissement de commande de ressources radio (RRC) au second dispositif de réseau. De cette manière, le dispositif terminal peut obtenir la configuration MCCH. De plus, il est également possible d'empêcher un dispositif terminal, qui ne rejoint pas une session de multidiffusion, d'acquérir la configuration MCCH, ce qui permet de garantir la sécurité d'un MCCH.
PCT/CN2023/115378 2022-09-29 2023-08-29 Procédé et appareil de communication Ceased WO2024066858A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211204988.4 2022-09-29
CN202211204988.4A CN117793624A (zh) 2022-09-29 2022-09-29 一种通信的方法和装置

Publications (1)

Publication Number Publication Date
WO2024066858A1 true WO2024066858A1 (fr) 2024-04-04

Family

ID=90378661

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/115378 Ceased WO2024066858A1 (fr) 2022-09-29 2023-08-29 Procédé et appareil de communication

Country Status (2)

Country Link
CN (1) CN117793624A (fr)
WO (1) WO2024066858A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113596735A (zh) * 2020-04-30 2021-11-02 大唐移动通信设备有限公司 管控mbms业务广播区域的方法、基站及存储介质
CN113647150A (zh) * 2019-09-18 2021-11-12 Oppo广东移动通信有限公司 一种信息配置方法及装置、终端设备、网络设备
CN113853824A (zh) * 2019-10-26 2021-12-28 华为技术有限公司 一种通信方法及装置
WO2022030452A1 (fr) * 2020-08-03 2022-02-10 京セラ株式会社 Procédé de commande de communication, station de base et équipement d'utilisateur
CN115443667A (zh) * 2021-04-01 2022-12-06 北京小米移动软件有限公司 广播多播业务传输方法、装置及存储介质
CN115567981A (zh) * 2021-07-02 2023-01-03 维沃移动通信有限公司 多播业务接收、接收配置方法、装置、终端及网络侧设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113647150A (zh) * 2019-09-18 2021-11-12 Oppo广东移动通信有限公司 一种信息配置方法及装置、终端设备、网络设备
CN113853824A (zh) * 2019-10-26 2021-12-28 华为技术有限公司 一种通信方法及装置
CN113596735A (zh) * 2020-04-30 2021-11-02 大唐移动通信设备有限公司 管控mbms业务广播区域的方法、基站及存储介质
WO2022030452A1 (fr) * 2020-08-03 2022-02-10 京セラ株式会社 Procédé de commande de communication, station de base et équipement d'utilisateur
CN115443667A (zh) * 2021-04-01 2022-12-06 北京小米移动软件有限公司 广播多播业务传输方法、装置及存储介质
CN115567981A (zh) * 2021-07-02 2023-01-03 维沃移动通信有限公司 多播业务接收、接收配置方法、装置、终端及网络侧设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
TD TECH, CHENGDU TD TECH: "Multicast reception in RRC_INACTIVE state", 3GPP DRAFT; R3-225337, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. E-meeting; 20221010 - 20221018, 25 September 2022 (2022-09-25), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052265475 *

Also Published As

Publication number Publication date
CN117793624A (zh) 2024-03-29

Similar Documents

Publication Publication Date Title
US20230300938A1 (en) Methods and systems for managing mbs service continuity for a ue
US20230397299A1 (en) Method and apparatus for multicast and broadcast services
US12294915B2 (en) Service data transmission method and apparatus, and terminal device
WO2022126359A1 (fr) Procédés et appareils pour services de multidiffusion et de diffusion
WO2021051312A1 (fr) Procédé et appareil de configuration d'informations, équipement terminal et dispositif de réseau
CN113661722B (zh) 一种业务数据传输方法及装置、网络设备、终端设备
WO2018059294A1 (fr) Procédé de transmission d'informations de système, équipement utilisateur et dispositif côté réseau
WO2022006875A1 (fr) Procédé et appareil permettant d'établir un service mbs, ainsi que dispositif terminal et dispositif de réseau
CN117676891A (zh) 通信方法和通信装置
WO2022141255A1 (fr) Procédé et appareil de configuration mbs, dispositif de réseau et dispositif de terminal
CN117480857A (zh) 一种mbs业务的管理方法及装置、终端设备、网络设备
WO2023165588A1 (fr) Procédé et appareil de réception de service de multidiffusion, support de stockage, dispositif terminal et dispositif réseau
US20240365177A1 (en) Method for determining configuration information, terminal device and chip
TW202224454A (zh) 用於mbs的無線通信的裝置和方法
WO2019028918A1 (fr) Procédé de recherche de dispositif et dispositif associé
WO2022006849A1 (fr) Procédé et appareil de gestion d'état tci de service mbs et dispositif terminal
US20240349184A1 (en) A downlink multicast service transmission
EP4535921A1 (fr) Procédé et appareil pour déterminer une zone de service de multidiffusion inactive, et procédé et appareil pour configurer une zone de service de multidiffusion inactive
WO2024066858A1 (fr) Procédé et appareil de communication
WO2022133877A1 (fr) Procédé et appareil d'indication de service mbs, dispositif terminal et dispositif de réseau
EP4637190A1 (fr) Procédé et appareil de communication
WO2024066901A1 (fr) Procédé et appareil de communication
CN114846825B (zh) 一种数据转发方法及装置、通信设备
CN117835163A (zh) 一种通信的方法和装置
WO2024152843A1 (fr) Procédé de communication et appareil de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23870101

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 23870101

Country of ref document: EP

Kind code of ref document: A1