WO2023015573A1

WO2023015573A1 - Communication method, devices and storage medium

Info

Publication number: WO2023015573A1
Application number: PCT/CN2021/112617
Authority: WO
Inventors: 杨皓睿; 郭雅莉; 卢飞
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-08-13
Filing date: 2021-08-13
Publication date: 2023-02-16
Also published as: CN117223303A

Abstract

Provided in the present application are a communication method, devices and a storage medium. The communication method comprises: a terminal device acquiring first information; and receiving and transmitting multicast broadcast service (MBS) data according to the first information, wherein the first information comprises at least configuration information related to an MBS. The terminal device may be a remote device in a relay scenario or a relay device, and learns, by means of first information, a configuration parameter of the relaying of an MBS, so as to achieve the aim of relaying the MBS, thereby improving the communication quality of a system.

Description

Communication method, device and storage medium

technical field

The embodiments of the present application relate to the field of communication technologies, and in particular, to a communication method, device, and storage medium.

Background technique

In wireless communication, proximity service (Proximity service, ProSe) means that the data of user equipment can be directly transmitted between user equipment without going through the network, and it can also be called device-to-device (D2D) service. At present, the fifth generation (5th generation, 5G) mobile communication system introduces the multicast broadcast service MBS, how to realize the user equipment to transmit MBS data is one of the problems that need to be solved urgently.

Contents of the invention

Embodiments of the present application provide a communication method, device, and storage medium, so as to realize the purpose of relaying MBS services, and further improve system communication quality.

In a first aspect, an embodiment of the present application provides a communication method, including: a terminal device acquires first information, the first information includes at least configuration information related to a multicast broadcast service MBS, and the first information is used for the The terminal device sends and receives MBS data.

In the second aspect, the embodiment of the present application provides a communication method, including: the network device sends first information to the terminal device, the first information includes at least configuration information related to the multicast broadcast service MBS, and the first information uses Sending and receiving MBS data to the terminal device.

In a third aspect, the embodiment of the present application provides a terminal device, including: an acquisition module, configured to acquire first information, the first information includes at least configuration information related to the multicast broadcast service MBS, and the first information uses Sending and receiving MBS data to the terminal device.

In a fourth aspect, the embodiment of the present application provides a network device, including: a sending module, configured to send first information to a terminal device, where the first information includes at least configuration information related to a multicast broadcast service MBS, and the first A message is used for the terminal equipment to send and receive MBS data.

In the fifth aspect, the embodiment of the present application provides a terminal device, a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the processing The computer executes the computer program to execute the method described in the first aspect of the present application.

In a sixth aspect, an embodiment of the present application provides a network device, a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the processing The computer executes the computer program to execute the method described in the second aspect of the present application.

In a seventh aspect, the embodiment of the present application provides a computer storage medium for storing a computer program, and when the computer program runs on a computer, the computer executes the method described in the first aspect of the present application.

In an eighth aspect, the embodiment of the present application provides a computer storage medium for storing a computer program, and when the computer program is run on a computer, the computer executes the method described in the second aspect of the present application.

In a ninth aspect, the embodiment of the present application provides a computer program product, which, when the computer program product is run on a computer, causes the computer to execute the method described in the first aspect of the present application.

In a tenth aspect, the embodiment of the present application provides a computer program product, which, when running on a computer, causes the computer to execute the method described in the second aspect of the present application.

Embodiments of the present application provide a communication method, device, and storage medium. The communication method includes: the terminal device acquires first information, and transmits and receives MBS data according to the first information, wherein the first information at least includes configuration information related to the multicast broadcast service MBS. The terminal device can be a remote device or a relay device in a relay scenario, and can obtain the configuration parameters of the relay MBS through the first information, so as to achieve the purpose of relaying the MBS, thereby improving the communication quality of the system.

Description of drawings

FIG. 1 is a first schematic diagram of a network architecture applicable to a communication method in an embodiment of the present application;

FIG. 2 is a second schematic diagram of a network architecture applicable to the communication method of the embodiment of the present application;

FIG. 3 is a first schematic diagram of a discovery process applicable to the embodiment of the present application;

FIG. 4 is a second schematic diagram of the discovery process applicable to the embodiment of the present application;

FIG. 5 is a schematic flowchart of a communication method according to an embodiment of the present application;

FIG. 6 is a first interactive schematic diagram of a communication method according to an embodiment of the present application;

FIG. 7 is a second schematic diagram of interaction of the communication method in the embodiment of the present application;

FIG. 8 is a schematic structural diagram of a terminal device provided in an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a remote device provided by an embodiment of the present application;

FIG. 10 is a schematic structural diagram of a relay device provided in an embodiment of the present application;

FIG. 11 is a schematic structural diagram of a network device provided in an embodiment of the present application;

FIG. 12 is a schematic diagram of a hardware structure of a terminal device provided in an embodiment of the present application;

FIG. 13 is a schematic diagram of a hardware structure of a network device provided by an embodiment of the present application.

Detailed ways

The technical solution in this application will be described below with reference to the accompanying drawings.

The communication method provided by this application can be applied to various communication systems, for example: Long Term Evolution (Long Term Evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) Communication System, Fifth Generation (5th Generation, 5G) Mobile Communication System or New Wireless Access Technology (new radio access technology, NR). Wherein, the 5G mobile communication system may include non-standalone networking (non-standalone, NSA) and/or standalone networking (standalone, SA).

The communication method provided by this application can also be applied to machine type communication (machine type communication, MTC), inter-machine communication long-term evolution technology (Long Term Evolution-machine, LTE-M), device to device (device to device, D2D) network , machine to machine (machine to machine, M2M) network, Internet of things (internet of things, IoT) network or other networks. Wherein, the IoT network may include, for example, the Internet of Vehicles. Among them, the communication methods in the Internet of Vehicles system are collectively referred to as vehicle to other devices (vehicle to X, V2X, X can represent anything), for example, the V2X can include: vehicle to vehicle (vehicle to vehicle, V2V) communication, vehicle and Infrastructure (vehicle to infrastructure, V2I) communication, vehicle to pedestrian (vehicle to pedestrian, V2P) or vehicle to network (vehicle to network, V2N) communication, etc.

The communication method provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system and the like. This application is not limited to this.

In the embodiment of the present application, the terminal equipment may also be referred to as user equipment (user equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal , wireless communication device, user agent, or user device.

A terminal device may be a device that provides voice/data connectivity to users, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like. At present, examples of some terminals can be: mobile phone (mobile phone), tablet computer (pad), computer with wireless transceiver function (such as notebook computer, palmtop computer, etc.), mobile internet device (mobile internet device, MID), virtual reality (virtual reality, VR) equipment, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control (industrial control), wireless terminals in self driving (self driving), wireless in remote medical (remote medical) Terminals, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless Telephones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices, or connected Other processing devices to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in the 5G network or terminal devices in the future evolution of the public land mobile network (PLMN), etc.

Among them, wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction. Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.

In addition, the terminal device may also be a terminal device in an Internet of Things (Internet of things, IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, so as to realize the intelligent network of human-machine interconnection and object interconnection. IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrow band (NB) technology.

In addition, terminal equipment can also include sensors such as smart printers, train detectors, and gas stations. The main functions include collecting data (partial terminal equipment), receiving control information and downlink data from network equipment, and sending electromagnetic waves to transmit uplink data to network equipment. .

In this embodiment of the present application, the network device may be any device with a wireless transceiver function. Network equipment includes but not limited to: evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller, BSC) , base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), wireless fidelity (wireless fidelity, WiFi) system Access point (access point, AP), wireless relay node, wireless backhaul node, transmission point (transmission point, TP) or transmission and reception point (transmission and reception point, TRP), etc., can also be 5G, such as NR , a gNB in the system, or, a transmission point (TRP or TP), one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or, it can also be a network node that constitutes a gNB or a transmission point, Such as a baseband unit (BBU), or a distributed unit (distributed unit, DU), etc.

In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU can be responsible for processing non-real-time protocols and services, for example, it can implement the radio resource control (radio resource control, RRC) layer, service data adaptive protocol (service data) Adaptation protocol (SDAP) layer and/or packet data convergence protocol (packet data convergence protocol, PDCP) layer functions. DU can be responsible for handling physical layer protocols and real-time services. For example, functions of a radio link control (radio link control, RLC) layer, a media access control (media access control, MAC) layer, and a physical (physical, PHY) layer may be implemented. A DU can be connected to only one CU or to multiple CUs, and a CU can be connected to multiple DUs, and CUs and DUs can communicate through the F1 interface. The AAU can realize some physical layer processing functions, radio frequency processing and related functions of active antennas. Because the information of the RRC layer will eventually be submitted to the PHY layer to become the information of the PHY layer, or converted from the information of the PHY layer, therefore, under this architecture, high-level signaling, such as RRC layer signaling, also It can be considered as sent by the DU, or sent by the DU+AAU.

