Method for configuring a bearer, network-side device and terminal

Abstract

The application discloses a method for configuring a bearer, a network side device and a terminal, and belongs to the technical field of wireless communication. The method for configuring the bearer comprises the following steps: a radio access network (RAN) node sends first configuration information to a first user equipment (UE), wherein the first configuration information is used for configuring a bearer of multi-UE cooperative transmission.

Description

Technical Field

[0001] This application belongs to the field of wireless communication technology, specifically relating to a bearer configuration method, network-side equipment, and terminal. Background Technology

[0002] In the existing mechanism, a User Equipment (UE) establishes its own control plane and user plane connections with the core network, such as a Protocol Data Unit (PDU) session. When the UE moves between different cells, different base stations, or even different core network nodes, the network side transmits the UE's control plane and user plane connections, as well as its transmission status, between different network nodes to ensure that the UE's service transmission can be continuous, uninterrupted, and achieve lossless performance as required.

[0003] When two UEs transmit data, each UE establishes its own core network or access network control plane connection and user plane connection. For example, the Non-Access Stratum (NAS) connection (core network control plane), Radio Resource Control (RRC) connection (access network control plane), PDU session (core network user plane), Data Radio Bearer (DRB), and Quality of Service (QoS) flow (access network user plane) are all independent for each UE. Therefore, multi-UE cooperative transmission cannot be achieved in existing technologies. Summary of the Invention

[0004] This application provides a bearer configuration method, network-side device, and terminal, which can solve the problem that multi-UE cooperative transmission cannot be achieved in the prior art.

[0005] In a first aspect, a bearer configuration method is provided, comprising: a radio access network (RAN) node sending first configuration information to a first user equipment (UE), wherein the first configuration information is used to configure a bearer for multi-UE cooperative transmission.

[0006] Secondly, a bearer configuration device is provided, comprising: a first acquisition module, configured to acquire first configuration information of a first UE, wherein the first configuration information is used to configure a bearer for multi-UE cooperative transmission; and a first transceiver module, configured to send the first configuration information to the first UE.

[0007] Thirdly, a configuration method for multi-UE cooperative transmission is provided, including: the core network device sending association information to the RAN node, wherein the association information is used to indicate that a first UE and a second UE have an association relationship, and the first UE and the second UE have the ability to establish multi-UE cooperative transmission.

[0008] Fourthly, a configuration device for multi-UE cooperative transmission is provided, comprising: a second acquisition module for acquiring association information, wherein the association information is used to indicate that a first UE and a second UE have an association relationship, and the first UE and the second UE have the ability to establish multi-UE cooperative transmission; and a second transceiver module for sending the association relationship to a RAN node.

[0009] Fifthly, a method for requesting multi-UE cooperative transmission is provided, comprising: a first UE sending a first request to a RAN node, wherein the first request is used to request the RAN node to configure a bearer for multi-UE cooperative transmission for the first UE, and the first request carries an identifier of a second UE.

[0010] In a sixth aspect, a request apparatus for multi-UE cooperative transmission is provided, comprising: a first determining module, configured to determine that a first UE needs to perform multi-UE cooperative transmission; and a third transceiver module, configured to send a first request to a RAN node, wherein the first request is configured to request the RAN node to configure a bearer for multi-UE cooperative transmission for the first UE, and the first request carries an identifier of a second UE.

[0011] In a seventh aspect, a response method for multi-UE cooperative transmission is provided, comprising: a second UE receiving second configuration information sent by a RAN node, wherein the second configuration information is used to instruct the second UE to perform bearer configuration for multi-UE cooperative transmission for a first UE; and, if agreeing to perform multi-UE cooperative transmission for the first UE, the second UE applying the second configuration information to send a configuration completion message to the RAN node.

[0012] Eighthly, a response device for multi-UE cooperative transmission is provided, comprising: a fourth transceiver module, configured to receive second configuration information sent by a RAN node, wherein the second configuration information is used to instruct the second UE to perform bearer configuration for multi-UE cooperative transmission for a first UE; a second determination module, configured to determine whether to agree to perform multi-UE cooperative transmission for the first UE; the fourth transceiver module is further configured to, if agreeing to perform multi-UE cooperative transmission for the first UE, the second UE applies the second configuration information and sends a configuration completion message to the RAN node.

[0013] In a ninth aspect, a terminal is provided, the terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method as described in the fifth aspect, or implement the steps of the method as described in the seventh aspect.

[0014] In a tenth aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the seventh aspect, and the communication interface is configured to communicate with an external device.

[0015] Eleventhly, a network-side device is provided, the network-side device including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein when the program or instructions are executed by the processor, they implement the steps of the method described in the first aspect, or implement the steps of the method described in the third aspect.

[0016] In a twelfth aspect, a network-side device is provided, including a processor and a communication interface, wherein the processor is configured to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the third aspect, and the communication interface is configured to communicate with an external device.

[0017] In a thirteenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fifth aspect, or the steps of the method described in the seventh aspect.

[0018] In a fourteenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fifth aspect, or the steps of the method described in the seventh aspect.

[0019] In a fifteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a non-transient storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method described in the first aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fifth aspect, or the steps of the method described in the seventh aspect.

[0020] In this embodiment of the application, the Radio Access Network (RAN) node can send a first configuration to the first UE to configure the bearer for multi-UE cooperative transmission, thereby enabling the first UE to perform multi-UE cooperative transmission. Attached Figure Description

[0021] Figure 1 This diagram illustrates a wireless communication system to which embodiments of this application may be applied;

[0022] Figure 2 This illustration shows a flowchart of a bearer configuration method provided in an embodiment of this application;

[0023] Figure 3a This diagram illustrates a multi-UE transmission architecture provided in an embodiment of this application.

[0024] Figure 3b A schematic diagram of another multi-UE transmission architecture provided in an embodiment of this application is shown;

[0025] Figure 3c This diagram illustrates yet another multi-UE transmission architecture provided in an embodiment of this application;

[0026] Figure 4 This illustration shows a flowchart of a configuration method for multi-UE cooperative transmission provided in an embodiment of this application;

[0027] Figure 5 This illustration shows a flowchart of a configuration method for multi-UE cooperative transmission provided in an embodiment of this application;

[0028] Figure 6 This illustration shows a flowchart of a response method for multi-UE cooperative transmission provided in an embodiment of this application;

[0029] Figure 7 This illustration shows a flowchart of a bearer establishment method for multi-UE cooperative transmission provided in an embodiment of this application;

[0030] Figure 8 This illustration shows another flowchart of the bearer establishment method for multi-UE cooperative transmission provided in an embodiment of this application;

[0031] Figure 9 This illustration shows a structural schematic diagram of a carrying configuration device provided in an embodiment of this application;

[0032] Figure 10 This illustration shows a structural diagram of a configuration device for multi-UE cooperative transmission provided in an embodiment of this application;

[0033] Figure 11 This illustration shows a structural diagram of a configuration device for multi-UE cooperative transmission provided in an embodiment of this application;

[0034] Figure 12 This diagram illustrates a structural schematic of a response device for multi-UE cooperative transmission provided in an embodiment of this application.

[0035] Figure 13 This illustration shows a structural diagram of a communication device provided in an embodiment of this application;

[0036] Figure 14 This illustration shows a hardware structure diagram of a terminal provided in an embodiment of this application;

[0037] Figure 15 This diagram illustrates the hardware structure of a network-side device according to an embodiment of this application. Detailed Implementation

[0038] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0039] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0040] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to applications beyond NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0041] Figure 1This diagram illustrates a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as a terminal device or user equipment (UE). The terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), etc. Wearable devices include smartwatches, wristbands, headphones, glasses, etc. It should be noted that this application does not limit the specific type of terminal 11. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this application embodiment, only the base station in the NR system is used as an example, but the specific type of base station is not limited.

[0042] The following description, in conjunction with the accompanying drawings, details the bearer configuration method, network-side equipment, and terminal provided in this application through some embodiments and application scenarios.

[0043] Figure 2 This diagram illustrates a flowchart of a bearer configuration method according to an embodiment of this application. This method 200 can be executed by a RAN node. In other words, the method can be executed by software or hardware installed on the RAN node. Figure 2 As shown, the method may include the following steps.

[0044] S210, the RAN node sends first configuration information to the first UE, wherein the first configuration information is used to configure the bearer for multi-UE cooperative transmission.

[0045] In the embodiments of this application, the RAN node can be a base station or a centralized unit (CU), and there is no specific limitation in the embodiments of this application.

[0046] In related technologies, the access network or core network connections of different UEs are independent of each other, and each UE can only transmit services independently. However, in actual use, users may need two UEs to transmit services together. For example, when a user is listening to music / books on their phone indoors and is about to go for a run, the user wants the wristband to continuously receive related services to provide a continuous service experience. Alternatively, when the transmit power of a UE is limited or the uplink transmission rate is insufficient, the transmit power and transmission capacity of two or more UEs can be used for joint transmission. Or, when the user's service has high reliability, a connection backup can be established between two or more UEs, and the link used for transmission can be determined based on the link quality to meet the requirements of low latency and high reliability. However, these scenarios cannot be supported in the existing architecture and mechanism. Users need to manually set the service reception and reception progress on the new device or through the service layer to achieve the effect of continuous reception, or use hard handover to change the link, which reduces the convenience of the experience and the user's QoS experience. In the technical solution provided in the embodiments of this application, the RAN node configures a bearer for multi-UE cooperative transmission for the first UE, thereby enabling the first UE to be used for multi-UE cooperative transmission, improving the convenience of service transmission and the user QoS experience.

