WO2023061430A1 - 承载的配置方法、网络侧设备及终端 - Google Patents

承载的配置方法、网络侧设备及终端 Download PDF

Info

Publication number
WO2023061430A1
WO2023061430A1 PCT/CN2022/125040 CN2022125040W WO2023061430A1 WO 2023061430 A1 WO2023061430 A1 WO 2023061430A1 CN 2022125040 W CN2022125040 W CN 2022125040W WO 2023061430 A1 WO2023061430 A1 WO 2023061430A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
ran node
request
identifier
configuration information
Prior art date
Application number
PCT/CN2022/125040
Other languages
English (en)
French (fr)
Inventor
刘佳敏
鲍炜
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2023061430A1 publication Critical patent/WO2023061430A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present application belongs to the technical field of wireless communication, and specifically relates to a bearer configuration method, a network side device and a terminal.
  • a user equipment In the existing mechanism, a user equipment (User Equipment, UE) establishes its own control plane connection and user plane connection with the core network, such as a protocol data unit (Protocol Data Unit, PDU) session (session).
  • the core network such as a protocol data unit (Protocol Data Unit, PDU) session (session).
  • PDU Protocol Data Unit
  • the network side transfers the UE's control plane connection, user plane connection and transmission status between different network nodes, In order to ensure that the service transmission of the UE can be continuous, uninterrupted, and lossless as required.
  • Non-access stratum Non Access Stratum, NAS
  • Radio Resource Control Radio Resource Control, RRC
  • RRC Radio Resource Control
  • DRB data radio bearer
  • QoS Quality of Service
  • the embodiment of the present application provides a bearer configuration method, network side equipment and terminal, which can solve the problem that multi-UE cooperative transmission cannot be realized in the prior art.
  • a method for configuring a bearer including: a radio access network RAN node sends first configuration information to a first user equipment UE, where the first configuration information is used to configure a bearer for multi-UE coordinated transmission .
  • an apparatus for configuring a bearer including: a first acquiring module, configured to acquire first configuration information of a first UE, where the first configuration information is used to configure a bearer for multi-UE coordinated transmission; A first transceiver module, configured to send the first configuration information to the first UE.
  • a method for configuring multi-UE coordinated transmission including: a core network device sends association relationship information to a RAN node, where the association relationship information is used to indicate that the first UE has an association relationship with the second UE, The first UE and the second UE are capable of establishing multi-UE coordinated transmission.
  • an apparatus for configuring multi-UE cooperative transmission including: a second acquiring module, configured to acquire association relationship information, wherein the association relationship information is used to indicate that the first UE has an association relationship with the second UE , the first UE and the second UE have the capability of establishing multi-UE coordinated transmission; the second transceiver module is configured to send the association relationship to a RAN node.
  • a method for requesting multi-UE coordinated transmission including: a first UE sends a first request to a RAN node, where the first request is used to request the RAN node to configure the first UE
  • the bearer of multi-UE coordinated transmission, the first request carries the identity of the second UE.
  • an apparatus for requesting multi-UE coordinated transmission including: a first determination module, configured to determine that the first UE needs to perform multi-UE coordinated transmission; a third transceiver module, configured to send the first request to a RAN node , wherein the first request is used to request the RAN node to configure a multi-UE coordinated transmission bearer for the first UE, and the first request carries an identifier of the second UE.
  • a method for responding to multi-UE coordinated transmission including: the second UE receives second configuration information sent by a RAN node, where the second configuration information is used to indicate that the second UE is the first The UE performs bearer configuration for multi-UE coordinated transmission; in the case of agreeing to perform multi-UE coordinated transmission for the first UE, the second UE applies the second configuration information and sends a configuration complete message to the RAN node.
  • an apparatus for responding to multi-UE coordinated transmission including: a fourth transceiver module, configured to receive second configuration information sent by a RAN node, where the second configuration information is used to indicate that the second The UE performs bearer configuration for multi-UE coordinated transmission for the first UE; the second determining module is configured to determine whether to agree to perform multi-UE coordinated transmission for the first UE; When the first UE performs multi-UE coordinated transmission, the second UE applies the second configuration information and sends a configuration complete message to the RAN node.
  • a terminal includes a processor, a memory, and a program or instruction stored in the memory and operable on the processor.
  • the program or instruction is executed by the processor.
  • a tenth aspect provides a terminal, including a processor and a communication interface, wherein the processor is used 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
  • the communication interface is used to communicate with external devices.
  • a network-side device includes a processor, a memory, and a program or instruction stored in the memory and operable on the processor, and the program or instruction is executed by the When the processor executes, implement the steps of the method described in the first aspect, or implement the steps of the method described in the third aspect.
  • a twelfth aspect provides a network side device, 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 implement the steps of the method described in the third aspect Step, the communication interface is used to communicate with external equipment.
  • a thirteenth aspect provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method as described in the first aspect are implemented, or The steps of the method described in the third aspect, or the implementation of the steps of the method described in the fifth aspect, or the implementation of the steps of the method described in the seventh aspect.
  • a chip in a fourteenth aspect, there is provided a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run programs or instructions, and implement the method described in the first aspect The steps of the method, or realize the steps of the method described in the third aspect, or realize the steps of the method described in the fifth aspect, or realize the steps of the method described in the seventh aspect.
  • a computer program/program product is provided, the computer program/program product is stored in a non-transitory storage medium, and the computer program/program product is executed by at least one processor to implement the first
  • the radio access network (Radio Access Network, RAN) node may send the first configuration to the first UE, and configure the bearer of multi-UE coordinated transmission, so that the first UE can perform multi-UE coordinated transmission.
  • Radio Access Network, RAN Radio Access Network
  • FIG. 1 shows a schematic diagram of a wireless communication system to which an embodiment of the present application is applicable
  • FIG. 2 shows a schematic flowchart of a bearer configuration method provided by an embodiment of the present application
  • FIG. 3a shows a schematic diagram of a multi-UE transmission architecture provided by an embodiment of the present application
  • FIG. 3b shows a schematic diagram of another multi-UE transmission architecture provided by an embodiment of the present application.
  • FIG. 3c shows a schematic diagram of another multi-UE transmission architecture provided by the embodiment of the present application.
  • FIG. 4 shows a schematic flowchart of a method for configuring multi-UE coordinated transmission provided by an embodiment of the present application
  • FIG. 5 shows a schematic flowchart of a method for configuring multi-UE coordinated transmission provided by an embodiment of the present application
  • FIG. 6 shows a schematic flowchart of a response method for multi-UE coordinated transmission provided by an embodiment of the present application
  • Fig. 7 shows a schematic flow chart of a method for establishing a bearer for multi-UE coordinated transmission provided by an embodiment of the present application
  • FIG. 8 shows another schematic flowchart of a method for establishing a bearer for multi-UE coordinated transmission provided by an embodiment of the present application
  • FIG. 9 shows a schematic structural diagram of a carrying configuration device provided by an embodiment of the present application.
  • FIG. 10 shows a schematic structural diagram of an apparatus for configuring multi-UE coordinated transmission provided by an embodiment of the present application
  • FIG. 11 shows a schematic structural diagram of an apparatus for configuring multi-UE coordinated transmission provided by an embodiment of the present application
  • FIG. 12 shows a schematic structural diagram of a response apparatus for multi-UE coordinated transmission provided by an embodiment of the present application
  • FIG. 13 shows a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 14 shows a schematic diagram of a hardware structure of a terminal provided by an embodiment of the present application.
  • FIG. 15 shows a schematic diagram of a hardware structure of a network side device provided by an embodiment of the present application.
  • first, second and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific sequence or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein and that "first" and “second” distinguish objects. It is usually one category, and the number of objects is not limited. For example, there may be one or more first objects.
  • “and/or” in the description and claims means at least one of the connected objects, and the character “/” generally means that the related objects are an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used for the above-mentioned system and radio technology, and can also be used for other systems and radio technologies.
  • NR New Radio
  • the following description describes the New Radio (NR) system for illustrative purposes, and uses NR terminology in most of the following descriptions, but these techniques can also be applied to applications other than NR system applications, such as the 6th generation (6 th Generation, 6G) communication system.
  • 6G 6th Generation
  • Fig. 1 shows a schematic diagram of a wireless communication system to which this embodiment of the present application is applicable.
  • the wireless communication system includes a terminal 11 and a network side device 12 .
  • the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (VUE), Pedestrian Terminal (PUE) and other terminal-side devices, wearable devices include: smart watches, bracelets, earphones, glasses, etc.
  • the network side device 12 may be a base station or a core network, where a base station may be called a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service Basic Service Set (BSS), Extended Service Set (ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN access point, WiFi node, transmission Receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiment of this application, only The base station in the NR system is taken as an example, but the specific type of the base station is not limited.
  • Fig. 2 shows a schematic flowchart of a bearer configuration method in an embodiment of the present application, and the method 200 may be executed by a RAN node.
  • the method can be performed by software or hardware installed on a RAN node.
  • the method may include the following steps.
  • the RAN node sends first configuration information to the first UE, where the first configuration information is used to configure a bearer for multi-UE coordinated transmission.
  • the RAN node may be a base station or a centralized unit (Centralized Unit, CU), which is not specifically limited in the embodiment of the present application.
  • CU Centralized Unit
  • the access network connections or core network connections of different UEs are independent of each other, and each UE can only perform service transmission independently.
  • a user may need to perform common service transmission between two UEs. For example, when a user uses a mobile phone to listen to music/books indoors and is about to go out for a run, the user hopes that the wristband can continuously receive related services and bring continuous service experience to the user. Or, when the transmit power of one UE is limited or the uplink transmission rate is insufficient, the transmit power and transmission capabilities of two or more UEs may be used for joint transmission.
  • a connection backup can be established between two or more UEs, and which link is currently used for transmission can be determined according to the link quality to meet low-latency and high-reliability transmission need.
  • 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 through hard switching Link changes are achieved, which reduces the convenience of experience and the effect of user QoS experience.
  • the RAN node configures the bearer for multi-UE cooperative transmission for the first UE, so that the first UE can be used for multi-UE cooperative transmission, improving the convenience of service transmission and user QoS Experience the effect.
  • the first configuration information may include: an identifier of the second UE and configuration information of a bearer structure.
  • the configuration information of the bearer architecture refers to the multi-UE architecture configuration of multi-UE coordinated transmission (also referred to as aggregated transmission, backup transmission, or handover transmission, etc.), for example, it may include the configuration information shown in FIG. 3a Packet Data Convergence Protocol (Packet Data Convergence Protocol, PDCP) anchor (anchor) architecture, radio link control (Radio Link Control, RLC) anchor architecture shown in Figure 3b, Media Access Control (Medium Access Control) shown in Figure 3c , MAC) configuration information of at least one of the anchor architectures.
  • Packet Data Convergence Protocol Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Media Access Control
  • the multi-UE architecture can also adopt other architectures.
  • ) is set on the first UE, and the split function is set on the second UE.
  • the protocol can choose one or more architectures. If one architecture is selected, the first configuration information includes the configuration of protocol entities related to the architecture. If two or more architectures are adopted, the RAN node can The selection and configuration of different architectures are performed as required, which is not limited in this embodiment of the present application.
  • 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 sends second configuration information to the second UE, where the second configuration information is used to indicate the The second UE performs multi-UE coordinated transmission bearer configuration for the first UE; the RAN node receives a configuration completion message returned by the second UE.
  • the RAN node first sends the second configuration information to the second UE, and then sends the first configuration information to the first UE after receiving the configuration completion message sent by the second UE, Therefore, the bearer of the first UE can be reconfigured after the second UE agrees to perform multi-UE coordinated transmission with the first UE, thereby avoiding waste of procedures.
  • the RAN node may determine by itself to send the first configuration information to the first UE, or may also send the first configuration information to the first UE under the trigger of the core network, or may also send the first configuration information to the first UE at the first
  • the first configuration information is sent to the first UE at the request of the UE, which will be described separately below.
  • the method may further include: the RAN node receiving association relationship information issued by the core network, where the association relationship information is used to indicate the relationship between the first UE and the second UE relationship between.
  • the association relationship (also called the binding relationship) between them is made static through a process such as signing.
  • a process such as signing.
  • the association relationship between each other can be initialized through a signing process.
  • the relationship between each other can also be initialized through a pre-process.
  • association relationship of the signing process or the pre-initialization process needs to be stored in the core network node, and the core network node is responsible for verifying the validity of the association relationship.
  • a contracted or pre-associated relationship may include one of the following:
  • a group of UE lists with an association relationship The UEs in the list can cooperate with each other for transmission, and each UE decides to be a primary UE (P-UE) or a secondary UE (S-UE) according to needs;
  • P-UE primary UE
  • S-UE secondary UE
  • a set of associated UE lists which set the attributes that each UE can support, such as P-UE only, S-UE only or bothP-UE and S-UE;
  • the above-mentioned association relationship may be based on UE granularity, that is, any service between these UEs can be established and transmitted in a multi-UE architecture, or it may be further based on the granularity of a specific service, that is, on the basis of the UE list, limit the number of connections between these UEs.
  • the service restriction can be the service identifier, the specific QoS parameters of the service, the range of the specific QoS parameters of the service, etc.
  • the above-mentioned primary UE (Primary UE, P-UE) is the UE that initiates the service or the high-level protocol of the service source/service transmission is located in the UE, and the secondary UE (Secondary UE, S-UE) assists the primary UE in service transmission.
  • P-UE Primary UE
  • S-UE secondary UE
  • the core network stores the association relationship of the above-mentioned subscription process or pre-initialization process, and sends it to the RAN node when necessary, so that the RAN node can perform subsequent multi-UE architecture configuration.
  • the association relationship information issued by the core network to the RAN node may include at least one of the following:
  • a UE ID list with an association relationship wherein the UE ID list includes the ID of the first UE and the ID of the second UE; for example, a UE ID list with a binding relationship, wherein the UE ID It can be a globally unique identifier, a UE identifier in a public land mobile network (Public Land Mobile Network, PLMN), an identifier in an access and mobility management function (Access and Mobility Management Function, AMF) node, or an identifier in a gNB/CU. It can be S-Temporary Mobile Subscription Identifier (S-TMSI), AMF UE ID or gNB UE ID, etc.
  • PLMN Public Land Mobile Network
  • AMF Access and Mobility Management Function
  • the first service identification information is used to indicate a service capable of performing multi-UE coordinated 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 can be a service identifier (service ID, service code, QoS flow ID, etc.), and can also be a service feature, for example, a service that satisfies a QoS parameter equal to a certain value or in a certain interval.
  • Attributes of each UE in the UE ID list having an association relationship For example, P-UE only, S-UE only, or both P-UE and S-UE.
  • the core network device may send the association relationship information to the RAN node under at least one of the following conditions:
  • the core network device learns that both the first UE and the second UE are in the connected state; since the CN can obtain the connected state UE activated under the RAN node from the information reported by the RAN node in real time, therefore The CN can send all the association relationship information of UEs with association relationship to the RAN node;
  • the core network device finds that the first UE enters 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 finds that the UE has an association relationship, and sends the association relationship information of the UE to the serving RAN node of the UE;
  • the core network device After the core network device discovers that the first UE enters the connected state and initiates the first service, wherein the first UE and the second UE have an association relationship based on a target service, and the target service includes the For example, when a UE enters the connected state and initiates a service, if the core network device finds that the UE has an association relationship based on the service, it sends the association relationship information of the UE to the serving RAN node of the UE;
  • the second request sent by the RAN node is received, the second request is used to request all UEs associated with the first UE, or the second request is used to request the UEs with which the first UE has an association relationship. That is, the RAN node actively requests to the CN node. For example, the RAN node can make a request to the CN node according to the needs, which can be judged by the RAN node itself, or triggered after the UE requests the RAN node. Wherein, the RAN node may request the binding relationship of all UEs under it, or the binding relationship of a specific UE, or the binding relationship of a specific service of a specific UE.
  • the RAN node can configure bearers for multi-UE coordinated transmission for the first UE and the second UE respectively under the trigger of the core network equipment, so that the first UE and the second UE can realize collaborative transmission.
  • the RAN node may send the first configuration information to the first UE when it is determined that the first condition is met.
  • the first condition includes but is not limited to at least one of the following:
  • the RAN node obtains the association relationship information between the first UE and the second UE from the core network; It is possible or necessary to carry out cooperative transmission (or aggregation/backup/switching transmission);
  • the RAN node as the serving node of the first UE, determines that the first UE having an association relationship and the second UE are in a connected state; Two or more UEs have entered the connected state, and it is feasible to establish cooperation/aggregation/backup/handover transmission;
  • the RAN node as the serving node of the first UE, determines that at least part of the service transmission of the first UE cannot meet the QoS requirements or service experience requirements; the RAN node paging 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 Within the range covered by the above RAN nodes, perform paging corresponding to the S-UE, make the S-UE enter the connected state, and perform coordination/aggregation/backup/handover transmission for the P-UE;
  • At least some of the current services of the first UE have the feature of supporting multi-UE transmission.
  • the current service of the P-UE has the characteristics of supporting cooperative/aggregation/backup/handover transmission.
  • the method may further include : The RAN node determines that the transmission distance and/or the link condition between the first UE and the second UE meets a multi-UE transmission requirement. For example, the RAN node may judge according to information such as positioning or a home cell, or may inquire the first UE to obtain the transmission distance and/or link condition between the first UE and the second UE.
  • the RAN may determine at least one of the following: the first UE and the second UE have an association relationship permitted by the CN, the first UE and the second UE are located in the same base station and can communicate with each other, the first The service of the UE has the feature of establishing a multi-UE architecture bearer. Therefore, the RAN node can initiate the procedure of establishing a multi-UE architecture. For example, the following steps could be included:
  • Step 1 The RAN node sends a reconfiguration message to the second UE, which carries second configuration information.
  • the second configuration information may include: the identity of the first UE, the configuration of a split bearer, etc., so that the second UE can determine whether to agree to establish a multi-UE coordinated transmission framework for the first UE ;
  • 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 service bearer for the first UE.
  • the second UE can Judging whether to agree to perform multi-UE coordinated transmission for the designated DRB (that is, the DRB corresponding to the second DRB identifier) of the first UE.
  • Step 2 if the second UE agrees, complete the configuration according to the received reconfiguration message indication, and return a configuration completion message to the network side (ie, the RAN node);
  • Step 3 the RAN node sends a reconfiguration message to the first UE, which carries the first configuration information;
  • the first configuration information may include: the identity of the second UE, bearer structure information and related configurations, so that the first UE knows that a multi-UE transmission structure has been established with the second UE, and according to the received reconfiguration A message indicating that the configuration is complete;
  • the first configuration information may further carry a third DRB-ID, which is used to indicate the service bearer of the multi-UE coordinated transmission configured for the first UE.
  • Step 4 the first UE returns a configuration complete message to the network side.
  • the first UE may send the data packet (designated DRB ID) to the second UE, and the second UE transmits to the network side, and the downlink transmission is similar.
  • the function of the above-mentioned second DRB ID and third DRB ID is to enable the second UE and the first UE to obtain the association relationship of the bifurcated bearer: for example, for a certain DRB bearer (the bearer ID is DRB ID 1) , which splits out the locale setting identifier (LCID) 1 located at the first UE and the LCID 2 located at the second UE, then the RAN node can configure the association in the following manner when configuring the first configuration information and the second configuration information:
  • the configuration for the first UE is that DRB ID 1 is split into LCID1 of the first UE and LCID2 of the second UE (that is, the third DRB identity), and that LCID 2 (that is, the second DRB identity) is configured for the second UE. It can be known through LCID2 between the first UE and the second UE that the data streams are all associated with DRB1;
  • the RAN node may also ask the first UE whether to establish a multi-UE architecture, or ask the first UE whether to establish a multi-UE architecture for a specific service, and upon receiving the response from the first UE After the affirmative answer, execute S210.
  • the RAN node may query the first UE after determining that the first condition is satisfied.
  • the RAN node also needs to inquire whether the second UE agrees to establish a multi-UE architecture or a multi-UE architecture based on a specific service.
  • the bearer configuration is also needed to inquire whether the second UE agrees to establish a multi-UE architecture or a multi-UE architecture based on a specific service.
  • the RAN node can configure the bearer of the multi-UE coordinated transmission or the bearer of the multi-UE coordinated transmission of a specific service when the first condition is met, so as to realize the multi-UE coordinated transmission.
  • the method may further include: receiving a first request sent by the first UE, where the first request is used to request the first configuration information, and the first A request carries the identifier of the second UE.
  • the first UE requests the RAN node to perform cooperative transmission (or called aggregation transmission, backup transmission, handover transmission) with the second UE.
  • the first request may also carry second service identification information, which is used to indicate service information that the first UE expects to perform multi-UE coordinated transmission.
  • the second service identification information includes but is not limited to at least one of the following:
  • a first radio data bearer (DRB) identifier may be an identifier of a data radio bearer currently established by the first UE;
  • the service ID can be the service ID that the current first UE is transmitting or will transmit subsequently;
  • QoS flow identification can be the QoS flow identification that the current first UE is transmitting or will transmit subsequently.
  • the characteristic information of the business For example, the value of the QoS parameter is equal to a certain value, or is located in a certain interval, and so on. Through the feature information, it can be determined that the first UE expects to perform multi-UE protocol transmission services.
  • the RAN node after receiving the first request sent by the first UE, the RAN node sends second configuration information to the second UE, where the second configuration information is used to indicate that the first The second UE performs bearer configuration for multi-UE coordinated transmission for the first UE.
  • the second configuration information is the same as the second configuration information in the foregoing possible implementation manners, for details, reference may be made to relevant descriptions in the foregoing implementation manners, and details are not repeated here.
  • the RAN node after the RAN node sends the second configuration information to the second UE, if the RAN node receives the configuration completion message sent by the second UE, it indicates that the second UE agrees to provide the configuration information for the second UE.
  • the RAN node sends a reconfiguration message to the first UE, where the reconfiguration message carries the first configuration information.
  • the first configuration information is the same as the first configuration information in the foregoing possible implementation manners, for details, reference may be made to relevant descriptions in the foregoing implementation manners, and details are not repeated here.
  • the bearer of multi-UE coordinated transmission after the above multi-UE cooperative transmission is established, for some reason, for example, the service transmission of the first UE changes, or the service transmission of the second UE changes, or the load of the RAN node changes, it is necessary to Modify or release the bearer of multi-UE coordinated transmission. Therefore, after the above-mentioned bearer of multi-UE coordinated transmission is established, the bearer may also need to be modified or released.
  • the method may further include:
  • 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 reconfigured first bearer identifier, and the reconfigured Configured content information, the bearer corresponding to the first bearer identifier is the bearer of the multi-UE coordinated transmission;
  • 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.
  • the RAN node can first send the first reconfiguration command to the second UE, and then send the second reconfiguration command to the first UE, or it can first The first UE sends the second reconfiguration command, and then sends the first reconfiguration command to the second UE, which is not limited in this embodiment of the present application.
  • the RAN node may send the second reconfiguration command to the first UE after receiving the reconfiguration complete message sent by the second UE.
  • the RAN node may also receive a reconfiguration complete message sent by the first UE, so that the RAN node may know that the first UE has completed the reconfiguration command. Reconfigure.
  • the method may further include:
  • Step 1 the RAN node sends a first release command to the second UE, where the first release command carries the identifier of the first UE, the identifier of the released second bearer, and the released content information,
  • the bearer corresponding to the second bearer identifier is the bearer of the multi-UE coordinated transmission;
  • Step 2 The RAN node sends a second release command to the first UE, where the second release command carries the identifier of the second UE, the identifier of the second bearer, and released content information.
  • the RAN node can first send the first release command to the second UE, and then send the second release command to the first UE, or the first The UE sends the second release command, and then sends the first release command to the second UE, which is not limited in this embodiment of the present application.
  • the RAN node may send the second release command to the first UE after receiving the release completion message sent by the second UE.
  • the RAN node may also receive a release complete message sent by the first UE, so that the RAN node may know that the first UE completes the release.
  • the multi-UE architecture is a joint transmission architecture established between the RAN node, the first UE, and the second UE, it is possible for the RAN node, the first UE, and the second UE to use the joint transmission architecture (that is, the above-mentioned multi-UE architecture) , or multi-UE transmission architecture, or multi-UE cooperative transmission architecture) proposes a modification.
  • the first UE or the second UE may request the network, and after the network agrees, execute the modified procedure.
  • the method further includes: receiving the modification sent by the first UE or the second UE request, wherein the modification request is used to request modification of the bearer corresponding to the first bearer identifier.
  • the method further includes: receiving a release request sent by the first UE or the second UE, where the release request uses In order to request to release the bearer corresponding to the second bearer identifier.
  • the RAN node has direct decision-making power. For example, when the RAN node has a high load and cannot support this multi-UE transmission architecture, the RAN node can modify part or all of the multi-UE cooperation. Transport bearer. For another example, when the service of the UE ends, the RAN node may directly release the bearer of multi-UE coordinated transmission.
  • FIG. 4 shows a flow chart of a method for configuring multi-UE coordinated transmission provided by an embodiment of the present application, and the method 400 may be executed by a core network device.
  • the method can be executed by software or hardware installed on core network equipment.
  • the method may include the following steps.
  • the core network device sends association relationship information to the RAN node, where the association relationship information is used to indicate that the first UE has an association relationship with the second UE, and the first UE and the second UE have the ability to establish multi-UE cooperation ability to transmit.
  • the method 400 provided in the embodiment of the present application is the execution process of the core network side corresponding to the method 200, and has corresponding implementations related to the possible implementations related to the core network equipment involved in the method 200. For details, please refer to the description of the method 200. The following can only A possible implementation of the steps involving core network devices will be described.
  • the method before the core network device sends association relationship information to the RAN node, the method further includes at least one of the following:
  • the core network device learns that both the first UE and the second UE are in a connected state
  • the core network device discovers that the first UE enters a connected state, wherein the first UE and the second UE have an association relationship based on any service;
  • the core network device After the core network device discovers that the first UE enters the connected state and initiates the first service, wherein the first UE and the second UE have an association relationship based on a target service, and the target service includes the the first business;
  • the second request sent by the RAN node is received, the second request is used to request all UEs associated with the first UE, or the second request is used to request the UEs with which the first UE has an association relationship.
  • the association relationship information sent by the core network device to the RAN node may include at least one of the following:
  • UE identities list includes the identity of the first UE and the identity of the second UE;
  • First service identification information wherein the first service identification information is used to indicate a service that can perform multi-UE coordinated transmission; for example, the first service identification information may include DRB ID, Service ID, QoS flow ID or service feature information, etc.
  • the method before the core network device sends the association relationship information to the RAN node, the method further includes: the core network device acquiring the association relationship information subscribed by the first UE or the first UE The association relationship information set.
  • the contracted or pre-set association relationship information may include one of the following:
  • a list of UEs with a binding relationship can cooperate with each other for transmission, and each UE decides to be a P-UE or S-UE according to needs;
  • the above-mentioned binding relationship can be based on UE granularity, that is, any service between these UEs can be established and transmitted in a multi-UE architecture, or it can be further based on the granularity of a specific service, that is, on the basis of the UE list, restrict these UEs Among them, only for what kind of business can the multi-UE architecture be established and transmitted, where the service restriction can be the service identifier, the specific QoS parameters of the service, the range of the specific QoS parameters of the service, etc.
  • the core network device can trigger the RAN node to perform multi-UE cooperative transmission bearer configuration, so that multi-UE cooperative transmission can be performed between the first UE and the second UE, ensuring the service experience of the UE and system efficiency.
  • FIG. 5 shows a flow chart of a method for configuring multi-UE coordinated transmission provided by an embodiment of the present application, and the method 500 may be executed by a first UE.
  • the method can be executed by software or hardware installed on the first UE.
  • the method may include the following steps.
  • the first UE sends a first request to the RAN node, where the first request is used to request the RAN node to configure a multi-UE coordinated transmission bearer for the first UE, and the first request carries the first request. 2.
  • the method 500 provided in the embodiment of the present application is the execution flow of the first UE corresponding to the method 200, and has corresponding implementation modes related to the possible implementation modes related to the first UE involved in the method 200.
  • implementation modes related to the possible implementation modes related to the first UE involved in the method 200 please refer to the description of the method 200. The following only A possible implementation manner of the steps performed by the first UE is described.
  • the method may further include:
  • Step 1 the first UE sends a third request through an interface between UEs, where the third request is used to request aggregation transmission for the first UE;
  • Step 2 The first UE receives an acknowledgment message fed back by the second UE, wherein the acknowledgment message carries the identity of the second UE.
  • the first UE can interact with the second UE to acquire the identity of the second UE.
  • the first request sent by the first UE further carries second service identification information, and the second service identification information is used to indicate that the first UE expects to perform multi-UE coordinated transmission. business information.
  • the second service identification information includes but is not limited to at least one of the following:
  • the method may further include:
  • Step 1 the first UE receives a reconfiguration message sent by the RAN node, wherein the reconfiguration message carries first configuration information, and the first configuration information is used to configure multiple UEs for the first UE bearer of cooperative transmission;
  • Step 2 the first UE applies the first configuration information to perform reconfiguration.
  • the RAN node may send the above reconfiguration message to the first UE after completing the reconfiguration of the second UE according to the first request, so as to configure the bearer of the multi-UE transmission architecture for the first UE.
  • the first configuration information includes: the second UE identifier and configuration information of a bearer architecture.
  • the first configuration information further includes: a third DRB identifier, which is used to indicate the service bearer of the multi-UE coordinated transmission configured for the first UE.
  • the method further includes:
  • Step 1 Receive a second reconfiguration command sent by the RAN node, wherein the second reconfiguration signaling carries the identifier of the second UE, the reconfigured first bearer identifier, and the reconfigured first bearer identifier.
  • Content information, the bearer corresponding to the first bearer identifier is the bearer of the multi-UE coordinated transmission;
  • Step 2 execute the second reconfiguration command.
  • the RAN node may send the second reconfiguration command to modify the multi-UE coordinated transmission bearer when the current network state cannot support one or more multi-UE coordinated transmissions.
  • the method may further include : Sending a modification request to the RAN node, where the modification request is used to request modification of a bearer corresponding to the first bearer identifier.
  • the method further includes:
  • Step 1 Receive a second release command sent by the RAN node, where the second release command carries the identifier of the second UE, the identifier of the released second bearer, and the released content information, and the second The bearer corresponding to the bearer identifier is the bearer of the multi-UE coordinated transmission;
  • Step 2 Execute the second release command to release the bearer corresponding to the second bearer identifier.
  • the RAN node may send the second release command after completing the service that the first UE requires coordinated transmission.
  • the RAN node may also send the second release command based on the request of the first UE. Therefore, in an optional implementation manner, before receiving the second release command sent by the RAN node, the method may further include: sending a release request to the RAN node, where the release request is used to request release of the bearer corresponding to the second bearer identifier.
  • the first UE can request the RAN node to perform multi-UE coordinated transmission bearer configuration when needed, so that multi-UE coordinated transmission can be performed between the first UE and the second UE, ensuring UE service experience and system efficiency.
  • FIG. 6 shows a flow chart of a method for responding to multi-UE coordinated transmission provided by an embodiment of the present application, and the method 600 may be executed by a second UE.
  • the method can be executed by software or hardware installed on the second UE.
  • the method may include the following steps.
  • the second UE receives second configuration information sent by the RAN node, where the second configuration information is used to instruct the second UE to perform bearer configuration for multi-UE coordinated transmission for the first UE.
  • the second UE applies the second configuration information and sends a configuration complete message to the RAN node.
  • the method 600 provided in the embodiment of the present application is the execution flow of the second UE corresponding to the method 200, and has corresponding implementations related to the possible implementations related to the second UE involved in the method 200. For details, please refer to the description of the method 200. The following only A possible implementation manner of the steps performed by the second UE is described.
  • the second configuration information includes: an identifier of the first UE and configuration information of forked bearers.
  • the second configuration information further includes: a second DRB identifier, configured to indicate that the second UE is a service bearer for multi-UE coordinated transmission for the first UE.
  • the method before the second UE receives the second configuration information sent by the RAN node, the method further includes:
  • Step 1 the second UE receives a third request sent by the first UE, where the third request is used to request aggregation transmission for the first UE;
  • Step 2 the second UE feeds back an acknowledgment message to the first UE, where the acknowledgment message carries the identity of the second UE.
  • the method further includes:
  • 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 reconfigured first bearer identifier, and the reconfigured first bearer identifier.
  • Content information, the bearer corresponding to the first bearer identifier is the bearer of the multi-UE coordinated transmission;
  • Step 2 execute the first reconfiguration command.
  • the RAN node may send the first reconfiguration command to modify the bearer of multi-UE cooperative transmission when service transmission or network environment changes.
  • the RAN node may also modify the bearer of multi-UE coordinated transmission based on the request of the second UE, for example, the service transmission of the second UE itself is increased or decreased, and the capacity of the first UE's coordinated transmission is decreased or increased. If the bearer of multi-UE coordinated transmission is modified, a request can be sent to the RAN node. Therefore, in a possible implementation manner, before receiving the first reconfiguration command sent by the RAN node, the method further includes: sending a modification request to the RAN node, where the modification request is used to request modification The first bearer identifies a corresponding bearer.
  • the method further includes:
  • Step 1 Receive the first release command sent by the RAN node, wherein the first release command carries the identifier of the first UE, the identifier of the released second bearer, and the released content information, and the second The bearer corresponding to the bearer identifier is the bearer of the multi-UE coordinated transmission;
  • Step 2 Execute the first release command to release the bearer corresponding to the second bearer identifier.
  • the RAN node may send the first release command after the service that the first UE requests for coordinated transmission is completed.
  • the RAN node may also modify the bearer of multi-UE coordinated transmission based on the request of the second UE. If the bearer is released, a request can be sent to the RAN node. Therefore, in a possible implementation manner, before receiving the first release command sent by the RAN node, the method further includes: sending a release request to the RAN node, where the release request is used to request the release of the A bearer corresponding to the second bearer identifier.
  • the second UE can respond to the RAN node to perform multi-UE coordinated transmission bearer configuration, thereby establishing a multi-UE coordinated transmission bearer, so that multi-UE coordinated transmission can be performed between the first UE and the second UE , ensuring the service experience and system efficiency of the UE.
  • the technical solutions provided by the embodiments of the present application will be described below by taking the request of the first UE (that is, the primary UE, P-UE) as an example.
  • FIG. 7 shows a schematic flowchart of a method for establishing a bearer for multi-UE coordinated transmission provided by an embodiment of the present application. As shown in FIG. 7 , the method mainly includes the following steps.
  • the P-UE is a UE that needs to transmit services, and requests other S-UEs around itself through the interface between the UEs, for example, sending an aggregation (Aggregation) transmission request (reques) t, which can also be a backup transmission request, switch transfer request, etc. Through this request, the S-UE is asked whether it can perform aggregation transmission for itself.
  • Aggregation aggregation
  • At least one or a combination of the following information can be carried:
  • the user ID of the P-UE is used to identify the P-UE. On the one hand, it is to confirm the willingness and credit. Another important aspect is to facilitate the gNB to identify and identify the two UEs in the subsequent process.
  • the identification can be It is a globally unique identifier, a unique identifier within a PLMN, an identifier under a serving base station/cell, etc., such as S-TMSI, C-RNTI, etc.
  • the function of carrying the serving base station is to implement the multi-UE architecture under one base station as much as possible, avoiding the introduction of interfaces between base stations, which will cause much higher complexity and delay.
  • the S-UE initiates an RRC connection establishment process to the corresponding serving base station, and performs a process of activating its own security mode command (Security Mode Command, SMC).
  • SMC Security Mode Command
  • this step can be omitted.
  • the UE identity of a S-UE that can be identified by the gNB can be obtained.
  • the identity can be a globally unique identity, a unique identity within the PLMN, an identity under the serving base station/cell, etc., such as S-TMSI, C-RNTI, etc.,
  • the S-UE may reply a confirmation to the P-UE and inform the UE identity of itself.
  • the P-UE After the P-UE obtains the consent of the S-UE or obtains its UE identity, it reports to its serving base station a request for multi-UE architecture configuration, and carries the UE identity of the S-UE, indicating that the P-UE is compatible with the designated S-UE. Make aggregation/backup/switchover transfers.
  • S704 can be directly initiated without S701-S703, as long as the P-UE and S-UE have interacted and have the user identity of the S-UE.
  • the base station After receiving the request from the P-UE, the base station generates a corresponding configuration and sends it to the designated S-UE.
  • the consent of the S-UE can be sought to see whether it is willing to perform aggregation/backup/handover transmission for the P-UE.
  • the configuration information sent by the base station to the S-UE carries the P-UE identifier, indicating the P-UE of the configured multi-UE architecture, which is convenient for the S-UE to judge the current willingness and the subsequent cooperative operation.
  • the gNB performs a multi-architecture confirmation operation to the P-UE.
  • the message sent by the gNB to the P-UE may also carry the corresponding configuration of the multi-UE architecture.
  • any aggregation/backup/handover bearer can be established between the two UEs at this time.
  • all the bearers of the P-UE can be configured as multi-UE architecture transmission; or, it can be determined by the base station algorithm, and according to the service QoS, etc., the required P-UE bearers can be configured for multi-UE architecture transmission;
  • the base station may perform multi-UE architecture transmission configuration on the bearer of the permitted P-UE according to the binding information issued by the core network.
  • FIG. 8 shows another schematic flowchart of a method for establishing a bearer for multi-UE coordinated transmission provided by an embodiment of the present application. As shown in FIG. 8 , the method mainly includes the following steps.
  • the P-UE sends a multi-UE architecture request to the network, and the request may carry the user identifier of the S-UE and service information expected to be transmitted by the multi-UE architecture.
  • the business information may include at least one of the following:
  • DRB ID the identification of the data radio bearer that the current P-UE has established
  • Service ID or QoS flow ID the service identification that the P-UE is currently transmitting or will be transmitted in the future, the QoS flow identification, etc.
  • the characteristics of the service for example, the QoS parameter value is equal to a certain value, or is located in a certain interval.
  • method 700 Before S801, S701-S703 in method 700 may also be executed.
  • the difference between method 800 and method 700 is that method 800 is a process of establishing a multicast architecture based on a specific service.
  • the base station sends reconfiguration information to the S-UE, which is used to configure bearers related to the multi-UE architecture.
  • the reconfiguration information sent by the base station to the S-UE may carry the following information:
  • the user identifier of the P-UE which is convenient for the S-UE to identify the P-UE, whether it is willing to establish aggregation/backup/handover bearer for it, and if it is willing, to identify each other in subsequent collaborative work;
  • the base station returns a bearer reconfiguration confirmation to the P-UE, and determines that the requested or specified bearer DRB ID has been configured with corresponding aggregation/backup/handover multi-UE architecture configuration.
  • the P-UE can hand over the data of its own DRB ID to the S-UE, and the S-UE will send it to the gNB.
  • the multi-UE architecture configuration of aggregation/backup/handover mentioned in the above method 700 mainly refers to the PDCP anchor architecture shown in Figure 3a, the RLC anchor architecture shown in Figure 3b, and the MAC anchor architecture shown in Figure 3c. one or more.
  • the protocol may select one or more architectures. If only one architecture is selected, the network side can configure the protocol entities related to the architecture by default. If two or more architectures are selected, the network side can select and configure different architectures as required.
  • the RAN side can configure multiple UEs, so that the UEs can transmit with multiple devices under the control of the network side, which ensures the service experience and system efficiency of the UEs.
  • the bearer configuration method provided in the embodiment of the present application may be executed by a bearer configuration device, or a control module in the bearer configuration device for executing the bearer configuration method.
  • the bearer configuration device provided in the embodiment of the present application is described by taking the bearer configuration device executing the bearer configuration method as an example.
  • FIG. 9 shows a schematic structural diagram of a bearer configuration device provided by an embodiment of the present application.
  • the device 900 mainly includes: a first acquiring module 901 and a first transceiver module 902 .
  • the first acquiring module 901 is configured to acquire first configuration information of the first UE, wherein the first configuration information is used to configure the bearer of multi-UE coordinated transmission; the first transceiving module 902 is configured to to send the first configuration information to the first UE.
  • the first transceiving module 902 is further configured to receive association relationship information issued by the core network before sending the first configuration information to the first UE, where the association relationship information is used to indicate the An association relationship between the first UE and the second UE.
  • the association relationship information includes at least one of the following:
  • a list of UE identities with an association relationship wherein the UE identities list includes the identity of the first UE and the identity of the second UE;
  • First service identification information where the first service identification information is used to indicate a service that can perform multi-UE coordinated transmission
  • Attributes of each UE in the UE identification list having an association relationship.
  • the first acquiring module 901 is further configured to determine that the first condition is met.
  • the first condition includes at least one of the following:
  • the serving node of the first UE it is determined that at least part of the service transmission of the first UE cannot meet the quality of service (QoS) requirement or the service experience requirement; the RAN node paging the second UE, and determines that the second UE 2.
  • the UE enters the connected state;
  • At least some of the current services of the first UE have the feature of supporting multi-UE transmission.
  • the first acquiring module 901 is further configured to determine the transmission distance and/or link between the first UE and the second UE before sending the first configuration information to the first UE The situation satisfies the multi-UE transmission requirements.
  • 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, where the second configuration information is used for Instructing the second UE to perform multi-UE coordinated transmission bearer configuration for the first UE; receiving a configuration completion message sent by the second UE.
  • the first transceiving 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, where the first request is used to request For the first configuration information, the first request carries the identity of the second UE.
  • the first request further carries second service identification information, which is used to indicate service information that the first UE expects to perform multi-UE coordinated transmission.
  • the second service identification information includes at least one of the following:
  • 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, where the second configuration information Bearer configuration for instructing the second UE to perform multi-UE coordinated transmission for the first UE.
  • the second configuration information includes: an identifier of the first UE and configuration information of forked bearers.
  • the second configuration information further includes: a second DRB identifier, configured to indicate that the second UE is a service bearer for multi-UE coordinated transmission for the first UE.
  • 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; send a reconfiguration message to the first UE A configuration message, wherein the reconfiguration message carries the first configuration information.
  • the first configuration information includes:
  • An identifier of the second UE and configuration information of a bearer architecture An identifier of the second UE and configuration information of a bearer architecture.
  • the first configuration information further includes: a third DRB identifier, configured to indicate a service bearer configured for the first UE for multi-UE coordinated transmission.
  • the first transceiving module 902 is further configured to send a first reconfiguration command to the second UE after sending the first configuration information to the first user equipment UE, wherein the first reconfiguration command
  • the configuration signaling carries the identifier of the first UE, the reconfigured first bearer identifier, and reconfigured content information, and the bearer corresponding to the first bearer identifier is the bearer of the multi-UE coordinated transmission;
  • the first UE sends a second reconfiguration command, where the second reconfiguration signaling carries the identifier of the second UE, the first bearer identifier, and content information of the reconfiguration.
  • the first transceiving 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.
  • the first transceiver module 902 is further configured to send a first release command to the second UE after sending the first configuration information to the first user equipment UE, where the first release command Carry the identifier of the first UE, the identifier of the released second bearer, and the released content information, the bearer corresponding to the second bearer identifier is the bearer of the multi-UE coordinated transmission; send the first UE to the first UE A release command, wherein the second release command carries the identifier of the second UE, the identifier of the second bearer, and released content information.
  • 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, where the The release request is used to request to release the bearer corresponding to the second bearer identifier.
  • the bearer configuration device in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a network side device.
  • the apparatus may be a base station or a CU, which is not specifically limited in this embodiment of the present application.
  • the bearer configuration device in this embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in this embodiment of the present application.
  • the bearer configuration device provided in the embodiment of the present application can implement the various processes implemented by the RAN node in the method embodiments in FIG. 2 to FIG. 8 and achieve the same technical effect. To avoid repetition, details are not repeated here.
  • FIG. 10 shows a schematic structural diagram of an apparatus for configuring multi-UE coordinated transmission provided by an embodiment of the present application.
  • the apparatus mainly includes: a second acquiring module 1001 and a second transceiving module 1002 .
  • the second obtaining module 1001 is configured to obtain association relationship information, wherein the association relationship information is used to indicate that the first UE has an association relationship with the second UE, and the first UE and the second UE have an association relationship.
  • the UE has the capability of establishing multi-UE coordinated transmission; the second transceiver module 1002 is configured to send the association relationship to the RAN node.
  • the second transceiver module 1002 is further configured to perform at least one of the following before sending the association relationship information to the RAN node:
  • the first UE After finding that the first UE enters the connected state and initiates the first service, wherein the first UE and the second UE have an association relationship based on a target service, and the target service includes the first service;
  • the second request is used to request all UEs associated with the first UE, or the second request is used to request
  • the UE has an association relationship with the UE.
  • the association relationship information includes at least one of the following:
  • a list of UE identities with an association relationship wherein the UE identities list includes the identity of the first UE and the identity of the second UE;
  • First service identification information where the first service identification information is used to indicate a service that can perform multi-UE coordinated transmission
  • Attributes of each UE indicated in the UEID list having an association relationship Attributes of each UE indicated in the UEID list having an association relationship.
  • the second acquiring module 1001 is further configured to acquire association relationship information subscribed by the first UE or association relationship information preset by the first UE before sending the association relationship information to the RAN node.
  • the device for configuring multi-UE cooperative transmission in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a network side device.
  • the apparatus may be a base station or a CU, which is not specifically limited in this embodiment of the present application.
  • the device for configuring multi-UE coordinated transmission in the embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in this embodiment of the present application.
  • the device for configuring multi-UE cooperative transmission provided by the embodiment of the present application can implement the various processes implemented by the core network device or the core network in the method embodiments in Fig. 2 to Fig. 8, and achieve the same technical effect. To avoid repetition, it is not repeated here repeat.
  • FIG. 11 shows a schematic structural diagram of an apparatus for requesting multi-UE coordinated transmission provided by an embodiment of the present application.
  • the apparatus 1100 mainly includes: a first determination module 1101 and a third transceiver module 1102 .
  • the first determination module 1101 is configured to determine that the first UE needs to perform multi-UE coordinated transmission; the third transceiver module 1102 is configured to send a first request to the RAN node, wherein the first request uses In order to request the RAN node to configure a multi-UE coordinated transmission bearer for the first UE, the first request carries an identifier of the second UE.
  • 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, where the third request is used to request performing aggregation transmission by the first UE; receiving an acknowledgment message fed back by the second UE, wherein the acknowledgment message carries the identity of the second UE.
  • 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 the first configuration information , the first configuration information is used to configure a multi-UE coordinated transmission bearer for the first UE; reconfiguration is performed by applying the first configuration information.
  • the first configuration information includes: the second UE identifier and configuration information of a bearer structure.
  • the first configuration information further includes: a third DRB identifier, configured to indicate a service bearer configured for the first UE for multi-UE coordinated transmission.
  • 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
  • the signaling carries the identifier of the second UE, the reconfigured first bearer identifier, and the reconfigured content information, and the bearer corresponding to the first bearer identifier is the bearer of the multi-UE coordinated transmission; Describe the second reconfiguration command.
  • 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, where the modification request is used to request modification
  • the first bearer identifies a corresponding bearer.
  • the third transceiver module 1102 is further configured to, after receiving the reconfiguration message sent by the RAN node, receive a second release command sent by the RAN node, wherein the second release command Carrying the identifier of the second UE, the identifier of the released second bearer, and the released content information, the bearer corresponding to the second bearer identifier is the bearer of the multi-UE coordinated transmission; execute the second release command, release The second bearer identifies a corresponding bearer.
  • 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, where the release request is used to request to release the A bearer corresponding to the second bearer identifier.
  • the first request further carries second service identification information, where the second service identification information is used to indicate service information that the first UE expects to perform multi-UE coordinated transmission.
  • the second service identification information includes at least one of the following:
  • the device for requesting multi-UE coordinated transmission in this embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal device.
  • the apparatus may be a base station or a CU, which is not specifically limited in this embodiment of the present application.
  • the device for requesting multi-UE coordinated transmission in the embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in this embodiment of the present application.
  • the device for requesting multi-UE cooperative transmission provided in the embodiment of the present application can realize each process implemented by the first UE in the method embodiments in FIG. 2 to FIG. 8 , and achieve the same technical effect. To avoid repetition, details are not repeated here.
  • FIG. 12 shows a schematic structural diagram of an apparatus for responding to multi-UE coordinated transmission provided by an embodiment of the present application.
  • the apparatus 1200 mainly includes: a fourth transceiver module 1201 and a second determination module 1202 .
  • the fourth transceiver module 1201 is configured to receive second configuration information sent by the RAN node, where the second configuration information is used to instruct the second UE to perform multi-UE coordinated transmission for the first UE bearer configuration; the second determining module 1202 is configured to determine whether to agree to perform multi-UE coordinated transmission for the first UE; the fourth transceiver module 1201 is also configured to agree to perform multi-UE coordinated transmission for the first UE In the case of , the second UE applies the second configuration information and sends a configuration complete message to the RAN node.
  • the second configuration information includes: an identifier of the first UE and configuration information of forked bearers.
  • the second configuration information further includes: a second DRB identifier, configured to indicate that the second UE is a service bearer for multi-UE coordinated transmission for the first UE.
  • 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, where the third request is used to request performing aggregation transmission for the first UE; feeding back an acknowledgment message to the first UE, where the acknowledgment message carries the identity of the second UE.
  • the fourth transceiver module 1201 is further configured to receive the first reconfiguration command sent by the RAN node after sending the configuration completion message to the RAN node, where the first reconfiguration message
  • the command carries the identifier of the first UE, the reconfigured first bearer identifier, and the reconfigured content information, and the bearer corresponding to the first bearer identifier is the bearer of the multi-UE coordinated transmission; execute the The first configuration command.
  • 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, where the modification request is used to request modification
  • the first bearer identifies a corresponding bearer.
  • the fourth transceiver module 1201 is further configured to receive the first release command sent by the RAN node after sending the configuration complete message to the RAN node, where the first release command carries There are the identifier of the first UE, the identifier of the released second bearer, and the released content information, and the bearer corresponding to the second bearer identifier is the bearer of the multi-UE coordinated transmission; execute the first release command to release the released bearer A bearer corresponding to the second bearer identifier.
  • 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, where the release request is used to request to release the A bearer corresponding to the second bearer identifier.
  • the response of the multi-UE cooperative transmission in the embodiment of the present application may be a device, or a component, an integrated circuit, or a chip in a terminal device.
  • the apparatus may be a base station or a CU, which is not specifically limited in this embodiment of the present application.
  • the response to the multi-UE coordinated transmission in the embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in this embodiment of the present application.
  • the multi-UE cooperative transmission response provided by the embodiment of the present application can implement various processes implemented by the second UE in the method embodiments shown in FIG. 2 to FIG.
  • this embodiment of the present application further provides a communication device 1300, including a processor 1301, a memory 1302, and programs or instructions stored in the memory 1302 and operable on the processor 1301,
  • a communication device 1300 including a processor 1301, a memory 1302, and programs or instructions stored in the memory 1302 and operable on the processor 1301,
  • the communication device 1300 is a terminal
  • the program or instruction is executed by the processor 1301
  • each process of the above-mentioned embodiment of the method 400 or the embodiment of the method 500 can be achieved, and the same technical effect can be achieved.
  • the communication device 1300 is a network-side device
  • the program or instruction is executed by the processor 1301
  • each process of the above-mentioned method 200 embodiment or method 300 embodiment can be achieved, and the same technical effect can be achieved. In order to avoid repetition, it is not repeated here repeat.
  • the embodiment of the present application also provides a terminal, including a processor and a communication interface, the processor is used to implement the processes of the above method 400 embodiment or the method 500 embodiment, and the communication interface is used to communicate with external devices.
  • This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.
  • FIG. 14 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 1400 includes but not limited to: a radio frequency unit 1401, a network module 1402, an audio output unit 1403, an input unit 1404, a sensor 1405, a display unit 1406, a user input unit 1407, an interface unit 1408, a memory 1409, and a processor 1410, etc. .
  • the terminal 1400 can also include a power supply (such as a battery) for supplying power to various components, and the power supply can be logically connected to the processor 1410 through the power management system, so as to manage charging, discharging, and power consumption through the power management system. Management and other functions.
  • a power supply such as a battery
  • the terminal structure shown in FIG. 14 does not constitute a limitation on the terminal.
  • the terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange different components, which will not be repeated here.
  • the input unit 1404 may include a graphics processor (Graphics Processing Unit, GPU) 14041 and a microphone 14042, and the graphics processor 14041 is used for the image capture device (such as the image data of the still picture or video obtained by the camera) for processing.
  • the display unit 1406 may include a display panel 14061, and the display panel 14061 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 . Touch panel 14071, also called touch screen.
  • the touch panel 14071 may include two parts, a touch detection device and a touch controller.
  • Other input devices 14072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.
  • the radio frequency unit 1401 receives the downlink data from the network-side device, and sends it to the processor 1410 for processing; in addition, sends the uplink data to the network-side device.
  • 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, and the like.
  • the memory 1409 can be used to store software programs or instructions as well as various data.
  • the memory 1409 may mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area may store an operating system, an application program or instructions required by at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • the memory 1409 may include a high-speed random access memory, and may also include a non-transitory memory, wherein the non-transitory memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • PROM erasable programmable read-only memory
  • Erasable PROM Erasable PROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one disk storage device, flash memory device, or other non-transitory solid state storage device.
  • the processor 1410 may include one or more processing units; optionally, the processor 1410 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, application programs or instructions, etc., Modem processors mainly handle wireless communications, such as baseband processors. It can be understood that the foregoing modem processor may not be integrated into the processor 1410 .
  • the radio frequency unit 1401 is configured to send a first request to the RAN node, where the first request is used to request the RAN node to configure a multi-UE coordinated transmission bearer for the first UE, and the first request Carries the identity of the second UE.
  • the radio frequency unit 1401 is configured to receive second configuration information sent by the RAN node, where the second configuration information is used to instruct the second UE to perform multi-UE coordinated transmission bearer configuration for the first UE;
  • the second UE applies the second configuration information and sends a configuration complete message to the RAN node.
  • the embodiment of the present application also provides a network side device, including a processor and a communication interface, the processor is used to implement the processes of the above method 200 embodiment or the method 300 embodiment, and the communication interface is used to communicate with external devices.
  • the network-side device embodiment corresponds to the above-mentioned network-side device method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.
  • the embodiment of the present application also provides a network side device.
  • the network device 1500 includes: an antenna 1501 , a radio frequency device 1502 , and a baseband device 1503 .
  • the antenna 1501 is connected to the radio frequency device 1502 .
  • the radio frequency device 1502 receives information through the antenna 1501, and sends the received information to the baseband device 1503 for processing.
  • the baseband device 1503 processes the information to be sent and sends it to the radio frequency device 1502
  • the radio frequency device 1502 processes the received information and sends it out through the antenna 1501 .
  • the foregoing frequency band processing device may be located in the baseband device 1503 , and the method performed by the network side device in the above embodiments may be implemented in the baseband device 1503 , and the baseband device 1503 includes a processor 1504 and a memory 1505 .
  • the baseband device 1503 may include, for example, at least one baseband board, and the baseband board is provided with a plurality of chips, as shown in FIG. The network device operations shown in the above method embodiments.
  • 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 (common public radio interface, CPRI for short).
  • a network interface 1506 for exchanging information with the radio frequency device 1502, such as a common public radio interface (common public radio interface, CPRI for short).
  • the network-side device in this embodiment of the present application further includes: instructions or programs stored in the memory 1505 and operable on the processor 1504, and the processor 1504 calls the instructions or programs in the memory 1505 to execute the instructions shown in Figure 9 or Figure 10.
  • the methods executed by each module are shown to achieve the same technical effect. In order to avoid repetition, the details are not repeated here.
  • the embodiment of the present application also provides a readable storage medium, the readable storage medium may be volatile or non-volatile, and a program or instruction is stored on the readable storage medium, the program or
  • a program or instruction is stored on the readable storage medium, the program or
  • the processor is the processor in the terminal described in the foregoing embodiments.
  • the readable storage medium includes computer readable storage medium, such as computer read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc.
  • the embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement each of the above method 200 embodiments process, or realize the various processes of the above-mentioned method 300 embodiment, or realize the various processes of the above-mentioned method 400 embodiment, or realize the various processes of the above-mentioned method 500 embodiment, and can achieve the same technical effect, in order to avoid repetition, no longer repeat.
  • the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.
  • the embodiment of the present application also provides a computer program/program product, the computer program/program product is stored in a non-transitory storage medium, and the computer program/program product is executed by at least one processor to implement the above method 200 embodiment, or realize the various processes of the above-mentioned method 300 embodiment, or realize the various processes of the above-mentioned method 400 embodiment, or realize the various processes of the above-mentioned method 500 embodiment, and can achieve the same technical effect, in order to avoid Repeat, no more details here.
  • the term “comprising”, “comprising” or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase “comprising a " does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that element.
  • the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions are performed, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
  • the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation.
  • the technical solution of the present application can be embodied in the form of computer software products, which are stored in a storage medium (such as ROM/RAM, magnetic disk, etc.) , CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present application.