It can be understood that the network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU can be divided into network devices in an access network (radio access network, RAN), and the CU can also be divided into network devices in a core network (core network, CN), which is not limited in this application.

The network device provides services for the cell, and the terminal device communicates with the cell through the transmission resources (for example, frequency domain resources, or spectrum resources) allocated by the network device. The cell may belong to a macro base station (for example, a macro eNB or a macro gNB, etc.) , can also belong to the base station corresponding to a small cell, where the small cell can include: a metro cell, a micro cell, a pico cell, a femto cell, etc. , these small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

In order to facilitate understanding of the embodiment of the present application, firstly, a network architecture of a communication system applicable to the embodiment of the present application is described with reference to FIG. 1 .

FIG. 1 is a first schematic diagram of a network architecture applicable to a communication method according to an embodiment of the present application. As shown in Figure 1, the network architecture includes: terminals (including user equipment, UE), access networks (including radio access network, RAN or access network , AN), user plane function (user plane function, UPF) network element, access and mobility management function (access and mobility management function, AMF) network element, session management function (session management function, SMF) network element, policy Control function (policy control function, PCF) network element, application function (application function, AF), data network (data network, DN), network slice selection function (Network Slice Selection Function, NSSF), authentication service function (Authentication Server Function, AUSF), unified data management function (Unified Data Management, UDM).

The following briefly introduces the network functions of each network element shown in FIG. 1 .

The UPF network element, the AMF network element, the SMF network element, and the PCF network element are network elements of the 3GPP core network (referred to as core network elements). UPF network elements can be called user plane functional network elements, which are mainly responsible for the transmission of user data, and other network elements can be called control plane functional network elements, which are mainly responsible for authentication, authorization, registration management, session management, mobility management and policy control etc. to ensure reliable and stable transmission of user data.

The UPF network element can be used to forward and receive terminal data. For example, the UPF network element can receive service data from the data network and transmit it to the terminal through the access network device; the UPF network element can also receive user data from the terminal through the access network device and forward it to the data network. Among them, the transmission resource allocated and scheduled by the UPF network element for the terminal is managed and controlled by the SMF network element. The bearer between the terminal and the UPF network element may include: the user plane connection between the UPF network element and the access network device, and the establishment of a channel between the access network device and the terminal. Wherein, the user plane connection is a quality of service (quality of service, QoS) flow (flow) that can establish data transmission between the UPF network element and the access network device.

The AMF network element can be used to manage the terminal's access to the core network, such as: terminal location update, network registration, access control, terminal mobility management, terminal attachment and detachment, etc. The AMF network element may also provide storage resources on the control plane for the session of the terminal in the case of providing services for the session, so as to store the session identifier, the SMF network element identifier associated with the session identifier, and the like.

The SMF network element can be used to select a user plane network element for the terminal, redirect the user plane network element for the terminal, assign an Internet protocol (internet protocol, IP) address to the terminal, and establish a bearer between the terminal and the UPF network element (also called session), session modification, release, and QoS control.

PCF network elements are used to provide policies to AMF network elements and SMF network elements, such as QoS policies and slice selection policies.

The AF network element is used to interact with the 3GPP core network element to support the routing of application-affected data, access the network exposure function, and interact with the PCF network element for policy control, etc.

The DN can provide users with data services such as the IP Multi-media Service (IMS) network and the Internet. In the DN, there can be various application servers (application server, AS), which provide different application services, such as operator services, Internet access or third-party services, etc., and the AS can realize the function of AF.

NSSF is used for the selection of network slices. The supported functions are: select the network slice instance set serving the UE; determine the allowed network slice selection assistance information (Network Slice Selection Assistance Information, NSSAI), and determine the contracted single Mapping of network slice selection assistance information (Single-Network Slice Selection Assistance Information, S-NSSAI); determine the configured NSSAI, and determine the mapping to the contracted S-NSSAI if necessary; determine the AMF set that may be used to query the UE , or determine a list of candidate AMFs based on configuration.

The AUSF is used to receive the request from the AMF to authenticate the terminal, request a key from the UDM, and then forward the issued key to the AMF for authentication processing.

UDM includes functions such as generation and storage of user subscription data, management of authentication data, and supports interaction with external third-party servers.

It should be understood that FIG. 1 is only an example, and does not constitute a limitation to the network architecture of the embodiment of the present application. During specific implementation, the network architecture may include more or fewer network elements than those shown in the figure, or combine certain network elements.

It should also be understood that each network element in FIG. 1 may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform). This embodiment of the application is not limited.

The short-distance service ProSe technology is a short-distance communication technology based on the 3GPP communication system. The ProSe service has the following functions:

1. EPC-level ProSe Discovery, EPC-level ProSe discovery function.

2. EPC support for WLAN direct discovery and communication, WLAN discovery and direct connection function.

3. Direct discovery, direct connection discovery function, for example, the terminal discovers that there are terminals that can be directly connected around.

4. Direct communication, direct communication, such as data interaction with surrounding terminals.

5. UE-to-Network Relay (U2N relay), terminal-to-network relay function. For example, UE A is in an area without network service, UE B is in a service area with network, and UE A is close to UE B, then UE A can communicate with the network through UE B's relay.

ProSe services include network controlled interactive services (NCIS). NCIS services are mainly aimed at applications such as AR/VR and games, and have high requirements on service quality such as speed, delay, packet loss rate, and high-speed codec. For example, for VR games, the rate needs to reach 10Gbps, and the packet loss rate should not exceed 10E-4. The session established for the NCIS service is an NCIS session, and UEs in the same NCIS session can be considered to form an NCIS group, such as forming a team in a game.

FIG. 2 is a second schematic diagram of a network architecture applicable to the communication method of the embodiment of the present application. As shown in Figure 2, the network architecture includes remote UE, relay UE (UE-to-Network relay), 5G radio access network (NG-RAN), 5G core network (5GC) and data network (DN). The relay UE can be a layer 3 or layer 2 relay. A PC5 link is established between the remote UE and the relay UE, and the relay UE uses a protocol data unit (PDU) session to relay data from the remote UE to the remote UE, so that the remote UE can communicate with the network. communication. Each of these PDU sessions has a type such as IPv4, IPv6, IPv6, ethernet, unstructured. Only data of this type can be transmitted using the corresponding PDU session.

In order to implement relay communication, before performing relay communication, the relay UE and the remote UE need to obtain necessary configuration parameters for relay communication. Before transmitting data, the remote UE needs to find a suitable relay UE and establish a PC5 connection with it. The relay discovery can have the following two modes: mode A (as shown in FIG. 3 ) or mode B (as shown in FIG. 4 ).

FIG. 3 is a first schematic diagram of a discovery process applicable to the embodiment of the present application. As shown in FIG. 3 , in the discovery process, the relay UE actively broadcasts a relay service code (relay service code, RSC) that can provide the relay service. For example, UE1 in FIG. 3 sends an announcement message (announcement message) to UE2, UE3, and UE4, and the announcement message includes the RSC that UE1 can provide the relay service to.

FIG. 4 is a second schematic diagram of a discovery process applicable to the embodiment of the present application. As shown in Figure 4, in the discovery process, the remote UE first sends out the RSC it needs, and if there is a relay UE around that can support the RSC, the relay UE feeds back to the remote UE. For example, UE1 in FIG. 4 sends a solicitation message to UE2, UE3, and UE4. The solicitation message includes the RSC required by UE1, and UE2 and UE3 return response messages to UE1.

After the above discovery process, the relay UE establishes a PC5 connection with the remote UE, and the remote UE communicates with the network through the relay UE.

In the evolved packet system (evolved packet system, EPS), the relay UE can relay the data of the temporary mobile group identity (TMGI) for the remote UE, and only supports the broadcast service. The remote UE first discovers the relay UE according to the RSC, establishes a PC5 connection with the relay UE, and then sends a TMGI monitoring request (TMGI monitoring request) to the relay UE. The relay UE asks the network whether to allow the relay of the TMGI, and after the network agrees, the relay UE relays the data of the TMGI for the remote UE.

At present, the multicast broadcast service has also been introduced into the 5G system, and how to realize the relay MBS is an urgent problem to be solved. It should be noted that the multicast broadcast service of the 5G system is also referred to as 5MBS for short.