[0047] Optionally, the first configuration information may include: the identifier of the second UE and the configuration information of the bearer architecture.

[0048] In this embodiment, the configuration information of the bearer architecture refers to the multi-UE architecture configuration for multi-UE cooperative transmission (also known as aggregation transmission, backup transmission, or handover transmission, etc.), which may include, for example, the configuration of the multi-UE architecture for multi-UE cooperative transmission (also known as aggregation transmission, backup transmission, or handover transmission, etc.). Figure 3a The Packet Data Convergence Protocol (PDCP) anchor architecture shown is as follows: Figure 3b The Radio Link Control (RLC) anchor architecture shown is as follows: Figure 3c Configuration information for at least one of the Media Access Control (MAC) anchor architectures shown.

[0049] Of course, it's not limited to this; multi-UE architecture, in addition to... Figures 3a to 3c In addition to the architecture shown, other architectures can also be adopted. For example, some common functions of a certain layer (such as PDCP or MAC) can be set in the first UE, while the split functions can be set in the second UE.

[0050] In practical applications, the protocol can choose one or more architectures. If an architecture is selected, the first configuration information includes the configuration of the protocol entities related to that architecture. If two or more architectures are used, the RAN node can select and configure different architectures as needed. This application does not limit the specific implementation.

[0051] In one possible implementation, to avoid a situation where the first UE needs to release the newly established multi-UE cooperative transmission bearer due to the second UE disagreeing with multi-UE cooperative transmission, the method may further include: before the RAN node sends the first configuration information to the first UE, the method further includes: the RAN node sending the second configuration information to the second UE, wherein the second configuration information is used to instruct the second UE to configure the bearer for multi-UE cooperative transmission for the first UE; the RAN node receiving a configuration completion message returned by the second UE. Using this possible implementation, the RAN node first sends the second configuration information to the second UE, and after receiving the configuration completion message from the second UE, it then sends the first configuration information to the first UE. This allows the bearer of the first UE to be reconfigured only after the second UE agrees to multi-UE cooperative transmission, avoiding wasted time.

[0052] In the embodiments of this application, the RAN node can independently determine whether to send the first configuration information to the first UE, or it can send the first configuration information to the first UE under the trigger of the core network, or it can send the first configuration information to the first UE at the request of the first UE. These will be described separately below.

[0053] (I) Core Network Triggering

[0054] In this possible implementation, prior to S210, the method may further include: the RAN node receiving association information issued by the core network, wherein the association information is used to indicate the association relationship between the first UE and the second UE.

[0055] Because multi-UE architecture involves deep cooperation between two or more UEs, it requires the use of the transmission capabilities and hardware resources of other UEs, and involves some billing and security factors. Therefore, a typical scenario is that users who need to perform multi-UE architecture transmission first go through a process such as signing up to statically establish their association (also known as binding relationship). For example, a user's mobile phone and wearable device, or even home appliance, can initialize their association through a signing process. Similarly, specific equipment in a factory that needs to work collaboratively can also initialize their association through a pre-defined process.

[0056] Generally, the relationships between the signing process or the pre-initialization process need to be stored in the core network node, which is responsible for verifying the validity of the relationships.

[0057] Optionally, a contractual or pre-existing relationship may include one of the following:

[0058] (1) A group of UEs with related relationships, in which the UEs can cooperate with each other to transmit, and each UE can decide whether to be the primary UE (P-UE) or the secondary UE (S-UE) as needed;

[0059] (2) A list of UEs with related relationships, wherein the attribute P-UE or S-UE of each UE is preset in advance;

[0060] (3) A list of related UEs, in which the attributes that each UE can support are set, such as P-UEonly, S-UE only, or both P-UE and S-UE;

[0061] The aforementioned relationships can be based on UE granularity, meaning that any service between these UEs can be established and transmitted through a multi-UE architecture. Alternatively, they can be based on the granularity of a specific service, meaning that based on the UE list, restrictions can be placed on what kind of services these UEs can establish and transmit through a multi-UE architecture. These service restrictions can include service identifiers, specific QoS parameters of the service, and the range of specific QoS parameters of the service.

[0062] Among them, the primary UE (P-UE) is the UE that initiates the service or the service source / higher-level protocol of the service transmission is located in the UE, while the secondary UE (S-UE) assists the primary UE in performing service transmission. It generally only has the lower-level protocol layer of the transmission protocol and only performs the related functions of assisting transmission.

[0063] The core network stores the association relationships of the aforementioned subscription process or pre-initialization process, and sends them to the RAN nodes when needed to facilitate subsequent multi-UE architecture configuration by the RAN nodes. In one possible implementation, the association relationship information sent by the core network to the RAN nodes may include at least one of the following:

[0064] (1) A list of UE identifiers with associated relationships, wherein the list of UE identifiers includes the identifier of the first UE and the identifier of the second UE; for example, a list of UE IDs with binding relationships, wherein the UE ID can be a globally unique identifier, a UE identifier within a Public Land Mobile Network (PLMN), an identifier within an Access and Mobility Management Function (AMF) node, or an identifier within a gNB / CU, and can be an S-Temporary Mobile Subscription Identifier (S-TMSI), an AMF UE ID, or a gNB UE ID, etc.

[0065] (2) First service identification information, wherein the first service identification information is used to indicate services capable of performing multi-UE cooperative transmission; that is, to indicate that each UE in the UE identification list has an association relationship based on a specific service. The first service identification information may be a service identifier (service ID, service code, QoS flow ID, etc.) or a service characteristic, such as a service that satisfies that the QoS parameter is equal to a certain value or is within a certain range.

[0066] (3) The attributes of each UE in the UE identifier list that have a relationship. For example, P-UE only, S-UE only, or both P-UE and S-UE.

[0067] In this possible implementation, the core network device may send the association information to the RAN node under at least one of the following circumstances:

[0068] (1) The core network device (CN) learns that both the first UE and the second UE are in the connected state; since the CN can obtain the connected UEs activated under the RAN node from the information reported by the RAN node in real time, the CN can send the association information of the related UEs to the RAN node;

[0069] (2) The core network device discovers that the first UE has entered the connected state, wherein the first UE and the second UE have an association relationship based on any service; for example, when a UE enters the connected state, if the core network device discovers that the UE has an association relationship, it sends the association relationship information of the UE to the UE's serving RAN node.

[0070] (3) After the core network device discovers that the first UE has entered the connected state and initiated the first service, the first UE and the second UE are associated with each other based on the target service, and the target service includes the first service; for example, when a UE enters the connected state and initiates a service, if the core network device discovers that the UE is associated with the service, it sends the association information of the UE to the UE's serving RAN node.

[0071] (4) Receive a second request sent by the RAN node. The second request is used to request all UEs associated with the first UE, or the second request is used to request UEs that are associated with the first UE based on a second service. That is, the RAN node actively requests the CN node. For example, the RAN node requests the CN node as needed, which can be determined by the RAN node itself or triggered after a UE requests the RAN node. The RAN node can request the binding relationships of all its UEs, the binding relationships of a specific UE, or the binding relationships of a specific service of a specific UE.

[0072] Through the technical solution provided in the embodiments of this application, the RAN node can configure bearers for multi-UE cooperative transmission for the first UE and the second UE respectively under the trigger of the core network equipment, thereby realizing the cooperative transmission between the first UE and the second UE.

[0073] (ii) RAN nodes are determined automatically

[0074] In this possible implementation, the RAN node may send first configuration information to the first UE if it determines that the first condition is met.

[0075] Optionally, the first condition includes, but is not limited to, at least one of the following:

[0076] (1) The RAN node obtains the association relationship information between the first UE and the second UE from the core network; for example, the RAN node is sent the association relationship between UEs by the CN, so it knows whether the UEs can or need to carry out cooperative transmission (or aggregation / backup / switching transmission);

[0077] (2) The RAN node, as the service node of the first UE, determines that the first UE and the second UE with an association relationship are in a connected state; for example, when the RAN node, as the service node of the UE, discovers that two or more UEs with a binding relationship have entered the connected state, it has the feasibility to establish cooperative / aggregated / backup / switching transmission.

[0078] (3) The RAN node, as the serving node of the first UE, determines that at least some of the service transmissions of the first UE cannot meet the QoS requirements or service experience requirements; the RAN node pages the second UE to determine that the second UE enters the connected state; for example, if the RAN node, as the serving node of the P-UE, finds that one or more service transmissions of the P-UE cannot meet the QoS requirements or service experience requirements, it can actively page the corresponding S-UE within the coverage area of ​​the RAN node to make the S-UE enter the connected state and perform cooperative / aggregated / backup / switching transmissions for the P-UE.

[0079] (4) At least some of the services currently provided by the first UE have the feature of supporting multi-UE transmission. For example, the services currently provided by the -P-UE have the feature of supporting collaborative / aggregated / backup / switching transmission.

[0080] In one possible implementation, to ensure communication between the first UE and the second UE, before sending the first configuration information to the first UE after the RAN node determines that predetermined conditions are met, the method may further include: the RAN node determining that the transmission distance and / or link status between the first UE and the second UE meets the multi-UE transmission requirements. For example, the RAN node can determine this based on location or home cell information, or it can query the first UE to obtain the transmission distance and / or link status between the first UE and the second UE.