Landscapes

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

Abstract

本申请公开了一种承载的配置方法、网络侧设备及终端，属于无线通信技术领域。本申请实施例的承载的配置方法，包括：无线接入网络RAN节点向第一用户设备UE发送第一配置信息，其中，所述第一配置信息用于配置多UE协作传输的承载。

Description

承载的配置方法、网络侧设备及终端
相关申请的交叉引用
本申请要求在2021年10月14日提交的中国专利申请第202111200149.0号的优先权，该中国专利申请的全部内容通过引用包含于此。
技术领域
本申请属于无线通信技术领域，具体涉及一种承载的配置方法、网络侧设备及终端。
背景技术
在现有机制中，一个用户设备(User Equipment，UE)与核心网建立自己的控制面连接和用户面连接，例如协议数据单元(Protocol Data Unit，PDU)会话(session)。当UE在不同的小区、不同的基站，甚至是不同的核心网节点之间移动时，网络侧将该UE的控制面连接和用户面连接以及传输状态，在不同的网络节点之间进行传递，以确保UE的业务传输能够连续、不中断、以及按照需求达到无损的要求。
当两个UE进行数据传输时，两个UE各自建立自己的核心网或接入网的控制面连接和用户面连接，例如非接入层(Non Access Stratum，NAS)连接(核心网控制面)、无线资源控制(Radio Resource Control，RRC)连接(接入网控制面)，PDU session(核心网用户面)、数据无线承载(Data Radio Bearer，DRB)以及服务质量(Quality of Service，QoS)流(flow)(接入网用户面)等都是两个UE各自独立的。因此，在现有技术中无法实现多UE协作传输。
发明内容
本申请实施例提供一种承载的配置方法、网络侧设备及终端，能够解决 现有技术中无法实现多UE协作传输的问题。
第一方面，提供了一种承载的配置方法，包括：无线接入网络RAN节点向第一用户设备UE发送第一配置信息，其中，所述第一配置信息用于配置多UE协作传输的承载。
第二方面，提供了一种承载的配置装置，包括：第一获取模块，用于获取第一UE的第一配置信息，其中，所述第一配置信息用于配置多UE协作传输的承载；第一收发模块，用于向所述第一UE发送所述第一配置信息。
第三方面，提供了一种多UE协作传输的配置方法，包括：核心网设备向RAN节点发送关联关系信息，其中，所述关联关系信息用于指示第一UE与第二UE具有关联关系，所述第一UE和所述第二UE具有建立多UE协作传输的能力。
第四方面，提供了一种多UE协作传输的配置装置，包括：第二获取模块，用于获取关联关系信息，其中，所述关联关系信息用于指示第一UE与第二UE具有关联关系，所述第一UE和所述第二UE具有建立多UE协作传输的能力；第二收发模块，用于向RAN节点发送所述关联关系。
第五方面，提供了一种多UE协作传输的请求方法，包括：第一UE向RAN节点发送第一请求，其中，所述第一请求用于请求所述RAN节点为所述第一UE配置多UE协作传输的承载，所述第一请求中携带有第二UE的标识。
第六方面，提供了一种多UE协作传输的请求装置，包括：第一确定模块，用于确定第一UE需要执行多UE协作传输；第三收发模块，用于向RAN节点发送第一请求，其中，所述第一请求用于请求所述RAN节点为所述第一UE配置多UE协作传输的承载，所述第一请求中携带有第二UE的标识。
第七方面，提供了一种多UE协作传输的响应方法，包括：第二UE接收RAN节点发送的第二配置信息，其中，所述第二配置信息用于指示所述第二UE为第一UE进行多UE协作传输的承载配置；在同意为所述第一UE 进行多UE协作传输的情况下，所述第二UE应用所述第二配置信息，向所述RAN节点发送配置完成消息。
第八方面，提供了一种多UE协作传输的响应装置，包括：第四收发模块，用于接收RAN节点发送的第二配置信息，其中，所述第二配置信息用于指示所述第二UE为第一UE进行多UE协作传输的承载配置；第二确定模块，用于确定是否同意为所述第一UE进行多UE协作传输；所述第四收发模块还用于在同意为所述第一UE进行多UE协作传输的情况下，所述第二UE应用所述第二配置信息，向所述RAN节点发送配置完成消息。
第九方面，提供了一种终端，该终端包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第五方面所述的方法的步骤，或者实现如第七方面所述的方法的步骤。
第十方面，提供了一种终端，包括处理器及通信接口，其中，所述处理器用于实现如第一方面所述的方法的步骤，或者实现如第七方面所述的方法的步骤所述通信接口用于与外部设备进行通信。
第十一方面，提供了一种网络侧设备，该网络侧设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤。
第十二方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述处理器用于实现如第一方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤，所述通信接口用于与外部设备进行通信。
第十三方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤，或者实现如第五方面所述的方法的步骤，或者实现如第七方面所述的方法的步骤。
第十四方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤，或者实现如第五方面所述的方法的步骤，或者实现如第七方面所述的方法的步骤。
第十五方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在非瞬态的存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现第一方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤，或者实现如第五方面所述的方法的步骤，或者实现如第七方面所述的方法的步骤。
在本申请实施例中，无线接入网络(Radio Access Network，RAN)节点可以向第一UE发送第一配置，配置多UE协作传输的承载，从而使得第一UE可以进行多UE协作传输。
附图说明
图1示出本申请实施例可应用的一种无线通信系统的示意图；
图2示出本申请实施例提供的承载的配置方法的一种流程示意图；
图3a示出本申请实施例提供的一种多UE传输架构的示意图；
图3b示出本申请实施例提供的另一种多UE传输架构的示意图；
图3c示出本申请实施例提供的又一种多UE传输架构的示意图；
图4示出本申请实施例提供的多UE协作传输的配置方法的一种流程示意图；
图5示出本申请实施例提供的多UE协作传输的配置方法的一种流程示意图；
图6示出本申请实施例提供的多UE协作传输的响应方法的一种流程示意图；
图7示出本申请实施例提供的多UE协作传输的承载建立方法的一种流 程示意图；
图8示出本申请实施例提供的多UE协作传输的承载建立方法的另一种流程示意图；
图9示出本申请实施例提供的承载的配置装置的一种结构示意图；
图10示出本申请实施例提供的多UE协作传输的配置装置的一种结构示意图；
图11示出本申请实施例提供的多UE协作传输的配置装置的一种结构示意图；
图12示出本申请实施例提供的多UE协作传输的响应装置的一种结构示意图；
图13示出本申请实施例提供的一种通信设备的结构示意图；
图14示出本申请实施例提供的一种终端的硬件结构示意图；
图15示出本申请实施例提供的一种网络侧设备的硬件结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(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)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的应用，如第6代(6 th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的示意图。无线通信系统包括终端11和网络侧设备12。其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(VUE)、行人终端(PUE)等终端侧设备，可穿戴式设备包括：智能手表、手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点 (Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的承载的配置方法、网络侧设备及终端进行详细地说明。
图2示出本申请实施例中的承载的配置方法的一种流程示意图，该方法200可以由RAN节点执行。换言之，所述方法可以由安装在RAN节点上的软件或硬件来执行。如图2所示，该方法可以包括以下步骤。
S210，RAN节点向第一UE发送第一配置信息，其中，所述第一配置信息用于配置多UE协作传输的承载。
在本申请实施例中，RAN节点可以是基站或者集中式单元(Centralized Unit，CU)，具体本申请实施例中不作限定。
在相关技术中，不同UE的接入网连接或核心网连接彼此之间独立，各个UE只能独立的进行业务传输，然而在实际使用中，用户可能需要两个UE之间进行业务共同传输，例如用户在室内使用手机进行听歌/听书时，准备出门跑步，用户希望手环能够连续的进行相关业务的接收，给用户带来连续性的业务体验。或者，当一个UE的发送功率受限或者上行传输速率不够的情况下，可以使用两个或者多个UE的发送功率和传输能力进行共同传输。或者，当用户的业务具有比较高的可靠性时，可以在两个或者更多UE建立连接备份，根据链路质量决定当前使用哪条链路传输，以满足低时延和高可靠性的传输需求。然而这些场景在现有的架构和机制中是无法支持的，需要用户手动的在新设备上对业务的接收和接收进度进行设置或者通过业务层，才能达到连续性接收的效果，或者通过硬切换达到链路变化，降低了体验的便利性和用户QoS体验效果。而在本申请实施例提供的技术方案中，RAN节点为第一UE配置用于多UE协作传输的承载，从而使得第一UE可以用于多 UE协作传输，提高业务传输的便利性和用户QoS体验效果。
可选地，所述第一配置信息可以包括：第二UE的标识以及承载架构的配置信息。
在本申请实施例中，所述承载架构的配置信息是指多UE协作传输(也可以称为聚合传输、备份传输或切换传输等)的多UE架构配置，例如，可以包括图3a所示的分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)锚(anchor)架构、图3b所示的无线链路控制(Radio Link Control，RLC)anchor架构、图3c所示的媒体接入控制(Medium Access Control，MAC)anchor架构中的至少之一的配置信息。
当然，并不限于此，多UE架构除了图3a至图3c中所示的架构之外，还可以采用其它的架构，例如，将某一层(例如PDCP或MAC)的部分公共功能(common function)设置于第一UE，而将分叉功能(split function)设置于第二UE。
在具体应用中，协议可以选择一种或多种架构，如果选择一种架构，则第一配置信息中包括该架构相关的协议实体的配置，如果采用两种或以上的架构，则RAN节点可以按需进行不同架构的选择和配置，具体本申请实施例中不作限定。
在一个可能的实现方式中，为了避免第二UE不同意与第一UE进行多UE协作传输而导致第一UE还需要释放刚建立的多UE协作传输的承载的情况，该方法还可以包括：在所述RAN节点向第一UE发送第一配置信息之前，所述方法还包括：所述RAN节点向所述第二UE发送第二配置信息，其中，所述第二配置信息用于指示所述第二UE为所述第一UE进行多UE协作传输的承载配置；所述RAN节点接收所述第二UE返回的配置完成消息。采用该可能的实现方式，RAN节点先向第二UE发送所述第二配置信息，在接收到所述第二UE发送的配置完成消息之后，再向第一UE发送所述第一配置信息，从而可以在第二UE同意与第一UE进行多UE协作传输之后，再重配置 第一UE的承载，避免了流程的浪费。
在本申请实施例中，RAN节点可以自行判断向第一UE发送第一配置信息，或者，也可以在核心网的触发下向第一UE发送第一配置信息，或者，也可以是在第一UE的请求下向第一UE发送第一配置信息，下面分别进行说明。
(一)核心网触发
在该可能的实现方式中，在S210之前，该方法还可以包括：RAN节点接收核心网下发的关联关系信息，其中，所述关联关系信息用于指示所述第一UE与第二UE之间的关联关系。
由于多UE架构牵涉到两个或者多个UE之间的深度合作，需要使用到其它UE的传输能力和传输硬件资源，以及涉及到一些计费和安全因素，因此一种比较典型的场景是，需要进行多UE架构传输的用户之间，先经过签约等过程使彼此之间的关联关系(也可以称为绑定关系)静态化。例如，一个用户的手机与可穿戴设备，甚至是与家用设备之间，可以通过签约过程初始化彼此之间的关联关系。再比如，一个工厂的特定设备之间因为需要协同工作，也可以通过预先的过程初始化彼此之间的关联关系。
一般来说，签约过程或者预先初始化过程的关联关系需要存储在核心网节点，由核心网节点负责验证关联关系的有效性。
可选地，签约或者预先的关联关系，可以包括以下之一：
(1)一组具有关联关系的UE列表，列表中的UE彼此之间可以互相协作传输，每个UE根据需要决定作为主UE(P-UE)或者辅UE(S-UE)；
(2)一组具有关联关系的UE列表，其中每个UE的属性P-UE还是S-UE是提前预设的；
(3)一组具有关联关系的UE列表，其中设定了每个UE可以支持的属性，例如P-UE only，S-UE only或者bothP-UE and S-UE；
其中，上述关联关系可以是基于UE粒度，即这些UE之间的任何业务 都可以进行多UE架构建立和传输，也可以进一步基于特定业务的粒度，即在UE列表的基础上，限制这些UE之间，针对什么样的业务进行多UE架构建立和传输，其中业务限制可以是业务标识，业务的具体QoS参数，业务的具体QoS参数的范围等。
其中，上述主UE(Primary UE，P-UE)是业务发起的UE或者业务源/业务传输的高层协议位于该UE，辅UE(Secondary UE，S-UE)是协助主UE进行业务传输的，一般只具有传输协议较低层的协议层，只完成协助传输的相关功能。
核心网存储上述签约过程或者预先初始化过程的关联关系，在需要时下发给RAN节点，便于RAN节点进行后续的多UE架构的配置。在一个可能实现方式中，核心网下发给RAN节点的关联关系信息可以包括以下至少之一：
(1)具有关联关系的UE标识列表，其中，所述UE标识列表中包括所述第一UE的标识和所述第二UE的标识；例如，具有绑定关系的UE ID list，其中UE ID可以为全球唯一标识、公共陆地移动网络(Public Land Mobile Network，PLMN)内UE标识、接入和移动管理功能(Access and Mobility Management Function，AMF)节点内标识或者gNB/CU内的标识，可以是S-临时移动签约标识(S-Temporary Mobile Subscription Identifier，S-TMSI)、AMF UE ID或者gNB UE ID等。
(2)第一业务识别信息，其中，所述第一业务识别信息用于指示能够执行多UE协作传输的业务；即指示UE标识列表中的各个UE基于特定业务具有关联关系。其中，第一业务识别信息可以为业务标识(service ID，service code，QoS flow ID等)，也可以是业务特征，例如，满足QoS参数等于某个数值或者处于某一个特定区间的业务。
(3)具有关联关系的UE标识列表中的各个UE的属性。例如P-UE only,S-UE only，或者both P-UE and S-UE。
在该可能的实现方式中，核心网设备可以在以下至少之一的情况下，向RAN节点发送所述关联关系信息：
(1)所述核心网设备(CN)获知所述第一UE和所述第二UE均处于连接态；由于CN可以从RAN节点实时上报的信息中获取RAN节点下激活的连接态UE，因此CN可以将其中有关联关系的UE的关联关系信息都下发给RAN节点；
(2)所述核心网设备发现所述第一UE进入连接态，其中，所述第一UE与所述第二UE基于任意业务均具有关联关系；例如，当一个UE进入连接态之后，如果核心网设备发现该UE具有关联关系，则下发该UE的关联关系信息给该UE的服务RAN节点；
(3)所述核心网设备发现所述第一UE进入连接态且发起第一业务之后，其中，所述第一UE与所述第二UE基于目标业务具有关联关系，所述目标业务包括所述第一业务；例如，当一个UE进入连接态并发起业务之后，如果核心网设备发现基于该业务该UE具有关联关系，则下发该UE的关联关系信息给该UE的服务RAN节点；
(4)接收到所述RAN节点发送的第二请求，所述第二请求用于请求所述第一UE所关联的所有UE，或者，所述第二请求用于请求基于第二业务与所述第一UE具有关联关系的UE。即RAN节点主动向CN节点请求，例如，RAN节点根据需要，该需要可以是RAN节点自行判断，也可以是UE向RAN节点请求之后触发，向CN节点请求。其中，RAN节点可以请求所有其下UE的绑定关系，也可以是特定UE的绑定关系，也可以是特定UE的特定业务的绑定关系。
通过本申请实施例提供的技术方案，RAN节点可以在核心网设备的触发下，为第一UE和第二UE分别配置用于多UE协作传输的承载，从而可以实现第一UE与第二UE的协作传输。
(二)RAN节点自行确定
在该可能的实现方式中，所述RAN节点可以在确定满足第一条件的情况下，向第一UE发送第一配置信息。
可选地，第一条件包括但不限于以下至少之一：
(1)所述RAN节点从核心网获取到所述第一UE与所述第二UE的关联关系信息；例如，RAN节点被CN下发了UE之间的关联关系，因此获知了UE之间是可以或者需要进行协作传输(或聚合/备份/切换传输)；
(2)所述RAN节点作为所述第一UE的服务节点，确定具有关联关系的第一UE和第二UE处于连接态；例如，RAN节点作为UE的服务节点，当发现具有绑定关系的两个或者更多UE进入了连接态，具备建立协作/聚合/备份/切换传输的可行性；
(3)所述RAN节点作为所述第一UE的服务节点，确定所述第一UE的至少部分业务传输无法满足QoS需求或业务体验需求；所述RAN节点对所述第二UE进行寻呼，确定所述第二UE进入连接态；例如，RAN节点作为P-UE的服务节点，如果发现P-UE的一个或多个业务传输，无法满足QoS需求或者业务体验需求，可以主动的在所述RAN节点覆盖的范围内，进行对应S-UE的寻呼，使S-UE进入连接态，为P-UE进行协作/聚合/备份/切换传输；
(4)所述第一UE当前的至少部分业务具有支持多UE传输的特征。例如，-P-UE当前的业务，具有支持协作/聚合/备份/切换传输的特征。
在一个可能的实现方式中，为了确保第一UE与第二UE之间的通信，在所述RAN节点确定满足预定条件之后，向第一UE发送第一配置信息之前，所述方法还可以包括：所述RAN节点确定所述第一UE与所述第二UE之间的传输距离和/或链路情况满足多UE传输需求。例如，RAN节点可以根据定位或者归属小区等信息判断，也可以向第一UE进行问询得到所述第一UE与所述第二UE之间的传输距离和/或链路情况。
在满足上述前提之后，RAN可以确定以下至少之一：第一UE和第二 UE之间有CN许可的关联关系、第一UE和第二UE位于同一个基站下，可以进行彼此通信、第一UE的业务具有建立多UE架构承载的特征。因此，RAN节点可以发起建立多UE架构的流程。例如，可以包括以下步骤：
步骤1、RAN节点向第二UE发送重配置消息，其中携带第二配置信息。
可选地，第二配置信息中可以包括：第一UE标识、和分叉承载(split bearer)的配置等，使得第二可以UE判断是否同意为该第一UE进行多UE协作传输架构的建立；
可选地，第二配置信息中还可以包括第二DRB标识，用于指示所述第二UE为所述第一UE进行多UE协作传输的业务承载，通过第二DRB标识，第二UE可以判断是否同意为第一UE的指定DRB(即与第二DRB标识对应的DRB)进行多UE协作传输。
步骤2，如果第二UE同意，则按照接收到的重配置消息指示完成配置，并向网络侧(即RAN节点)返回配置完成消息；
如果第二UE不同意，则流程结束。
步骤3，RAN节点向第一UE发送重配置消息，其中携带第一配置信息；
可选地，所述第一配置信息可以包括：第二UE标识、和承载架构信息及相关配置，便于第一UE获知是与第二UE建立了多UE传输架构，并按照接收到的重配置消息指示完成配置；
可选地，第一配置信息中还可以携带第三DRB-ID，用于指示为所述第一UE配置的多UE协作传输的业务承载。
步骤4，第一UE向网络侧返回配置完成消息。
之后，第一UE可以将(指定DRB ID)的数据包向第二UE进行发送，由第二UE向网络侧进行传输，下行传输也是类似的。
需要说明是的是，上述第二DRB ID和第三DRB ID的作用是使第二UE和第一UE获取分叉承载的关联关系：例如，对于某个DRB承载(承载标识为DRB ID 1)，其分裂出位于第一UE的区域设置标识符(LCID)1以及位 于第二UE的LCID 2，则RAN节点在配置第一配置信息和第二配置信息时，可以通过以下方式配置关联：
(1)给第一UE的配置为DRB ID 1分裂到第一UE的LCID1和第二UE的LCID2(即第三DRB标识)，给第二UE配置LCID 2(即第二DRB标识)，第一UE和第二UE之间通过LCID2可以获知数据流都关联到DRB1上的；
(2)给第一UE配置DRB ID1关联第一UE的LCID(即第三DRB标识)1，给第二UE配置LCID2关联第一UE的DRB ID 1(即第二DRB标识)，第一UE和第二UE之间通过DRB ID 1，可以获知两个数据流都关联到同一个DRB1上。
在该可能的实现方式中，RAN节点也可以向第一UE询问是否进行多UE架构的建立，或者，向第一UE询问是否进行特定业务的多UE架构的建立，在接收到第一UE返回的肯定回答后，执行S210。例如，RAN节点可以在确定满足所述第一条件后，向第一UE进行询问。
其中，RAN节点还需要问询第二UE是否同意进行多UE架构或者基于特定业务的多UE架构的建立，待同意之后进行多UE架构或者特定业务多UE架构的配置，即进行多UE协作传输的承载配置。
通过该可能的实现方式，RAN节点可以在满足第一条件时，进行多UE协作传输的承载的配置或特定业务的多UE协作传输的承载的配置，从而可以实现多UE协作传输。
(三)第一UE请求
在该可能的实现方式中，在S210之前，该方法还可以包括：接收所述第一UE发送的第一请求，其中，所述第一请求用于请求所述第一配置信息，所述第一请求中携带有第二UE的标识。通过第一请求，第一UE向RAN节点请求与第二UE进行协作传输(或称为聚合传输、备份传输、切换传输)。
可选地，该第一请求中还可以携带第二业务识别信息，用于指示所述第一UE期望进行多UE协作传输的业务信息。
例如，所述第二业务识别信息包括但不限于以下至少之一：
(1)第一无线数据承载(DRB)标识；所述第一DRB标识可以为当前第一UE已经建立的数据无线承载的标识；
(2)服务标识(Service ID)；所述服务标识可以为当前第一UE正在传输或者后续将要传输的业务标识；
(3)QoS流标识(QoS flow ID)；所述QoS流标识可以为当前第一UE正在传输或者后续将要传输的QoS流标识。
(4)业务的特征信息。例如，QoS参数值等于某个值，或者位于一定的区间等，通过该特征信息，可以确定第一UE期望进行多UE协议传输的业务。
在一个可能的实现方式中，在接收第一UE发送的第一请求后，所述RAN节点向所述第二UE发送第二配置信息，其中，所述第二配置信息用于指示所述第二UE为所述第一UE进行多UE协作传输的承载配置。
其中，第二配置信息与上述可能实现方式中的第二配置信息相同，具体可以参见上述实现方式中的相关描述，在此不再赘述。
在一个可能的实现方式中，在所述RAN节点向所述第二UE发送第二配置信息之后，如果RAN节点接收所述第二UE发送的配置完成消息，则表明第二UE同意为所述第一UE进行多UE协作传输，则RAN节点向所述第一UE发送重配置消息，其中，所述重配置消息中携带所述第一配置信息。
其中，第一配置信息与上述可能实现方式中的第一配置信息相同，具体可以参见上述实现方式中的相关描述，在此不再赘述。
在具体应用中，在建立上述多UE协作传输之后，由于某种原因，例如，第一UE的业务传输发生变化、或者第二UE的业务传输发生变化、或者RAN节点的负荷等发生变化，需要修改或释放多UE协作传输的承载，因此，在建立上述多UE协作传输的承载之后，还可以需要修改或释放该承载。
因此，在一个可能的实现方式中，在S210之后，该方法还可以包括：
步骤1，所述RAN节点向所述第二UE发送第一重配置命令，其中，所述第一重配置信令中携带有所述第一UE的标识、重配置的第一承载标识以及重配置的内容信息，所述第一承载标识对应的承载为所述多UE协作传输的承载；
步骤2，所述RAN节点向所述第一UE发送第二重配置命令，其中，所述第二重配置信令中携带有所述第二UE的标识、所述第一承载标识以及所述重配置的内容信息。
需要说明的是，上述步骤1和步骤2在执行顺序上没有严格的顺序，RAN节点可以先向第二UE发送第一重配置命令，再向第一UE发送第二重配置命令，也可以先第一UE发送第二重配置命令，再向第二UE发送第一重配置命令，具体本申请实施例不作限定。例如，作为一种可选的方案，RAN节点可以在接收到第二UE发送的重配置完成消息之后，再向第一UE发送所述第二重配置命令。
可选地，在所述RAN节点向所述第一UE发送第二重配置命令之后，所述RAN节点还可以接收第一UE发送的重配置完成消息，从而使得RAN节点可以获知第一UE完成重配置。
在另一个可能的实现方式中，在S210之后，该方法还可以包括：
步骤1，所述RAN节点向所述第二UE发送第一释放命令，其中，所述第一释放命令中携带有所述第一UE的标识、释放的第二承载标识以及释放的内容信息，所述第二承载标识对应的承载为所述多UE协作传输的承载；
步骤2，所述RAN节点向所述第一UE发送第二释放命令，其中，所述第二释放命令中携带有所述第二UE的标识、所述第二承载标识以及释放的内容信息。
需要说明的是，上述步骤1和步骤2在执行顺序上没有严格的顺序，RAN节点可以先向第二UE发送第一释放命令，再向第一UE发送第二释放命令，也可以先第一UE发送第二释放命令，再向第二UE发送第一释放命令，具 体本申请实施例不作限定。例如，作为一种可选的方案，RAN节点可以在接收到第二UE发送的释放完成消息之后，再向第一UE发送所述第二释放命令。
可选地，在所述RAN节点向所述第一UE发送第二释放命令之后，所述RAN节点还可以接收第一UE发送的释放完成消息，从而使得RAN节点可以获知第一UE完成释放。
由于多UE架构是在RAN节点、第一UE以及第二UE之间建立的联合传输架构，因此RAN节点、第一UE以及第二UE都有可能对该联合传输架构(即上述的多UE架构，或多UE传输架构，或多UE协作传输架构)提出修改。例如，第一UE或者第二UE可以向网络进行请求，当网络同意之后，来执行修改的流程。
因此，在一个可能的实现方式中，在所述RAN节点向所述第二UE发送第一重配置命令之前，所述方法还包括：接收所述第一UE或所述第二UE发送的修改请求，其中，所述修改请求用于请求修改所述第一承载标识对应的承载。
或者，在所述RAN节点向所述第二UE发送第一释放命令之前，所述方法还包括：接收所述第一UE或所述第二UE发送的释放请求，其中，所述释放请求用于请求释放所述第二承载标识对应的承载。
当然，并不限于此，RAN节点作为集中控制实体，具有直接的决策权，例如当RAN节点负荷较高，不能支持这种多UE传输架构时，则RAN节点可以修改一部分或者全部的多UE协作传输的承载。再例如当UE的业务结束时，RAN节点可以直接释放多UE协作传输的承载。
在多UE架构承载完成了修改或者释放，后续不再使用，或者使用新的配置进行传输。
图4示出本申请实施例提供的多UE协作传输的配置方法的一种流程图，该方法400可以由核心网设备执行。换言之，所述方法可以由安装在核心网 设备上的软件或硬件来执行。如图4所示，该方法可以包括以下步骤。
S410，核心网设备向RAN节点发送关联关系信息，其中，所述关联关系信息用于指示第一UE与第二UE具有关联关系，所述第一UE和所述第二UE具有建立多UE协作传输的能力。
本申请实施例提供的方法400是与方法200对应的核心网侧的执行流程，具有与方法200涉及核心网设备相关的可能实现方式的对应实现方式，具体可以参见方法200的描述，下面只能涉及核心网设备的步骤的可能实现方式进行说明。
在一个可能的实现方式中，在核心网设备向RAN节点发送关联关系信息之前，所述方法还包括以下至少之一：
(1)所述核心网设备获知所述第一UE和所述第二UE均处于连接态；
(2)所述核心网设备发现所述第一UE进入连接态，其中，所述第一UE与所述第二UE基于任意业务均具有关联关系；
(3)所述核心网设备发现所述第一UE进入连接态且发起第一业务之后，其中，所述第一UE与所述第二UE基于目标业务具有关联关系，所述目标业务包括所述第一业务；
(4)接收到所述RAN节点发送的第二请求，所述第二请求用于请求所述第一UE所关联的所有UE，或者，所述第二请求用于请求基于第二业务与所述第一UE具有关联关系的UE。
可选地，核心网设备向RAN节点发送的关联关系信息可以包括以下至少之一：
(1)具有关联关系的UE标识列表，其中，所述UE标识列表中包括所述第一UE的标识和所述第二UE的标识；
(2)第一业务识别信息，其中，所述第一业务识别信息用于指示能够执行多UE协作传输的业务；例如，第一业务识别信息可以包括DRB ID、Service ID、QoS flow ID或者业务的特征信息等。
(3)具有关联关系的UE标识列表中指示的各个UE的属性。
在一个可能的实现方式中，在核心网设备向RAN节点发送关联关系信息之前，所述方法还包括：所述核心网设备获取所述第一UE签约的关联关系信息或所述第一UE预先设置的关联关系信息。
例如，签约或预先设置的关联关系信息可以包括以下之一：
(1)一组具有绑定关系的UE列表，列表中的UE彼此之间可以互相协作传输，每个UE根据需要决定作为P-UE或者S-UE；
(2)一组具有绑定关系的UE列表，其中每个UE的属性P-UE还是S-UE是提前预设的；
(3)一组具有绑定关系的UE列表，其中每个UE可以支持的属性，例如P-UE only，S-UE only或者both P-UE and S-UE是设定的。
其中，上述绑定关系可以是基于UE粒度，即这些UE之间的任何业务都可以进行多UE架构建立和传输，也可以进一步基于特定业务的粒度，即在UE列表的基础上，限制这些UE之间，只能针对什么样的业务进行多UE架构建立和传输，其中业务限制可以是业务标识，业务的具体QoS参数，业务的具体QoS参数的范围等。
通过本申请实施例提供的技术方案，核心网设备可以触发RAN节点进行多UE协作传输的承载配置，从而使得第一UE与第二UE之间可以进行多UE协作传输，保障了UE的业务体验和系统效率。
图5示出本申请实施例提供的多UE协作传输的配置方法的一种流程图，该方法500可以由第一UE执行。换言之，所述方法可以由安装在第一UE上的软件或硬件来执行。如图5所示，该方法可以包括以下步骤。
S510，第一UE向RAN节点发送第一请求，其中，所述第一请求用于请求所述RAN节点为所述第一UE配置多UE协作传输的承载，所述第一请求中携带有第二UE的标识。
本申请实施例提供的方法500是与方法200对应的第一UE的执行流程， 具有与方法200涉及第一UE相关的可能实现方式的对应实现方式，具体可以参见方法200的描述，下面只能涉及第一UE执行的步骤的可能实现方式进行说明。
在一个可能的实现方式中，在第一UE向RAN节点发送第一请求之前，所述方法还可以包括：
步骤1，所述第一UE通过UE之间的接口，发送第三请求，其中，所述第三请求用于请求为所述第一UE进行聚合传输；
步骤2，所述第一UE接收所述第二UE反馈的确认消息，其中，所述确认消息中携带的所述第二UE的标识。
通过该可能的实现方式，第一UE可以与第二UE进行交互，获取第二UE的标识。
在一个可能的实现方式中，第一UE发送的所述第一请求中还携带有第二业务识别信息，所述第二业务识别信息用于指示所述第一UE期望进行多UE协作传输的业务信息。
可选地，所述第二业务识别信息包括但不限于以下至少之一：
(1)第一DRB标识；
(2)服务标识；
(3)QoS流标识；
(4)业务的特征信息。
在一个可能的实现方式中，在第一UE向RAN节点发送第一请求之后，所述方法还可以包括：
步骤1，所述第一UE接收所述RAN节点发送的重配置消息，其中，所述重配置消息中携带第一配置信息，所述第一配置信息用于为所述第一UE配置多UE协作传输的承载；
步骤2，所述第一UE应用所述第一配置信息进行重配置。
例如，RAN节点可以在接收到第一请求之后，根据第一请求，对第二 UE进行重配置完成之后，向第一UE发送上述重配置消息，为第一UE配置多UE传输架构的承载。
可选地，所述第一配置信息包括：所述第二UE标识、以及承载架构的配置信息。
可选地，所述第一配置信息还包括：第三DRB标识，用于指示为所述第一UE配置的多UE协作传输的业务承载。
在一个可能的实现方式，在所述第一UE接收所述RAN节点发送的重配置消息之后，所述方法还包括：
步骤1，接收所述RAN节点发送的第二重配置命令，其中，所述第二重配置信令中携带有所述第二UE的标识、重配置的第一承载标识以及所述重配置的内容信息，所述第一承载标识对应的承载为所述多UE协作传输的承载；
步骤2，执行所述第二重配置命令。
例如，RAN节点可以在当前网络状态不能支持一个或多个多UE协作传输时，发送所述第二重配置命令，对多UE协作传输承载进行修改。
或者，也可以是第一UE请求RAN节点对多UE协作传输进行修改，因此，在一个可能的实现方式中，在接收所述RAN节点发送的第二重配置命令之前，所述方法还可以包括：向所述RAN节点发送修改请求，其中，所述修改请求用于请求修改所述第一承载标识对应的承载。
在另一个可能的实现方式中，在所述第一UE接收所述RAN节点发送的重配置消息之后，所述方法还包括：
步骤1，接收所述RAN节点发送的第二释放命令，其中，所述第二释放命令中携带有所述第二UE的标识、释放的第二承载标识以及释放的内容信息，所述第二承载标识对应的承载为所述多UE协作传输的承载；
步骤2，执行所述第二释放命令，释放所述第二承载标识对应的承载。
例如，RAN节点可以在完成第一UE需要协作传输的业务之后，发送所 述第二释放命令。
或者，RAN节点也可以是基于第一UE的请求，发送所述第二释放命令，因此，在一个可选的实现方式中，在接收所述RAN节点发送的第二释放命令之前，所述方法还可以包括：向所述RAN节点发送释放请求，其中，所述释放请求用于请求释放所述第二承载标识对应的承载。
通过本申请实施例提供的技术方案，第一UE可以在需要时，请求RAN节点进行多UE协作传输的承载配置，从而使得第一UE与第二UE之间可以进行多UE协作传输，保障了UE的业务体验和系统效率。
图6示出本申请实施例提供的多UE协作传输的响应方法的一种流程图，该方法600可以由第二UE执行。换言之，所述方法可以由安装在第二UE上的软件或硬件来执行。如图6所示，该方法可以包括以下步骤。
S610，第二UE接收RAN节点发送的第二配置信息，其中，所述第二配置信息用于指示所述第二UE为第一UE进行多UE协作传输的承载配置。
S612，在同意为所述第一UE进行多UE协作传输的情况下，所述第二UE应用所述第二配置信息，向所述RAN节点发送配置完成消息。
本申请实施例提供的方法600是与方法200对应的第二UE的执行流程，具有与方法200涉及第二UE相关的可能实现方式的对应实现方式，具体可以参见方法200的描述，下面只能涉及第二UE执行的步骤的可能实现方式进行说明。
在一个可能的实现方式中，所述第二配置信息包括：所述第一UE的标识、以及分叉承载的配置信息。
在一个可能的实现方式中，所述第二配置信息还包括：第二DRB标识，用于指示所述第二UE为所述第一UE进行多UE协作传输的业务承载。
在一个可能的实现方式中，在第二UE接收RAN节点发送的第二配置信息之前，所述方法还包括：
步骤1，所述第二UE接收所述第一UE发送的第三请求，其中，所述第 三请求用于请求为所述第一UE进行聚合传输；
步骤2，所述第二UE向所述第一UE反馈确认消息，其中，所述确认消息中携带所述第二UE的标识。
在一个可能的实现方式中，在向所述RAN节点发送配置完成消息之后，所述方法还包括：
步骤1，接收所述RAN节点发送的第一重配置命令，其中，所述第一重配置信令中携带有所述第一UE的标识、重配置的第一承载标识以及所述重配置的内容信息，所述第一承载标识对应的承载为所述多UE协作传输的承载；
步骤2，执行所述第一重配置命令。
例如，RAN节点可以在业务传输或网络环境发生改变是，发送所述第一重配置命令，对多UE协作传输的承载进行修改。
或者，RAN节点也可以基于第二UE的请求，对多UE协作传输的承载进行修改，例如，第二UE本身的业务传输增加或减少，为第一UE协作传输的能力减少或增加，需要对多UE协作传输的承载进行修改，则可以向RAN节点发起请求。因此，在一个可能的实现方式中，在接收所述RAN节点发送的第一重配置命令之前，所述方法还包括：向所述RAN节点发送修改请求，其中，所述修改请求用于请求修改所述第一承载标识对应的承载。
在一个可能的实现方式，在向所述RAN节点发送配置完成消息之后，所述方法还包括：
步骤1，接收所述RAN节点发送的第一释放命令，其中，所述第一释放命令中携带有所述第一UE的标识、释放的第二承载标识以及释放的内容信息，所述第二承载标识对应的承载为所述多UE协作传输的承载；
步骤2，执行所述第一释放命令，释放所述第二承载标识对应的承载。
例如，RAN节点可以在第一UE请求协作传输的业务完成后，发送所述第一释放命令。
或者，RAN节点也可以基于第二UE的请求，对多UE协作传输的承载进行修改，例如，第二UE本身的业务传输增加，无法为第一UE进行协作传输，需要对多UE协作传输的承载进行释放，则可以向RAN节点发起请求。因此，在一个可能的实现方式中，在接收所述RAN节点发送的第一释放命令之前，所述方法还包括：向所述RAN节点发送释放请求，其中，所述释放请求用于请求释放所述第二承载标识对应的承载。
通过本申请实施例提供的技术方案，第二UE可以响应RAN节点进行多UE协作传输的承载配置，从而建立多UE协作传输承载，使得第一UE与第二UE之间可以进行多UE协作传输，保障了UE的业务体验和系统效率。
下面以第一UE(即主UE，P-UE)请求为例，对本申请实施例提供的技术方案进行说明。
图7示出本申请实施例提供的多UE协作传输的承载建立方法的一种流程示意图，如图7所示，该方法主要包括以下步骤。
S701，P-UE即有业务需要传输的UE，通过UE之间的接口，向自己周围的其它S-UE进行请求，例如，发送聚合(Aggregation)传输请求(reques)t，还可以为备份传输请求、切换传输请求等。通过该请求向S-UE请求一下是否能够为自己进行聚合传输。
其中，在该请求中，可以携带如下信息其中至少一种或者组合：
(1)P-UE的用户标识，该用户标识是为了识别P-UE，一方面是为了确认意愿和授信，另一个重要方面就是便于gNB对两个UE进行后续过程的标识和识别，标识可以是全球唯一标识、PLMN内唯一标识、服务基站/小区下的标识等，例如S-TMSI，C-RNTI等。
(2)P-UE自己的服务基站，携带服务基站的作用是为了将多UE架构尽量在一个基站下进行实现，避免因此引入基站之间的接口，复杂度和时延会高很多。
S702，S-UE向对应的服务基站发起RRC连接建立过程，并进行激活自 己的安全模式指令(Security Mode Command，SMC)的过程。
其中，如果S-UE当前如果处于RRC Connected状态，则该步骤可以省略。通过该步骤，可以获取一个gNB可以识别的S-UE的UE标识，该标识可以是全球唯一标识、PLMN内唯一标识，服务基站/小区下的标识等，例如S-TMSI，C-RNTI等、
S703，S-UE如果同意为P-UE进行聚合/备份/切换传输，则可以向P-UE回复确认，并告知自己的UE标识。
S704，P-UE在获得S-UE同意或者获得其UE标识之后，向自己的服务基站上报请求进行多UE架构配置，并携带S-UE的UE标识，表明P-UE与指定的S-UE进行聚合/备份/切换传输。
其中，S704可以在省略S701-S703的情况下直接发起，只要P-UE和S-UE之间交互过，具有S-UE的用户标识即可。
S705，基站在接收到P-UE的请求之后，生成对应的配置，发送给指定的S-UE。
通过S705，可以征求S-UE的同意看其是否愿意为P-UE进行聚合/备份/切换传输。其中，基站发送给S-UE的配置信息中携带P-UE标识，指示配置的多UE架构的P-UE，便于S-UE进行当下的意愿判断以及后续的协同操作。
S706，S-UE同意之后，执行配置，并向gNB返回确认。
S707，gNB向P-UE进行多架构确认操作，可选的，gNB向P-UE发送的消息中还可以携带多UE架构的对应配置。
在上述的流程中，给出了P-UE和S-UE建立多UE架构的请求和相关信令流程的示意举例，因为在上述过程中没有指示任何的业务信息，只是针对两个UE进行了许可和配置，则可以理解这两个UE之间此时是可以建立任何的聚合/备份/切换的承载的。例如，可以将P-UE的所有承载，都配置成多UE架构传输；或者，可以由基站算法来决定，根据业务QoS等，对需要的P-UE的承载，进行多UE架构传输配置；又或者，可以由基站根据核心网下 发的绑定信息，对许可的P-UE的承载，进行多UE架构传输配置。
图8示出本申请实施例提供的多UE协作传输的承载建立方法的另一流程示意图，如图8所示，该方法主要包括以下步骤。
S801，P-UE向网络发送多UE架构请求，该请求中可以携带S-UE的用户标识以及携带期望进行多UE架构传输的业务信息。
其中，该业务信息可以包括以下至少之一：
(1)DRB ID，当前P-UE已经建立的数据无线承载的标识；
(2)Service ID或者QoS flow ID，当前P-UE正在传输或者后续将要传输的业务标识，QoS流标识等；
(3)业务的特征，例如QoS参数值等于某个值，或者位于一定的区间等。
在S801之前，还可以执行方法700中的S701-S703。方法800与方法700的区别在于，方法800是基于特定业务进行多播架构建立的流程。
S802，基站向S-UE发送重配置信息，用于配置多UE架构相关的承载。
其中，基站向S-UE发送的重配置信息可以携带如下信息：
(1)P-UE的用户标识，便于S-UE对P-UE进行识别，是否愿意为其建立聚合/备份/切换承载，以及如果愿意则后续为协同工作时，互相标识；
(2)DRB ID，基站明确指明，为哪个承载进行聚合/备份/切换配置；
(3)RLC、MAC、物理层(Physical Layer，PHY)、LCID等信息，通过这些信息可以对为了聚合/备份/切换承载进行的S-UE侧的配置。
S803，S-UE如果同意，则按照配置进行准备，且向基站回复配置完成.
S804，基站向P-UE返回承载重配置确认，确定为请求的或者指定的承载DRB ID已经配置了相应的聚合/备份/切换的多UE架构配置.
后续，P-UE就可以将自己的该DRB ID的数据交给S-UE，由S-UE向gNB进行发送。
在上述方法700中所提到的聚合/备份/切换的多UE架构配置，主要指图 3a所示的PDCP anchor架构、图3b所示的RLC anchor架构、以及图3c所示MAC anchor架构中的一个或多个。
当然除了上述举例的架构之外，也不排除将某一层，例如PDCP或者MAC的部分common function位于P-UE，而将split function位于S-UE，这样的架构也是可以工作的。
协议可能选定一种或者多种架构，如果仅选择了一种架构，则网络侧默认进行该架构相关的协议实体的配置即可。如果选择了两种或者以上的架构，则网络侧可以按需进行不同架构的选择和配置。
通过本申请实施例提供的上述方法，RAN侧可以对多个UE进行配置，使得UE在网络侧的控制之下能够多设备共同传输，保障了UE的业务体验和系统效率。
需要说明的是，本申请实施例提供的承载的配置方法，执行主体可以为承载的配置装置，或者，该承载的配置装置中的用于执承载的配置方法的控制模块。本申请实施例中以承载的配置装置执行承载的配置方法为例，说明本申请实施例提供的承载的配置装置。
图9示出本申请实施例提供的承载的配置装置的一种结构示意图，如图9所示，该装置900主要包括：第一获取模块901和第一收发模块902。
在本申请实施例中，第一获取模块901，用于获取第一UE的第一配置信息，其中，所述第一配置信息用于配置多UE协作传输的承载；第一收发模块902，用于向所述第一UE发送所述第一配置信息。
在一个可能的实现方式中，第一收发模块902还用于在向第一UE发送第一配置信息之前，接收核心网下发的关联关系信息，其中，所述关联关系信息用于指示所述第一UE与第二UE之间的关联关系。
在一个可能的实现方式中，所述关联关系信息包括以下至少之一：
具有关联关系的UE标识列表，其中，所述UE标识列表中包括所述第一UE的标识和所述第二UE的标识；
第一业务识别信息，其中，所述第一业务识别信息用于指示能够执行多UE协作传输的业务；
具有关联关系的UE标识列表中的各个UE的属性。
在一个可能的实现方式中，所述第一获取模块901还用于确定满足第一条件。
在一个可能的实现方式中，所述第一条件包括以下至少之一：
从核心网获取到所述第一UE与所述第二UE的关联关系信息；
作为所述第一UE的服务节点，确定具有关联关系的第一UE和第二UE处于连接态；
作为所述第一UE的服务节点，确定所述第一UE的至少部分业务传输无法满足服务质量QoS需求或业务体验需求；所述RAN节点对所述第二UE进行寻呼，确定所述第二UE进入连接态；
所述第一UE当前的至少部分业务具有支持多UE传输的特征。
在一个可能的实现方式中，第一获取模块901还用于在向第一UE发送第一配置信息之前，确定所述第一UE与所述第二UE之间的传输距离和/或链路情况满足多UE传输需求。
在一个可能的实现方式中，第一收发模块902还用于在向第一UE发送第一配置信息之前，向所述第二UE发送第二配置信息，其中，所述第二配置信息用于指示所述第二UE为所述第一UE进行多UE协作传输的承载配置；接收所述第二UE发送的配置完成消息。
在一个可能的实现方式中，第一收发模块902还用于在向第一UE发送第一配置信息之前，接收所述第一UE发送的第一请求，其中，所述第一请求用于请求所述第一配置信息，所述第一请求中携带有第二UE的标识。
在一个可能的实现方式中，所述第一请求中还携带有第二业务识别信息，用于指示所述第一UE期望进行多UE协作传输的业务信息。
在一个可能的实现方式中，所述第二业务识别信息包括以下至少之一：
第一无线数据承载DRB标识；
服务标识；
QoS流标识；
业务的特征信息。
在一个可能的实现方式中，第一收发模块902还用于在接收所述第一UE发送的第一请求之后，向所述第二UE发送第二配置信息，其中，所述第二配置信息用于指示所述第二UE为所述第一UE进行多UE协作传输的承载配置。
在一个可能的实现方式中，所述第二配置信息包括：所述第一UE的标识、以及分叉承载的配置信息。
在一个可能的实现方式中，所述第二配置信息还包括：第二DRB标识，用于指示所述第二UE为所述第一UE进行多UE协作传输的业务承载。
在一个可能的实现方式中，第一收发模块902还用于在向所述第二UE发送第二配置信息之后，接收所述第二UE发送的配置完成消息；向所述第一UE发送重配置消息，其中，所述重配置消息中携带所述第一配置信息。
在一个可能的实现方式中，所述第一配置信息包括：
所述第二UE的标识、以及承载架构的配置信息。
在一个可能的实现方式中，所述第一配置信息还包括：第三DRB标识，用于指示为所述第一UE配置的多UE协作传输的业务承载。
在一个可能的实现方式中，第一收发模块902还用于在向第一用户设备UE发送第一配置信息之后，向所述第二UE发送第一重配置命令，其中，所述第一重配置信令中携带有所述第一UE的标识、重配置的第一承载标识以及重配置的内容信息，所述第一承载标识对应的承载为所述多UE协作传输的承载；向所述第一UE发送第二重配置命令，其中，所述第二重配置信令中携带有所述第二UE的标识、所述第一承载标识以及所述重配置的内容信息。
在一个可能的实现方式中，第一收发模块902还用于在向所述第二UE发送第一重配置命令之前，接收所述第一UE或所述第二UE发送的修改请求，其中，所述修改请求用于请求修改所述第一承载标识对应的承载。
在一个可能的实现方式中，第一收发模块902还用于在向第一用户设备UE发送第一配置信息之后，向所述第二UE发送第一释放命令，其中，所述第一释放命令中携带有所述第一UE的标识、释放的第二承载标识以及释放的内容信息，所述第二承载标识对应的承载为所述多UE协作传输的承载；向所述第一UE发送第二释放命令，其中，所述第二释放命令中携带有所述第二UE的标识、所述第二承载标识以及释放的内容信息。
在一个可能的实现方式中，第一收发模块902还用于在向所述第二UE发送第一释放命令之前，接收所述第一UE或所述第二UE发送的释放请求，其中，所述释放请求用于请求释放所述第二承载标识对应的承载。
本申请实施例中的承载的配置装置可以是装置，也可以是网络侧设备中的部件、集成电路、或芯片。该装置可以是基站，也可以是CU，本申请实施例不作具体限定。
本申请实施例中的承载的配置装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的承载的配置装置能够实现图2至图8的方法实施例中RAN节点实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
图10示出本申请实施例提供的多UE协作传输的配置装置的一种结构示意图，如图10所示，该装置主要包括：第二获取模块1001和第二收发模块1002。
基本申请实施例中，第二获取模块1001，用于获取关联关系信息，其中，所述关联关系信息用于指示第一UE与第二UE具有关联关系，所述第一UE 和所述第二UE具有建立多UE协作传输的能力；第二收发模块1002，用于向RAN节点发送所述关联关系。
在一个可能的实现方式中，第二收发模块1002还用于在向RAN节点发送关联关系信息之前，执行以下至少之一：
获知所述第一UE和所述第二UE均处于连接态；
发现所述第一UE进入连接态，其中，所述第一UE与所述第二UE基于任意业务均具有关联关系；
发现所述第一UE进入连接态且发起第一业务之后，其中，所述第一UE与所述第二UE基于目标业务具有关联关系，所述目标业务包括所述第一业务；
接收到所述RAN节点发送的第二请求，所述第二请求用于请求所述第一UE所关联的所有UE，或者，所述第二请求用于请求基于第二业务与所述第一UE具有关联关系的UE。
在一个可能的实现方式中，所述关联关系信息包括以下至少之一：
具有关联关系的UE标识列表，其中，所述UE标识列表中包括所述第一UE的标识和所述第二UE的标识；
第一业务识别信息，其中，所述第一业务识别信息用于指示能够执行多UE协作传输的业务；
具有关联关系的UE标识列表中指示的各个UE的属性。
在一个可能的实现方式中，第二获取模块1001还用于在向RAN节点发送关联关系信息之前，获取所述第一UE签约的关联关系信息或所述第一UE预先设置的关联关系信息。
本申请实施例中的多UE协作传输的配置装置可以是装置，也可以是网络侧设备中的部件、集成电路、或芯片。该装置可以是基站，也可以是CU，本申请实施例不作具体限定。
本申请实施例中的多UE协作传输的配置装置可以为具有操作系统的装 置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的多UE协作传输的配置装置能够实现图2至图8的方法实施例中核心网设备或核心网实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
图11示出本申请实施例提供的多UE协作传输的请求装置的一种结构示意图，如图11所示，该装置1100主要包括：第一确定模块1101和第三收发模块1102。
在本申请实施例中，第一确定模块1101，用于确定第一UE需要执行多UE协作传输；第三收发模块1102，用于向RAN节点发送第一请求，其中，所述第一请求用于请求所述RAN节点为所述第一UE配置多UE协作传输的承载，所述第一请求中携带有第二UE的标识。
在一个可能的实现方式中，第三收发模块1102还用于在向RAN节点发送第一请求之前，通过UE之间的接口，发送第三请求，其中，所述第三请求用于请求为所述第一UE进行聚合传输；接收所述第二UE反馈的确认消息，其中，所述确认消息中携带的所述第二UE的标识。
在一个可能的实现方式中，第三收发模块1102还用于在向RAN节点发送第一请求之后，接收所述RAN节点发送的重配置消息，其中，所述重配置消息中携带第一配置信息，所述第一配置信息用于为所述第一UE配置多UE协作传输的承载；应用所述第一配置信息进行重配置。
在一个可能的实现方式中，所述第一配置信息包括：所述第二UE标识、以及承载架构的配置信息。
在一个可能的实现方式中，所述第一配置信息还包括：第三DRB标识，用于指示为所述第一UE配置的多UE协作传输的业务承载。
在一个可能的实现方式中，第三收发模块1102还用于在接收所述RAN节点发送的重配置消息之后，接收所述RAN节点发送的第二重配置命令， 其中，所述第二重配置信令中携带有所述第二UE的标识、重配置的第一承载标识以及所述重配置的内容信息，所述第一承载标识对应的承载为所述多UE协作传输的承载；执行所述第二重配置命令。
在一个可能的实现方式中，第三收发模块1102还用于在接收所述RAN节点发送的第二重配置命令之前，向所述RAN节点发送修改请求，其中，所述修改请求用于请求修改所述第一承载标识对应的承载。
在一个可能的实现方式中，第三收发模块1102还用于在接收所述RAN节点发送的重配置消息之后，接收所述RAN节点发送的第二释放命令，其中，所述第二释放命令中携带有所述第二UE的标识、释放的第二承载标识以及释放的内容信息，所述第二承载标识对应的承载为所述多UE协作传输的承载；执行所述第二释放命令，释放所述第二承载标识对应的承载。
在一个可能的实现方式中，第三收发模块1102还用于在接收所述RAN节点发送的第二释放命令之前，向所述RAN节点发送释放请求，其中，所述释放请求用于请求释放所述第二承载标识对应的承载。
在一个可能的实现方式中，所述第一请求中还携带有第二业务识别信息，所述第二业务识别信息用于指示所述第一UE期望进行多UE协作传输的业务信息。
在一个可能的实现方式中，所述第二业务识别信息包括以下至少之一：
第一无线数据承载DRB标识；
服务标识；
QoS流标识；
业务的特征信息。
本申请实施例中的多UE协作传输的请求装置可以是装置，也可以是终端设备中的部件、集成电路、或芯片。该装置可以是基站，也可以是CU，本申请实施例不作具体限定。
本申请实施例中的多UE协作传输的请求装置可以为具有操作系统的装 置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的多UE协作传输的请求装置能够实现图2至图8的方法实施例中第一UE实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
图12示出本申请实施例提供的多UE协作传输的响应装置的一种结构示意图，如图12所示，该装置1200主要包括：第四收发模块1201和第二确定模块1202。
在本申请实施例中，第四收发模块1201，用于接收RAN节点发送的第二配置信息，其中，所述第二配置信息用于指示所述第二UE为第一UE进行多UE协作传输的承载配置；第二确定模块1202，用于确定是否同意为所述第一UE进行多UE协作传输；所述第四收发模块1201还用于在同意为所述第一UE进行多UE协作传输的情况下，所述第二UE应用所述第二配置信息，向所述RAN节点发送配置完成消息。
在一个可能的实现方式中，所述第二配置信息包括：所述第一UE的标识、以及分叉承载的配置信息。
在一个可能的实现方式中，所述第二配置信息还包括：第二DRB标识，用于指示所述第二UE为所述第一UE进行多UE协作传输的业务承载。
在一个可能的实现方式中，第四收发模块1201还用于在接收RAN节点发送的第二配置信息之前，接收所述第一UE发送的第三请求，其中，所述第三请求用于请求为所述第一UE进行聚合传输；向所述第一UE反馈确认消息，其中，所述确认消息中携带所述第二UE的标识。
在一个可能的实现方式中，第四收发模块1201还用于在向所述RAN节点发送配置完成消息之后，接收所述RAN节点发送的第一重配置命令，其中，所述第一重配置信令中携带有所述第一UE的标识、重配置的第一承载标识以及所述重配置的内容信息，所述第一承载标识对应的承载为所述多UE 协作传输的承载；执行所述第一重配置命令。
在一个可能的实现方式中，第四收发模块1201还用于在接收所述RAN节点发送的第一重配置命令之前，向所述RAN节点发送修改请求，其中，所述修改请求用于请求修改所述第一承载标识对应的承载。
在一个可能的实现方式中，第四收发模块1201还用于在向所述RAN节点发送配置完成消息之后，接收所述RAN节点发送的第一释放命令，其中，所述第一释放命令中携带有所述第一UE的标识、释放的第二承载标识以及释放的内容信息，所述第二承载标识对应的承载为所述多UE协作传输的承载；执行所述第一释放命令，释放所述第二承载标识对应的承载。
在一个可能的实现方式中，第四收发模块1201还用于在接收所述RAN节点发送的第一释放命令之前，向所述RAN节点发送释放请求，其中，所述释放请求用于请求释放所述第二承载标识对应的承载。
本申请实施例中的多UE协作传输的响应可以是装置，也可以是终端设备中的部件、集成电路、或芯片。该装置可以是基站，也可以是CU，本申请实施例不作具体限定。
本申请实施例中的多UE协作传输的响应可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的多UE协作传输的响应能够实现图2至图8的方法实施例中第二UE实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选的，如图13所示，本申请实施例还提供一种通信设备1300，包括处理器1301，存储器1302，存储在存储器1302上并可在所述处理器1301上运行的程序或指令，例如，该通信设备1300为终端时，该程序或指令被处理器1301执行时实现上述方法400实施例或方法500实施例的各个过程，且能达到相同的技术效果。该通信设备1300为网络侧设备时，该程序或指令被 处理器1301执行时实现上述方法200实施例或方法300实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，处理器用于实现上述方法400实施例或方法500实施例的各个过程，通信接口用于与外部设备进行通信。该终端实施例是与上述终端侧方法实施例对应的，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。具体地，图14为实现本申请实施例的一种终端的硬件结构示意图。
该终端1400包括但不限于：射频单元1401、网络模块1402、音频输出单元1403、输入单元1404、传感器1405、显示单元1406、用户输入单元1407、接口单元1408、存储器1409、以及处理器1410等部件。
本领域技术人员可以理解，终端1400还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器1410逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图14中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元1404可以包括图形处理器(Graphics Processing Unit，GPU)14041和麦克风14042，图形处理器14041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1406可包括显示面板14061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板14061。用户输入单元1407包括触控面板14071以及其他输入设备14072。触控面板14071，也称为触摸屏。触控面板14071可包括触摸检测装置和触摸控制器两个部分。其他输入设备14072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元1401将来自网络侧设备的下行数据接收后， 给处理器1410处理；另外，将上行的数据发送给网络侧设备。通常，射频单元1401包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器1409可用于存储软件程序或指令以及各种数据。存储器1409可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器1409可以包括高速随机存取存储器，还可以包括非瞬态性存储器，其中，非瞬态性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非瞬态性固态存储器件。
处理器1410可包括一个或多个处理单元；可选的，处理器1410可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1410中。
其中，射频单元1401，用于向RAN节点发送第一请求，其中，所述第一请求用于请求所述RAN节点为所述第一UE配置多UE协作传输的承载，所述第一请求中携带有第二UE的标识。
或者，射频单元1401，用于接收RAN节点发送的第二配置信息，其中，所述第二配置信息用于指示所述第二UE为第一UE进行多UE协作传输的承载配置；在同意为所述第一UE进行多UE协作传输的情况下，所述第二UE应用所述第二配置信息，向所述RAN节点发送配置完成消息。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，处理器用于实现上述方法200实施例或方法300实施例的各个过程，通信接口用于与外部设备进行通信。该网络侧设备实施例是与上述网络侧设备方法实施例 对应的，上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中，且能达到相同的技术效果。
具体地，本申请实施例还提供了一种网络侧设备。如图15所示，该网络设备1500包括：天线1501、射频装置1502、基带装置1503。天线1501与射频装置1502连接。在上行方向上，射频装置1502通过天线1501接收信息，将接收的信息发送给基带装置1503进行处理。在下行方向上，基带装置1503对要发送的信息进行处理，并发送给射频装置1502，射频装置1502对收到的信息进行处理后经过天线1501发送出去。
上述频带处理装置可以位于基带装置1503中，以上实施例中网络侧设备执行的方法可以在基带装置1503中实现，该基带装置1503包括处理器1504和存储器1505。
基带装置1503例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图15所示，其中一个芯片例如为处理器1504，与存储器1505连接，以调用存储器1505中的程序，执行以上方法实施例中所示的网络设备操作。
该基带装置1503还可以包括网络接口1506，用于与射频装置1502交互信息，该接口例如为通用公共无线接口(common public radio interface，简称CPRI)。
具体地，本申请实施例的网络侧设备还包括：存储在存储器1505上并可在处理器1504上运行的指令或程序，处理器1504调用存储器1505中的指令或程序执行图9或图10所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质可以是易失性的，也可以是非易失性的，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述方法200实施例的各个过程，或实现上述方法300实施例的各个过程，或实现上述方法400实施例的各个过程，或实现上述方法500实施例的各个过程，且能达到相同的技术效果，为避免重复， 这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述方法200实施例的各个过程，或实现上述方法300实施例的各个过程，或实现上述方法400实施例的各个过程，或实现上述方法500实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例还提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在非瞬态的存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述方法200实施例的各个过程，或实现上述方法300实施例的各个过程，或实现上述方法400实施例的各个过程，或实现上述方法500实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、 省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (50)

  1. 一种承载的配置方法，包括：
    无线接入网络RAN节点向第一用户设备UE发送第一配置信息，其中，所述第一配置信息用于配置多UE协作传输的承载。
  2. 根据权利要求1所述的方法，其中，在所述RAN节点向第一UE发送第一配置信息之前，所述方法还包括：
    所述RAN节点接收核心网下发的关联关系信息，其中，所述关联关系信息用于指示所述第一UE与第二UE之间的关联关系。
  3. 根据权利要求2所述的方法，其中，所述关联关系信息包括以下至少之一：
    具有关联关系的UE标识列表，其中，所述UE标识列表中包括所述第一UE的标识和所述第二UE的标识；
    第一业务识别信息，其中，所述第一业务识别信息用于指示能够执行多UE协作传输的业务；
    具有关联关系的UE标识列表中的各个UE的属性。
  4. 根据权利要求1所述的方法，其中，在所述RAN节点向第一UE发送第一配置信息之前，所述方法还包括：
    所述RAN节点确定满足第一条件。
  5. 根据权利要求4所述的方法，其中，所述第一条件包括以下至少之一：
    所述RAN节点从核心网获取到所述第一UE与所述第二UE的关联关系信息；
    所述RAN节点作为所述第一UE的服务节点，确定具有关联关系的第一UE和第二UE处于连接态；
    所述RAN节点作为所述第一UE的服务节点，确定所述第一UE的至少部分业务传输无法满足服务质量QoS需求或业务体验需求；所述RAN节点对所述第二UE进行寻呼，确定所述第二UE进入连接态；
    所述第一UE当前的至少部分业务具有支持多UE传输的特征。
  6. 根据权利要求4所述的方法，其中，在所述RAN节点确定满足预定条件之后，向第一UE发送第一配置信息之前，所述方法还包括：
    所述RAN节点确定所述第一UE与所述第二UE之间的传输距离和/或链路情况满足多UE传输需求。
  7. 根据权利要求1至6任一项所述的方法，其中，在所述RAN节点向第一UE发送第一配置信息之前，所述方法还包括：
    所述RAN节点向所述第二UE发送第二配置信息，其中，所述第二配置信息用于指示所述第二UE为所述第一UE进行多UE协作传输的承载配置；
    所述RAN节点接收所述第二UE发送的配置完成消息。
  8. 根据权利要求1所述的方法，其中，在所述RAN节点向第一UE发送第一配置信息之前，所述方法还包括：
    接收所述第一UE发送的第一请求，其中，所述第一请求用于请求所述第一配置信息，所述第一请求中携带有第二UE的标识。
  9. 根据权利要求8所述的方法，其中，所述第一请求中还携带有第二业务识别信息，用于指示所述第一UE期望进行多UE协作传输的业务信息。
  10. 根据权利要求9所述的方法，其中，所述第二业务识别信息包括以下至少之一：
    第一无线数据承载DRB标识；
    服务标识；
    QoS流标识；
    业务的特征信息。
  11. 根据权利要求8所述的方法，其中，在接收所述第一UE发送的第一请求之后，所述方法还包括：
    所述RAN节点向所述第二UE发送第二配置信息，其中，所述第二配置信息用于指示所述第二UE为所述第一UE进行多UE协作传输的承载配置。
  12. 根据权利要求7或11所述的方法，其中，所述第二配置信息包括：所述第一UE的标识、以及分叉承载的配置信息。
  13. 根据权利要求12所述的方法，其中，所述第二配置信息还包括：第二DRB标识，用于指示所述第二UE为所述第一UE进行多UE协作传输的业务承载。
  14. 根据权利要求11所述的方法，其中，在所述RAN节点向所述第二UE发送第二配置信息之后，所述方法还包括：
    所述RAN节点接收所述第二UE发送的配置完成消息；
    所述RAN节点向所述第一UE发送重配置消息，其中，所述重配置消息中携带所述第一配置信息。
  15. 根据权利要求2至14中任一项所述的方法，其中，所述第一配置信息包括：
    所述第二UE的标识、以及承载架构的配置信息。
  16. 根据权利要求15所述的方法，其中，所述第一配置信息还包括：第三DRB标识，用于指示为所述第一UE配置的多UE协作传输的业务承载。
  17. 根据权利要求2至14中任一项所述的方法，其中，在RAN节点向第一用户设备UE发送第一配置信息之后，所述方法还包括：
    所述RAN节点向所述第二UE发送第一重配置命令，其中，所述第一重配置信令中携带有所述第一UE的标识、重配置的第一承载标识以及重配置的内容信息，所述第一承载标识对应的承载为所述多UE协作传输的承载；
    所述RAN节点向所述第一UE发送第二重配置命令，其中，所述第二重配置信令中携带有所述第二UE的标识、所述第一承载标识以及所述重配置的内容信息。
  18. 根据权利要求17所述的方法，其中，在所述RAN节点向所述第二UE发送第一重配置命令之前，所述方法还包括：
    接收所述第一UE或所述第二UE发送的修改请求，其中，所述修改请求用于请求修改所述第一承载标识对应的承载。
  19. 根据权利要求2至14中任一项所述的方法，其中，在RAN节点向第一用户设备UE发送第一配置信息之后，所述方法还包括：
    所述RAN节点向所述第二UE发送第一释放命令，其中，所述第一释放命令中携带有所述第一UE的标识、释放的第二承载标识以及释放的内容信息，所述第二承载标识对应的承载为所述多UE协作传输的承载；
    所述RAN节点向所述第一UE发送第二释放命令，其中，所述第二释放命令中携带有所述第二UE的标识、所述第二承载标识以及释放的内容信息。
  20. 根据权利要求19所述的方法，其中，在所述RAN节点向所述第二UE发送第一释放命令之前，所述方法还包括：
    接收所述第一UE或所述第二UE发送的释放请求，其中，所述释放请求用于请求释放所述第二承载标识对应的承载。
  21. 一种多UE协作传输的配置方法，包括：
    核心网设备向RAN节点发送关联关系信息，其中，所述关联关系信息用于指示第一UE与第二UE具有关联关系，所述第一UE和所述第二UE具有建立多UE协作传输的能力。
  22. 根据权利要求21所述的方法，其中，在核心网设备向RAN节点发送关联关系信息之前，所述方法还包括以下至少之一：
    所述核心网设备获知所述第一UE和所述第二UE均处于连接态；
    所述核心网设备发现所述第一UE进入连接态，其中，所述第一UE与所述第二UE基于任意业务均具有关联关系；
    所述核心网设备发现所述第一UE进入连接态且发起第一业务之后，其中，所述第一UE与所述第二UE基于目标业务具有关联关系，所述目标业务包括所述第一业务；
    接收到所述RAN节点发送的第二请求，所述第二请求用于请求所述第一UE所关联的所有UE，或者，所述第二请求用于请求基于第二业务与所述第一UE具有关联关系的UE。
  23. 根据权利要求21所述的方法，其中，所述关联关系信息包括以下至少之一：
    具有关联关系的UE标识列表，其中，所述UE标识列表中包括所述第 一UE的标识和所述第二UE的标识；
    第一业务识别信息，其中，所述第一业务识别信息用于指示能够执行多UE协作传输的业务；
    具有关联关系的UE标识列表中指示的各个UE的属性。
  24. 根据权利要求21至23中任一项所述的方法，其中，在核心网设备向RAN节点发送关联关系信息之前，所述方法还包括：
    所述核心网设备获取所述第一UE签约的关联关系信息或所述第一UE预先设置的关联关系信息。
  25. 一种多UE协作传输的请求方法，包括：
    第一UE向RAN节点发送第一请求，其中，所述第一请求用于请求所述RAN节点为所述第一UE配置多UE协作传输的承载，所述第一请求中携带有第二UE的标识。
  26. 根据权利要求25所述的方法，其中，在第一UE向RAN节点发送第一请求之前，所述方法还包括：
    所述第一UE通过UE之间的接口，发送第三请求，其中，所述第三请求用于请求为所述第一UE进行聚合传输；
    所述第一UE接收所述第二UE反馈的确认消息，其中，所述确认消息中携带的所述第二UE的标识。
  27. 根据权利要求25所述的方法，其中，在第一UE向RAN节点发送第一请求之后，所述方法还包括：
    所述第一UE接收所述RAN节点发送的重配置消息，其中，所述重配置消息中携带第一配置信息，所述第一配置信息用于为所述第一UE配置多UE协作传输的承载；
    所述第一UE应用所述第一配置信息进行重配置。
  28. 根据权利要求27所述的方法，其中，所述第一配置信息包括：所述第二UE标识、以及承载架构的配置信息。
  29. 根据权利要求28所述的方法，其中，所述第一配置信息还包括：第 三DRB标识，用于指示为所述第一UE配置的多UE协作传输的业务承载。
  30. 根据权利要求27至29任一项所述的方法，其中，在所述第一UE接收所述RAN节点发送的重配置消息之后，所述方法还包括：
    接收所述RAN节点发送的第二重配置命令，其中，所述第二重配置信令中携带有所述第二UE的标识、重配置的第一承载标识以及所述重配置的内容信息，所述第一承载标识对应的承载为所述多UE协作传输的承载；
    执行所述第二重配置命令。
  31. 根据权利要求30所述的方法，其中，在接收所述RAN节点发送的第二重配置命令之前，所述方法还包括：
    向所述RAN节点发送修改请求，其中，所述修改请求用于请求修改所述第一承载标识对应的承载。
  32. 根据权利要求27至29任一项所述的方法，其中，在所述第一UE接收所述RAN节点发送的重配置消息之后，所述方法还包括：
    接收所述RAN节点发送的第二释放命令，其中，所述第二释放命令中携带有所述第二UE的标识、释放的第二承载标识以及释放的内容信息，所述第二承载标识对应的承载为所述多UE协作传输的承载；
    执行所述第二释放命令，释放所述第二承载标识对应的承载。
  33. 根据权利要求32所述的方法，其中，在接收所述RAN节点发送的第二释放命令之前，所述方法还包括：
    向所述RAN节点发送释放请求，其中，所述释放请求用于请求释放所述第二承载标识对应的承载。
  34. 根据权利要求25至29任一项所述的方法，其中，所述第一请求中还携带有第二业务识别信息，所述第二业务识别信息用于指示所述第一UE期望进行多UE协作传输的业务信息。
  35. 根据权利要求34所述的方法，其中，所述第二业务识别信息包括以下至少之一：
    第一无线数据承载DRB标识；
    服务标识；
    QoS流标识；
    业务的特征信息。
  36. 一种多UE协作传输的响应方法，包括：
    第二UE接收RAN节点发送的第二配置信息，其中，所述第二配置信息用于指示所述第二UE为第一UE进行多UE协作传输的承载配置；
    在同意为所述第一UE进行多UE协作传输的情况下，所述第二UE应用所述第二配置信息，向所述RAN节点发送配置完成消息。
  37. 根据权利要求36所述的方法，其中，所述第二配置信息包括：所述第一UE的标识、以及分叉承载的配置信息。
  38. 根据权利要求37所述的方法，其中，所述第二配置信息还包括：第二DRB标识，用于指示所述第二UE为所述第一UE进行多UE协作传输的业务承载。
  39. 根据权利要求38所述的方法，其中，在第二UE接收RAN节点发送的第二配置信息之前，所述方法还包括：
    所述第二UE接收所述第一UE发送的第三请求，其中，所述第三请求用于请求为所述第一UE进行聚合传输；
    所述第二UE向所述第一UE反馈确认消息，其中，所述确认消息中携带所述第二UE的标识。
  40. 根据权利要求36至39中任一项所述的方法，其中，在向所述RAN节点发送配置完成消息之后，所述方法还包括：
    接收所述RAN节点发送的第一重配置命令，其中，所述第一重配置信令中携带有所述第一UE的标识、重配置的第一承载标识以及所述重配置的内容信息，所述第一承载标识对应的承载为所述多UE协作传输的承载；
    执行所述第一重配置命令。
  41. 根据权利要求40所述的方法，其中，在接收所述RAN节点发送的第一重配置命令之前，所述方法还包括：
    向所述RAN节点发送修改请求，其中，所述修改请求用于请求修改所述第一承载标识对应的承载。
  42. 根据权利要求36至39任一项所述的方法，其中，在向所述RAN节点发送配置完成消息之后，所述方法还包括：
    接收所述RAN节点发送的第一释放命令，其中，所述第一释放命令中携带有所述第一UE的标识、释放的第二承载标识以及释放的内容信息，所述第二承载标识对应的承载为所述多UE协作传输的承载；
    执行所述第一释放命令，释放所述第二承载标识对应的承载。
  43. 根据权利要求42所述的方法，其中，在接收所述RAN节点发送的第一释放命令之前，所述方法还包括：
    向所述RAN节点发送释放请求，其中，所述释放请求用于请求释放所述第二承载标识对应的承载。
  44. 一种承载的配置装置，包括：
    第一获取模块，用于获取第一UE的第一配置信息，其中，所述第一配置信息用于配置多UE协作传输的承载；
    第一收发模块，用于向所述第一UE发送所述第一配置信息。
  45. 一种多UE协作传输的配置装置，包括：
    第二获取模块，用于获取关联关系信息，其中，所述关联关系信息用于指示第一UE与第二UE具有关联关系，所述第一UE和所述第二UE具有建立多UE协作传输的能力；
    第二收发模块，用于向RAN节点发送所述关联关系。
  46. 一种多UE协作传输的请求装置，包括：
    第一确定模块，用于确定第一UE需要执行多UE协作传输；
    第三收发模块，用于向RAN节点发送第一请求，其中，所述第一请求用于请求所述RAN节点为所述第一UE配置多UE协作传输的承载，所述第一请求中携带有第二UE的标识。
  47. 一种多UE协作传输的响应装置，包括：
    第四收发模块，用于接收RAN节点发送的第二配置信息，其中，所述第二配置信息用于指示所述第二UE为第一UE进行多UE协作传输的承载配置；
    第二确定模块，用于确定是否同意为所述第一UE进行多UE协作传输；
    所述第四收发模块还用于在同意为所述第一UE进行多UE协作传输的情况下，所述第二UE应用所述第二配置信息，向所述RAN节点发送配置完成消息。
  48. 一种网络侧设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至20任一项所述的承载的配置方法的步骤，或者实现如权利要求21至24任一项所述的多UE协作传输的配置方法的步骤。
  49. 一种终端，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求25至35任一项所述的多UE协作传输的请求方法的步骤，或者实现如权利要求36至43任一项所述的多UE协作传输的响应方法的步骤。
  50. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至20任一项所述的承载的配置方法的步骤，或者实现如权利要求21至24任一项所述的多UE协作传输的配置方法的步骤，或者实现如权利要求25至35任一项所述的多UE协作传输的请求方法的步骤，或者实现如权利要求36至43任一项所述的多UE协作传输的响应方法的步骤。
PCT/CN2022/125040 2021-10-14 2022-10-13 承载的配置方法、网络侧设备及终端 WO2023061430A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111200149.0A CN115988578A (zh) 2021-10-14 2021-10-14 承载的配置方法、网络侧设备及终端
CN202111200149.0 2021-10-14

Publications (1)

Publication Number Publication Date
WO2023061430A1 true WO2023061430A1 (zh) 2023-04-20

Family

ID=85962800

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/125040 WO2023061430A1 (zh) 2021-10-14 2022-10-13 承载的配置方法、网络侧设备及终端

Country Status (2)

Country Link
CN (1) CN115988578A (zh)
WO (1) WO2023061430A1 (zh)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014026385A1 (zh) * 2012-08-17 2014-02-20 华为技术有限公司 协作通信方法及系统、接入网设备、用户设备
WO2014026390A1 (zh) * 2012-08-17 2014-02-20 华为技术有限公司 一种无线承载建立方法、装置及系统
WO2014026384A1 (zh) * 2012-08-17 2014-02-20 华为技术有限公司 用户设备配对处理方法、网络侧设备和用户设备
WO2014026389A1 (zh) * 2012-08-17 2014-02-20 华为技术有限公司 一种无线承载的建立方法、装置及系统
WO2014101146A1 (zh) * 2012-12-28 2014-07-03 华为技术有限公司 协作通信方法、装置及基站
WO2014101140A1 (zh) * 2012-12-28 2014-07-03 华为技术有限公司 协作通信方法、用户设备及基站
WO2015096072A1 (zh) * 2013-12-25 2015-07-02 华为技术有限公司 一种建立协同通信的方法、装置及系统
CN114339714A (zh) * 2020-09-29 2022-04-12 维沃移动通信有限公司 传输配置的方法、装置和设备

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014026385A1 (zh) * 2012-08-17 2014-02-20 华为技术有限公司 协作通信方法及系统、接入网设备、用户设备
WO2014026390A1 (zh) * 2012-08-17 2014-02-20 华为技术有限公司 一种无线承载建立方法、装置及系统
WO2014026384A1 (zh) * 2012-08-17 2014-02-20 华为技术有限公司 用户设备配对处理方法、网络侧设备和用户设备
WO2014026389A1 (zh) * 2012-08-17 2014-02-20 华为技术有限公司 一种无线承载的建立方法、装置及系统
WO2014101146A1 (zh) * 2012-12-28 2014-07-03 华为技术有限公司 协作通信方法、装置及基站
WO2014101140A1 (zh) * 2012-12-28 2014-07-03 华为技术有限公司 协作通信方法、用户设备及基站
WO2015096072A1 (zh) * 2013-12-25 2015-07-02 华为技术有限公司 一种建立协同通信的方法、装置及系统
CN114339714A (zh) * 2020-09-29 2022-04-12 维沃移动通信有限公司 传输配置的方法、装置和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
OPPO, ERICSSON: "Clarification to support associating URLLC traffic to redundant PDU sessions", 3GPP DRAFT; S2-1904656 WAS3200 CLARIFICATION TO SUPPORT ASSOCIATING URLLC TRAFFIC TO REDUNDANT PDU SESSIONS - R1.1, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANC, vol. SA WG2, no. Xi’an P.R. China.; 20190408 - 20190412, 11 April 2019 (2019-04-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051704790 *

Also Published As

Publication number Publication date
CN115988578A (zh) 2023-04-18

Similar Documents

Publication Publication Date Title
US10827342B2 (en) Operator-assisted device-to-device (D2D) discovery
US11219084B2 (en) TA update in RRC_INACTIVE
CN108521880B (zh) 切换基站的方法、装置及系统
US9763274B2 (en) Method and apparatus for device-to-device communication
WO2021239021A1 (zh) 配置信息获取方法、装置、用户设备及系统
US10750355B2 (en) Method and system for managing session across multiple electronic devices in network system
WO2022089430A1 (zh) 指示方法、装置、设备及可读存储介质
JP2024518518A (ja) スライス固有ｒａｃｈリソースプールにアクセスするための方法およびｕｅ
US20240073650A1 (en) Data Transmission Method and Related Device
EP2809109A1 (en) Wireless communication system, radio base station, radio terminal, and wireless communication method
CN112333795A (zh) 网络接入方法及装置
WO2023061430A1 (zh) 承载的配置方法、网络侧设备及终端
WO2022100667A1 (zh) 基于侧链路中继的切换方法、装置、设备及存储介质
WO2022127769A1 (zh) 中继通信方法及装置
WO2022022082A1 (zh) 通信方法和通信装置
WO2022228437A1 (zh) 切换方法、装置、设备及可读存储介质
CN111108785B (zh) 用于无线网络的网络切片特定寻呼周期
WO2022228446A1 (zh) 无线链路失败的处理方法、装置、设备及可读存储介质
WO2023280068A1 (zh) 旁链路资源推荐方法、信息接收方法、装置及终端
WO2022206663A1 (zh) Pdu会话建立方法、相关设备及可读存储介质
WO2014177757A1 (en) Connection management in wireless communications
WO2023051507A1 (zh) Ue的能力变更方法、终端及网络侧设备
WO2022262843A1 (zh) Gap请求消息的发送/接收方法和设备
WO2023061453A1 (zh) 能力变更方法、终端及网络侧设备
WO2024041422A1 (zh) 通信方法、装置、终端及核心网节点

Legal Events

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

Ref document number: 22880366

Country of ref document: EP

Kind code of ref document: A1