In the communication method shown in the embodiment of this application, starting from the related configuration of MBS, the terminal device in the communication system, whether it is a remote device or a relay device, needs to receive configuration information related to MBS, which is used to learn the relay information in the relay scenario. MBS configuration parameters to achieve the purpose of relaying MBS. Further, the inventor considers that after the PC5 connection is established between the devices, the relay device still needs to ask the network whether it can transmit a specific multicast or broadcast service, and the communication efficiency is low, so the MBS-related information can be added to the network configuration. The mapping relationship, such as the mapping relationship between MBS and RSC, saves the number of device and network interactions, reduces the occupation of network resources, and improves the communication quality of the system.

The technical solutions shown in this application will be described in detail below through specific embodiments.

It should be noted that the following embodiments may exist independently or be combined with each other. For the same or similar content, for example, explanations of terms or nouns, and explanations of steps, etc., in different embodiments, reference may be made to each other, and repeated descriptions will not be repeated.

FIG. 5 is a schematic flowchart of a communication method according to an embodiment of the present application. As shown in Figure 5, the communication method of this embodiment includes the following steps:

Step 101, the terminal device acquires first information, the first information includes at least configuration information related to the MSB of the multicast broadcast service, and the first information is used for the terminal device to send and receive MBS data.

Step 102, the terminal device sends and receives MBS data according to the first information. (optional)

In this embodiment, the terminal device may be a relay device and/or a remote device in a relay scenario, or any terminal device in a short-distance communication scenario.

In this embodiment, the configuration information related to MBS includes at least one of the following information:

1. The mapping relationship between the relay service code RSC and the MBS identifier;

2. The mapping relationship between the data network name DNN and the MBS identifier;

3. The mapping relationship between the single network slice selection auxiliary information S-NSSAI and the MBS identifier;

4. The mapping relationship between the transmission mode and the MBS identifier;

5. The mapping relationship between QoS parameters and MBS identifiers;

6. The mapping relationship between the L2 identifier used when transmitting MBS data and the MBS identifier;

7. The mapping relationship between the access technology or access type and the MBS identifier.

In message 1, RSC is used to indicate a specific service that can be relayed. The MBS identifier is used to indicate a specific multicast service or broadcast service. The mapping relationship in information 1 indicates that the MBS identifies the MBS services that are allowed to be relayed.

Exemplarily, after the relay device receives the mapping relationship between the RSC and the MBS identifier, it receives an inquiry message broadcast by the remote device, the inquiry message includes the RSC required by the remote device, and the relay device uses the RSC and the first A mapping relationship between the RSC and the MBS identifier in the information determines whether to return a response message to the remote device. If the mapping relationship between the RSC and the MBS identifier in the first information includes the RSC in the query message, the relay device sends a response message to the remote device. The remote device can establish a PC5 connection with the relay device according to the response message. In this example, since the remote device acquires the first information including the mapping relationship between RSC and MBS identifiers, the remote device does not need to broadcast the RSC and MBS it needs through two messages, thus saving the time spent on transmitting messages. resources, which can improve the communication quality of the system.

Exemplarily, after the remote device receives the mapping relationship between the RSC and the MBS identifier, it receives a notification message broadcast by the relay device, the notification message includes the RSC supported by the relay device, and the remote device receives the RSC and The mapping relationship between the RSC and the MBS identifier in the first information determines whether to establish a PC5 connection with the relay device. If the mapping relationship between the RSC and the MBS identifier in the first information includes the RSC in the notification message, the remote device establishes a PC5 connection with the relay device. In this example, since the relay device acquires the first information including the mapping relationship between RSC and MBS identifiers, the relay device does not need to broadcast the RSC and MBS supported by itself through two messages, thus saving the time spent on transmitting messages. resources, which can improve the communication quality of the system.

In information 2, DNN is a parameter determined by the operator. Different DNNs will determine different egress locations of the core network (that is, UPF), and also determine access to different external networks. For example: IP Multimedia System (IP Multimedia System, IMS)-DNN, Internet-DNN, etc.

In information 3, S-NSSAI is an end-to-end identifier, that is, a slice identifier that can be recognized by UE, base station, and core network equipment. Different MBSs correspond to different S-NSSAIs.

Optionally, the first information includes a mapping relationship between the DNN, the S-NSSAI and the MBS identifier.

In information 4, the transmission mode includes unicast (unicast), groupcast (multicast) (groupcast/multicast), and broadcast (broadcast). The terminal device determines the MSB to be used, and based on the mapping relationship of information 4, it can determine which transmission mode to use on the PC5 interface.

In information 5, the QoS parameters may include PC5 service quality index (PC5QoS Index, PQI), 5G service quality index (5G QoS Index, 5QI), guaranteed bit rate (guaranteed bit rate, GBR), maximum bit rate (maximum bit rate , MBR), a packet delay budget (packet delay bucket, PDB) ratio (for example, 20%) corresponding to the PC5 interface, and the like. Through the mapping relationship of information 5, the terminal device can determine the QoS parameters that a certain MBS should guarantee.

In information 6, layer 2 (L2) may be the MAC layer or other layers in the access layer. Through the mapping relationship of the information 6, the terminal device can determine the L2 identification ID that should be used when transmitting the data of a certain MBS. If the first information includes the mapping relationship of the information 6, the signaling for the terminal device to query the network can be saved.

In information 7, the access technology or access type includes 3GPP access and non-3GPP access. Wherein, the 3GPP access may refer to the evolved UMTS terrestrial radio access (Evolved-UMTS Terrestrial Radio Access, E-UTRA), NR, etc. used by the PC5 interface. Non-3GPP access may refer to short-distance communication technology access, such as wifi, bluetooth, Zigbee, and the like. When the terminal device uses non-3GPP access, the terminal device uses the non-3GPP technology on the PC5 interface to transmit the corresponding MBS data. When the terminal device uses 3GPP access, the terminal device uses the 3GPP technology on the PC5 interface to transmit corresponding MBS data.

It should be noted that the above mapping relationship may also be described as a corresponding relationship.

It should be noted that the above mapping relationship is used to assist the terminal device in performing MBS-related communications.

In some embodiments, the terminal device determines the transmission mode corresponding to the MBS identifier supported by the terminal device according to the MBS identifier supported by the terminal device and the mapping relationship between the transmission mode and the MBS identifier in the first information. In this embodiment, the terminal device does not need to confirm to the network side which transmission mode the MBS identifier supported by the terminal device corresponds to, which saves interactive signaling between the terminal device and the network device.

In some embodiments, the terminal device determines the DNN corresponding to the MBS identifier supported by the terminal device according to the MBS identifier supported by the terminal device and the mapping relationship between the DNN and the MBS identifier in the first information. In this embodiment, the terminal device does not need to confirm to the network side which DNN the MBS identifier supported by the terminal device corresponds to, which saves interactive signaling between the terminal device and the network device.

In some embodiments, the terminal device determines the S-NSSAI corresponding to the MBS identifier supported by the terminal device according to the MBS identifier supported by the terminal device and the mapping relationship between the S-NSSAI and the MBS identifier. In this embodiment, the terminal device does not need to confirm to the network side which S-NSSAI the MBS identifier supported by the terminal device corresponds to, which saves interactive signaling between the terminal device and the network device.

In some embodiments, the terminal device determines the Qos parameter corresponding to the MBS ID supported by the terminal device according to the MBS ID supported by the terminal device and the mapping relationship between the QoS parameter and the MBS ID. In this embodiment, the terminal device does not need to confirm to the network side the Qos parameters corresponding to the MBS identifiers supported by the terminal device, which saves interactive signaling between the terminal device and the network device.

In some embodiments, the terminal device determines the L2 identity corresponding to the MBS identity supported by the terminal device according to the MBS identity supported by the terminal device and the mapping relationship between the L2 identity used when transmitting MBS data and the MBS identity. In this embodiment, the terminal device does not need to confirm the L2 identifier corresponding to the MBS identifier supported by the terminal device to the network side, which can save the interaction signaling between the terminal device and the network device.

In some embodiments, the terminal device determines the access technology (or access type) corresponding to the MBS ID supported by the terminal device according to the MBS ID supported by the terminal device and the mapping relationship between the access technology (or access type) and the MBS ID. ). In this embodiment, the terminal device does not need to confirm to the network side which access technology (or access type) the MBS identifier supported by the terminal device corresponds to, which saves interactive signaling between the terminal device and the network device.

In an optional embodiment of this embodiment, the MBS identifier in the above configuration information includes a temporary mobile group identifier TMGI, and the TMGI is used to indicate the service (multicast or multicast service) of the MBS. For example, TMGI 1 is used to indicate a specific multicast service, and TMGI 2 is used to indicate a specific broadcast service.

Optionally, the configuration information related to MBS includes at least one of the following information:

The mapping relationship between relay service code RSC and TMGI;