[0081] After satisfying the above prerequisites, the RAN can determine at least one of the following: there is a CN-licensed association between the first UE and the second UE; the first UE and the second UE are located under the same base station and can communicate with each other; or the service of the first UE has the characteristics of establishing a multi-UE architecture. Therefore, the RAN node can initiate the process of establishing a multi-UE architecture. For example, it may include the following steps:

[0082] Step 1: The RAN node sends a reconfiguration message to the second UE, which carries the second configuration information.

[0083] Optionally, the second configuration information may include: the first UE identifier and the configuration of the split bearer, etc., so that the second UE can determine whether to agree to establish a multi-UE cooperative transmission architecture for the first UE;

[0084] Optionally, the second configuration information may also include a second DRB identifier, which is used to indicate that the second UE performs multi-UE cooperative transmission for the first UE. Through the second DRB identifier, the second UE can determine whether it agrees to perform multi-UE cooperative transmission for the first UE's designated DRB (i.e., the DRB corresponding to the second DRB identifier).

[0085] Step 2: If the second UE agrees, the configuration is completed according to the received reconfiguration message, and a configuration completion message is returned to the network side (i.e., the RAN node).

[0086] If the second UE disagrees, the process ends.

[0087] Step 3: The RAN node sends a reconfiguration message to the first UE, which carries the first configuration information;

[0088] Optionally, the first configuration information may include: the second UE identifier, and bearer architecture information and related configurations, so that the first UE knows that a multi-UE transmission architecture has been established with the second UE and completes the configuration according to the received reconfiguration message instructions;

[0089] Optionally, the first configuration information may also carry a third DRB-ID, which is used to indicate the service bearer configured for multi-UE cooperative transmission for the first UE.

[0090] Step 4: The first UE returns a configuration completion message to the network side.

[0091] Afterwards, the first UE can send the data packet (with the specified DRB ID) to the second UE, which will then transmit it to the network side. Downlink transmission is similar.

[0092] It should be noted that the purpose of the second and third DRB IDs mentioned above is to enable the second UE and the first UE to obtain the association relationship of the forked bearer. For example, for a certain DRB bearer (bearer identifier DRB ID 1), which forks into a Local Area Identifier (LCID) 1 located in the first UE and an LCID 2 located in the second UE, the RAN node can configure the association in the following way when configuring the first and second configuration information:

[0093] (1) Configure the first UE as DRB ID 1 to split into the first UE's LCID1 and the second UE's LCID2 (i.e., the third DRB identifier), and configure the second UE as LCID 2 (i.e. the second DRB identifier). The first UE and the second UE can know that the data stream is associated with DRB1 through LCID2;

[0094] (2) Configure DRB ID1 for the first UE and associate it with the LCID (i.e., the third DRB identifier) ​​1 of the first UE. Configure LCID2 for the second UE and associate it with the DRB ID 1 (i.e., the second DRB identifier) ​​of the first UE. The first UE and the second UE can know that the two data streams are associated with the same DRB1 through DRB ID 1.

[0095] In this possible implementation, the RAN node may also query the first UE whether to establish a multi-UE architecture, or query the first UE whether to establish a multi-UE architecture for a specific service. After receiving an affirmative response from the first UE, S210 is executed. For example, the RAN node may query the first UE after determining that the first condition is met.

[0096] The RAN node also needs to query the second UE to see if it agrees to establish a multi-UE architecture or a multi-UE architecture based on a specific service. After the UE agrees, the multi-UE architecture or the multi-UE architecture for a specific service is configured, that is, the bearer configuration for multi-UE cooperative transmission is performed.

[0097] Through this possible implementation, the RAN node can configure the bearer for multi-UE cooperative transmission or the bearer for multi-UE cooperative transmission of a specific service when the first condition is met, thereby enabling multi-UE cooperative transmission.

[0098] (III) First UE Request

[0099] In this possible implementation, prior to S210, the method may further include: receiving a first request sent by the first UE, wherein the first request is used to request the first configuration information, and the first request carries an identifier of the second UE. Through the first request, the first UE requests the RAN node to perform cooperative transmission (or aggregate transmission, backup transmission, handover transmission) with the second UE.

[0100] Optionally, the first request may also carry second service identification information, which is used to indicate the service information that the first UE expects to perform multi-UE cooperative transmission.

[0101] For example, the second service identification information includes, but is not limited to, at least one of the following:

[0102] (1) First Radio Data Bearer (DRB) identifier; the first DRB identifier may be an identifier of a data radio bearer that has been established by the current first UE;

[0103] (2) Service ID; the service ID can be the identifier of a service that the first UE is currently transmitting or will transmit in the future;

[0104] (3) QoS flow ID; the QoS flow ID can be the QoS flow ID that the first UE is currently transmitting or will transmit in the future.

[0105] (4) Service characteristic information. For example, the QoS parameter value is equal to a certain value or is within a certain range. Through this characteristic information, it can be determined that the first UE expects to perform multi-UE protocol transmission services.

[0106] In one possible implementation, after receiving a first request from the first UE, the RAN node sends second configuration information to the second UE, wherein the second configuration information is used to instruct the second UE to perform bearer configuration for multi-UE cooperative transmission for the first UE.

[0107] The second configuration information is the same as the second configuration information in the above possible implementation methods. For details, please refer to the relevant descriptions in the above implementation methods, which will not be repeated here.

[0108] In one possible implementation, after the RAN node sends the second configuration information to the second UE, if the RAN node receives a configuration completion message sent by the second UE, it indicates that the second UE agrees to perform multi-UE cooperative transmission for the first UE. Then, the RAN node sends a reconfiguration message to the first UE, wherein the reconfiguration message carries the first configuration information.

[0109] The first configuration information is the same as the first configuration information in the above possible implementation methods. For details, please refer to the relevant descriptions in the above implementation methods, which will not be repeated here.

[0110] In practical applications, after the above-mentioned multi-UE cooperative transmission is established, due to some reason, such as changes in the service transmission of the first UE, changes in the service transmission of the second UE, or changes in the load of the RAN node, it is necessary to modify or release the bearer of the multi-UE cooperative transmission. Therefore, after the above-mentioned multi-UE cooperative transmission bearer is established, it may be necessary to modify or release the bearer.

[0111] Therefore, in one possible implementation, after S210, the method may further include:

[0112] Step 1: The RAN node sends a first reconfiguration command to the second UE, wherein the first reconfiguration signaling carries the identifier of the first UE, the first bearer identifier for reconfiguration, and the reconfiguration content information, and the bearer corresponding to the first bearer identifier is the bearer for multi-UE cooperative transmission;

[0113] Step 2: The RAN node sends a second reconfiguration command to the first UE, wherein the second reconfiguration signaling carries the identifier of the second UE, the first bearer identifier, and the reconfiguration content information.

[0114] It should be noted that there is no strict order in which steps 1 and 2 are executed. The RAN node can send the first reconfiguration command to the second UE first, and then send the second reconfiguration command to the first UE, or vice versa. This application does not limit the specific implementation. For example, as an optional approach, the RAN node can send the second reconfiguration command to the first UE after receiving the reconfiguration completion message from the second UE.

[0115] Optionally, after the RAN node sends the second reconfiguration command to the first UE, the RAN node may also receive a reconfiguration completion message sent by the first UE, so that the RAN node can know that the first UE has completed the reconfiguration.

[0116] In another possible implementation, after S210, the method may further include:

[0117] Step 1: The RAN node sends a first release command to the second UE, wherein the first release command carries the identifier of the first UE, the second bearer identifier to be released, and the content information to be released, and the bearer corresponding to the second bearer identifier is the bearer for the multi-UE cooperative transmission;

[0118] Step 2: The RAN node sends a second release command to the first UE, wherein the second release command carries the identifier of the second UE, the second bearer identifier, and the release content information.

[0119] It should be noted that there is no strict order in which steps 1 and 2 are executed. The RAN node can send the first release command to the second UE first, and then send the second release command to the first UE, or vice versa. This application does not limit the specific implementation. For example, as an optional approach, the RAN node can send the second release command to the first UE after receiving the release completion message from the second UE.

[0120] Optionally, after the RAN node sends the second release command to the first UE, the RAN node may also receive a release completion message sent by the first UE, so that the RAN node can know that the first UE has completed the release.

[0121] Since the multi-UE architecture is a joint transmission architecture established between the RAN node, the first UE, and the second UE, the RAN node, the first UE, and the second UE may all propose modifications to this joint transmission architecture (i.e., the aforementioned multi-UE architecture, or multi-UE transmission architecture, or multi-UE cooperative transmission architecture). For example, the first UE or the second UE can request modifications from the network, and once the network agrees, the modification process will be executed.

[0122] Therefore, in one possible implementation, before the RAN node sends the first reconfiguration command to the second UE, the method further includes: receiving a modification request sent by the first UE or the second UE, wherein the modification request is used to request modification of the bearer corresponding to the first bearer identifier.

[0123] Alternatively, before the RAN node sends the first release command to the second UE, the method further includes: receiving a release request sent by the first UE or the second UE, wherein the release request is used to request the release of the bearer corresponding to the second bearer identifier.

