WO2023040748A1 - Procédé et appareil de commande de multidiffusion, procédé et appareil de commutation de configuration, et dispositif - Google Patents
Procédé et appareil de commande de multidiffusion, procédé et appareil de commutation de configuration, et dispositif Download PDFInfo
- Publication number
- WO2023040748A1 WO2023040748A1 PCT/CN2022/117843 CN2022117843W WO2023040748A1 WO 2023040748 A1 WO2023040748 A1 WO 2023040748A1 CN 2022117843 W CN2022117843 W CN 2022117843W WO 2023040748 A1 WO2023040748 A1 WO 2023040748A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- multicast
- side device
- pdu session
- terminal
- network side
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
-
- 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/12—Setup of transport tunnels
Definitions
- the present application belongs to the communication field, and in particular relates to a method, device and equipment for multicast control and handover configuration.
- unicast transmission is to establish an independent pipeline and an independent transmission processing mechanism for each user terminal (User Equipment, UE) according to the service requirements of the UE, and the consumption of resources is doubled with the increase of the number of UEs. increase.
- the multicast transmission is based on the planned multicast service plan, first collects a list of interested UEs, and then performs multicast establishment and transmission to the UEs in the list.
- the existing multicast services have relatively high transmission efficiency, the entire pre-preparation process is cumbersome due to the need for pre-planning and collection of UE interest lists, which is not conducive to the flexible and rapid establishment and transmission of dynamic multicast services according to needs. Therefore, It cannot solve more business and transmission requirements well.
- Embodiments of the present application provide a method, device and device for multicast control and handover configuration, which can solve the problem that the prior art cannot perform multicast control flexibly.
- a multicast control method including:
- the core network node sends multicast protocol data unit PDU session signaling to the first network side device based on the first information
- the first information includes at least one of the following:
- the first service is the same as the service transmitted by the multicast PDU session, and the first service is a service requested by the first terminal through the cell where the multicast PDU session is established or by the first network side device;
- a multicast PDU session update request is used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session, the second terminal moves out of the first network side device, and the second terminal joins
- the cell corresponding to the multicast PDU session and the service performed is the same as the service corresponding to the multicast PDU session;
- the second terminal stops receiving the multicast service transmitted by the multicast PDU session
- the second terminal is not interested in the multicast service transmitted by the multicast PDU session.
- a multicast control device which is applied to a core network node, including:
- a first sending module configured to send multicast protocol data unit PDU session signaling to the first network side device based on the first information
- the first information includes at least one of the following:
- the first service is the same as the service transmitted by the multicast PDU session, and the first service is a service requested by the first terminal through the cell where the multicast PDU session is established or by the first network side device;
- a multicast PDU session update request is used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session, the second terminal moves out of the first network side device, and the second terminal joins
- the cell corresponding to the multicast PDU session and the service performed is the same as the service corresponding to the multicast PDU session;
- the second terminal stops receiving the multicast service transmitted by the multicast PDU session
- the second terminal is not interested in the multicast service transmitted by the multicast PDU session.
- a multicast control method including:
- the first network side device receives the multicast protocol data unit PDU session signaling sent by the core network node.
- a multicast control device which is applied to a first network side device, including:
- the first receiving module is configured to receive the multicast protocol data unit PDU session signaling sent by the core network node.
- a switching configuration method including:
- the second network side device sends the first configuration information of the fourth terminal to the first network side device
- the second network side device receives the second configuration information fed back by the first network side device
- the first configuration information is the transmission configuration of the fourth terminal under the second network side device, and the first configuration information includes a correspondence relationship between a service flow and a unicast radio bearer and/or a multicast radio bearer, and the The second configuration information is the transmission configuration used after the fourth terminal switches to the first network side device.
- a handover configuration device which is applied to a second network side device, including:
- the second sending module is configured to send the first configuration information of the fourth terminal to the first network side device
- the second receiving module is configured to receive second configuration information fed back by the first network side device
- the first configuration information is the transmission configuration of the fourth terminal under the second network side device, and the first configuration information includes a correspondence relationship between a service flow and a unicast radio bearer and/or a multicast radio bearer, and the The second configuration information is the transmission configuration used after the fourth terminal switches to the first network side device.
- a core network node in a seventh aspect, includes a processor, a memory, and a program or instruction stored in the memory and operable on the processor.
- the program or instruction is executed by the When executed by the processor, the steps of the method described in the first aspect are realized.
- a core network node including a processor and a communication interface, wherein the communication interface is used to send multicast protocol data unit PDU session signaling to the first network side device based on the first information ;
- the first information includes at least one of the following:
- the first service is the same as the service transmitted by the multicast PDU session, and the first service is a service requested by the first terminal through the cell where the multicast PDU session is established or by the first network side device;
- a multicast PDU session update request is used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session, the second terminal moves out of the first network side device, and the second terminal joins
- the cell corresponding to the multicast PDU session and the service performed is the same as the service corresponding to the multicast PDU session;
- the second terminal stops receiving the multicast service transmitted by the multicast PDU session
- the second terminal is not interested in the multicast service transmitted by the multicast PDU session.
- a ninth aspect provides a network-side device, the network-side device is a first network-side device, including a processor, a memory, and a program or instruction stored in the memory and operable on the processor, When the program or instruction is executed by the processor, the steps of the method described in the third aspect are realized.
- a network-side device is a first network-side device, and includes a processor and a communication interface, wherein the communication interface is used to receive a multicast protocol data unit sent by a core network node PDU session signaling.
- a network-side device is provided, the network-side device is a second network-side device, including a processor, a memory, and a program or program stored in the memory and operable on the processor Instructions, when the program or instructions are executed by the processor, implement the steps of the method as described in the third aspect.
- a network-side device is a second network-side device, and includes a processor and a communication interface, wherein the communication interface is used to send the first configuration information of the fourth terminal to the The first network-side device; receiving second configuration information fed back by the first network-side device;
- the first configuration information is the transmission configuration of the fourth terminal under the second network side device, and the first configuration information includes a correspondence relationship between a service flow and a unicast radio bearer and/or a multicast radio bearer, and the The second configuration information is the transmission configuration used after the fourth terminal switches to the first network side device.
- a readable storage medium on which a program or an instruction is stored, and when the program or instruction is executed by a processor, the implementation as described in the first aspect, the third aspect, or the fifth aspect is achieved. steps of the method described above.
- a chip in a fourteenth aspect, there is provided a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the first aspect and the third Aspect or the step of the method described in the fifth aspect.
- a computer program product is provided, the computer program product is stored in a non-transitory storage medium, and the computer program product is executed by at least one processor to implement the first aspect and the third aspect Or the steps of the method described in the fifth aspect.
- an electronic device configured to execute the steps of the method described in the first aspect, the third aspect or the fifth aspect.
- dynamic control of the multicast can be performed according to the network status, which improves the flexibility of the multicast control.
- FIG. 1 is a block diagram of a wireless communication system to which an embodiment of the present application is applicable;
- FIG. 2 is one of the schematic flow diagrams of the multicast control method of the embodiment of the present application.
- FIG. 3 is one of the schematic diagrams of the modules of the multicast control device according to the embodiment of the present application.
- FIG. 4 is a structural block diagram of a core network node in an embodiment of the present application.
- FIG. 5 is a second schematic flow diagram of a multicast control method according to an embodiment of the present application.
- FIG. 6 is the second schematic diagram of the modules of the multicast control device according to the embodiment of the present application.
- FIG. 7 is a schematic flowchart of a handover configuration method according to an embodiment of the present application.
- FIG. 8 is a schematic diagram of modules of a switch configuration device according to an embodiment of the present application.
- FIG. 9 is a structural block diagram of a communication device according to an embodiment of the present application.
- first, second and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific sequence or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein and that "first" and “second” distinguish objects. It is usually one category, and the number of objects is not limited. For example, there may be one or more first objects.
- “and/or” in the description and claims means at least one of the connected objects, and the character “/” generally means that the related objects are an "or” relationship.
- LTE Long Term Evolution
- LTE-Advanced LTE-Advanced
- LTE-A Long Term Evolution-Advanced
- CDMA Code Division Multiple Access
- TDMA Time Division Multiple Access
- FDMA Frequency Division Multiple Access
- OFDMA Orthogonal Frequency Division Multiple Access
- SC-FDMA Single-carrier Frequency-Division Multiple Access
- system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used for the above-mentioned system and radio technology, and can also be used for other systems and radio technologies.
- NR New Radio
- the following description describes the New Radio (NR) system for illustrative purposes, and uses NR terminology in most of the following descriptions, but these techniques can also be applied to applications other than NR system applications, such as the 6th generation (6 th Generation, 6G) communication system.
- 6G 6th Generation
- Fig. 1 shows a block diagram of a wireless communication system to which the embodiment of the present application is applicable.
- the wireless communication system includes a terminal 11 and a network side device 12 .
- the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (Vehicle User Equipment, VUE), pedestrian terminal (Pedestrian User Equipment, PUE) and other terminal-side equipment, wearable devices include: smart watches, bracelets, earphones, glasses, etc.
- the network side device 12 may be a base station or a core network, where a base station may be called a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service Basic Service Set (BSS), Extended Service Set (ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, Wireless Local Area Network (WLAN) ) access point, wireless fidelity (Wireless Fidelity, WiFi) node, transmitting and receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to Specific technical terms, it should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the
- MBSFN Multimedia Broadcast Multicast Service Single Frequency Network
- SC-RTM single cell point-to-point Multipoint
- MBSFN Multimedia Broadcast Multicast Service
- SC-RTM single cell point-to-point Multipoint
- the biggest difference from the MBSFN method is that it is only scheduled and transmitted in a single cell, and is assigned by the group Radio Network Temporary Identifier (RNTI) (group RNTI, G-RNTI) for service scheduling.
- group RNTI group RNTI
- G-RNTI group Radio Network Temporary Identifier
- the scheduling information is notified by the Physical Downlink Control Channel (PDCCH) scrambled by G-RNTI.
- the data part is sent in multicast mode. It is equivalent to that the interested UE monitors the G-RNTI to obtain data scheduling and then receives it.
- PTP Point To Point
- PTM Point To Multipoint
- the network side can configure two paths for the UE to transmit at the same time, one is the PTP path (PTP leg), and the other is the PTM path (PTM leg).
- PTP path refers to the use of a common RNTI, such as G-RNTI, for PDCCH scrambling. All users in the group jointly monitor the scheduling of the G-RNTI and receive subsequent scheduling data.
- G-RNTI UE-specific cell radio network temporary identifier
- C-RNTI UE-specific cell radio network temporary identifier
- PTM transmits to multiple UEs at the same time, and the transmission efficiency is high, but it needs to comprehensively consider the coverage of all UEs, so the selection of transmission parameters needs to be applicable to all UEs as much as possible, such as using omnidirectional antennas, considering poor users link quality, etc., PTM may not be effective for individual UEs with extremely poor link quality.
- PTP is a dedicated transmission for a UE. You can adjust the transmission parameters by considering the link conditions of this user, such as using directional or shaped antennas, and setting appropriate transmission parameters according to the current UE link. Therefore, the transmission effect for a single UE is relatively low. Good, but if there are multiple users, multiple transmission resources are required, which is less resource efficient.
- the embodiment of the present application provides a multicast control method, including:
- Step 201 the core network node sends a multicast protocol data unit (Protocol Data Unit, PDU) session signaling to the first network side device based on the first information;
- PDU Protocol Data Unit
- the multicast PDU session signaling can be a multicast PDU session establishment signaling, or a multicast PDU session update signaling.
- the core network node can only send the first network side device Send multicast PDU session establishment signaling or multicast PDU session update signaling.
- the first information includes at least one of the following:
- the terminal information may refer to the number of terminals, because a control plane connection and a user plane pipeline need to be established for the terminal between the core network node and the first network side device, that is to say, the core network node can directly The number of terminals accessing the first network side device is acquired.
- the core network node can also directly obtain what kind of service the terminal performs, and the service information is mainly used to distinguish the service type and service content.
- A13 The home cell of the terminal accessing the first network side device
- the home cell is a cell that the terminal accesses under the first network side device, and it can also be understood that the home cell is a serving cell of the terminal.
- the multicast PDU session establishment request is usually sent by the first network side device to the core network node, and is used to request the core network node to establish the multicast PDU session.
- the first service is the same as the service transmitted by the multicast PDU session;
- the first service is a service requested by the first terminal through the cell where the multicast PDU session is established or by the first network side device;
- the multicast PDU session update request is used to indicate at least one of the following:
- the second terminal moves out of the cell corresponding to the multicast PDU session
- the second terminal moves out of the first network side device
- the second terminal joins the cell corresponding to the multicast PDU session and executes the same service as the service corresponding to the multicast PDU session.
- the multicast PDU session update request is usually sent by the first network side device to the core network node, and is used to request the core network node to update the multicast PDU session.
- the second terminal stops receiving the multicast service transmitted by the multicast PDU session
- the second terminal is not interested in the multicast service transmitted by the multicast PDU session.
- the first network side device mentioned in the embodiment of the present application refers to the device on the access network side, for example, the first network side device is a base station or a central unit (Central Unit) on the access network side )node.
- the first network side device is a base station or a central unit (Central Unit) on the access network side )node.
- Central Unit central Unit
- the core network node sends a multicast PDU session establishment signaling to the first network side device according to at least one of A11-A14.
- the core network node sends multicast PDU session establishment signaling to the first network side device according to A11 and A12
- the core network node is based on the terminals that access the first network side device and perform the same service (for example, perform the same type of service with the same content, for example, multiple terminals perform the same video transmission), and send multicast PDU session establishment signaling to the first network side device.
- the core network node determines that the number of terminals performing the same service accessing the first network side device is greater than or equal to the first threshold, then sending a multicast PDU session establishment signal to the first network side device make.
- this situation can be understood as that the core network node establishes a large multicast path for the first network side device, and the multicast path is for the first network side device as a whole.
- the first network side device needs to further determine the cells capable of establishing the multicast path according to the multicast path establishment signaling.
- the core network node sends multicast PDU session establishment signaling to the first network side device according to A11, A12 and A13
- the core network node can obtain the cell to which the terminal belongs, the core network node can accurately establish a multicast path for the cell.
- the first network side device will A cell or a terminal performs cell handover under the first network side device, because the home cell of the terminal has changed, so the first network side device needs to send the terminal's home cell to to core network nodes.
- the core network node sends multicast PDU session establishment signaling to the first network side device according to the number of terminals accessing the same cell of the first network side device and performing the same service.
- the core network node determines that the number of terminals performing the same service accessing the same cell of the first network side device is greater than or equal to the second threshold, then sending a multicast PDU to the first network side device Session establishment signaling.
- the core network node acquires that there are 50 terminals connected in cell A under the first network side device, 100 terminals connected in cell B, and 80 terminals connected in cell C
- the set The second threshold is 3.
- the core network node determines that the number of terminals performing the same service in cell A is 2, the number of terminals performing the same service in cell B is 5, and the number of terminals performing the same service in cell C is 2 based on the service information performed by the terminals.
- the core network node establishes a multicast path for cell B, and sends a multicast path establishment signaling to the core network node.
- the specific use case 1 and the specific use case 2 are the multicast establishment process triggered by the core network node, for example, it may be performed by the access and mobility management function (Access and Mobility Management Function, AMF) or the session management function ( Session Management Function, SMF) trigger, because the core network node has a relatively detailed grasp of which services each UE has, so it can directly determine the number of UEs receiving the same service, but the core network node currently does not grasp the UE's home cell in real time Yes, because the core network nodes belong to the core network side nodes, the interaction between the core network (Core Network, CN) and the access network (Radio Access Network, RAN) is mostly at the base station level, that is, according to In the existing process, the CN node can know which base station the UE belongs to, but it does not need to know the specific cell (cell) information at all times.
- AMF Access and Mobility Management Function
- SMF Session Management Function
- A12 of this application in order to be a core network node, it can clearly judge that the same service is received under the same cell.
- the number of UEs needs to update the serving cell information of each UE to the CN node in real time, and for the case that although they belong to different cells, but because the coverage of the cells is the same, they can be handed over to the same cell, it is also necessary to update the service cell information of each UE to the CN node.
- the coverage of the cell is known to the CN node. In short, knowing the above information, the CN node can clearly determine the number of UEs accessing the same cell and receiving the same service.
- the core network node sends multicast PDU session establishment signaling to the first network side device according to A14
- the multicast PDU session establishment request is usually sent by the first network side device to the core network node, and the first network side device usually performs the multicast PDU session according to the number of connected terminals receiving the same service. Sending of session establishment request.
- the first network-side device may send a multicast PDU session establishment request according to the number of terminals that it accesses that receive the same service. For example, when the first network-side device knows If the number of terminals is greater than or equal to the third threshold, a multicast PDU session establishment request may be sent to the core network node.
- the first network-side device may also send a multicast PDU session establishment request according to the number of terminals receiving the same service accessed under each cell. For example, when the first network-side device knows that cell A If the number of terminals receiving the same service accessed under cell B and cell C is greater than or equal to the fourth threshold, a multicast PDU session establishment request may be sent to the core network node.
- the core network node in order to enable the first network side device to distinguish whether the terminal is performing the same service, the core network node should send service attribute information to the first network side device, and the service attribute information It is used to determine whether different terminals perform the same service.
- the multicast (multicast) establishment in this application is not planned in advance, but is dynamically determined according to the service situation of the UE or the number of UEs receiving the same service.
- a typical situation is that there are already N UEs receiving the same service through unicast in a cell, and the core network nodes (such as SMF/AMF/User Plane Function (UPF)) are based on the belongingness of these UEs In the same cell and the service content is consistent, and the service meets certain Quality of Service (QoS) attributes, such as strong real-time performance and not sensitive to block error rate, etc., it can be decided to establish a multicast method for these UEs. Transmission of business.
- QoS Quality of Service
- the core network node (for example, it may be AMF) initiates a new PDU session (session) establishment process to the base station where these UEs are located, for establishing a multicast path between the core network node and the base station.
- the multicast The broadcast path can also be called a multicast channel, which includes a multicast PDU session (multicast PDU session) and a general packet radio service (General Packet Radio Service, GPRS) tunneling protocol user plane (GPRS Tunneling Protocol User Plane) of the multicast user plane, GTP-U) channel (Multicast GTP-U tunnel), the multicast PDU session is the control plane connection of the multicast path, and the Multicast GTP-U tunnel is the user plane transmission pipeline of the multicast path.
- GPRS General Packet Radio Service
- a multicast PDU A session corresponds to one or more Multicast GTP-U tunnels.
- the multicast PDU session establishment signaling needs to carry identification information of at least one terminal related to the session (which can be understood as carrying a list of terminals (UE list) related to the session), optionally, the identification information Can be AMF terminal next generation (Next Generation, NG) interface application protocol identification (AMF UE next generation application protocol (Next Generation Application Protocol, NGAP) identity identification number (Identity document, ID)), wireless access network terminal NG interface application At least one of the protocol identifier (RAN UE NGAP ID) and the 5G Temporary Mobile Subscription Identifier (5G S-Temporary Mobile Subscription Identifier, 5G-S-TMSI).
- these UEs need to be UEs under the base station and belong to the same cell or can be handed over to the same cell; or when the multicast path is established for a base station
- the base station after receiving the multicast PDU session establishment signaling, the base station decides which cells to use PTM according to the cell conditions of the terminal contained in the UE list, and responds to the CN node.
- the current home cell of each UE can be updated to the core network node through the mobility process, so the core network node knows the current home cell of the UE.
- the serving base station will notify the new serving cell during or after the handover AMF, as for other UEs that can be handed over to the same cell, it is based on the condition that the home cell of other UEs is in the same coverage as the cell to be established for multicasting, and is known by the core network node through network planning or deployment information.
- the first network side device when the first network side device receives the multicast PDU session establishment signaling and obtains the UE list, it can further implement the following process:
- the third terminal switches to the terminal corresponding to the multicast PDU session
- the cell adding the cell corresponding to the multicast PDU session as the secondary cell of the third terminal, notifying the third terminal of the cell corresponding to the multicast PDU session and its configuration
- the serving cell of the third terminal is different from the cell corresponding to the multicast PDU session.
- the first network side device can initiate a handover process to the UE that is not connected to the current cell to switch it to the current cell or add the current cell It is a secondary cell (scell); if the UE not in the current cell has relevant capabilities (for example, it can receive multicast services on a non-serving cell), the first network side device may not perform the above process, but directly transfer the multicast The cell corresponding to the broadcast PDU session and the configuration can be notified to the terminal.
- the following process may be further implemented:
- the first network side device sends a response message to the core network node
- the response message carries acceptance information and/or rejection information
- the rejection information is used to indicate terminal information that cannot perform multicast reception in a cell under the first network side device
- the acceptance information is used to indicate terminal information capable of receiving multicast in a cell under the first network side device.
- the first network side device may feed back the accepted and/or rejected terminals to the core network node.
- the first network side device configures a multicast radio bearer (multicast radiobearer, MRB) for UEs capable of multicast reception in the UE list through a dedicated radio resource control (Radio Resource Control, RRC) signaling (dedicated RRC signaling) process
- RRC Radio Resource Control
- RRC Radio Resource Control
- Related configurations such as G-RNTI, Discontinuous Reception (DRX) parameters, MRB ID, etc., also include Service Data Adaptation Protocol (Service Data Adaptation Protocol, SDAP)/Packet Data Convergence Protocol , PDCP)/Radio Link Control (RLC)/Media Access Control (Medium Access Control, MAC)/Physical (Physical, PHY) layer configuration, and the mapping of QoS flow (flow) to MRB (mapping) relation.
- SDAP Service Data Adaptation Protocol
- SDAP Packet Data Convergence Protocol
- PDCP Radio Link Control
- RLC Radio Link Control
- MAC Media Access Control
- Physical Physical, PHY
- the core network node After the first network side device completes the establishment of the multicast PDU session, it needs to feed back a multicast PDU session establishment completion message to the core network node. After the core network node obtains the multicast PDU session establishment completion message, the core network node transmits the public data on one or more Multicast GTP-U tunnels corresponding to the multicast PDU session, and no longer uses the unicast path originally used by each UE for these data (requires).
- the unicast path can also be called a unicast channel, which includes a unicast PDU session and a unicast user plane general packet radio service tunneling protocol channel (unicast GTP-U tunnel), and the unicast PDU session is a unicast
- the control plane connection of the path, the unicast GTP-U tunnel is the user plane transmission pipeline of the unicast path.
- one unicast PDU session corresponds to one or more unicast GTP-U tunnels to transmit these public data.
- the core network can decide Whether to release or retain the unicast path, the reason for the reservation is generally that there are UE-specific services that need to be transmitted on the unicast path, or reserved for better mobility of the UE. If the unicast path is reserved, the base station will not delete the corresponding The data radio bearer (Data Radio Bearer, DRB). It should be noted that the DRB is used for unicast transmission, so it can also be called a unicast radio bearer). If the unicast path is released, the base station will Send corresponding DRB release signaling to UE.
- DRB Data Radio Bearer
- the UE For the UE, if it receives a reconfiguration message or MRB establishment signaling in the connected state, it will establish an MRB according to the message, return a completion message to the base station, and start monitoring the data scheduled by the corresponding group radio network temporary identifier G-RNTI.
- the core network can start to use this path to transmit public data, that is, the public data is first transmitted to the base station through the public multicast GTP-U tunnel, and then the base station passes through G-RNTI
- the group scheduling method sends to N UEs at one time, which greatly saves resource overhead, and changes from the original unicast scheduling that requires N transmission resources to multicast scheduling that only requires one transmission resource.
- the base station is a network architecture composed of Centralized Unit/Distributed Unit (CU-DU) nodes
- CU-DU Centralized Unit/Distributed Unit
- the multicast path from the core network node to the base station establishes the data between UPF and CU nodes
- Flat pipelines such as GTP-U tunnels
- pipelines are also required between CU and DU nodes to carry them.
- a shared F1 pipeline such as GTP-U tunnels, can be used to transmit from the CU to the DU where the cell is located node.
- the network transmits data through each UE's own unicast GTP-U tunnel. Since each UE joins the service at different times, the transmission status of its unicast GTP-U tunnel Not the same, specifically, the GTP-U tunnel serial number (Sequence Number, SN) may be different. Then, for the newly established multicast GTP-U tunnel, since it is impossible to ensure synchronous docking with the unicast GTP-U tunnels of all UEs at the same time, the easiest way is to use the multicast GTP-U tunnel as a new pipeline and start from the The initial state starts to transfer.
- the GTP-U tunnel serial number Sequence Number, SN
- the situation of different UEs can be considered, and the slower UEs should be taken into account as much as possible, that is, the transmission will start from the progress of the slower UEs, so that the downlink data seen by most users is continuous, and there may be a small amount of data. Repeat but nothing is missed.
- MRB and DRB are typically completely independent protocols
- the stack and PDCP entities are independent and SN-independent, so the UE side cannot perform any reordering or duplicate detection to achieve a completely lossless and continuous service experience. If lossless and continuous are required, related sorting and duplication detection work needs to be performed on the service source side. Therefore, it is more suitable for live broadcast or real-time video services.
- the multicast pipeline is established/released/modified, causing a certain UE to enter a multicast group (multicast group) or exit a multicast group;
- the core network node sends a multicast PDU session update signaling to the first network side device according to one of A15-A18.
- the core network node sends multicast PDU session update signaling to the first network side device according to A15
- the core network learns that there is a new terminal that can rejoin the multicast PDU session, and then sends a multicast PDU session update signaling to the first network side device to indicate that the multicast PDU session is in progress.
- a terminal is added.
- the identification information of the first terminal (newly added terminal) will be carried in the multicast PDU session update signaling.
- the core network node sends multicast PDU session update signaling to the first network side device according to A16
- the update of the multicast PDU session is requested by the first network side device.
- the first network side device moves out of the cell corresponding to the multicast PDU session or moves out of the second terminal
- a multicast PDU session update request is sent to the core network node.
- this update is to reduce the number of terminals, and the multicast PDU session update signaling is used to indicate that the second terminal does not include
- only the identifier of the second terminal is carried in the multicast PDU session update signaling or the updated UE list may also be carried in the multicast PDU session update signaling.
- the first network side device may also send the multicast PDU session to the core network node when the second terminal joins the cell corresponding to the multicast PDU session and performs the same service as the service corresponding to the multicast PDU session Update request, it should be noted that this update is to add a terminal, and the multicast PDU session update signaling is used to indicate that the second terminal is included in the multicast PDU session.
- the multicast PDU session update Only the identifier of the second terminal is carried in the signaling or the updated UE list may also be carried in the multicast PDU session update signaling.
- the core network node sends a multicast PDU session update signaling to the first network side device according to A17 or A18
- the second terminal stops receiving the multicast service transmitted by the multicast PDU session or the second terminal is not interested in the multicast service transmitted by the multicast PDU session, it means that it is not suitable for the second terminal If multicast is used for transmission, the second terminal needs to be deleted from the multicast path at this time.
- the update in this case is to reduce the number of terminals, and the multicast PDU session update signaling is used to indicate that the second terminal is not included in the multicast PDU session.
- the updated UE list may also be carried in the identification of the second terminal or in the multicast PDU session update signaling.
- the core network finds that the service is in the If the cell has established a multicast pipeline, the core network has two ways to handle the request of the new UE:
- the first way is to directly initiate the multicast PDU session modification process, and add a new UE to the UE list involved in the multicast PDU session to inform the NR node (NR Node B, gNB) that the new UE also wants to receive the same service, then gNB Then the new UE can be configured with the same MRB and layer configuration as other UEs in other multicast groups, so that the new UE can use the multicast channel for service reception;
- NR Node B NR Node B
- the core network also initiates the traditional unicast PDU session establishment process at the same time, triggering gNB to establish MRB and DRB for the new UE, among which unicast PDU session, unicast GTP-U tunnel and
- the establishment of the DRB is mainly for other UE personalized DL data transmissions other than public downlink (Downlink, DL) data, UE UL data transmission, and backup preparations for various path switches that may occur.
- the core network and the UE can use the configured pipes for data transmission.
- the multicast path may no longer be applicable. At this time, it is necessary to release the multicast path.
- a specific implementation method of the embodiment of the present application is as follows:
- the core network node sends a multicast PDU session release signaling to the first network side device according to the second information
- the second information includes at least one of the following:
- the core network node actively releases the multicast path.
- the core network node can perform multicast according to the number of terminals receiving multicast services accessed under the first network side device Sending of PDU session release signaling, for example, when the number of terminals receiving multicast services accessed by the first network side device is less than or equal to the fifth threshold, sending a multicast PDU session to the first network side device Release the signaling; or, optionally, the core network node may send the multicast PDU session release signaling according to the number of terminals receiving the multicast service that access the specific cell under the first network side device, for example, when the first network side device A network side device sends multicast PDU session release signaling to the first network side device when the number of terminals receiving multicast services accessing a specific cell (for example, cell A) is less than or equal to the sixth threshold.
- a specific cell for example, cell A
- a multicast PDU session release request where the multicast PDU session release request is sent by the first network side device.
- the multicast PDU session release request is usually sent by the first network side device to the core network node, and the first network side device may send the multicast PDU session release request according to the following conditions.
- Case 1 Send a multicast PDU session release request according to the information of the terminal receiving the multicast service accessed
- the terminal information may be the number of terminals.
- the first network side device may send a multicast PDU session release request to the core network node.
- the terminal information may be the number of terminals.
- the first network side device knows that the number of terminals receiving multicast services accessed under cell A, cell B, and cell C is less than or equal to the eighth threshold, it can send the multicast PDU session to the core network node Release request.
- the first threshold to the eighth threshold mentioned in the embodiment of the present application may be agreed by a protocol or configured by the network side.
- the gNB performs a multicast PDU session to the core network node
- the modification process removes the UE from the UE list.
- the gNB will also send a reconfiguration signaling to the UE to remove all configurations related to the MRB.
- the UE When the UE is removed from the multicast group, the UE no longer monitors the G-RNTI, but only monitors the C-RNTI scheduling, and the core network will re-switch the UE's business data to the unicast GTP-U tunnel for transmission, and the Uu interface It is transmitted through the DRB, and the data of the UE is switched from the unicast channel to the multicast channel.
- the network may decide to release the multicast pipeline and transfer the remaining UEs to the unicast pipeline for reception .
- the gNB can request, or the core network node decides independently, to perform the multicast PDU session release (release) process, AMF sends signaling to the gNB for release, and the gNB uses dedicated signaling to initiate the MRB and configuration release process to the UEs included in the group , and then return a completion message to the core network.
- release multicast PDU session release
- the embodiment of the present application provides a dynamic multicast management method, and the network side can flexibly perform management processes such as multicast establishment and release as needed, and transmit multiple UEs with the same service in a multicast manner. , so that the resource efficiency is improved on the basis of taking into account the receiving performance of the UE, and the overall system efficiency and resource utilization rate are greatly improved.
- the multicast control method provided in the embodiment of the present application may be executed by a multicast control device, or a control module in the multicast control device for executing the multicast control method.
- the multicast control device provided in the embodiment of the present application is described by taking the execution of the multicast control method by the multicast control device as an example.
- the embodiment of the present application provides a multicast control device 300, which is applied to a core network node, including:
- the first sending module 301 is configured to send multicast protocol data unit PDU session signaling to the first network side device based on the first information;
- the first information includes at least one of the following:
- the first service is the same as the service transmitted by the multicast PDU session, and the first service is a service requested by the first terminal through the cell where the multicast PDU session is established or by the first network side device;
- a multicast PDU session update request is used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session, the second terminal moves out of the first network side device, and the second terminal joins
- the cell corresponding to the multicast PDU session and the service performed is the same as the service corresponding to the multicast PDU session;
- the second terminal stops receiving the multicast service transmitted by the multicast PDU session
- the second terminal is not interested in the multicast service transmitted by the multicast PDU session.
- the multicast PDU session signaling includes at least one of the following:
- the device when the first information includes a multicast PDU session establishment request, the device further includes:
- a third sending module configured to send service attribute information to the first network side device
- the service attribute information is used to determine whether different terminals perform the same service.
- the multicast PDU session establishment signaling includes identification information of at least one terminal
- the identification information includes at least one of the following: access and mobility management function AMF terminal NG interface application protocol identification, wireless access network terminal NG interface application protocol identification and 5G temporary mobile user identification code.
- the device when the multicast PDU session signaling includes multicast PDU session update signaling, the device further includes:
- a fourth sending module configured to send unicast PDU session establishment signaling to the first network side device.
- the multicast PDU session update message carries identification information of the first terminal.
- the multicast PDU session update message is used to indicate that the second terminal is not included in the multicast PDU session.
- the device when the first information includes a multicast PDU session establishment request, the device further includes:
- a third receiving module configured to receive a response message sent by the first network side device
- the response message carries acceptance information and/or rejection information
- the rejection information is used to indicate terminal information that cannot perform multicast reception in a cell under the first network side device
- the acceptance information is used to indicate terminal information capable of multicast reception in a cell under the first network side device.
- the device also includes:
- a fifth sending module configured to send multicast PDU session release signaling to the first network side device according to the second information
- the second information includes at least one of the following:
- a multicast PDU session release request where the multicast PDU session release request is sent by the first network side device.
- the device when the first information includes a multicast PDU session update request, the device further includes:
- a fourth receiving module configured to receive a multicast PDU session update request sent by the first network side device
- the multicast PDU session update request is that the first network side device moves out of the cell corresponding to the multicast PDU session, moves out of the first network side device and joins the cell corresponding to the multicast PDU session, and executes services related to the multicast PDU session. It is sent when at least one of the services corresponding to the broadcast PDU session is the same.
- this device embodiment corresponds to the above-mentioned method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this device embodiment, and can achieve the same technical effect.
- the multicast control device provided by the embodiment of the present application can realize each process realized by the method embodiment in FIG. 2 and achieve the same technical effect. To avoid repetition, details are not repeated here.
- the embodiment of the present application also provides a core network node, including a processor and a communication interface, where the communication interface is used to send multicast protocol data unit PDU session signaling to the first network side device based on the first information;
- the first information includes at least one of the following:
- the first service is the same as the service transmitted by the multicast PDU session, and the first service is the service requested by the first terminal through the cell or the first network side device establishing the multicast PDU session;
- a multicast PDU session update request is used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session, the second terminal moves out of the first network side device, and the second terminal joins
- the cell corresponding to the multicast PDU session and the service performed is the same as the service corresponding to the multicast PDU session;
- the second terminal stops receiving the multicast service transmitted by the multicast PDU session
- the second terminal is not interested in the multicast service transmitted by the multicast PDU session.
- FIG. 4 is a schematic diagram of a hardware structure of a core network node implementing an embodiment of the present application.
- the core network node 400 includes: an antenna 401 , a radio frequency device 402 , and a baseband device 403 .
- the antenna 401 is connected to the radio frequency device 402 .
- the radio frequency device 402 receives information through the antenna 401, and sends the received information to the baseband device 403 for processing.
- the baseband device 403 processes the information to be sent and sends it to the radio frequency device 402
- the radio frequency device 402 processes the received information and sends it out through the antenna 401 .
- the foregoing frequency band processing apparatus may be located in the baseband apparatus 403 , and the method performed by the first network side device in the above embodiments may be implemented in the baseband apparatus 403 , and the baseband apparatus 403 includes a processor 404 and a memory 405 .
- the baseband device 403 may include at least one baseband board, for example, a plurality of chips are arranged on the baseband board, as shown in FIG. The data transmission method shown in the above method embodiment.
- the baseband device 403 may also include a network interface 406 for exchanging information with the radio frequency device 402, such as a Common Public Radio Interface (CPRI).
- CPRI Common Public Radio Interface
- the first network-side device in this embodiment of the present application further includes: instructions or programs stored in the memory 405 and executable on the processor 404, and the processor 404 invokes the instructions or programs in the memory 405 to execute the The method executed by each module achieves the same technical effect, so in order to avoid repetition, it is not repeated here.
- the embodiment of the present application also provides a core network node, including a processor, a memory, and a program or instruction stored in the memory and operable on the processor.
- a core network node including a processor, a memory, and a program or instruction stored in the memory and operable on the processor.
- the program or instruction is executed by the processor, an application
- Each process of the embodiment of the multicast control method on the node side of the core network can achieve the same technical effect, and will not be repeated here to avoid repetition.
- the embodiment of the present application also provides a readable storage medium.
- the computer-readable storage medium stores programs or instructions.
- the various processes of the embodiments of the data transmission method applied to the node side of the core network are implemented. , and can achieve the same technical effect, in order to avoid repetition, it will not be repeated here.
- the computer-readable storage medium is, for example, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
- ROM Read-Only Memory
- RAM Random Access Memory
- magnetic disk or an optical disk and the like.
- the embodiment of the present application also provides a multicast control method, including:
- Step 501 the first network side device receives the multicast protocol data unit PDU session signaling sent by the core network node.
- the multicast PDU session signaling is sent by the core network node based on the first information, and the first information includes at least one of the following:
- the first service is the same as the service transmitted by the multicast PDU session, and the first service is a service requested by the first terminal through the cell where the multicast PDU session is established or by the first network side device;
- a multicast PDU session update request is used to indicate at least one of the following: the second terminal moves out of the cell corresponding to the multicast PDU session, the second terminal moves out of the first network side device, and the second terminal joins
- the cell corresponding to the multicast PDU session and the service performed is the same as the service corresponding to the multicast PDU session;
- the second terminal stops receiving the multicast service transmitted by the multicast PDU session
- the second terminal is not interested in the multicast service transmitted by the multicast PDU session.
- the multicast PDU session signaling includes at least one of the following:
- the first network side device before the first network side device receives the multicast protocol data unit PDU session signaling sent by the core network node, it further includes:
- the first network side device sends the home cell of the terminal to the core network node.
- the first network side device sending the home cell of the terminal to the core network node includes:
- the first network side device sends the home cell of the terminal to the core network node when the access cell of the terminal accessing the first network side device changes.
- the first network side device before the first network side device receives the multicast protocol data unit PDU session signaling sent by the core network node, it further includes:
- the first network side device sends a multicast PDU session establishment request to the core network node.
- the first network side device before the first network side device sends the multicast PDU session establishment request to the core network node, it further includes:
- the first network side device receives the service attribute information sent by the core network node
- the service attribute information is used to determine whether different terminals perform the same service.
- the multicast PDU session establishment signaling includes identification information of at least one terminal
- the identification information includes at least one of the following: access and mobility management function AMF terminal NG interface application protocol identification, wireless access network terminal NG interface application protocol identification and 5G temporary mobile user identification code.
- the method further includes:
- the first network side device receives the unicast PDU session establishment signaling sent by the core network node.
- the multicast PDU session update signaling carries the identification information of the first terminal.
- the multicast PDU session update signaling is used to indicate that the second terminal is not included in the multicast PDU session.
- the method further includes:
- the second terminal moves out of the cell corresponding to the multicast PDU session, moves out of the second network side device and joins the cell corresponding to the multicast PDU session, and performs at least one of the same services as the service corresponding to the multicast PDU session , sending a multicast PDU session update request to the core network node.
- the method further includes:
- the first network side device sends a response message to the core network node
- the response message carries acceptance information and/or rejection information
- the rejection information is used to indicate terminal information that cannot perform multicast reception in a cell under the first network side device
- the acceptance information is used to indicate terminal information capable of receiving multicast in a cell under the first network side device.
- the method also includes:
- the third terminal switches to the cell corresponding to the multicast PDU session
- the serving cell of the third terminal is different from the cell corresponding to the multicast PDU session.
- the method also includes:
- the first network side device sends a multicast PDU session release request to the core network node.
- the first network side device sends a multicast PDU session release request to the core network node, including:
- the first network side device sends a multicast PDU session release request to the core network node according to the terminal information receiving the multicast service.
- the embodiment of the present application also provides an implementation method of how to perform configuration to ensure that the terminal can perform data transmission smoothly when the terminal switches to the first network side device.
- the specific implementation process is as follows:
- the first network side device receives the first configuration information of the fourth terminal sent by the second network side device, where the first configuration information includes the service flow of the fourth terminal and the unicast radio bearer and/or multicast radio bearer Correspondence;
- the first network-side device determines second configuration information used by the fourth terminal according to the first configuration information, and the second configuration information is a transmission configuration used by the fourth terminal after switching to the first network-side device;
- the first network side device sends the second configuration information to the second network side device.
- the first network-side device mentioned in the embodiment of the present application refers to the network-side device that the terminal will access
- the second network-side device refers to the network-side device that the terminal will access before the handover.
- the accessed network side device, the second network side device may be considered as a source network side device, for example, a source base station
- the first network side device may be considered as a target network side device, for example, a target base station.
- the terminal switches between different cells of the same network-side device, the source network-side device and the target network-side device are the same network-side device, and the cell accessed by the terminal before the handover is called the source cell.
- the cell, the cell that the terminal accesses after the handover is called the target cell.
- the first network side device determines second configuration information used by the fourth terminal according to the first configuration information, including at least one of the following:
- the first network side device uses unicast transmission, and determines that the second configuration information is unicast transmission
- This implementation method includes the following situations:
- the first case source cell unicast (unicast path and DRB) transmission, target cell unicast transmission, this is a traditional handover scenario, you can directly use the traditional handover process, that is, the terminal can directly transfer from the source The cell is handed over to the target cell;
- the second case source cell multicast mode (multicast path and MRB) transmission, target cell unicast mode transmission; this mode is common when the source cell side uses multicast mode transmission, but the target side does not support this mechanism or the UE If the number is not enough, the multicast method cannot be used for transmission, so the target side needs to use unicast method for transmission. In this way, since multicast cannot be directly switched to unicast and also across cells, it is more reasonable to switch to unicast transmission on the source cell side first, and then perform the traditional switching process, or switch to the third case below .
- the third case the source cell transmits in multicast mode and has unicast mode configuration, and the target cell transmits in unicast mode; similar to the second case, this method is also common when the source cell side uses multicast mode transmission, but the target side does not support it. This mechanism or the insufficient number of UEs cannot also use the multicast method for transmission, so the target side needs to use the unicast method for transmission. And this method is more recommended than the second case above because it is more friendly to the switching process.
- a typical way is to convert the data from the multicast path to the unicast path before the handover at the source cell side, and the handover process is equivalent to performing a traditional handover process.
- the first network side device at least uses multicast transmission, and determines that the second configuration information is unicast transmission
- This implementation method includes the following situations:
- the first case unicast transmission in the source cell and multicast transmission in the target cell; in order to achieve handover continuity and compatibility, it is not recommended to directly switch from unicast to multicast across cells. A more reasonable way is to use unicast in the source cell first. Switch to unicast in the target cell, and perform conversion from unicast to multicast in the target cell.
- the second case the source cell transmits in unicast mode, the target cell transmits in multicast mode and has unicast mode configuration; in this mode, the switching from unicast to unicast part is similar to the traditional process, and the path is changed after reaching the target cell, from unicast to multicast path.
- the first network side device uses multicast transmission, and determines that the second configuration information is multicast transmission
- This implementation method includes the following situations:
- the source cell multicast mode transmits, and the target cell multicast mode transmits; this method is also ideal.
- the UE accesses the target cell, it can continue to receive in multicast mode directly, but due to the lack of correlation between the multicast PDU session and the MRB of the source cell and the target cell , it can be considered that two independent pipes do not transmit any status information, so the service continuity of the UE cannot be guaranteed.
- the second network-side device adopts multicast transmission and unicast transmission, and the first network-side device adopts multicast transmission and unicast transmission, determine that the second configuration information is multicast transmission and unicast transmission ;
- This implementation method includes the following situations:
- the first case the source cell is transmitted in multicast mode, and the target cell is transmitted in multicast mode with unicast configuration; this method is not recommended to exist. Before the source cell is handed over, it is usually necessary to establish unicast before switching, that is, the conversion is as follows the third case.
- the second case the source cell is transmitted in multicast mode with unicast mode configuration, and the target cell is transmitted in multicast mode; although this method can be implemented, it is debatable when the unicast PDU session will be released, and it is usually converted to the third method below situation.
- Case 3 The source cell transmits in multicast mode and has unicast mode configuration, and the target cell transmits in multicast mode and has unicast mode configuration; this mode has multicast channel configuration in both the source cell and the target cell, and also has unicast channel configuration , can better perform service handover. In general, traditional handover is performed between unicast and unicast.
- the main difference between multicast handover and traditional handover is that when the source cell sends a handover preparation message to the target cell, it can carry the source cell’s Multicast configuration, when the target cell decides to accept the service of the UE, it can also configure multicast and unicast configurations at the same time, and feed back the configuration of the target cell to the source cell, and the source cell sends it to the UE through a handover command. According to the configuration of unicast and multicast on the target side, the UE receives relevant multicast and unicast after accessing the target cell.
- the handover can be implemented in the above manner according to the difference in the way the source cell and the target cell send the same service.
- the handover process from unicast to unicast channel is a transmission channel and pipe dedicated to the UE, so for the data delivered by the core network, the sent data can remain continuous before and after the handover, and PDCP SN status transfer (status transfer) and data forwarding (data forwarding) processes can also be performed between the interfaces of the source base station and the target base station, and the UE is supported and configured to report the PDCP status report, thereby ensuring lossless and continuous service.
- PDCP SN status transfer status transfer
- data forwarding data forwarding
- the core network cannot ensure the continuity of service transmission, and the interface between base stations cannot perform status and data transmission.
- the PDCP layer of the UE should also be reset and then based on the first received at the target side.
- a data packet is used to set the initial value of PDCP SN, so lossless and continuity of services cannot be ensured.
- the connection can only be ensured to a certain extent, eg according to the temporal characteristics of the live broadcast. Therefore, for the case where lossless business is required, at least switching from unicast to unicast is usually included, while for other services that do not require lossless, switching from unicast to unicast may not be included.
- the network behavior when the terminal is handed over is specified on the basis of dynamic multicast control, so as to ensure the smooth handover of the terminal and the transmission reliability of the terminal service during the handover process.
- the embodiment of the present application also provides a multicast control device 600, which is applied to the first network side device, including:
- the first receiving module 601 is configured to receive multicast protocol data unit PDU session signaling sent by a core network node.
- the multicast PDU session signaling includes at least one of the following:
- the first receiving module 601 before the first receiving module 601 receives the multicast protocol data unit PDU session signaling sent by the core network node, it further includes:
- the sixth sending module is configured to send the home cell of the terminal to the core network node.
- the sixth sending module is configured to:
- the home cell of the terminal is sent to the core network node.
- the first receiving module 601 before the first receiving module 601 receives the multicast protocol data unit PDU session signaling sent by the core network node, it further includes:
- a seventh sending module configured to send a multicast PDU session establishment request to a core network node.
- the seventh sending module sends the multicast PDU session establishment request to the core network node, it further includes:
- the fifth receiving module is used to receive the service attribute information sent by the core network node
- the service attribute information is used to determine whether different terminals perform the same service.
- the multicast PDU session establishment signaling includes identification information of at least one terminal
- the identification information includes at least one of the following: access and mobility management function AMF terminal NG interface application protocol identification, wireless access network terminal NG interface application protocol identification and 5G temporary mobile user identification code.
- the device when the multicast PDU session signaling includes multicast PDU session update signaling, the device further includes:
- the sixth receiving module is configured to receive the unicast PDU session establishment signaling sent by the core network node.
- the multicast PDU session update signaling carries the identification information of the first terminal.
- the multicast PDU session update signaling is used to indicate that the second terminal is not included in the multicast PDU session.
- the device when the multicast PDU session signaling includes multicast PDU session update signaling, the device further includes:
- the eighth sending module is used to move the second terminal out of the cell corresponding to the multicast PDU session, move out of the second network side device, and join the cell corresponding to the multicast PDU session, and perform the same service as the service corresponding to the multicast PDU session In the case of at least one of them, a multicast PDU session update request is sent to the core network node.
- the device when the multicast PDU session signaling includes multicast PDU session establishment signaling, the device further includes:
- a ninth sending module configured to send a response message to a core network node
- the response message carries acceptance information and/or rejection information
- the rejection information is used to indicate terminal information that cannot perform multicast reception in a cell under the first network side device
- the acceptance information is used to indicate terminal information capable of receiving multicast in a cell under the first network side device.
- the device also includes:
- a tenth sending module configured to send a configuration message to the third terminal if there is a third terminal among the terminals corresponding to the multicast PDU session, and the configuration message is used to indicate at least one of the following:
- the third terminal switches to the cell corresponding to the multicast PDU session
- the serving cell of the third terminal is different from the cell corresponding to the multicast PDU session.
- the device also includes:
- An eleventh sending module configured to send a multicast PDU session release request to a core network node.
- the twelfth sending module is used for:
- the device also includes:
- the seventh receiving module is configured to receive the first configuration information of the fourth terminal sent by the second network side device, the first configuration information includes the service flow and unicast radio bearer and/or multicast radio bearer of the fourth terminal bearer correspondence;
- the determining module is used for the first network side device to determine the second configuration information used by the fourth terminal according to the first configuration information, and the second configuration information is used after the fourth terminal switches to the first network side device transport configuration;
- a twelfth sending module configured to send the second configuration information to the second network side device.
- the determination module is configured to implement at least one of the following:
- the first network side device uses unicast transmission, and determines that the second configuration information is unicast transmission
- the first network side device at least uses multicast transmission, and determines that the second configuration information is unicast transmission;
- the first network-side device adopts multicast transmission, and determines that the second configuration information is multicast transmission;
- the first network-side device adopts multicast transmission and unicast transmission, and determines that the second configuration information is multicast transmission and unicast transmission.
- this device embodiment corresponds to the above-mentioned method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this device embodiment, and can achieve the same technical effect.
- the embodiment of the present application further provides a network-side device
- the network-side device is a first network-side device, including a processor, a memory, and a program or instruction stored in the memory and operable on the processor , when the program or instruction is executed by the processor, each process of the embodiment of the multicast control method applied to the first network side device side can be achieved, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
- the embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored on the computer readable storage medium, and when the program or instruction is executed by a processor, the embodiment of the multicast control method applied to the first network side device side is implemented
- a readable storage medium on which a program or instruction is stored on the computer readable storage medium, and when the program or instruction is executed by a processor, the embodiment of the multicast control method applied to the first network side device side is implemented
- the computer-readable storage medium is, for example, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
- ROM Read-Only Memory
- RAM Random Access Memory
- magnetic disk or an optical disk and the like.
- the embodiment of the present application also provides a network side device, the network side device is a first network side device, including a processor and a communication interface, and the communication interface is used to receive the multicast protocol data unit PDU session signaling sent by the core network node .
- the network-side device embodiment corresponds to the above-mentioned network-side device method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.
- the embodiment of the present application also provides a network side device, and the network side device is a first network side device.
- the structure of the first network side device can refer to the structure in FIG. 4 , which will not be repeated here.
- the processor invokes instructions or programs in the memory to execute the methods executed by the modules shown in FIG. 6 and achieve the same technical effect. To avoid repetition, details are not repeated here.
- the embodiment of the present application also provides a handover configuration method, including:
- Step 701 the second network side device sends the first configuration information of the fourth terminal to the first network side device
- Step 702 the second network side device receives the second configuration information fed back by the first network side device
- the first configuration information is the transmission configuration of the fourth terminal under the second network side device, and the first configuration information includes a correspondence relationship between a service flow and a unicast radio bearer and/or a multicast radio bearer, and the The second configuration information is the transmission configuration used after the fourth terminal switches to the first network side device.
- the second network side device receives the second configuration information fed back by the first network side device, at least one of the following is further included:
- the second network side device adopts multicast mode for transmission, if the second configuration information is for unicast mode transmission, then convert the terminal to unicast mode for transmission, and switch to the first network side device;
- the second network side device at least uses unicast transmission, and if the second configuration information is unicast transmission, switch to the first network side device;
- the second network side device adopts multicast transmission, if the second configuration information is multicast transmission, switch to the first network side device;
- the device on the second network side adopts multicast transmission, if the second configuration information is multicast transmission and unicast transmission, establishes unicast transmission for the terminal, and switches to the first network side device;
- the second network side device adopts multicast transmission and unicast transmission, and if the second configuration information is multicast transmission and unicast transmission, switch to the first network side device.
- the embodiment of the present application also provides a handover configuration apparatus 800, which is applied to the second network side device, including:
- the second sending module 801 is configured to send the first configuration information of the fourth terminal to the first network side device;
- the second receiving module 802 is configured to receive second configuration information fed back by the first network side device
- the first configuration information is the transmission configuration of the fourth terminal under the second network side device, and the first configuration information includes a correspondence relationship between a service flow and a unicast radio bearer and/or a multicast radio bearer, and the The second configuration information is the transmission configuration used after the fourth terminal switches to the first network side device.
- the second receiving module 802 receives the second configuration information fed back by the first network side device, at least one of the following is further included:
- the first switching module is configured to use multicast transmission on the second network side device, if the second configuration information is unicast transmission, convert the terminal to unicast transmission, and switch to the first network side device;
- the second switching module is configured to use at least unicast transmission on the second network side device, and switch to the first network side device if the second configuration information is transmitted in unicast mode;
- the third switching module is configured to use multicast transmission on the second network side device, and switch to the first network side device if the second configuration information is multicast transmission;
- the fourth switching module is configured to use multicast transmission on the second network side device, if the second configuration information is multicast transmission and unicast transmission, establish unicast transmission for the terminal, and switch to the first network side equipment;
- the fifth switching module is configured to use multicast transmission and unicast transmission on the second network side device, and switch to the first network side device if the second configuration information is multicast transmission and unicast transmission.
- this device embodiment corresponds to the above-mentioned method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this device embodiment, and can achieve the same technical effect.
- the embodiment of the present application further provides a network-side device
- the network-side device is a second network-side device, including a processor, a memory, and programs or instructions stored in the memory and operable on the processor , when the program or instruction is executed by the processor, each process of the embodiment of the handover configuration method applied to the second network side device side can be achieved, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
- the embodiment of the present application also provides a readable storage medium, where a program or an instruction is stored on the computer-readable storage medium, and when the program or instruction is executed by a processor, the embodiment of the handover configuration method applied to the second network side device side is implemented.
- a program or an instruction is stored on the computer-readable storage medium, and when the program or instruction is executed by a processor, the embodiment of the handover configuration method applied to the second network side device side is implemented.
- the computer-readable storage medium is, for example, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
- ROM Read-Only Memory
- RAM Random Access Memory
- magnetic disk or an optical disk and the like.
- the readable storage medium in the embodiment of the present application may be volatile or nonvolatile, and in addition, the readable storage medium may be a non-transitory readable storage medium.
- the embodiment of the present application also provides a network-side device, the network-side device is a second network-side device, including a processor and a communication interface, and the communication interface is used to send the first configuration information of the fourth terminal to the first network-side device ; Receiving second configuration information fed back by the first network side device;
- the first configuration information is the transmission configuration of the fourth terminal under the second network side device, and the first configuration information includes a correspondence relationship between a service flow and a unicast radio bearer and/or a multicast radio bearer, and the The second configuration information is the transmission configuration used after the fourth terminal switches to the first network side device.
- the embodiment of the present application also provides a network-side device, which is a second network-side device.
- a network-side device which is a second network-side device.
- the structure of the first network-side device can refer to the structure in FIG. 4 , which will not be repeated here.
- the processor invokes instructions or programs in the memory to execute the methods executed by the modules shown in FIG. 8 and achieve the same technical effect. To avoid repetition, details are not repeated here.
- this embodiment of the present application further provides a communication device 900, including a processor 901, a memory 902, and programs or instructions stored in the memory 902 and operable on the processor 901,
- a communication device 900 including a processor 901, a memory 902, and programs or instructions stored in the memory 902 and operable on the processor 901
- the communication device 900 is the second network side device
- the program or instruction is executed by the processor 901
- each process of the above-mentioned handover configuration method embodiment can be realized, and the same technical effect can be achieved.
- the communication device 900 is the first network side device
- the program or instruction is executed by the processor 901
- each process of the embodiment of the multicast control method described above can be achieved, and the same technical effect can be achieved.
- the communication device 900 is a core network node
- the program or instruction is executed by the processor 901
- each process of the above-mentioned multicast control method embodiment can be achieved, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
- the terminal involved in this embodiment of the present application may be a device that provides voice and/or data connectivity to users, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem.
- the name of the terminal equipment may be different.
- the terminal equipment may be called User Equipment (User Equipment, UE).
- the wireless terminal device can communicate with one or more core networks (Core Network, CN) via the radio access network (Radio Access Network, RAN), and the wireless terminal device can be a mobile terminal device, such as a mobile phone (or called a "cellular "telephones) and computers with mobile terminal equipment, such as portable, pocket, hand-held, computer built-in or vehicle-mounted mobile devices, which exchange language and/or data with the radio access network.
- CN Core Network
- RAN Radio Access Network
- RAN Radio Access Network
- the wireless terminal device can be a mobile terminal device, such as a mobile phone (or called a "cellular "telephones) and computers with mobile terminal equipment, such as portable, pocket, hand-held, computer built-in or vehicle-mounted mobile devices, which exchange language and/or data with the radio access network.
- PCS Personal Communication Service
- SIP Session Initiated Protocol
- WLL Wireless Local Loop
- PDA Personal Digital Assistant
- Wireless terminal equipment can also be called system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point , remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user agent (user agent), and user device (user device), which are not limited in this embodiment of the application.
- the first network-side device and the second network-side device involved in the embodiment of the present application may be a base station (Base Transceiver) in Global System of Mobile communication (GSM) or Code Division Multiple Access (CDMA). Station, BTS), or a base station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), or an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, Or relay stations or access points, or base stations in future 5G networks, etc., are not limited here.
- GSM Global System of Mobile communication
- CDMA Code Division Multiple Access
- Station BTS
- NodeB, NB base station
- WCDMA Wideband Code Division Multiple Access
- Evolutional Node B, eNB or eNodeB evolved base station
- LTE Long Term Evolution
- relay stations or access points or base stations in future 5G networks, etc.
- One or more antennas can be used between the network-side device and the terminal for Multi Input Multi Output (MIMO) transmission, and MIMO transmission can be Single User MIMO (Single User MIMO, SU-MIMO) or Multi-User MIMO (Multiple User MIMO, MU-MIMO).
- MIMO transmission can be Single User MIMO (Single User MIMO, SU-MIMO) or Multi-User MIMO (Multiple User MIMO, MU-MIMO).
- MIMO transmission can be two-dimensional multiple-input multiple-output (2 Dimension MIMO, 2D-MIMO), three-dimensional multiple-input multiple-output (3 Dimension MIMO, 3D-MIMO), full-dimensional multiple input multiple output (Full Dimension MIMO, FD-MIMO) or large-scale multiple-input multiple-output (massive-MIMO), it can also be diversity transmission or precoding transmission or beamforming transmission, etc.
- the embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the above multicast control method or switching
- the chip includes a processor and a communication interface
- the communication interface is coupled to the processor
- the processor is used to run programs or instructions to implement the above multicast control method or switching
- chips mentioned in the embodiments of the present application may also be called system-on-chip, system-on-chip, system-on-a-chip, or system-on-a-chip.
- An embodiment of the present application further provides a computer program product, the computer program product is stored in a non-transitory storage medium, and the computer program product is executed by at least one processor to implement the above multicast control method or switching configuration
- Each process of the method embodiment can achieve the same technical effect, and will not be repeated here to avoid repetition.
- the embodiment of the present application further provides an electronic device, the electronic device is configured to execute the various processes of the above-mentioned multicast control method or switching configuration method embodiment, and can achieve the same technical effect, in order to avoid repetition, it is not repeated here repeat.
- the term “comprising”, “comprising” or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase “comprising a " does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that element.
- the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions are performed, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
- the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation.
- the technical solution of the present application can be embodied in the form of a software product in essence or the part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to enable a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in various embodiments of the present application.
- a terminal which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Sont divulgués dans la présente demande un procédé et un appareil de commande de multidiffusion, un procédé et un appareil de commutation de configuration, et un dispositif. Le procédé de commande de multidiffusion comprend les étapes suivantes : un nœud de réseau central envoie une signalisation de session de PDU de multidiffusion à un premier dispositif côté réseau sur la base de premières informations, les premières informations comprenant au moins l'un des éléments suivants : des informations d'un terminal qui accède au premier dispositif côté réseau ; des informations d'un service qui est mis en œuvre par le terminal ; une cellule domestique du terminal qui accède au premier dispositif côté réseau ; une demande d'établissement de session PDU de multidiffusion ; un premier service qui est le même qu'un service transmis par une session PDU de multidiffusion, et le premier service étant un service qui est demandé par un premier terminal au moyen d'une cellule qui établit la session PDU de multidiffusion, ou au moyen du premier dispositif côté réseau ; une demande de mise à jour de session PDU de multidiffusion ; un second terminal arrêtant de recevoir un service de multidiffusion qui est transmis par la session de PDU de multidiffusion ; et le second terminal qui n'est pas intéressé par le service de multidiffusion qui est transmis par la session de PDU de multidiffusion.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111081558.3 | 2021-09-15 | ||
| CN202111081558.3A CN115942400A (zh) | 2021-09-15 | 2021-09-15 | 多播控制、切换配置方法、装置及设备 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2023040748A1 true WO2023040748A1 (fr) | 2023-03-23 |
Family
ID=85601882
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2022/117843 Ceased WO2023040748A1 (fr) | 2021-09-15 | 2022-09-08 | Procédé et appareil de commande de multidiffusion, procédé et appareil de commutation de configuration, et dispositif |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115942400A (fr) |
| WO (1) | WO2023040748A1 (fr) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024230513A1 (fr) * | 2023-05-11 | 2024-11-14 | 大唐移动通信设备有限公司 | Procédé et appareil de transmission de session de multidiffusion, dispositif et support |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113068134A (zh) * | 2020-01-02 | 2021-07-02 | 维沃移动通信有限公司 | 多播业务会话操作的方法、装置和通信设备 |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3725035B1 (fr) * | 2017-12-12 | 2024-10-02 | Nokia Solutions and Networks Oy | Procédé, système et appareil de gestion de session de multidiffusion dans un réseau de communication 5g |
| CN115361656A (zh) * | 2019-11-07 | 2022-11-18 | 华为技术有限公司 | 通信方法、装置及设备 |
| CN112788543B (zh) * | 2019-11-07 | 2023-04-07 | 华为技术有限公司 | 通信方法、装置及设备 |
| CN113163337B (zh) * | 2020-01-07 | 2023-03-24 | 大唐移动通信设备有限公司 | 一种传输方式的修改方法、装置、系统、设备及介质 |
| CN113301446A (zh) * | 2020-02-21 | 2021-08-24 | 华为技术有限公司 | 传输组播业务的方法和装置 |
-
2021
- 2021-09-15 CN CN202111081558.3A patent/CN115942400A/zh active Pending
-
2022
- 2022-09-08 WO PCT/CN2022/117843 patent/WO2023040748A1/fr not_active Ceased
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113068134A (zh) * | 2020-01-02 | 2021-07-02 | 维沃移动通信有限公司 | 多播业务会话操作的方法、装置和通信设备 |
Non-Patent Citations (2)
| Title |
|---|
| "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on architectural enhancements for 5G multicast-broadcast services (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.757, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V17.0.0, 31 March 2021 (2021-03-31), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 298, XP052000263 * |
| NOKIA, NOKIA SHANGHAI BELL: "PDU session enhanced for multicast to provide the basic multicast connectivity service", 3GPP DRAFT; S2-1911366, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Reno, Nevada, USA; 20191118 - 20191122, 8 November 2019 (2019-11-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051821458 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024230513A1 (fr) * | 2023-05-11 | 2024-11-14 | 大唐移动通信设备有限公司 | Procédé et appareil de transmission de session de multidiffusion, dispositif et support |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115942400A (zh) | 2023-04-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US12587907B2 (en) | Handover method and apparatus, and information transmitting method and apparatus | |
| US11438941B2 (en) | Communication method and communications apparatus | |
| JP6017733B2 (ja) | 複数のキャリアを支援する移動通信システムで信号送受信方法及び装置 | |
| EP3783994B1 (fr) | Procédé, dispositif et système de communication | |
| JP5122638B2 (ja) | 無線資源制御状態の切替え方法、基地局およびユーザ装置 | |
| CA3190827C (fr) | Méthode de transmission de données, terminal et nœud de réseau | |
| WO2021164564A1 (fr) | Procédé et appareil de transmission de service de multidiffusion | |
| EP4199582B1 (fr) | Procédé de transmission de données mbs, appareil côté réseau et dispositif | |
| CN113661722B (zh) | 一种业务数据传输方法及装置、网络设备、终端设备 | |
| WO2022073246A1 (fr) | Procédé et appareil de communication | |
| JP2007251945A (ja) | ポイント・ツー・マルチポイントmbmsサービス情報を取得する方法及び装置 | |
| WO2021063215A1 (fr) | Procédé et dispositif de multidiffusion d'une tranche de réseau | |
| CN115843126B (zh) | 数据传输方法、装置、核心网节点、网络侧设备及终端 | |
| CN116686338A (zh) | 用于在ran节点处处置mbs的方法及装置 | |
| WO2023040748A1 (fr) | Procédé et appareil de commande de multidiffusion, procédé et appareil de commutation de configuration, et dispositif | |
| WO2023000884A1 (fr) | Procédé de traitement de session de multidiffusion, entité de fonction de réseau, appareil, et support de stockage | |
| CN114531655B (zh) | 资源指示方法、接入网侧设备及核心网功能 | |
| WO2022037441A1 (fr) | Procédé et appareil d'indication de mode de transmission pour un service mbms, et support de stockage | |
| CN116508334A (zh) | 一种通信方法及装置 | |
| WO2019028918A1 (fr) | Procédé de recherche de dispositif et dispositif associé | |
| WO2022021235A1 (fr) | Procédé et appareil de transmission de services mbs, et dispositif de communication | |
| CN117714994A (zh) | 广播会话管理方法、装置及设备 | |
| WO2022022582A1 (fr) | Procédé de traitement de transfert et station de base source | |
| WO2021163832A1 (fr) | Procédé et appareil de transmission de données | |
| CN115696216A (zh) | 一种多播广播服务业务接收方法及相关设备 |
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: 22869117 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 16/08/2024) |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 22869117 Country of ref document: EP Kind code of ref document: A1 |