The mapping relationship between the data network name DNN and TMGI;

The mapping relationship between S-NSSAI and TMGI for single network slice selection auxiliary information;

The mapping relationship between transmission mode and TMGI;

Mapping relationship between quality of service QoS parameters and TMGI;

The mapping relationship between the L2 identifier used when transmitting TMGI data and TMGI;

The mapping relationship between access technology or access type and TMGI.

The configuration information in this embodiment may implicitly indicate that the terminal device is authorized to perform the MBS relay service.

In an optional embodiment of this embodiment, the first information further includes second information, and the second information is used to indicate whether the terminal device is authorized to perform the MBS relay service.

Optionally, the second information is used to indicate whether the terminal device is authorized to perform the MBS L2 relay service.

Optionally, the second information is used to indicate whether the terminal device is authorized to perform MBS Layer 3 (L3) relay service.

Optionally, the second information is used to indicate whether the terminal device is authorized to perform MBS L2 and L3 relay services.

The second information in this embodiment indicates whether the terminal device is authorized to perform the MBS relay service. It should be noted that both the remote device and/or the relay device in the relay scenario can obtain the above-mentioned second information.

In an optional embodiment of this embodiment, the terminal device acquiring the first information includes: the terminal device receiving the first information from the network device. Optionally, the network device may be a policy control function PCF network element or an application server AS, or other network elements, which is not limited in this embodiment.

In an optional embodiment of this embodiment, the acquiring the first information by the terminal device includes: acquiring the first information from pre-configured information by the terminal device. Optionally, the pre-configured information may be information pre-configured on the terminal device, that is, information pre-stored on the terminal device when it leaves the factory. The pre-configured information may also be information pre-configured on the SIM card of the terminal device, and the terminal device obtains the pre-stored information on the SIM card by reading the SIM card.

In some embodiments, the network device may send the first information of the same content to the terminal device of the same type according to the type of the terminal device. If the types of the two terminal devices are different, the content of the first information respectively obtained by the two terminal devices from the network side may be completely or partially different.

In some embodiments, a relay scenario includes a remote device and a relay device. The remote device receives the first information sent by the network device. The first information may include at least one of the above-mentioned mapping relationships related to MBS configured by the network for the remote device. Item parameters, such as the RSC and MBS identifier required by the remote device. Similarly, the relay device receives the first information sent by the network device, and the first information may include at least one mapping relationship related to MBS configured by the network for the relay device, and the relay device may choose to send and receive MBS according to the first information. Various parameters of the data, such as RSC and MBS identifiers supported by the relay device. In this embodiment, the contents of the first information received by the remote device and the relay device may be the same, or may be completely or partially different. In other words, the network device sends the same first information to the remote device and the relay device. Alternatively, the network device respectively sends the remote device-specific first information to the remote device, and sends the relay device-specific first information to the relay device. Optionally, the remote device-specific first information and the relay device-specific first information include one or more identical RSCs, and each identical RSC is mapped to the same MBS identifier.

In some embodiments, the network device may also send the first information of the same content to all terminal devices within the coverage of the network without distinguishing the types of the terminal devices. It should be understood that, in this embodiment, regardless of whether the terminal device is a remote device or a relay device, the content of the first information acquired from the network side is the same.

Exemplarily, the content of the configuration information in the first information sent by the network device to all terminal devices is the same, and the configuration information includes at least one of the following information:

Mapping relationship between all MBS identifiers supported by the network and RSC; mapping relationship between all MBS identifiers supported by the network and DNN; mapping relationship between all MBS identifiers supported by the network and S-NSSAI; mapping relationship between all MBS identifiers supported by the network and transmission modes ;The mapping relationship between all MBS identifiers supported by the network and QoS parameters; the mapping relationship between all MBS identifiers supported by the network and the L2 identifier used when transmitting MBS data; the mapping relationship between all MBS identifiers supported by the network and access technologies or access types relation.

In the communication method shown in this embodiment, the terminal device acquires first information, and transmits and receives MBS data according to the first information, wherein the first information includes at least configuration information related to the multicast broadcast service MBS. The terminal device may be a remote device or a relay device in a relay scenario, and can obtain the configuration parameters of the relay MBS through the first information, realize the purpose of relaying the MBS, and further improve the communication quality of the system.

The application of the above communication method in the relay scenario will be described in detail below in combination with several specific embodiments.

Exemplarily, FIG. 6 is an interactive schematic diagram 1 of the communication method according to the embodiment of the present application. The communication method in this embodiment involves the interaction between the remote device and the relay device, and the remote device and the relay device meet the short-distance communication requirements.

As shown in Figure 6, the communication method includes the following steps:

Step 201a, the remote device receives first information from the network device.

Step 201b, the relay device receives first information from the network device.

It should be noted that the execution order of step 201a and step 201b is not limited in this embodiment, that is, the remote device and the relay device may receive the first information at the same time, or receive the first information sequentially. The specific content of the first information received by the remote device and the relay device may be the same, or may be completely or partially different. For specific content of the first information, reference may be made to the foregoing embodiments, and details are not repeated here.

Step 202, the relay device sends third information to the remote device.

In this embodiment, the relay device broadcasts the third information to nearby devices, the remote device is any device within the communication range of the relay device, and the remote device can receive the third information broadcast by the relay device.

Step 203, the remote device determines whether to establish a PC5 connection with the relay device at least according to the third information.

In an optional embodiment of this embodiment, if the first information received by the remote device includes the mapping relationship between the RSC and the MBS identifier, the third information includes the first RSC for which the relay device provides the relay service. The above step 203 includes:

The remote device determines whether to establish a PC5 connection with the relay device according to the first RSC in the third information and the mapping relationship between the RSC and the MBS identifier in the first information received by the remote device. Specifically, if the mapping relationship between the RSC and the MBS identifier in the first information received by the remote device includes the first RSC, the remote device establishes a PC5 connection with the relay device.

It should be understood that if the mapping relationship between the RSC and the MBS identifier in the first information received by the remote device includes the first RSC, it means that the first RSC for which the relay device provides the relay service is an RSC supported by the remote device.

In an optional embodiment of this embodiment, if the first information received by the remote device includes the mapping relationship between the RSC and the TMGI, the third information includes the first RSC for which the relay device provides the relay service. The above step 203 includes:

The remote device determines whether to establish a PC5 connection with the relay device according to the first RSC in the third information and the mapping relationship between RSC and TMGI in the first information received by the remote device. Specifically, if the mapping relationship between RSC and TMGI in the first information received by the remote device includes the first RSC, the remote device establishes a PC5 connection with the relay device.

It should be understood that if the mapping relationship between RSC and TMGI in the first information received by the remote device includes the first RSC, it means that the first RSC for which the relay device provides the relay service is an RSC supported by the remote device.

In the above two optional embodiments, both the remote device and the relay device receive the first information from the network device, and the first information includes at least the mapping relationship between RSC and MBS identifier (or TMGI). The remote device receives third information from the relay device, where the third information includes the first RSC that the relay device provides the relay service to. The remote device may determine whether to establish a PC5 connection with the relay device according to the first information and the third information. Since the first information received by the remote device includes the mapping relationship between RSC and MBS identifier (or TMGI), if the mapping relationship includes the first RSC, the remote device can obtain the MBS identifier (or TMGI) corresponding to the first RSC based on the mapping relationship. TMGI), that is, it can be determined that both the remote device and the relay device support the first RSC and the MBS identifier (or TMGI) corresponding to the first RSC, so as to establish a PC5 connection with the relay device. Compared with the existing discovery process, the remote device does not need to ask the network through the relay device whether it is allowed to relay the data of a certain MBS identifier (or TMGI) after establishing a PC5 connection with the relay device, thus saving signaling Interaction, improve the communication efficiency of the system.

In an optional embodiment of this embodiment, if the first information received by the remote device does not include the mapping relationship between the RSC and the MBS identifier, the third information includes the first RSC and the first MBS identifier, and the first RSC is used to indicate The RSC supported by the relay device, the first MBS identifier is used to indicate the MBS service supported by the relay device. The above step 203 includes:

The remote device determines whether to establish a PC5 connection with the relay device according to the first RSC and the first MBS identifier in the third information. Specifically, if the first RSC is the RSC required by the remote device, and the first MBS identifier is the MBS identifier required by the remote device, then the remote device establishes a PC5 connection with the relay device.

In an optional embodiment of this embodiment, if the first information received by the remote device does not include the mapping relationship between RSC and TMGI, the third information includes the first RSC and the first TMGI, and the first RSC is used to indicate the relay The RSC supported by the device, and the first TMGI are used to indicate the MBS service supported by the relay device. The above step 203 includes: the remote device determines whether to establish a PC5 connection with the relay device according to the first RSC and the first TMGI in the third information. Specifically, if the first RSC is the RSC required by the remote device, and the first TMGI is the TMGI required by the remote device, then the remote device establishes a PC5 connection with the relay device.