[0124] Of course, this is not the only limitation. As a centralized control entity, the RAN node has direct decision-making power. For example, when the RAN node is under high load and cannot support this multi-UE transmission architecture, the RAN node can modify part or all of the bearers for multi-UE cooperative transmission. Furthermore, when a UE's service ends, the RAN node can directly release the bearers for multi-UE cooperative transmission.

[0125] Once the multi-UE architecture has been modified or released, it will no longer be used, or a new configuration will be used for transmission.

[0126] Figure 4 This diagram illustrates a configuration method for multi-UE cooperative transmission provided in an embodiment of this application. This method 400 can be executed by a core network device. In other words, the method can be executed by software or hardware installed on the core network device. Figure 4 As shown, the method may include the following steps.

[0127] S410, the core network device sends association information to the RAN node, wherein the association information is used to indicate that the first UE and the second UE have an association relationship, and the first UE and the second UE have the ability to establish multi-UE cooperative transmission.

[0128] The method 400 provided in this application embodiment is the core network side execution flow corresponding to method 200. It has a corresponding implementation method related to the possible implementation methods of method 200 involving core network equipment. For details, please refer to the description of method 200. The following only describes the possible implementation methods of the steps involving core network equipment.

[0129] In one possible implementation, before the core network device sends the association information to the RAN node, the method further includes at least one of the following:

[0130] (1) The core network device learns that both the first UE and the second UE are in a connected state;

[0131] (2) The core network equipment discovers that the first UE has entered the connected state, wherein the first UE and the second UE have an association relationship based on any service;

[0132] (3) After the core network device discovers that the first UE has entered the connected state and initiated the first service, the first UE and the second UE are associated based on the target service, and the target service includes the first service;

[0133] (4) Receive a second request sent by the RAN node, the second request being used to request all UEs associated with the first UE, or the second request being used to request UEs that are associated with the first UE based on the second service.

[0134] Optionally, the association information sent by the core network equipment to the RAN node may include at least one of the following:

[0135] (1) A list of UE identifiers with associated relationships, wherein the list of UE identifiers includes the identifier of the first UE and the identifier of the second UE;

[0136] (2) First service identification information, wherein the first service identification information is used to indicate a service that can perform multi-UE cooperative transmission; for example, the first service identification information may include DRB ID, Service ID, QoS flow ID or service feature information, etc.

[0137] (3) The attributes of each UE indicated in the UE identifier list with association relationships.

[0138] In one possible implementation, before the core network device sends the association information to the RAN node, the method further includes: the core network device obtaining the association information subscribed to by the first UE or the association information pre-set by the first UE.

[0139] For example, contractual or pre-set association information may include one of the following:

[0140] (1) A list of UEs with binding relationships, in which the UEs can cooperate with each other to transmit, and each UE can decide whether to act as a P-UE or S-UE as needed;

[0141] (2) A list of UEs with binding relationships, wherein the attribute P-UE or S-UE of each UE is preset in advance;

[0142] (3) A list of UEs with binding relationships, wherein each UE can support attributes such as P-UE only, S-UE only, or both P-UE and S-UE are set.

[0143] The aforementioned binding relationship can be based on UE granularity, meaning that any service between these UEs can establish and transmit a multi-UE architecture. Alternatively, it can be based on the granularity of a specific service, meaning that based on the UE list, restrictions can be placed on what kind of services these UEs can establish and transmit a multi-UE architecture for. These service restrictions can include service identifiers, specific QoS parameters of the service, and the range of specific QoS parameters of the service.

[0144] Through the technical solution provided in the embodiments of this application, the core network equipment can trigger the RAN node to perform bearer configuration for multi-UE cooperative transmission, thereby enabling multi-UE cooperative transmission between the first UE and the second UE, ensuring the UE's service experience and system efficiency.

[0145] Figure 5 This diagram illustrates a configuration method for multi-UE cooperative transmission provided in an embodiment of this application. This method 500 can be executed by a first UE. In other words, the method can be executed by software or hardware installed on the first UE. Figure 5 As shown, the method may include the following steps.

[0146] S510, the first UE sends a first request to the RAN node, wherein the first request is used to request the RAN node to configure a bearer for multi-UE cooperative transmission for the first UE, and the first request carries the identifier of the second UE.

[0147] The method 500 provided in this application embodiment is the execution flow of the first UE corresponding to method 200. It has a corresponding implementation method related to the possible implementation methods of method 200 involving the first UE. For details, please refer to the description of method 200. The following only describes the possible implementation methods of the steps executed by the first UE.

[0148] In one possible implementation, before the first UE sends the first request to the RAN node, the method may further include:

[0149] Step 1: The first UE sends a third request through the interface between UEs, wherein the third request is used to request aggregated transmission for the first UE;

[0150] Step 2: The first UE receives a confirmation message from the second UE, wherein the confirmation message carries the identifier of the second UE.

[0151] Through this possible implementation, the first UE can interact with the second UE and obtain the identifier of the second UE.

[0152] In one possible implementation, the first request sent by the first UE also carries second service identification information, which is used to indicate the service information that the first UE expects to perform multi-UE cooperative transmission.

[0153] Optionally, the second service identification information includes, but is not limited to, at least one of the following:

[0154] (1) First DRB identifier;

[0155] (2) Service identifier;

[0156] (3) QoS flow identifier;

[0157] (4) Business characteristics information.

[0158] In one possible implementation, after the first UE sends the first request to the RAN node, the method may further include:

[0159] Step 1: The first UE receives a reconfiguration message sent by the RAN node, wherein the reconfiguration message carries first configuration information, which is used to configure a bearer for multi-UE cooperative transmission for the first UE;

[0160] Step 2: The first UE applies the first configuration information to perform reconfiguration.

[0161] For example, after receiving the first request, the RAN node can reconfigure the second UE according to the first request, and then send the above-mentioned reconfiguration message to the first UE to configure the multi-UE transmission architecture bearer for the first UE.

[0162] Optionally, the first configuration information includes: the second UE identifier and the configuration information of the bearer architecture.

[0163] Optionally, the first configuration information further includes: a third DRB identifier, used to indicate the service bearer configured for multi-UE cooperative transmission for the first UE.

[0164] In one possible implementation, after the first UE receives the reconfiguration message sent by the RAN node, the method further includes:

[0165] Step 1: Receive the second reconfiguration command sent by the RAN node, wherein the second reconfiguration signaling carries the identifier of the second UE, the first bearer identifier of the reconfiguration, and the reconfiguration content information, and the bearer corresponding to the first bearer identifier is the bearer for multi-UE cooperative transmission;

[0166] Step 2: Execute the second reconfiguration command.

[0167] For example, when the current network state cannot support one or more multi-UE cooperative transmission, the RAN node can send the second configuration command to modify the multi-UE cooperative transmission bearer.

[0168] Alternatively, the first UE may request the RAN node to modify the multi-UE cooperative transmission. Therefore, in one possible implementation, before receiving the second reconfiguration command sent by the RAN node, the method may further include: sending a modification request to the RAN node, wherein the modification request is used to request modification of the bearer corresponding to the first bearer identifier.

[0169] In another possible implementation, after the first UE receives the reconfiguration message sent by the RAN node, the method further includes:

[0170] Step 1: Receive the second release command sent by the RAN node, wherein the second release command carries the identifier of the second UE, the second bearer identifier to be released, and the content information to be released, and the bearer corresponding to the second bearer identifier is the bearer of the multi-UE cooperative transmission;

[0171] Step 2: Execute the second release command to release the bearer corresponding to the second bearer identifier.

[0172] For example, the RAN node can send the second release command after completing the service that the first UE needs to cooperate in transmitting.

[0173] Alternatively, the RAN node may send the second release command based on a request from the first UE. Therefore, in an optional implementation, before receiving the second release command sent by the RAN node, the method may further include: sending a release request to the RAN node, wherein the release request is used to request the release of the bearer corresponding to the second bearer identifier.

[0174] The technical solution provided in this application embodiment allows the first UE to request the RAN node to configure the bearer for multi-UE cooperative transmission when needed, thereby enabling multi-UE cooperative transmission between the first UE and the second UE, ensuring the UE's service experience and system efficiency.

[0175] Figure 6This diagram illustrates a response method for multi-UE cooperative transmission provided in an embodiment of this application. This method 600 can be executed by a second UE. In other words, the method can be executed by software or hardware installed on the second UE. Figure 6 As shown, the method may include the following steps.

[0176] S610, the second UE receives second configuration information sent by the RAN node, wherein the second configuration information is used to instruct the second UE to perform bearer configuration for multi-UE cooperative transmission for the first UE.

[0177] S612, if the first UE agrees to perform multi-UE cooperative transmission, the second UE applies the second configuration information and sends a configuration completion message to the RAN node.

[0178] The method 600 provided in this application embodiment is the execution flow of the second UE corresponding to method 200. It has a corresponding implementation method related to the possible implementation methods of method 200 involving the second UE. For details, please refer to the description of method 200. The following only describes the possible implementation methods of the steps executed by the second UE.

[0179] In one possible implementation, the second configuration information includes: the identifier of the first UE and the configuration information of the forked bearer.

[0180] In one possible implementation, the second configuration information further includes: a second DRB identifier, used to indicate that the second UE performs multi-UE cooperative transmission of service bearers for the first UE.

[0181] In one possible implementation, before the second UE receives the second configuration information sent by the RAN node, the method further includes:

[0182] Step 1: The second UE receives a third request sent by the first UE, wherein the third request is used to request aggregated transmission for the first UE;

[0183] Step 2: The second UE sends a confirmation message to the first UE, wherein the confirmation message carries the identifier of the second UE.

[0184] In one possible implementation, after sending a configuration complete message to the RAN node, the method further includes:

[0185] Step 1: Receive the first reconfiguration command sent by the RAN node, wherein the first reconfiguration signaling carries the identifier of the first UE, the first bearer identifier of the reconfiguration, and the reconfiguration content information, and the bearer corresponding to the first bearer identifier is the bearer for multi-UE cooperative transmission;

[0186] Step 2: Execute the first reconfiguration command.

[0187] For example, when service transmission or network environment changes, the RAN node can send the first configuration command to modify the bearer for multi-UE cooperative transmission.

[0188] Alternatively, the RAN node can also modify the bearer for multi-UE cooperative transmission based on a request from the second UE. For example, if the second UE's own service transmission increases or decreases, and its ability to cooperate with the first UE decreases or increases, requiring modification of the bearer for multi-UE cooperative transmission, it can send a request to the RAN node. Therefore, in one possible implementation, before receiving the first reconfiguration command sent by the RAN node, the method further includes: sending a modification request to the RAN node, wherein the modification request is used to request modification of the bearer corresponding to the first bearer identifier.

[0189] In one possible implementation, after sending a configuration complete message to the RAN node, the method further includes:

[0190] Step 1: Receive a first release command sent by the RAN node, wherein the first release command carries the identifier of the first UE, the second bearer identifier to be released, and the content information to be released, and the bearer corresponding to the second bearer identifier is the bearer for multi-UE cooperative transmission;

[0191] Step 2: Execute the first release command to release the bearer corresponding to the second bearer identifier.

[0192] For example, the RAN node can send the first release command after the first UE has completed the service request for cooperative transmission.

[0193] Alternatively, the RAN node can also modify the bearer for multi-UE cooperative transmission based on a request from the second UE. For example, if the second UE's own service transmission increases, making it unable to cooperate with the first UE for transmission, and it needs to release the bearer for multi-UE cooperative transmission, it can initiate a request to the RAN node. Therefore, in one possible implementation, before receiving the first release command sent by the RAN node, the method further includes: sending a release request to the RAN node, wherein the release request is used to request the release of the bearer corresponding to the second bearer identifier.

[0194] Through the technical solution provided in the embodiments of this application, the second UE can respond to the RAN node to configure the bearer for multi-UE cooperative transmission, thereby establishing a multi-UE cooperative transmission bearer, enabling multi-UE cooperative transmission between the first UE and the second UE, and ensuring the UE's service experience and system efficiency.

[0195] The following description uses the first UE (i.e., the primary UE, P-UE) request as an example to illustrate the technical solution provided in the embodiments of this application.

[0196] Figure 7 This illustration shows a flowchart of a bearer establishment method for multi-UE cooperative transmission provided in an embodiment of this application, such as... Figure 7 As shown, the method mainly includes the following steps.

[0197] S701, P-UE refers to a UE that needs to transmit services. Through the UE-to-UE interface, it makes requests to other S-UEs in its vicinity. For example, it sends an aggregation transmission request, as well as backup transmission requests, handover transmission requests, etc. Through this request, it asks the S-UE whether it can perform aggregated transmission for itself.

[0198] The request may include at least one or a combination of the following information:

[0199] (1) User identifier of P-UE. This user identifier is used to identify P-UE. On the one hand, it is to confirm the intention and authorization. On the other hand, it is to facilitate the gNB to identify and recognize the two UEs in subsequent processes. The identifier can be a globally unique identifier, a unique identifier within the PLMN, or an identifier under the serving base station / cell, such as S-TMSI, C-RNTI, etc.

[0200] (2) The P-UE’s own serving base station. The purpose of carrying the serving base station is to implement the multi-UE architecture under one base station as much as possible, so as to avoid introducing interfaces between base stations, which would greatly increase complexity and latency.

[0201] S702, the S-UE initiates an RRC connection establishment process with the corresponding serving base station and performs the process of activating its own Security Mode Command (SMC).

[0202] If the S-UE is currently in RRC Connected state, this step can be omitted. This step obtains a UE identifier for the S-UE that the gNB can recognize. This identifier can be a globally unique identifier, a PLMN-unique identifier, or an identifier under the serving base station / cell, such as S-TMSI, C-RNTI, etc.

[0203] S703 If the S-UE agrees to perform aggregation / backup / switching transmission for the P-UE, it can reply with confirmation to the P-UE and inform it of its own UE identifier.

[0204] S704 After obtaining the consent of the S-UE or its UE identifier, the P-UE reports a request to its serving base station for multi-UE architecture configuration, carrying the UE identifier of the S-UE, indicating that the P-UE is performing aggregation / backup / switching transmission with the specified S-UE.

[0205] S704 can be initiated directly without omitting S701-S703, as long as there has been interaction between P-UE and S-UE and the user identifier of S-UE is available.

[0206] In S705, after receiving a request from a P-UE, the base station generates the corresponding configuration and sends it to the designated S-UE.

[0207] The S705 allows the base station to obtain the consent of the system-user (S-UE) to determine its willingness to perform aggregation / backup / switching transmissions for the user-user (P-UE). The configuration information sent by the base station to the S-UE includes a P-UE identifier, indicating the configured multi-UE architecture P-UE, facilitating the S-UE's current willingness assessment and subsequent collaborative operations.

[0208] After S706 and S-UE agree, the configuration is executed and a confirmation is returned to gNB.

[0209] S707, the gNB performs a multi-architecture confirmation operation to the P-UE. Optionally, the message sent by the gNB to the P-UE may also carry the corresponding configuration of the multi-UE architecture.

[0210] The above process provides a schematic example of the request and related signaling flow for establishing a multi-UE architecture between P-UE and S-UE. Since no service information is specified in this process, and only permission and configuration are applied to the two UEs, it can be understood that any aggregation / backup / switching bearer can be established between these two UEs at this time. For example, all bearers of the P-UE can be configured for multi-UE architecture transmission; alternatively, the base station algorithm can determine, based on service QoS, etc., the required P-UE bearers to be configured for multi-UE architecture transmission; or, the base station can configure the permitted P-UE bearers for multi-UE architecture transmission based on the binding information issued by the core network.

[0211] Figure 8 This illustration shows another flowchart of the bearer establishment method for multi-UE cooperative transmission provided in this application embodiment, such as... Figure 8 As shown, the method mainly includes the following steps.

[0212] S801, P-UE sends a multi-UE architecture request to the network. This request may carry the user identifier of S-UE and the service information that is expected to be transmitted in a multi-UE architecture.

[0213] This business information may include at least one of the following:

[0214] (1) DRB ID, the identifier of the data radio bearer that the current P-UE has established;

[0215] (2) Service ID or QoS flow ID, the identifier of the service that the P-UE is currently transmitting or will transmit in the future, QoS flow identifier, etc.

[0216] (3) Characteristics of the service, such as the QoS parameter value being equal to a certain value or falling within a certain range.

[0217] Before S801, S701-S703 of method 700 can also be executed. The difference between method 800 and method 700 is that method 800 is a process for establishing a multicast architecture based on specific business needs.

[0218] S802, the base station sends reconfiguration information to the S-UE to configure the bearer related to the multi-UE architecture.

[0219] The reconfiguration information sent by the base station to the S-UE can carry the following information:

[0220] (1) The user identifier of P-UE is used to facilitate S-UE to identify P-UE, whether it is willing to establish aggregation / backup / switching bearer for it, and if so, to identify each other when working together in the future;

[0221] (2) DRB ID, which the base station explicitly specifies for which bearer aggregation / backup / switching configuration;

[0222] (3) Information such as RLC, MAC, PHY, LCID, etc. can be used to configure the S-UE side for aggregation / backup / switching bearers.

[0223] S803 If the S-UE agrees, it will prepare according to the configuration and reply to the base station that the configuration is complete.

[0224] S804, the base station returns a bearer reconfiguration confirmation to the P-UE, confirming that the requested or specified bearer DRB ID has been configured with the corresponding aggregation / backup / handover multi-UE architecture configuration.

[0225] Subsequently, the P-UE can hand over its DRB ID data to the S-UE, which will then send it to the gNB.

[0226] The multi-UE architecture configuration for aggregation / backup / switching mentioned in method 700 above mainly refers to Figure 3a The PDCP anchor architecture shown Figure 3bThe RLC anchor architecture shown, and Figure 3c One or more of the MAC anchor architectures shown.

[0227] Of course, in addition to the architectures mentioned above, it is also possible to place some common functions of a certain layer, such as PDCP or MAC, in P-UE, while placing the split function in S-UE. Such an architecture can also work.

[0228] The protocol may select one or more architectures. If only one architecture is selected, the network side will configure the protocol entities related to that architecture by default. If two or more architectures are selected, the network side can select and configure different architectures as needed.

[0229] The method provided in this application embodiment allows the RAN side to configure multiple UEs, enabling multiple devices to transmit together under the control of the network side, thus ensuring the UE's service experience and system efficiency.