In the above two optional embodiments, both the remote device and the relay device receive the first information from the network device, and the first information does not include the mapping relationship between the RSC and the MBS identifier (or TMGI). The remote device receives third information from the relay device, the third information includes the first RSC and the first MBS identifier (or first TMGI), wherein the first RSC is used to indicate the RSC supported by the relay device, and the first MBS identifier (or the first TMGI) is used to indicate the MBS service supported by the relay device. The remote device can directly determine whether to establish a PC5 connection with the relay device according to the third information. Since the third information received by the remote device also includes the first RSC and the first MBS identifier (or the first TMGI) supported by the relay device, the remote device can directly determine whether it also supports the first RSC and the first MBS identifier ( or the first TMGI), so as to determine whether to establish a PC5 connection with the relay device. Compared with the existing discovery process, the remote device does not need to ask the network through the relay device whether it is allowed to relay the data of a certain MBS identifier (or TMGI) after establishing a PC5 connection with the relay device, thus saving signaling Interaction, improve the communication efficiency of the system.

Exemplarily, FIG. 7 is a second schematic diagram of interaction of the communication method according to the embodiment of the present application. The communication method in this embodiment involves the interaction between the remote device and the relay device, and the remote device and the relay device meet the short-distance communication requirements.

As shown in Figure 7, the communication method includes the following steps:

Step 301a, the remote device receives first information from the network device.

Step 301b, the relay device receives first information from the network device.

It should be noted that the execution sequence of step 301a and step 301b is not limited in this embodiment, that is, the remote device and the relay device may receive the first information at the same time, or receive the first information sequentially. The specific content of the first information received by the remote device and the relay device may be the same, or may be completely or partially different. For specific content of the first information, reference may be made to the foregoing embodiments, and details are not repeated here.

Step 302, the remote device sends fourth information to the relay device.

In this embodiment, the remote device broadcasts fourth information to nearby devices, the relay device is any device within the communication range of the remote device, and the relay device can receive the fourth information broadcast by the remote device.

Step 303, the relay device determines whether to respond to the fourth information at least according to the fourth information.

In an optional embodiment of this embodiment, if the first information received by the relay device includes the mapping relationship between the RSC and the MBS identifier, the fourth information includes the second RSC required by the remote device. The above step 303 specifically includes:

The relay device determines whether to respond to the fourth information according to the second RSC in the fourth information and the mapping relationship between the RSC and the MBS identifier in the first information received by the relay device. Specifically, if the mapping relationship between the RSC and the MBS identifier in the first information received by the relay device includes the second RSC, the relay device responds to the fourth information, that is, the relay device sends a response message to the remote device, and the response message It is used to indicate that the relay device supports the second RSC and the MBS identifier corresponding to the second RSC.

In an optional embodiment of this embodiment, if the first information received by the relay device includes the mapping relationship between the RSC and the TMGI, the fourth information includes the second RSC required by the remote device. The above step 303 specifically includes:

The relay device determines whether to respond to the fourth information according to the second RSC in the fourth information and the mapping relationship between the RSC and the TMGI in the first information received by the relay device. Specifically, if the mapping relationship between RSC and TMGI in the first information received by the relay device includes the second RSC, the relay device responds to the fourth information, that is, the relay device sends a response message to the remote device, and the response message uses To instruct the relay device to support the second RSC and the TMGI corresponding to the second RSC.

In the above two optional embodiments, both the remote device and the relay device receive the first information from the network device, and the first information includes at least the mapping relationship between RSC and MBS identifier (or TMGI). The relay device receives fourth information from the remote device, where the fourth information includes the second RSC required by the remote device. The relay device may determine whether to respond to the fourth information according to the first information and the fourth information. Since the first information received by the relay device includes the mapping relationship between the RSC and the MBS identifier (or TMGI), if the mapping relationship includes the second RSC, the relay device can obtain the MBS identifier (or TMGI) corresponding to the second RSC based on the mapping relationship. TMGI), that is, it can be determined that both the relay device and the remote device support the second RSC and the MBS identity (or TMGI) corresponding to the second RSC, so as to send a response message of the fourth information to the remote device. Compared with the existing discovery process, after the remote device receives the response message returned by the relay device, it no longer needs to ask the network through the relay device whether to allow the relay of a certain MBS identifier (or TMGI) data, thus saving Signaling interaction improves system communication efficiency.

In an optional embodiment of this embodiment, if the first information received by the relay device does not include the mapping relationship between the RSC and the MBS identifier, the fourth information includes the second RSC and the second MBS identifier, and the second RSC is used for Indicates the RSC required by the remote device, and the second MBS identifier is used to indicate the MBS service required by the remote device. The above step 303 includes:

The relay device determines whether to respond to the fourth information according to the second RSC and the second MBS identifier in the fourth information. Specifically, if the second RSC is the RSC supported by the relay device, and the second MBS identifier is the MBS identifier supported by the relay device, then the relay device responds to the fourth information, that is, the relay device sends a response message to the remote device , the response message is used to indicate that the relay device supports the second RSC and the second MBS identifier.

In an optional embodiment of this embodiment, if the first information received by the relay device does not include the mapping relationship between RSC and TMGI, the fourth information includes the second RSC and the second TMGI, and the second RSC is used to indicate the remote The RSC required by the end device, and the second TMGI is used to indicate the MBS service required by the remote device. The above step 303 includes:

The relay device determines whether to respond to the fourth information according to the second RSC and the second TMGI in the fourth information. Specifically, if the second RSC is the RSC supported by the relay device, and the second TMGI is the TMGI supported by the relay device, then the relay device responds to the fourth message, that is, the relay device sends a response message to the remote device, responding The message is used to indicate that the relay device supports the second RSC and the second TMGI.

In the above two optional embodiments, both the remote device and the relay device receive the first information from the network device, and the first information does not include the mapping relationship between the RSC and the MBS identifier (or TMGI). The relay device receives fourth information from the remote device, the fourth information includes a second RSC and a second MBS identifier (or a second TMGI), wherein the second RSC is used to indicate the RSC required by the remote device, and the second MBS identifier (or the second TMGI) is used to indicate the MBS service required by the remote device. The relay device may directly determine whether to respond to the fourth information according to the fourth information. Since the fourth information received by the relay device also includes the second RSC and the second MBS identifier (or the second TMGI) required by the remote device, the relay device can directly determine whether it supports the second RSC and the second MBS identifier (or second TMGI), so as to determine whether to send a response message of the fourth information to the remote device. Compared with the existing discovery process, the remote device does not need to ask the network through the relay device whether it is allowed to relay the data of a certain MBS identifier (or TMGI) after establishing a PC5 connection with the relay device, thus saving signaling Interaction, improve the communication efficiency of the system.

The communication method provided by the embodiment of the present application is described in detail above, and the terminal device and the network device provided by the embodiment of the present application will be described below.

FIG. 8 is a schematic structural diagram of a terminal device provided by an embodiment of the present application. As shown in FIG. 8 , the terminal device 400 in this embodiment includes: an acquiring module 401 .

The obtaining module 401 is configured to obtain first information, the first information at least includes configuration information related to a multicast broadcast service MBS, and the first information is used for the terminal device to send and receive MBS data.

In an optional embodiment of this embodiment, the configuration information includes at least one of the following information:

The mapping relationship between the relay service code RSC and the MBS identifier;

The mapping relationship between the data network name DNN and the MBS identifier;

A mapping relationship between single network slice selection auxiliary information S-NSSAI and the MBS identifier;

The mapping relationship between the transmission mode and the MBS identifier;

A mapping relationship between quality of service QoS parameters and the MBS identifier;

A mapping relationship between the L2 identifier used when transmitting the MBS data and the MBS identifier;

The mapping relationship between the access technology or access type and the MBS identifier.

In an optional embodiment of this embodiment, the MBS identifier includes a Temporary Mobile Group Identity TMGI, and the TMGI is used to indicate services of the MBS.

In an optional embodiment of this embodiment, the second information is used to indicate whether the terminal device is authorized to perform the MBS relay service, including:

The second information is used to indicate whether the terminal device is authorized to perform the L2 and/or L3 relay service of the MBS.

In an optional embodiment of this embodiment, the acquiring module 401 is configured to:

receiving a first message from a network device; or

The first information is acquired from preconfigured information.

The terminal device provided in this embodiment of the present application may be a remote device and/or a relay device in a relay scenario. The terminal device is used to implement the technical solution executed by the terminal device in the method embodiment shown in FIG. 5 , and its implementation principles and technical effects are similar, and details are not repeated here.

FIG. 9 is a schematic structural diagram of a remote device provided by an embodiment of the present application. As shown in FIG. 9 , the remote device 500 in this embodiment includes: an acquiring module 501 , a first processing module 502 and a first sending module 503 .

Wherein, the obtaining module 501 may execute various steps of the obtaining module 401 shown in FIG. 8 .

In an optional embodiment of this embodiment, the acquiring module 501 is further configured to:

Receive third information from the relay device, where the third information is used by the remote device to determine whether to establish a PC5 connection with the relay device.

In an optional embodiment of this embodiment, the third information includes a first RSC for which the relay device provides a relay service, and the first information includes a mapping relationship between an RSC and an MBS identifier.

The first processing module 502 is configured to determine whether to establish a PC5 connection with the relay device according to the first RSC in the third information and the mapping relationship between the RSC and the MBS identifier in the first information .

In an optional embodiment of this embodiment, the first processing module 502 is configured to:

If the mapping relationship between the RSC and the MBS identifier in the first information includes the first RSC, the remote device determines to establish a PC5 connection with the relay device.

In an optional embodiment of this embodiment, the third information includes a first RSC and a first MBS identifier, the first RSC is used to indicate the RSC supported by the relay device, and the first MBS identifier is used Indicates the MBS service supported by the relay device.

The first processing module 502 is configured to determine whether to establish a PC5 connection with the relay device according to the first RSC and the first MBS identifier in the third information.

If the first RSC is the RSC required by the remote device, and the first MBS identifier is the MBS identifier required by the remote device, the remote device determines to establish a PC5 connection with the relay device.

In an optional embodiment of this embodiment, the first sending module 503 is configured to broadcast fourth information, and the fourth information is used by the relay device to determine whether to respond to the fourth information; the first The fourth information includes at least the second RSC, where the second RSC is used to indicate the RSC required by the remote device.

In an optional embodiment of this embodiment, the fourth information includes at least the second RSC, including: the fourth information includes the second RSC and a second MBS identifier, and the second MBS identifier is used to indicate the The MBS service required by the remote device.

The remote device provided in the embodiment of the present application can execute the technical solution executed by the terminal device in the method embodiment shown in FIG. 5 , and can also execute the technical solution executed by the remote device in the method embodiment shown in FIG. 6 or FIG. 7 , The implementation principles and technical effects are similar, and will not be repeated here.

FIG. 10 is a schematic structural diagram of a relay device provided in an embodiment of the present application. As shown in FIG. 10 , the relay device 600 in this embodiment includes: an acquiring module 601 , a second sending module 602 and a second processing module 603 .

Wherein, the acquiring module 601 may execute various steps of the acquiring module 401 shown in FIG. 8 .

In an optional embodiment of this embodiment, the second sending module 602 is configured to broadcast third information, the third information is used by the remote device to determine whether to establish a PC5 connection with the relay device, and the The remote device is a device within the communication range of the relay device; the third information includes at least a first RSC, and the first RSC is used to indicate the RSC supported by the relay device.

In an optional embodiment of this embodiment, the third information includes at least the first RSC, including: the third information includes the first RSC and the first MBS identifier, and the first MBS identifier is used to indicate the The MBS service supported by the relay device.

In an optional embodiment of this embodiment, the obtaining module 601 is configured to receive fourth information from the remote device;

The second processing module 603 is configured to determine whether to respond to the fourth information at least according to the fourth information.

In an optional embodiment of this embodiment, the fourth information includes the second RSC required by the remote device, and the first information includes a mapping relationship between the RSC and the MBS identifier.

The second processing module 603 is configured to determine whether to respond to the fourth information according to the second RSC in the fourth information and the mapping relationship between the RSC and the MBS identifier in the first information.

In an optional embodiment of this embodiment, the second processing module 603 is configured to:

If the mapping relationship between the RSC and the MBS identifier in the first information includes the second RSC, the relay device determines to respond to the fourth information.

In an optional embodiment of this embodiment, the fourth information includes a second RSC and a second MBS identifier, the second RSC is used to indicate the RSC required by the remote device, and the second MBS identifier is used Indicates the MBS service required by the remote device.

The second processing module 603 is configured to determine whether to respond to the fourth information according to the second RSC and the second MBS identifier in the fourth information.

If the second RSC is an RSC supported by the relay device, and the second MBS identifier is an MBS identifier supported by the relay device, the relay device determines to respond to the fourth information.

The relay device provided in the embodiment of the present application can execute the technical solution executed by the terminal device in the method embodiment shown in FIG. 5 , and can also execute the technical solution executed by the relay device in the method embodiment shown in FIG. 6 or FIG. 7 , The implementation principles and technical effects are similar, and will not be repeated here.

FIG. 11 is a schematic structural diagram of a network device provided by an embodiment of the present application. As shown in FIG. 11 , the network device 700 of this embodiment includes: a sending module 701 .

The sending module 701 is configured to send first information to a terminal device, the first information at least includes configuration information related to a multicast broadcast service MBS, and the first information is used for the terminal device to send and receive MBS data.

The mapping relationship between the transmission mode and the MBS identifier;

In an optional embodiment of this embodiment, the terminal device includes a remote device and/or a relay device.

In an optional embodiment of this embodiment, the network device sends the same first information to the remote device and the relay device.

In an optional embodiment of this embodiment, the network device sends the remote device-specific first information to the remote device, and sends the relay device-specific first information to the relay device. a message.

In an optional embodiment of this embodiment, the remote device-specific first information and the relay device-specific first information include one or more identical RSCs, and each identical RSC is mapped to the same The MBS logo.

The network device provided in the embodiment of the present application is used to implement the technical solutions performed by the network device in the foregoing method embodiments, and its implementation principle and technical effect are similar, and details are not repeated here.

It should be noted that it should be understood that the above division of each module of the terminal device or network device is only a division of logical functions, which may be fully or partially integrated into one physical entity or physically separated during actual implementation. And these modules can all be implemented in the form of calling software through processing elements; they can also be implemented in the form of hardware; some modules can also be implemented in the form of calling software through processing elements, and some modules can be implemented in the form of hardware. For example, the processing module can be a separate processing element, or it can be integrated in a chip of the above-mentioned device. In addition, it can also be stored in the memory of the above-mentioned device in the form of program code, and a certain processing element of the above-mentioned device can Call and execute the functions of the modules identified above. The implementation of other modules is similar. In addition, all or part of these modules can be integrated together, and can also be implemented independently. The processing element mentioned here may be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or an instruction in the form of software.

For example, the above modules may be one or more integrated circuits configured to implement the above method, for example: one or more specific integrated circuits (application specific integrated circuit, ASIC), or, one or more microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (field programmable gate array, FPGA), etc. For another example, when one of the above modules is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (central processing unit, CPU) or other processors that can call program codes. For another example, these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).

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

FIG. 12 is a schematic diagram of a hardware structure of a terminal device provided by an embodiment of the present application. As shown in FIG. 12, the terminal device 800 in this embodiment may include:

Transceiver 801, processor 802, memory 803;

The memory 803 stores computer-executable instructions;

The processor 802 executes the computer-executed instructions stored in the memory 803, so that the processor 802 executes the technical solution of the terminal device in any of the foregoing method embodiments.

Optionally, the memory 803 can be independent or integrated with the processor 802 . When the memory 803 is a device independent of the processor 802, the electronic device 800 may further include: a bus 804, configured to connect the memory 803 and the processor 802.

Optionally, the processor 802 may be a chip.

The terminal device provided in this embodiment can be used to execute the method performed by the terminal device in any of the foregoing method embodiments, and its implementation principles and technical effects are similar, and will not be repeated here.

The embodiment of the present application also provides a network device. The network device may be a policy control function PCF network element or an application server AS, or other network elements, which is not limited in this embodiment.

FIG. 13 is a schematic structural diagram of a network device provided by an embodiment of the present application. As shown in FIG. 13, the network device 900 of this embodiment includes:

Transceiver 901, processor 902, memory 903;

The memory 903 stores computer-executable instructions;

The processor 902 executes the computer-executed instructions stored in the memory 903, so that the processor 902 executes the technical solution of the network device in any of the foregoing method embodiments.

Optionally, the memory 903 can be independent or integrated with the processor 902 . When the memory 903 is a device independent of the processor 902 , the electronic device 900 may further include: a bus 904 , configured to connect the memory 903 and the processor 902 .

Optionally, the processor 902 may be a chip.

The network device provided in this embodiment can be used to implement the method performed by the network device in any of the foregoing method embodiments, and its implementation principles and technical effects are similar, and will not be repeated here.