[0230] It should be noted that the bearer configuration method provided in this application embodiment can be executed by a bearer configuration device, or by a control module within the bearer configuration device for executing the bearer configuration method. This application embodiment uses the execution of the bearer configuration method by a bearer configuration device as an example to illustrate the bearer configuration device provided in this application embodiment.

[0231] Figure 9 This illustration shows a structural schematic diagram of a configuration device for carrying out an embodiment of this application, such as... Figure 9 As shown, the device 900 mainly includes: a first acquisition module 901 and a first transceiver module 902.

[0232] In this embodiment of the application, the first acquisition module 901 is used to acquire the first configuration information of the first UE, wherein the first configuration information is used to configure the bearer for multi-UE cooperative transmission; the first transceiver module 902 is used to send the first configuration information to the first UE.

[0233] In one possible implementation, the first transceiver module 902 is further configured to receive association information sent by the core network before sending the first configuration information to the first UE, wherein the association information is used to indicate the association relationship between the first UE and the second UE.

[0234] In one possible implementation, the association information includes at least one of the following:

[0235] A list of UE identifiers with associated relationships, wherein the list of UE identifiers includes the identifier of the first UE and the identifier of the second UE;

[0236] First service identification information, wherein the first service identification information is used to indicate a service capable of performing multi-UE cooperative transmission;

[0237] The attributes of each UE in the list of associated UE identifiers.

[0238] In one possible implementation, the first acquisition module 901 is further configured to determine that the first condition is met.

[0239] In one possible implementation, the first condition includes at least one of the following:

[0240] The association information between the first UE and the second UE is obtained from the core network;

[0241] As the service node of the first UE, it is determined that the first UE and the second UE with an association relationship are in a connected state;

[0242] As the serving node of the first UE, it determines that at least some of the service transmissions of the first UE cannot meet the Quality of Service (QoS) requirements or service experience requirements; the RAN node pages the second UE to determine that the second UE has entered the connected state;

[0243] At least some of the services currently provided by the first UE have the feature of supporting multi-UE transmission.

[0244] In one possible implementation, the first acquisition module 901 is further configured to determine, before sending the first configuration information to the first UE, whether the transmission distance and / or link conditions between the first UE and the second UE meet the multi-UE transmission requirements.

[0245] In one possible implementation, the first transceiver module 902 is further configured to send second configuration information to the second UE before sending the first configuration information to the first UE, wherein the second configuration information is used to instruct the second UE to perform bearer configuration for multi-UE cooperative transmission for the first UE; and to receive a configuration completion message sent by the second UE.

[0246] In one possible implementation, the first transceiver module 902 is further configured to receive a first request sent by the first UE before sending the first configuration information to the first UE, wherein the first request is used to request the first configuration information and carries the identifier of the second UE.

[0247] In one possible implementation, the first request also carries second service identification information, which indicates the service information that the first UE expects to perform multi-UE cooperative transmission.

[0248] In one possible implementation, the second service identification information includes at least one of the following:

[0249] First Wireless Data Bearer DRB Identifier;

[0250] Service identifier;

[0251] QoS flow identifier;

[0252] Business characteristics information.

[0253] In one possible implementation, the first transceiver module 902 is further configured to send second configuration information to the second UE after receiving the first request sent by the first UE, wherein the second configuration information is used to instruct the second UE to perform bearer configuration for multi-UE cooperative transmission for the first UE.

[0254] In one possible implementation, the second configuration information includes: the identifier of the first UE and the configuration information of the forked bearer.

[0255] In one possible implementation, the second configuration information further includes: a second DRB identifier, used to indicate that the second UE performs multi-UE cooperative transmission of service bearers for the first UE.

[0256] In one possible implementation, the first transceiver module 902 is further configured to receive a configuration completion message sent by the second UE after sending the second configuration information to the second UE; and send a reconfiguration message to the first UE, wherein the reconfiguration message carries the first configuration information.

[0257] In one possible implementation, the first configuration information includes:

[0258] The identifier of the second UE and the configuration information of the bearer architecture.

[0259] In one possible implementation, the first configuration information further includes: a third DRB identifier, used to indicate the service bearer configured for multi-UE cooperative transmission for the first UE.

[0260] In one possible implementation, the first transceiver module 902 is further configured to, after sending the first configuration information to the first user equipment (UE), send a first reconfiguration command to the second UE, wherein the first reconfiguration signaling carries the identifier of the first UE, the first bearer identifier for reconfiguration, and the reconfiguration content information, and the bearer corresponding to the first bearer identifier is the bearer for multi-UE cooperative transmission; and send a second reconfiguration command to the first UE, wherein the second reconfiguration signaling carries the identifier of the second UE, the first bearer identifier, and the reconfiguration content information.

[0261] In one possible implementation, the first transceiver module 902 is further configured to receive a modification request sent by the first UE or the second UE before sending the first reconfiguration command to the second UE, wherein the modification request is used to request modification of the bearer corresponding to the first bearer identifier.

[0262] In one possible implementation, the first transceiver module 902 is further configured to, after sending the first configuration information to the first user equipment (UE), send a first release command to the second UE, wherein the first release command carries the identifier of the first UE, the second bearer identifier to be released, and the content information to be released, and the bearer corresponding to the second bearer identifier is the bearer of the multi-UE cooperative transmission; and send a second release command to the first UE, wherein the second release command carries the identifier of the second UE, the second bearer identifier, and the content information to be released.

[0263] In one possible implementation, the first transceiver module 902 is further configured to receive a release request sent by the first UE or the second UE before sending the first release command to the second UE, wherein the release request is used to request the release of the bearer corresponding to the second bearer identifier.

[0264] The configuration device carried in the embodiments of this application can be a device, or a component, integrated circuit, or chip in a network-side device. This device can be a base station or a CU; the embodiments of this application do not specifically limit it.

[0265] The configuration device carried in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit it.

[0266] The configuration device provided in this application embodiment can achieve Figures 2 to 8 The various processes implemented by the RAN node in the method embodiment achieve the same technical effect, and will not be described again here to avoid repetition.

[0267] Figure 10 This illustration shows a structural diagram of a configuration device for multi-UE cooperative transmission provided in an embodiment of this application, such as... Figure 10 As shown, the device mainly includes: a second acquisition module 1001 and a second transceiver module 1002.

[0268] In the basic application embodiment, the second acquisition module 1001 is used to acquire association relationship information, wherein the association relationship information is used to indicate that the first UE and the second UE have an association relationship, and the first UE and the second UE have the ability to establish multi-UE cooperative transmission; the second transceiver module 1002 is used to send the association relationship to the RAN node.

[0269] In one possible implementation, the second transceiver module 1002 is further configured to perform at least one of the following before sending the association information to the RAN node:

[0270] It is known that both the first UE and the second UE are in a connected state;

[0271] The first UE is found to have entered the connected state, wherein the first UE and the second UE are associated with each other based on any service;

[0272] After the first UE is detected to enter the connected state and initiate the first service, wherein the first UE and the second UE are associated based on the target service, and the target service includes the first service;

[0273] Upon receiving a second request from the RAN node, the second request is used to request all UEs associated with the first UE, or the second request is used to request UEs that are associated with the first UE based on a second service.

[0274] In one possible implementation, the association information includes at least one of the following:

[0275] A list of UE identifiers with associated relationships, wherein the list of UE identifiers includes the identifier of the first UE and the identifier of the second UE;

[0276] First service identification information, wherein the first service identification information is used to indicate a service capable of performing multi-UE cooperative transmission;

[0277] The attributes of each UE indicated in the list of associated UE identifiers.

[0278] In one possible implementation, the second acquisition module 1001 is further configured to acquire the association relationship information subscribed to by the first UE or the association relationship information preset by the first UE before sending the association relationship information to the RAN node.

[0279] The configuration device for multi-UE cooperative transmission in the embodiments of this application can be a device, or a component, integrated circuit, or chip in a network-side device. This device can be a base station or a CU; the embodiments of this application do not specifically limit it.

[0280] The configuration device for multi-UE cooperative transmission in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit it.

[0281] The configuration device for multi-UE cooperative transmission provided in this application embodiment can achieve Figures 2 to 8 The various processes implemented by the core network device or core network in the method embodiment achieve the same technical effect, and will not be described again here to avoid repetition.

[0282] Figure 11 This illustration shows a structural diagram of a multi-UE cooperative transmission request device provided in an embodiment of this application, such as... Figure 11 As shown, the device 1100 mainly includes: a first determining module 1101 and a third transceiver module 1102.

[0283] In this embodiment of the application, the first determining module 1101 is used to determine that the first UE needs to perform multi-UE cooperative transmission; the third transceiver module 1102 is used to send a first request to the RAN node, wherein the first request is used to request the RAN node to configure a bearer for multi-UE cooperative transmission for the first UE, and the first request carries the identifier of the second UE.

[0284] In one possible implementation, the third transceiver module 1102 is further configured to send a third request through an interface between UEs before sending the first request to the RAN node, wherein the third request is used to request aggregated transmission for the first UE; and to receive an acknowledgment message from the second UE, wherein the acknowledgment message carries the identifier of the second UE.

[0285] In one possible implementation, the third transceiver module 1102 is further configured to receive a reconfiguration message sent by the RAN node after sending the first request to the RAN node, wherein the reconfiguration message carries first configuration information, the first configuration information being used to configure a bearer for multi-UE cooperative transmission for the first UE; and to perform reconfiguration by applying the first configuration information.

[0286] In one possible implementation, the first configuration information includes: the second UE identifier and the configuration information of the bearer architecture.

[0287] In one possible implementation, the first configuration information further includes: a third DRB identifier, used to indicate the service bearer configured for multi-UE cooperative transmission for the first UE.

[0288] In one possible implementation, the third transceiver module 1102 is further configured to receive a second reconfiguration command sent by the RAN node after receiving the reconfiguration message sent by the RAN node, wherein the second reconfiguration signaling carries the identifier of the second UE, the first bearer identifier of the reconfiguration, and the reconfiguration content information, and the bearer corresponding to the first bearer identifier is the bearer of the multi-UE cooperative transmission; and execute the second reconfiguration command.

[0289] In one possible implementation, the third transceiver module 1102 is further configured to send a modification request to the RAN node before receiving the second reconfiguration command sent by the RAN node, wherein the modification request is used to request modification of the bearer corresponding to the first bearer identifier.

[0290] In one possible implementation, the third transceiver module 1102 is further configured to receive a second release command sent by the RAN node after receiving the reconfiguration message sent by the RAN node, wherein the second release command carries the identifier of the second UE, the second bearer identifier to be released, and the content information to be released, and the bearer corresponding to the second bearer identifier is the bearer for multi-UE cooperative transmission; and execute the second release command to release the bearer corresponding to the second bearer identifier.

[0291] In one possible implementation, the third transceiver module 1102 is further configured to send a release request to the RAN node before receiving the second release command sent by the RAN node, wherein the release request is used to request the release of the bearer corresponding to the second bearer identifier.

[0292] In one possible implementation, the first request also carries second service identification information, which is used to indicate the service information that the first UE expects to perform multi-UE cooperative transmission.

[0293] In one possible implementation, the second service identification information includes at least one of the following:

[0294] First Wireless Data Bearer DRB Identifier;

[0295] Service identifier;

[0296] QoS flow identifier;

[0297] Business characteristics information.

[0298] The requesting device for multi-UE cooperative transmission in this application embodiment can be a device, or a component, integrated circuit, or chip in a terminal device. The device can be a base station or a CU; this application embodiment does not specifically limit the specific type of device.

[0299] The requesting device for multi-UE cooperative transmission in this embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this embodiment does not specifically limit the specific operating system.

[0300] The multi-UE cooperative transmission request device provided in this application embodiment can achieve Figures 2 to 8 The various processes implemented by the first UE in the method embodiment achieve the same technical effect, and will not be described again here to avoid repetition.

[0301] Figure 12 This illustration shows a structural diagram of a response device for multi-UE cooperative transmission provided in an embodiment of this application, such as... Figure 12 As shown, the device 1200 mainly includes: a fourth transceiver module 1201 and a second determination module 1202.

[0302] In this embodiment, the fourth transceiver module 1201 is used to receive second configuration information sent by the RAN node, wherein the second configuration information is used to instruct the second UE to perform bearer configuration for multi-UE cooperative transmission for the first UE; the second determination module 1202 is used to determine whether to agree to perform multi-UE cooperative transmission for the first UE; the fourth transceiver module 1201 is further used to, if agreeing to perform multi-UE cooperative transmission for the first UE, have the second UE apply the second configuration information and send a configuration completion message to the RAN node.

[0303] In one possible implementation, the second configuration information includes: the identifier of the first UE and the configuration information of the forked bearer.

[0304] In one possible implementation, the second configuration information further includes: a second DRB identifier, used to indicate that the second UE performs multi-UE cooperative transmission of service bearers for the first UE.

[0305] In one possible implementation, the fourth transceiver module 1201 is further configured to receive a third request sent by the first UE before receiving the second configuration information sent by the RAN node, wherein the third request is used to request aggregation transmission for the first UE; and to send a confirmation message to the first UE, wherein the confirmation message carries the identifier of the second UE.

[0306] In one possible implementation, the fourth transceiver module 1201 is further configured to receive a first reconfiguration command sent by the RAN node after sending a configuration completion message to the RAN node, wherein the first reconfiguration signaling carries the identifier of the first UE, the first bearer identifier of the reconfiguration, and the reconfiguration content information, and the bearer corresponding to the first bearer identifier is the bearer for multi-UE cooperative transmission; and execute the first reconfiguration command.

[0307] In one possible implementation, the fourth transceiver module 1201 is further configured to send a modification request to the RAN node before receiving the first reconfiguration command sent by the RAN node, wherein the modification request is used to request modification of the bearer corresponding to the first bearer identifier.

[0308] In one possible implementation, the fourth transceiver module 1201 is further configured to receive a first release command sent by the RAN node after sending a configuration completion message to the RAN node, wherein the first release command carries the identifier of the first UE, the second bearer identifier to be released, and the content information to be released, and the bearer corresponding to the second bearer identifier is the bearer for multi-UE cooperative transmission; and execute the first release command to release the bearer corresponding to the second bearer identifier.

[0309] In one possible implementation, the fourth transceiver module 1201 is further configured to send a release request to the RAN node before receiving the first release command sent by the RAN node, wherein the release request is used to request the release of the bearer corresponding to the second bearer identifier.

[0310] The response for multi-UE cooperative transmission in this application embodiment can be a device, or a component, integrated circuit, or chip in a terminal device. The device can be a base station or a CU; this application embodiment does not specifically limit the specific device.

[0311] The response for multi-UE cooperative transmission in this embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this embodiment does not impose specific limitations.

[0312] The multi-UE cooperative transmission response provided in this application embodiment can achieve Figures 2 to 8 The various processes implemented by the second UE in the method embodiment achieve the same technical effect, and will not be described again here to avoid repetition.

[0313] Optional, such as Figure 13As shown, this application embodiment also provides a communication device 1300, including a processor 1301, a memory 1302, and a program or instructions stored in the memory 1302 and executable on the processor 1301. For example, when the communication device 1300 is a terminal, the program or instructions executed by the processor 1301 implement the various processes of the above-described method 400 embodiment or method 500 embodiment, and achieve the same technical effect. When the communication device 1300 is a network-side device, the program or instructions executed by the processor 1301 implement the various processes of the above-described method 200 embodiment or method 300 embodiment, and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0314] This application also provides a terminal, including a processor and a communication interface. The processor is used to implement the various processes of the above-described method 400 embodiment or method 500 embodiment, and the communication interface is used to communicate with external devices. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 14 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0315] The terminal 1400 includes, but is not limited to, the following components: radio frequency unit 1401, network module 1402, audio output unit 1403, input unit 1404, sensor 1405, display unit 1406, user input unit 1407, interface unit 1408, memory 1409, and processor 1410.

[0316] Those skilled in the art will understand that the terminal 1400 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 1410 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 14 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0317] It should be understood that, in this embodiment, the input unit 1404 may include a graphics processing unit (GPU) 14041 and a microphone 14042. The GPU 14041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1406 may include a display panel 14061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1407 includes a touch panel 14071 and other input devices 14072. The touch panel 14071 is also called a touch screen. The touch panel 14071 may include a touch detection device and a touch controller. Other input devices 14072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0318] In this embodiment, the radio frequency unit 1401 receives downlink data from the network-side device and processes it for the processor 1410; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 1401 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0319] The memory 1409 can be used to store software programs or instructions and various data. The memory 1409 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1409 may include high-speed random access memory and non-transient memory, which may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-transient solid-state storage device.

[0320] Processor 1410 may include one or more processing units; optionally, processor 1410 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1410.

[0321] The radio frequency unit 1401 is used to send a first request to the RAN node, wherein the first request is used to request the RAN node to configure a bearer for multi-UE cooperative transmission for the first UE, and the first request carries the identifier of the second UE.

[0322] Alternatively, the radio frequency unit 1401 is used to receive second configuration information sent by the RAN node, wherein the second configuration information is used to instruct the second UE to perform bearer configuration for multi-UE cooperative transmission for the first UE; if the second UE agrees to perform multi-UE cooperative transmission for the first UE, the second UE applies the second configuration information and sends a configuration completion message to the RAN node.

[0323] This application also provides a network-side device, including a processor and a communication interface. The processor is used to implement the various processes of the above-described method 200 embodiment or method 300 embodiment, and the communication interface is used to communicate with external devices. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0324] Specifically, embodiments of this application also provide a network-side device. For example... Figure 15 As shown, the network device 1500 includes: an antenna 1501, a radio frequency (RF) device 1502, and a baseband device 1503. The antenna 1501 is connected to the RF device 1502. In the uplink direction, the RF device 1502 receives information through the antenna 1501 and transmits the received information to the baseband device 1503 for processing. In the downlink direction, the baseband device 1503 processes the information to be transmitted and sends it to the RF device 1502. The RF device 1502 processes the received information and transmits it through the antenna 1501.

[0325] The aforementioned frequency band processing device can be located in the baseband device 1503. The method executed by the network-side device in the above embodiments can be implemented in the baseband device 1503, which includes a processor 1504 and a memory 1505.

[0326] The baseband device 1503 may, for example, include at least one baseband board on which multiple chips are disposed, such as... Figure 15 As shown, one of the chips, for example, is a processor 1504, which is connected to a memory 1505 to call the program in the memory 1505 and execute the network device operation shown in the above method embodiment.