An embodiment of the present application also provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to implement the terminal in any of the foregoing method embodiments. Equipment technical solutions.

The embodiment of the present application also provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to implement the network in any of the preceding method embodiments. Equipment technical solutions.

The embodiment of the present application further provides a program, which is used to implement the technical solution of the terminal device in any of the foregoing method embodiments when the program is executed by a processor.

The embodiment of the present application further provides a program, which is used to execute the technical solution of the network device in any one of the foregoing method embodiments when the program is executed by a processor.

An embodiment of the present application further provides a computer program product, including program instructions, and the program instructions are used to implement the technical solution of the terminal device in any one of the foregoing method embodiments.

An embodiment of the present application further provides a computer program product, including program instructions, and the program instructions are used to realize the technical solution of the network device in any one of the foregoing method embodiments.

The embodiment of the present application also provides a chip, including: a processing module and a communication interface, where the processing module can implement the technical solutions of the terminal device in the foregoing method embodiments. Further, the chip also includes a storage module (such as a memory), the storage module is used to store instructions, and the processing module is used to execute the instructions stored in the storage module, and the execution of the instructions stored in the storage module makes the processing module execute the instructions of the terminal device. Technical solutions.

The embodiment of the present application also provides a chip, including: a processing module and a communication interface, where the processing module can implement the technical solution of the network device in the foregoing method embodiment. Further, the chip also includes a storage module (such as a memory), the storage module is used to store instructions, and the processing module is used to execute the instructions stored in the storage module, and the execution of the instructions stored in the storage module makes the processing module execute the instructions of the network device. Technical solutions.

In the present application, "at least two" means two or more, and "multiple" means two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the contextual objects are an "or" relationship; in the formula, the character "/" indicates that the contextual objects are a "division" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one item (piece) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein, a, b, c can be single or multiple indivual.

It can be understood that the various numbers involved in the embodiments of the present application are only for convenience of description, and are not used to limit the scope of the embodiments of the present application.

It can be understood that, in the embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the order of execution, and the order of execution of the processes should be determined by their functions and internal logic, and should not be used in the implementation of this application. The implementation of the examples constitutes no limitation.

Claims

A communication method, characterized in that, comprising:

The terminal device acquires first information, where the first information includes at least configuration information related to the multicast broadcast service MBS, and the first information is used for the terminal device to send and receive MBS data.
The method according to claim 1, wherein the configuration information includes at least one of the following information:

The mapping relationship between the relay service code RSC and the MBS identifier;

The mapping relationship between the data network name DNN and the MBS identifier;

A mapping relationship between single network slice selection auxiliary information S-NSSAI and the MBS identifier;

The mapping relationship between the transmission mode and the MBS identifier;

A mapping relationship between quality of service QoS parameters and the MBS identifier;

A mapping relationship between the L2 identifier used when transmitting the MBS data and the MBS identifier;

The mapping relationship between the access technology or access type and the MBS identifier.
The method according to claim 2, wherein the MBS identity includes a Temporary Mobile Group Identity (TMGI), and the TMGI is used to indicate services of the MBS.
The method according to any one of claims 1-3, wherein the first information further includes second information, and the second information is used to indicate whether the terminal device is authorized to perform the MBS centralization. Follow up service.
The method according to claim 4, wherein the second information is used to indicate whether the terminal device is authorized to perform the MBS relay service, comprising: the second information is used to indicate the terminal Whether the device is authorized to perform the L2 and/or L3 relay service of the MBS.
The method according to any one of claims 1-5, wherein the acquiring the first information by the terminal device includes:

The terminal device receives first information from a network device; or

The terminal device acquires the first information from preconfigured information.
The method according to any one of claims 1-6, wherein the terminal device is a remote device.
The method according to claim 7, wherein the method further comprises:

The remote device receives third information from the relay device, and the third information is used by the remote device to determine whether to establish a PC5 connection with the relay device.
The method according to claim 8, wherein the third information includes the first RSC for which the relay device provides relay services, and the first information includes a mapping relationship between RSC and MBS identifier; the method Also includes:

The remote device determines whether to establish a PC5 connection with the relay device according to the first RSC in the third information and the mapping relationship between the RSC and the MBS identifier in the first information.
The method according to claim 9, wherein the remote device determines whether to match the first RSC in the third information and the mapping relationship between the RSC and the MBS identifier in the first information The relay device establishes the PC5 connection, including:

If the mapping relationship between the RSC and the MBS identifier in the first information includes the first RSC, the remote device determines to establish a PC5 connection with the relay device.
The method according to claim 8, wherein the third information includes a first RSC and a first MBS identifier, the first RSC is used to indicate the RSC supported by the relay device, and the first MBS The identifier is used to indicate the MBS service supported by the relay device;

The method further includes: the remote device determines whether to establish a PC5 connection with the relay device according to the first RSC and the first MBS identifier in the third information.
The method according to claim 11, wherein the remote device determines whether to establish a PC5 connection with the relay device according to the first RSC and the first MBS identifier in the third information, include:

If the first RSC is the RSC required by the remote device, and the first MBS identifier is the MBS identifier required by the remote device, the remote device determines to establish a PC5 connection with the relay device.
The method according to claim 7, wherein the method further comprises:

The remote device broadcasts fourth information, and the fourth information is used by the relay device to determine whether to respond to the fourth information; the fourth information includes at least a second RSC, and the second RSC is used to indicate The RSC required by the remote device.
The method according to claim 13, wherein the fourth information includes at least the second RSC, including:

The fourth information includes the second RSC and a second MBS identifier, where the second MBS identifier is used to indicate the MBS service required by the remote device.
The method according to any one of claims 1-6, wherein the terminal device is a relay device.
The method according to claim 15, further comprising:

The relay device broadcasts third information, the third information is used by the remote device to determine whether to establish a PC5 connection with the relay device, and the remote device is a device within the communication range of the relay device; The third information includes at least a first RSC, and the first RSC is used to indicate the RSC supported by the relay device.
The method according to claim 16, wherein the third information includes at least the first RSC, including:

The third information includes the first RSC and a first MBS identifier, where the first MBS identifier is used to indicate the MBS service supported by the relay device.
The method according to claim 15, further comprising:

The relay device receives fourth information from the remote device;

The relay device determines whether to respond to the fourth information at least according to the fourth information.
The method according to claim 18, wherein the fourth information includes the second RSC required by the remote device, and the first information includes the mapping relationship between the RSC and the MBS identifier;

The relay device determines whether to respond to the fourth information at least according to the fourth information, including:

The relay device determines whether to respond to the fourth information according to the second RSC in the fourth information and the mapping relationship between the RSC and the MBS identifier in the first information.
The method according to claim 19, wherein the relay device determines whether to respond to the second RSC in the fourth information and the mapping relationship between the RSC and the MBS identifier in the first information The fourth information above, including:

If the mapping relationship between the RSC and the MBS identifier in the first information includes the second RSC, the relay device determines to respond to the fourth information.
The method according to claim 18, wherein the fourth information includes a second RSC and a second MBS identifier, the second RSC is used to indicate the RSC required by the remote device, and the second MBS The identifier is used to indicate the MBS service required by the remote device;

The relay device determines whether to respond to the fourth information at least according to the fourth information, including:

The relay device determines whether to respond to the fourth information according to the second RSC and the second MBS identifier in the fourth information.
The method according to claim 21, wherein the relay device determines whether to respond to the fourth information according to the second RSC and the second MBS identifier in the fourth information, including:

If the second RSC is an RSC supported by the relay device, and the second MBS identifier is an MBS identifier supported by the relay device, the relay device determines to respond to the fourth information.
A communication method, characterized in that, comprising:

The network device sends first information to the terminal device, where the first information includes at least configuration information related to the multicast broadcast service MBS, and the first information is used for the terminal device to send and receive MBS data.
The method according to claim 23, wherein the configuration information includes at least one of the following information:

The mapping relationship between the relay service code RSC and the MBS identifier;

The mapping relationship between the data network name DNN and the MBS identifier;

A mapping relationship between single network slice selection auxiliary information S-NSSAI and the MBS identifier;

The mapping relationship between the transmission mode and the MBS identifier;

A mapping relationship between quality of service QoS parameters and the MBS identifier;

A mapping relationship between the L2 identifier used when transmitting the MBS data and the MBS identifier;