[0327] The baseband device 1503 may also include a network interface 1506 for exchanging information with the radio frequency device 1502, such as a common public radio interface (CPRI).

[0328] Specifically, the network-side device in this embodiment of the invention further includes: instructions or programs stored in memory 1505 and executable on processor 1504, wherein processor 1504 calls the instructions or programs in memory 1505 to execute. Figure 9 or Figure 10 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0329] This application also provides a readable storage medium, which may be volatile or non-volatile. The readable storage medium stores a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described method 200 embodiment, or the various processes of the above-described method 300 embodiment, or the various processes of the above-described method 400 embodiment, or the various processes of the above-described method 500 embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0330] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0331] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described method 200 embodiment, or the various processes of the above-described method 300 embodiment, or the various processes of the above-described method 400 embodiment, or the various processes of the above-described method 500 embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0332] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0333] This application also provides a computer program / program product, which is stored in a non-transient storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-described method 200 embodiment, or the various processes of the above-described method 300 embodiment, or the various processes of the above-described method 400 embodiment, or the various processes of the above-described method 500 embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0334] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0335] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0336] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for configuring a carrier, characterized in that, include: The Radio Access Network (RAN) node receives association information from the core network, wherein the association information is used to indicate the association relationship between the first User Equipment (UE) and the second UE. The RAN node sends first configuration information to the first UE, wherein the first configuration information is used to configure the bearer for multi-UE cooperative transmission; The RAN node sending first configuration information to the first UE includes: the RAN node sending first configuration information to the first UE when it determines that a first condition is met; wherein the first condition includes: the RAN node, as the serving node of the first UE, determines that the first UE and the second UE with an association relationship are in a connected state; The method further includes, after the RAN node sends the first configuration information to the first UE: Receive a modification request sent by the first UE or the second UE, wherein the modification request is used to request modification of the bearer corresponding to the first bearer identifier; The RAN node sends a first reconfiguration command to the second UE, wherein the first reconfiguration command carries the identifier of the first UE, the first bearer identifier for reconfiguration, and the reconfiguration content information, and the bearer corresponding to the first bearer identifier is the bearer for multi-UE cooperative transmission; The RAN node sends a second reconfiguration command to the first UE, wherein the second reconfiguration command carries the identifier of the second UE, the first bearer identifier, and the reconfiguration content information; and / or Receive a release request sent by the first UE or the second UE, wherein the release request is used to request the release of the bearer corresponding to the second bearer identifier; The RAN node sends a first release command to the second UE, wherein the first release command carries the identifier of the first UE, the second bearer identifier to be released, and the content information to be released, and the bearer corresponding to the second bearer identifier is the bearer for the multi-UE cooperative transmission; The RAN node sends a second release command to the first UE, wherein the second release command carries the identifier of the second UE, the second bearer identifier, and the release content information.

2. The method according to claim 1, characterized in that, The association information includes at least one of the following: A list of UE identifiers with associated relationships, wherein the list of UE identifiers includes the identifier of the first UE and the identifier of the second UE; First service identification information, wherein the first service identification information is used to indicate a service capable of performing multi-UE cooperative transmission; The attributes of each UE in the list of associated UE identifiers.

3. The method according to claim 1, characterized in that, After the RAN node determines that the predetermined conditions are met, but before sending the first configuration information to the first UE, the method further includes: The RAN node determines the transmission distance and / or link conditions between the first UE and the second UE to meet the multi-UE transmission requirements.

4. The method according to claim 1, characterized in that, Before the RAN node sends the first configuration information to the first UE, the method further includes: The RAN node sends second configuration information to the second UE, wherein the second configuration information is used to instruct the second UE to perform bearer configuration for multi-UE cooperative transmission for the first UE; The RAN node receives the configuration completion message sent by the second UE.

5. The method according to claim 1, characterized in that, Before the RAN node sends the first configuration information to the first UE, the method further includes: The system receives a first request sent by the first UE, wherein the first request is used to request the first configuration information and carries the identifier of the second UE.

6. The method according to claim 5, characterized in that, The first request also carries second service identification information, which is used to indicate the service information that the first UE expects to perform multi-UE cooperative transmission.

7. The method according to claim 6, characterized in that, The second service identification information includes at least one of the following: First Wireless Data Bearer DRB Identifier; Service identifier; QoS flow identifier; Business characteristics information.

8. The method according to claim 5, characterized in that, After receiving the first request sent by the first UE, the method further includes: The RAN node sends second configuration information to the second UE, wherein the second configuration information is used to instruct the second UE to perform bearer configuration for multi-UE cooperative transmission for the first UE.

9. The method according to claim 4 or 8, characterized in that, The second configuration information includes: the identifier of the first UE and the configuration information of the fork bearer.

10. The method according to claim 9, characterized in that, The second configuration information also includes: a second DRB identifier, used to indicate that the second UE performs multi-UE cooperative transmission of service bearers for the first UE.

11. The method according to claim 8, characterized in that, After the RAN node sends the second configuration information to the second UE, the method further includes: The RAN node receives the configuration completion message sent by the second UE; The RAN node sends a reconfiguration message to the first UE, wherein the reconfiguration message carries the first configuration information.

12. The method according to claim 1, characterized in that, The first configuration information includes: The identifier of the second UE and the configuration information of the bearer architecture.

13. The method according to claim 12, characterized in that, The first configuration information also includes: a third DRB identifier, used to indicate the service bearer configured for multi-UE cooperative transmission for the first UE.

14. A configuration method for multi-UE cooperative transmission, characterized in that, include: The core network equipment sends association information to the RAN node, wherein the association information is used to indicate that the first UE and the second UE have an association relationship and that the first UE and the second UE have the ability to establish multi-UE cooperative transmission; The core network device sends the association information to the RAN node under at least one of the following circumstances: The core network device learns that both the first UE and the second UE are in a connected state; The core network device detects that the first UE has entered the connected state, wherein the first UE and the second UE have an association relationship based on any service; After the core network device discovers that the first UE has entered the connected state and initiated the first service, the first UE and the second UE are associated based on the target service, and the target service includes the first service.

15. The method according to claim 14, characterized in that, The association information includes at least one of the following: A list of UE identifiers with associated relationships, wherein the list of UE identifiers includes the identifier of the first UE and the identifier of the second UE; First service identification information, wherein the first service identification information is used to indicate a service capable of performing multi-UE cooperative transmission; The attributes of each UE indicated in the list of associated UE identifiers.

16. The method according to claim 14 or 15, characterized in that, Before the core network equipment sends the association information to the RAN node, the method further includes: The core network device obtains the association information signed by the first UE or the association information pre-set by the first UE.

17. A carrying configuration device, characterized in that, include: The first acquisition module is used to acquire the first configuration information of the first UE, wherein the first configuration information is used to configure the bearer for multi-UE cooperative transmission; The first transceiver module is used to send the first configuration information to the first UE; The first transceiver module is further configured to receive association information sent by the core network before sending the first configuration information to the first UE, wherein the association information is used to indicate the association relationship between the first UE and the second UE; The first transceiver module is further configured to: send first configuration information to the first UE when a first condition is met; wherein the first condition includes: the RAN node, as the serving node of the first UE, determines that the first UE and the second UE with an association relationship are in a connected state; After sending the first configuration information to the first UE, the first transceiver module is further configured to: Receive a modification request sent by the first UE or the second UE, wherein the modification request is used to request modification of the bearer corresponding to the first bearer identifier; Send a first reconfiguration command to the second UE, wherein the first reconfiguration command carries the identifier of the first UE, the first bearer identifier for reconfiguration, and the reconfiguration content information, and the bearer corresponding to the first bearer identifier is the bearer for multi-UE cooperative transmission; Send a second reconfiguration command to the first UE, wherein the second reconfiguration command carries the identifier of the second UE, the first bearer identifier, and the reconfiguration content information; and / or Receive a release request sent by the first UE or the second UE, wherein the release request is used to request the release of the bearer corresponding to the second bearer identifier; Send a first release command to the second UE, wherein the first release command carries the identifier of the first UE, the second bearer identifier to be released, and the content information to be released, and the bearer corresponding to the second bearer identifier is the bearer of the multi-UE cooperative transmission; A second release command is sent to the first UE, wherein the second release command carries the identifier of the second UE, the second bearer identifier, and the release content information.

18. A configuration device for multi-UE cooperative transmission, characterized in that, include: The second acquisition module is used to acquire association information, wherein the association information is used to indicate that the first UE and the second UE have an association relationship, and the first UE and the second UE have the ability to establish multi-UE cooperative transmission; The second transceiver module is used to send the association relationship to the RAN node; The second transceiver module is configured to send the association information to the RAN node under at least one of the following conditions: It is known that both the first UE and the second UE are in a connected state; The first UE is found to have entered the connected state, wherein the first UE and the second UE are associated with each other based on any service; After the first UE is detected to enter the connected state and initiate the first service, the first UE and the second UE are associated based on the target service, and the target service includes the first service.

19. A network-side device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein when the program or instructions are executed by the processor, they implement the steps of the bearer configuration method as described in any one of claims 1 to 13, or the steps of the multi-UE cooperative transmission configuration method as described in any one of claims 14 to 16.

20. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the bearer configuration method as described in any one of claims 1 to 13, or the steps of the multi-UE cooperative transmission configuration method as described in any one of claims 14 to 16.

Images