The mapping relationship between the access technology or access type and the MBS identifier.
The method according to claim 24, wherein the MBS identity includes a Temporary Mobile Group Identity (TMGI), and the TMGI is used to indicate services of the MBS.
The method according to any one of claims 23-25, wherein the first information further includes second information, and the second information is used to indicate whether the terminal device is authorized to perform the MBS centralization. Follow up service.
The method according to claim 26, wherein the second information is used to indicate whether the terminal device is authorized to perform the MBS relay service, comprising: the second information is used to indicate the terminal Whether the device is authorized to perform the L2 and/or L3 relay service of the MBS.
The method according to any one of claims 23-27, wherein the terminal device includes a remote device and/or a relay device.
The method according to claim 28, wherein the network device sends the same first information to the remote device and the relay device.
The method according to claim 28, wherein the network device sends the remote device-specific first information to the remote device, and sends the relay device-specific first information to the relay device. the first message.
The method according to claim 30, wherein the remote device-specific first information and the relay device-specific first information include one or more identical RSCs, and each identical RSC is mapped to to the same MBS ID.
A terminal device, characterized in that it includes:

An acquiring module, configured to acquire first information, where the first information includes at least configuration information related to a multicast broadcast service (MBS), and the first information is used for the terminal device to send and receive MBS data.
The terminal device according to claim 32, wherein the configuration information includes at least one of the following information:

The mapping relationship between the relay service code RSC and the MBS identifier;

The mapping relationship between the data network name DNN and the MBS identifier;

A mapping relationship between single network slice selection auxiliary information S-NSSAI and the MBS identifier;

The mapping relationship between the transmission mode and the MBS identifier;

A mapping relationship between quality of service QoS parameters and the MBS identifier;

A mapping relationship between the L2 identifier used when transmitting the MBS data and the MBS identifier;

The mapping relationship between the access technology or access type and the MBS identifier.
The terminal device according to claim 33, wherein the MBS identity includes a Temporary Mobile Group Identity (TMGI), and the TMGI is used to indicate services of the MBS.
The terminal device according to any one of claims 32-34, wherein the first information further includes second information, and the second information is used to indicate whether the terminal device is authorized to perform the MBS Relay service.
The terminal device according to claim 35, wherein the second information is used to indicate whether the terminal device is authorized to perform the MBS relay service, including: the second information is used to indicate the Whether the terminal device is authorized to perform the L2 and/or L3 relay service of the MBS.
The terminal device according to any one of claims 32-36, wherein the acquiring module is configured to:

receiving a first message from a network device; or

The first information is acquired from preconfigured information.
The terminal device according to any one of claims 32-37, wherein the terminal device is a remote device.
The terminal device according to claim 38, wherein the acquiring module is also used for:

Receive third information from the relay device, where the third information is used by the remote device to determine whether to establish a PC5 connection with the relay device.
The terminal device according to claim 39, wherein the third information includes a first RSC for which the relay device provides relay services, and the first information includes a mapping relationship between an RSC and an MBS identifier; the The remote device also includes: a first processing module;

The first processing module is configured to determine whether to establish a PC5 connection with the relay device according to the first RSC in the third information and the mapping relationship between the RSC and the MBS identifier in the first information.
The terminal device according to claim 40, wherein the first processing module is configured to:

If the mapping relationship between the RSC and the MBS identifier in the first information includes the first RSC, the remote device determines to establish a PC5 connection with the relay device.
The terminal device according to claim 39, wherein the third information includes a first RSC and a first MBS identifier, the first RSC is used to indicate the RSC supported by the relay device, and the first The MBS identifier is used to indicate the MBS service supported by the relay device; the remote device further includes: a first processing module;

The first processing module is configured to determine whether to establish a PC5 connection with the relay device according to the first RSC and the first MBS identifier in the third information.
The terminal device according to claim 42, wherein the first processing module is configured to:

If the first RSC is the RSC required by the remote device, and the first MBS identifier is the MBS identifier required by the remote device, the remote device determines to establish a PC5 connection with the relay device.
The terminal device according to any one of claims 39-43, wherein the remote device further comprises: a first sending module;

The first sending module is configured to broadcast fourth information, where the fourth information is used by the relay device to determine whether to respond to the fourth information; the fourth information includes at least a second RSC, and the second The RSC is used to indicate the RSC required by the remote device.
The terminal device according to claim 44, wherein the fourth information includes at least the second RSC, including:

The fourth information includes a second RSC and a second MBS identifier, where the second MBS identifier is used to indicate the MBS service required by the remote device.
The terminal device according to any one of claims 32-37, wherein the terminal device is a relay device.
The terminal device according to claim 46, wherein the relay device further comprises: a second sending module;

The second sending module is configured to broadcast third information, the third information is used by the remote device to determine whether to establish a PC5 connection with the relay device, and the remote device is within the communication range of the relay device the device; the third information includes at least a first RSC, and the first RSC is used to indicate the RSC supported by the relay device.
The terminal device according to claim 47, wherein the third information includes at least the first RSC, including:

The third information includes the first RSC and the first MBS identifier, where the first MBS identifier is used to indicate the MBS service supported by the relay device.
The terminal device according to claim 46, wherein the relay device further comprises: a second processing module;

The obtaining module is configured to receive fourth information from the remote device;

The second processing module is configured to determine whether to respond to the fourth information at least according to the fourth information.
The terminal device according to claim 49, wherein the fourth information includes the second RSC required by the remote device, and the first information includes the mapping relationship between the RSC and the MBS identifier;

The second processing module is configured to determine whether to respond to the fourth information according to the second RSC in the fourth information and the mapping relationship between the RSC and the MBS identifier in the first information.
The terminal device according to claim 50, wherein the second processing module is configured to:

If the mapping relationship between the RSC and the MBS identifier in the first information includes the second RSC, the relay device determines to respond to the fourth information.
The terminal device according to claim 49, wherein the fourth information includes a second RSC and a second MBS identifier, the second RSC is used to indicate the RSC required by the remote device, and the second The MBS identifier is used to indicate the MBS service required by the remote device;

The second processing module is configured to determine whether to respond to the fourth information according to the second RSC and the second MBS identifier in the fourth information.
The terminal device according to claim 52, wherein the second processing module is configured to:

If the second RSC is an RSC supported by the relay device, and the second MBS identifier is an MBS identifier supported by the relay device, the relay device determines to respond to the fourth information.
A network device, characterized in that it includes:

A sending module, configured to send first information to a terminal device, the first information at least including configuration information related to a multicast broadcast service MBS, and the first information is used for the terminal device to send and receive MBS data.
The network device according to claim 54, wherein the configuration information includes at least one of the following information:

The mapping relationship between the relay service code RSC and the MBS identifier;

The mapping relationship between the data network name DNN and the MBS identifier;

A mapping relationship between single network slice selection auxiliary information S-NSSAI and the MBS identifier;

The mapping relationship between the transmission mode and the MBS identifier;

A mapping relationship between quality of service QoS parameters and the MBS identifier;

A mapping relationship between the L2 identifier used when transmitting the MBS data and the MBS identifier;

The mapping relationship between the access technology or access type and the MBS identifier.
The network device according to claim 55, wherein the MBS identity includes a Temporary Mobile Group Identity (TMGI), and the TMGI is used to indicate services of the MBS.
The network device according to any one of claims 54-56, wherein the first information further includes second information, and the second information is used to indicate whether the terminal device is authorized to perform the MBS Relay service.
The network device according to claim 57, wherein the second information is used to indicate whether the terminal device is authorized to perform the MBS relay service, including: the second information is used to indicate the Whether the terminal device is authorized to perform the L2 and/or L3 relay service of the MBS.
The network device according to any one of claims 54-58, wherein the terminal device includes a remote device and/or a relay device.
The network device according to claim 59, wherein the network device sends the same first information to the remote device and the relay device.
The network device according to claim 59, wherein the network device sends the remote device-specific first information for the remote device, and sends the relay device for the relay device Specific primary information.
The network device according to claim 61, wherein the remote device-specific first information and the relay device-specific first information include one or more identical RSCs, and each identical RSC Map to the same MBS ID.
A terminal device, characterized in that it includes: a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the processor runs the The computer program performs the method according to any one of claims 1-22.
A network device, characterized by comprising: a memory and a processor, the memory is used to store a computer program, the processor is used to call and run the computer program from the memory, so that the processor runs the Said computer program performs the method according to any one of claims 23-31.
A computer storage medium, which is characterized in that it is used to store a computer program, and when the computer program is run on a computer, the computer is made to execute the method according to any one of claims 1-22.
A computer storage medium, characterized in that it is used for storing a computer program, and when the computer program is run on a computer, the computer is made to execute the method according to any one of claims 23-31.
A computer program product, characterized in that, when the computer program product is run on a computer, the computer is made to execute the method according to any one of claims 1-22.
A computer program product, characterized in that, when the computer program product is run on a computer, the computer is made to execute the method according to any one of claims 23-31.